Revision History:

v1.12 FINAL
- Verified and resolved an additional problem with multiple nodes.  Special 
  thanks to Wally Nickel for verifying the final change.

v1.12 BETA 2
- Fixed a couple of problems introduced by the compiler.
- Resolved problems with multiple nodes and active port list.   The
  problem manifested itself as an error in VMM. 
- Added "Keep port open during MS-DOS session" option. This allows
  WinFOSSIL to cooperate with the DigiBoard drivers which drop the DTR
  when closing the port. 
- Removed the dependency on ComXAutoAssign in the SYSTEM.INI, the contention 
  management settings are now handled automatically within WinFOSSIL.  
  Note that WinFOSSIL assumes FOSSIL ports 0 through 3 map to COM1 to COM4.
- Fixed a problem where DTR was always set high when the port was closed.

v1.12 BETA 1
- WinFOSSIL will now automatically open the port when WNFOSCTL is
  used to lock or unlock the baud rate.

v1.11
- Fixed timing problems encountered after handing off from FOSSIL-32
  applications.
- Fixed hanging condition when modem is not responsive.

v1.10
- WinFOSSIL provides port handling support for 32-bit applications 
  running under Windows 95.  Applications that take advantage of this
  feature can operate under Windows 95 and hand off the FOSSIL port
  to other FOSSIL aware applications.  For example, BinkleyTerm/32
  with WinFOSSIL support enabled can now hand off the port to a
  16-bit Maximus BBS package configured to use the same FOSSIL port.
  Authors: Contact Woodruff Software Systems for sample code if you
  are interested in supporting the FOSSIL extensions for Win32.
- Fixed a problem with the write functions where a timeout occurs
  when the CTS is not asserted for 30ms.  This would result in a
  30 second timeout in various applications.  Wildcat! 4 and L.O.R.D.
  experienced this problem in some system configurations.
- Fixed a problem with applications that expected the FOSSIL port to
  remain open (HOT) when passed from an active BBS connection.  When
  the port was not already open, this would result in the application
  using the BIOS routines instead of FOSSIL routines or reporting
  that the FOSSIL was not availble or the carrier had been disconnected.
  This "auto-open" feature is enabled by default for NEW
  installations, UPGRADES will need to use the Control Panel
  application to enable this feature per port.

v1.09
- Registration IDs are now invalid.  New signatures will be sent
  to customers who have registered the product. 
- Enabled finer control for time-slice management.  This is managed
  per COM port and is configured using the control panel application.
- Enabled port performance statistics.  These statistics can be monitored 
  using the System Monitor tool.  Logging of these statistics is
  not enabled by default as it has caused other performance problems
  on slower machines.  Again, this option can be controlled using 
  the control panel application.

v1.08
- Tracked down source of incompatibilities with TradeWars 2002 and
  other non-FOSSIL MS-DOS applications.  The hardware state for the 
  COM port is now properly reflected to these applications.
- Added WNFOSCTL, a utility to lock and unlock the FOSSIL baud rates
  for FAX modems requiring fixed DTE rates for receipt of faxes.

v1.07
- Made various performance enhancements related to improving throughput, 
  reducing time-outs and CRC errors. 
- Buffers limits automatically set to enable send XOFF request (or
  drop RTS) at 7/8 receive full and send XON request (or raise RTS)
  when it empties to 1/8 full.
- Hardware handshaking is now enabled by default for locked baud
  rates.
- Fixed more sleepy applications.  We have decided that Windows can
  handle time-slicing better than an application that is requesting to
  release it's time-slice while in the middle of a file transfer. 
  WinFOSSIL filters the "release time-slice" requests and only allow
  these requests when there is no activity on the COM port.  This
  prevents the MS-DOS session from sitting idle when there is really
  activity on the port.  This was not a problem for MS-DOS based FOSSIL
  drivers because interrupts from the hardware device always kept the
  MS-DOS session busy while servicing the interrupt.
- WinFOSSIL now supports up to 16 ports.

v1.06a
- Corrected installation to modify \WINDOWS\SYSTEM.INI not
  \WINDOWS\SYSTEM\SYSTEM.INI.

v1.06
- Fixed incompatibility with Blue Wave 3.11 (Max) mail reader door
  program.
- Fixed a another timing issue with the transmitter flush.
- Verified compatibility with Doorway 2.30.
- Worked around a problem in the Windows 95 COMM driver which was the
  source of another stuck transmitter problem frequently reproduced
  with Remote Access.

v1.05a
- Fixed another blocking situation with idle timeouts.  This one
  seems to be the source of CRC errors with my system while running
  BinkleyTerm and/or Maximus.  If these applications are configured to
  use multitasking features, the MS-DOS session running the BBS
  software was likely to sleep after it filled the transmit buffer. 
  The receiving system would timeout waiting for the completion of the
  actual data block and throughput was hindered considerably. 

v1.05
- Fixed more FrontDoor and RemoteAccess problems.  Performance was
  hindered by the constant "release time slice" signaling by these 
  applications. The MS-DOS session will now be awakened whenever there
  is an event pending on the serial device.
- Fixed peek character routine -- was returning a false status in
  some cases.
- Added VFOSSIL support.
- Fixed Ctrl-C/Ctrl-K handler.
- Enhanced the help file.
- Adjusted XON/XOFF limits to allow WinFOSSIL to leave control lines
  enabled with a higher buffer fill percentage.

v1.04
- Fixed deadlocks with FrontDoor and InterMail.
- Added support for enabling FOSSIL control on a port by port basis.

v1.03
- Return proper codes on port reactivation, enhanced timeout handling
  for receive character routine.
- Investigated reported issues regarding FrontDoor. 

v1.02
- Fixed performance and timeouts with Function AH=01h, WriteCharWait().

