Release Notes PN 93000315_D Digi ClassicBoard PCI 4/8 and Digi Neo Driver Version 2.03 Microsoft Windows NT 4.0 40002125_D June 11, 2001 INTRODUCTION This driver package supports the ClassicBoard PCI and Digi Neo adapters in Microsoft Windows NT 4.0 SUPPORTED PRODUCTS ClassicBoard 4 PCI ClassicBoard 8 PCI Digi Neo 4 Digi Neo 8 ENHANCEMENTS - Alt-Pin is now supported - User-definable baud rates are now supported - Digi Neo adapter now supports 921600 bps - Multiple adapters can now be installed without doing a re-boot - The default COM port for installation is now COM5 KNOWN LIMITATIONS - ClassicBoard ISA adapters are not supported - Alt-Pin is not compatible with DTR/DSR flow control ADDITIONAL INFORMATION Alt-Pin 10-pin RJ-45 plugs may be difficult to obtain in the retail market; therefore, the device driver software incorporates a feature called Alt-Pin, which swaps the logical functions of DSR (Data Set Ready) with DCD (Data Carrier Detect). When the Alt-Pin box is checked, DCD becomes available on pin 1 of an 8-pin RJ-45 connector (equivalent to pin 2 of a 10-pin connector). Force Baud Rate With the Force Baud Rate feature the device driver software forces the baud rate of a COM port to a fixed value. This enables older serial communication applications to use baud rates above the applications configuration limit (e.g. 115200). If Force Baud Rate is enabled, the driver replaces the applications baud rate with the forced baud rate value. HISTORY Version 2.03 - Added Alt-Pin support - Added User-definable baud rate support - Digi Neo adapter now supports 921600 bps - Multiple adapters can now be installed without doing a re-boot - The default COM port for installation is COM5 Version 2.02 - Added support for Digi Neo adapters Version 2.01 - Fixed disconnect problem seen in RAS when mulitple ports are active - Fixed Classic PCI driver trying to use com names already in use by other adapters - Cleaned up helpfile to remove old phone numbers Version 2.00 - Support for PCI adapters - If RTS/CTS handshaking is selected and if the application never sets RTS signal, the driver never raises the RTS signal. This caused CITRIX systems to fail. This problem is now fixed - Support Rev. DC and later of the 16654 UART - Allow disabling of the UART's Transmit FIFO Version 1.02 - Initial release