Release Notes
 Some notes on this release of the Expand Library
------------------------------------------------------------------------------

 1. Evaluation Version and Commercial Version:
 The Expand Library is now distributed as an "Evaluation Version", which
 simply shows a message when an Application linked with it is started, just
 to remember the user it still has to be purchased. When purchasing the
 Library, there is no such thing (ie. in the "Commercial Version").

 Note that this trick is easy to overcome, this was chosen by purpose,
 so the working of the Library is not affected (it's an init Function).

 2. Specific support for Blinker:
 The EXPAND.LNK file can be used as a "Nested Linker Response File" for the
 many lot of Clipper programmers who use Blinker. EXPAND.LNK anables an
 optimal use of the Overlaying possibilities, with a minor loss of
 speed. In very tight memory situations, one can also (and always) ALLOCATE
 the whole Expand library, but using @EXPAND.LNK is the preferred way when
 using Blinker. Note also that EXPAND.LNK contains some interesting
 information about the Library.

 Also, the Library is made with a Newer version of LIB, so Blinker will not
 generate a warning about a Cross-reference record not found.

 Future versions of the Expand Library might contain a resident part, ie.
 a number of modules that cannot be overlayed. That would ideally be handled
 in EXPAND.LNK. So, in a next release, use of EXPAND.LNK might become
 necessary.

 3. Preceding all function names with XP:
 Version 3.00 of the Library has seen the addition of XP in front of all
 Library functions, except the Norton Guide functions. This was chosen to
 prevent conflicts in Library symbols in the future. I very long considered
 not to do so, but finally decided to make the concession, and make sure
 every Expand Function is truly unique (from the Linker's viewpoint). I
 understand that quite some early Expand Library users will not be very glad
 with this change, because it probably means changing quite some sources.

 To alleviate the problem, an Upgrade module has been created. Use it only
 for maintenance of your current programs using the Expand Library. It will
 not be supported in the future, and I strongly suggest reflecting the
 programs with the new function names (and features!) of this version of
 Expand.

 The Upgrade module is the EXPAND52.C (Compiled into EXPAND52.OBJ) file
 (Note also that it is the Only C file of the package!). It simply contains
 all of Expand5 v2.xx Functions who call the appropriate Expand5 v3.00
 function.

 Just link EXPAND52.OBJ with your (old) application. Also link in the new
 version of the Library, and your Application should work without trouble
 (a little more overhead). EXPAND52.OBJ can be placed in the Overlay Area,
 but I wouldn't recommend it, due to the frequency of calling of it. I
 linked EXPAND52.C using the MSC 6.00 Compiler, but any C Compiler for
 Clipper should do.

 This file was supplied as an aid to using the new version of the Library
 on your applications. I do not recommend using it extensively, but rather
 take a few hours time to adapt the Applications. It's hard, but the choice
 to add "XP" really had to be made, and I hope it was a good one.

 4. Functions MouseAlert() and InitPrinter() removed:
 MouseAlert() had a bug.. A stupid bug, but seeing the number of reactions
 I had on it.. I could conclude that it was hardly being used! XPalert()
 could be seen as a replacement, but probably, there's no need for a
 replacement to Alert()?

 InitPrinter() was also Buggy. XPinitLpt() is the replacement in a sense.

 5. Removed EXPAND.KEY, added EXPAND.PCX:
 The keywords listing of the Expand library functions has been removed. As
 SNAP for Clipper 5 is not really useful (maybe, due to the nature of
 progamming in Clipper 5), a Keywords list is not really useful, is it not?
 If you want a List of all functions, see the Main list, entry #3; the
 alfabetical list of all the functions.

 EXPAND.PCX is a simple EGA PCX file, that can be used as a Demo of
 the XPfastPCX() function. There is support for EGA and VGA, but EGA
 was chosen as a common denominator.

 On disk one might find more files, depending on the space available on
 disk (and the final size of the Library and it's accompanying files).

 6. Other Assembler, Other Clipper coding technique:
 This version has been Assembled by the Microsoft Assembler 5.10. To keep as
 much as possible compatible with the Clipper Coding. All the Clipper code
 compiled into the Library generates no Warnings, nor have PUBLICs, PRIVATEs
 and such been used. It's as much 'good' Clipper 5.01 code, as it could be.