| mvBase
Tech Tip: |
#
mv109 |
| Pertinent
Release(s): |
Release
1.2 and 1.3 |
| Windows
O/S: |
95/98
and NT |
Implications
for mvBase SystemID's and Authorization Codes of re-installing
the Windows 95/98 or Windows NT Operating Systems
Should
the need arise to completely re-install Windows 95/98 or Windows NT
then it is extremely important to be aware of three facts:
-
The
mvBase Release 1.2 AND 1.3 Permanent Authorization Codes
are tied directly to the SystemID (System IDentity). This
association is critical in maintaining licensing authorization.
-
If
you reload and/or reinstall Windows the SystemID will
change. This will cause the existing Permanent Authorization
Code to be invalid.
-
The
mvBase server will not start as an application or service
if the Authorization Code is invalid (or if the SystemID
does not belong to the system on which it was generated.
To
avoid having to obtain a new Permanent Authorization Code, you
must record the 20-character System ID and the existing 24-character
mvBase Permanent Authorization Code before
(prior to, ahead of, preceding, etc.) reloading or reinstalling
Windows.
This
can be done in two ways:
-
Copy
them both from the Authorization edit box in the Server
tab of the mvBase Administration Utility (recommended)
-
Obtain
them from the Windows Registry (not recommended, due
to the great care which must be taken when working in the
Registry ).
-
Launch
the Registry Editor by clicking on Start | Run, (type
regedit or regedt32) and press Enter.
This
brings up the Registry Editor that looks somewhat like
Windows Explorer.
-
Now
click on the following + signs:
For
mvBase 1.2
HKEY_LOCAL_MACHINE
| SOFTWARE | GeneralAutomation | mvBase | Server
For
mvBase 1.3
HKEY_LOCAL_MACHINE
| SOFTWARE | General Automation | mvBase | 1.3 | Server
(Note
the space in between the words 'General' and 'Automation'
on 1.3)
and
then click on the boot directory.
Nine
values now display. Two of them are labeled AuthCode and
SystemID.
-
Copy
both of these String values somewhere for later use.
-
Now
reload/or re-install Windows and mvBase.
Once
you have reloaded and/or reinstalled Windows and mvBase,
it is mandatory to use the Windows Registry Editor to
reenter the previously existing (valid) SystemID data and to
create the AuthCode value.
A
SystemID will already exist when you use the Windows Registry
Editor only if you have attempted to start the mvBase server
(or invoked the Server|Authorization dialog in mvADMIN) after
re-installing mvBase.
To
create a new value:
-
Open
the boot directory in the Windows Registry as in option
2 of the previous section.
-
Click
on Edit | New | StringValue.
-
Type
AuthCode or SystemID as the name in place
of the New Value #1and then double click on the small ab
icon to the left of the name.
-
Enter
the 24-character AuthCode value or 20-character SystemID
value from before as appropriate.
To
modify an existing value:
-
Open
the boot directory in the Windows Registry as in option
2 of the previous section.
-
Select
the name of the value you wish to alter (SystemID)
by clicking on it in the right-hand pane and then click
on Edit | Modify.
or
Doubleclick
on the name of the value you wish to alter (SystemID).
-
In
the Edit String dialog box, the old value data will be initially
selected. Just enter the new 20-character SystemID value
from before, then click OK.
After
completing this step the mvBase server will start and will be
authorized to use the correct number of licenses as before.
CAUTION: The Windows Registry Editor should be avoided
whenever possible, and used with great caution and precision only
when it is absolutely necessary. It necessary to use it
to re-enter the SystemID and Authorization Codes.
|