home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C!T ROM 2
/
ctrom_ii_b.zip
/
ctrom_ii_b
/
PROGRAM
/
PASCAL
/
RKPLUS33
/
READ.ME
< prev
next >
Wrap
Text File
|
1993-10-19
|
4KB
|
94 lines
----------------------------------------------------------------------------
European Registrations
Serious Cybernetics now has a UK/Europe registration site (Frontier Bulletin
Board). If you are registering in the United Kingdom or Europe, please use
the REGISTER.EUR form. If you are registering in the United States or
Canada, please use the REGISTER.USA form. Users in other countries may use
either form, but must submit registration amounts in the appropriate
currency ($US or £UK) for the form being used.
----------------------------------------------------------------------------
Upgrading from RkPlus versions 3.0, 3.01 & 3.1
Due to a bug in the expiration date algorythms, expiring keys that were
generated with UseExpDays set to True were producing incorrect values for
some dates (ExpDay > 23 or ExpMonth = 12). This has been fixed in version
3.2, but will cause expiration dates from keys generated by earlier versions
to be shifted forward by a month.
----------------------------------------------------------------------------
Upgrading from RkPlus versions prior to 3.0
Version 3.0 is a MAJOR update to RkPlus. It offers several new features, as
well as some changes to the way that keys may be generated.
Due to conflicts between the enum values of Rkp.Status and those returned by
other units being developed by Serious Cybernetics, a new, more consistant
error reporting approach was chosen. Errors are now returned via 2
functions. RkpOK returns a boolean which will be True unless an error has
occured and RkpError returns a word containing the error code. The error
codes will be compatible with those returned by future Serious Cybernetics
units. Registration status is returned in the boolean Rkp.Registered (in the
Rkp record). All references to Rkp.Status will need to be changed. (see
RKPLUS.DOC for details)
If you want RkPlus to generate and use keys that are compatible with version
2.x, you MUST do the following :
[1] Change
Uses
RkPlus;
to
Uses
RkPlus, Rkp2Enc;
[2] Make sure that the values of BaseYear and UseExpDays are not changed by
your programme.
[3] Make sure that your programme doesn't call the SetEncode procedure.
----------------------------------------------------------------------------
Upgrading from RkPlus versions prior to 2.4
Due to a conflict between the naming of the RkPlus Registration Record as
"Reg" and the use of "Reg" in other programmes/units as a record for holding
registers, I have changed the name to "Rkp". Therefore all occurances of
"Reg." in your existing programmes will need to be replaced with "Rkp." This
can be done easily in the IDE by pressing CTRL-Q then CTRL-A then typing
"Reg." (without the quotes) and pressing ENTER then typing "Rkp." (without
the quotes) and pressing ENTER then typing "GNU" (without the quotes) and
pressing ENTER.
Also, due to a bug in the encryption algorythm, programmes which had an
OwnerCode and/or ProgramCode of less than 10 characters MAY have produced
incorrect keys under certain conditions. This has been fixed in versions
2.4 (and higher), but new keys MAY have to be generated for such programmes.
This problem did not exist (to the best of my knowledge) when the OwnerCode
and ProgramCode were both longer than 10 characters.
----------------------------------------------------------------------------