NoSnail+ Initial Release - March 14, 1995

Enclosed is the initial release of NoSnail+, the successor to NoSnail.  This
release of NoSnail+ is largely for those persons who have expressed an interest
in seeing further development of NoSnail, to include an OS/2 version as well
as NetBios file locking.  This release is largely on equal footing with NoSnail
v1.17, with the exception being the changes necessary for release with the
Watcom professional compiler.  Included are DOS 16 bit executables capable of
be used by any DOS based system, as well as OS/2 32bit executables which need
OS/2 v2.0 or higher (Warp highly recommended).

Please be careful with this release...it is largely targeted at those interested
in the assisting of testing of the product and OS/2 users testing the OS/2
version of NoSnail+ should be aware that we will need an OS/2 replacement for
MsgForm, as well as a DOS based replacement.  We planned on withholding release
of an early alpha/beta until we had concluded exhaustive testing ourselves, but
since several have expressed an early copy to test ... here it is.

We expect to begin work on adding features to NoSnail+ in late April; if you
have any thoughts or features you would like to see implemented feel free to
touch base with us (see SUPPORT.TXT).  We are no longer able to monitor and
participate in Fidonet echomail areas; rest assured we may still be contacted
via Fidonet netmail, as well on Internet email (again, see SUPPORT.TXT).

--------------------------------------------------------------------------------
Release 1.90a  March 25, 1995

Corrected problems and errors resulting from Stack Overflow errors. Only the
DOS version seems to have the difficulty, but the changes were made to both
the DOS and OS/2 version.  The problem is related to the change in compilers.

Corrected problems with the debug command line option not operating correctly
100% of the time by removing it from the command line and adding it to the
NoSnail.Cfg file.  Just place the word "debug" on a line by itself -- this
code will remain until the update is complete.  Another problem traced to the
change in compilers.

Replaced some of the original "utility" routines from our TicToss product which
are more streamline and functional.