This version of ULAn adds the following features/fixes the following
bugs:

ULAN v1.11 ---

o  Public Release.

ULAN v1.11 Beta-1b3b ---

o  Fixed problem with the append feature, where the rewritten ULAN
   would not properly create a ULAN.DAT if one was not there.  This
   now works.

o  Fixed problem with the rewritten /LIST parameter, where ULAN would
   ignore such obstacles as BUSY and Session Handshake Failure, and
   include the information from the next call in that call.  In some
   cases, ULAN reported that files were transferred when the line was
   busy!  This has been corrected.

ULAN v1.11 Alpha-8 ---

o  ULAn now supports the new Storm Watch Software key structure.

o  Complete rewrite.  All code has been rewritten or moved to a
   totally different position in the file.

ULAN v1.11 Gamma-3a ---

o  Added the /NOSITE parameter to support the new FrontDoor log
   keyword 'Site: ' for the location of the remote system.

o  Added the new Storm Watch Software key processing routines, which
   allows you to put your key either in the directory you run ULAN
   from, or in the directory pointed to by the environment variable
   SWSKEYS.  Currently, Beep and ULAn both support this environment
   variable, and future versions of any shareware programs will as
   well.

ULAN v1.00 ---

o  Added the /A parameter to append to the ULAN.DAT.
   {+} A valid key will allow this to work.

o  Added the /K parameter to kill the FD.LOG after processing is
   completed.
   {+} An $8 dollar investment is all it takes . . .

ULAN Closed Test Versions 0.11 - 0.90 ---

o  Added support for a list format.  The parameter is /LIST.
   It will cause information to be logged as follows:

   BBS Name             181:192/101     1-315-445-5643  14400/ARQ
        Sent C:\FD\OUTBOUND\0000000F.TU1; 935b, 450cps
        Rcvd C:\FD\NEWFILES\0000000E.MO9; 1535b, 850cps
        Session Time/Cost:  0:21, 13.

o  Also added support for removing various information from the
   ULAN.DAT file.  The /NO* parameters are for this purpose.  Use ULAN
   /? for full details on these paramters.

o  Added support for VOICE response from modem.  I'm honestly not sure
   what ULAN would do if it saw VOICE because I've been forced to turn
   off VOICE checking, however, from the look of another parameter I
   put in which would cause the same result, it wouldn't have been
   pretty 8-)  It probably would have had the same result as a session
   handshake failure, but it really doesn't matter now.  It's been
   fixed.

o  Added a new option to log only those calls which connect.  The
   parameter is /SUCCESS.  Using ULAN in this mode will force it to
   not log those calls in which the result is NO*, BUSY, or VOICE.  If
   I left out any possible results, please let me know.

ULAN v0.10 ---

o  Added support for logging only local as well as only long distance
   calls.  The parameter is /LOCAL.

o  Removed the Runtime Error problem if an invalid log was specified.
   ULAn now states that it is unable to open the log.

o  Fixed a bug which caused information after a session handshake
   failure to be incorrect.  ULAn still thought it was logging the
   same call, even if it was a new call or an inbound call.  Any '?'
   error now signals the end of a call.

o  Added the option of changing the output filename.  /OUTPUT=<file>
   will cause ULAN to direct output to <file> instead of the default
   ULAN.DAT.  {+} Must have a valid ULAN.KEY for this to work.

o  Added a parameter to search for a specified string in a phone
   number and log only calls made to numbers containing the string.
   {+} This option costs $8.  :-)

o  Rewrote the registration routines to check for a v1.15 key.  The
   older 1.00 and 1.01 keys no longer work with ULAN.  Any registered
   users will be sent new keys.

o  Added a help screen.  Since running ULAN with no parameters is
   perfectly valid, /? pulls up the help screen.  It lists all
   parameters you can use with ULAn.
