		 DigiBoard Intelligent Board Driver
			       for
		       Microsoft Windows 3.1

			   Version 1.4.0

			   May 25, 1994


This README.TXT file contains important information about this release
which was not available when the manual went to press.

_________________________________________________________________________

Table of Contents:

    1.  INSTALLATION
    2.  VIRTUAL 16550 UART SUPPORT
    3.  WINFAX 3.0 INSTALLATION
    4.  WINDOWS FOR WORKGROUPS 3.11 INSTALLATION
    5.  DETERMINING IF DIGIBOARD PORTS ARE WORKING
    6.  RELEASE NOTES / HISTORY
_________________________________________________________________________


1. INSTALLATION
---------------

    Before proceeding with the software installation for the Microsoft
    Windows 3.1 driver, you must first install the board(s) according
    to the board Installation Guide.

    After the board is installed, start the installation by selecting RUN
    from the Program Manager's File menu.  In the RUN dialog box, type

	A:\WINDOWS\SETUP

    and click on the OK button (if you install from a drive other than
    drive A, substitute the appropriate drive designation).

IMPORTANT!!!  The DigiBoard Windows driver and DigiBoard DOS driver
    must not both be installed on your system at one time.  If you have
    the DOS driver already installed, remove it before you install the
    Windows driver, as follows:

	1. Remove the following line from your CONFIG.SYS file:

	     DEVICE=C:\DIGI\XIDOS5.SYS

	2. Reboot your computer.



2. VIRTUAL 16550 SUPPORT
------------------------

    This feature allows DOS applications to access DigiBoard intelligent
    ports as if the ports were non-intelligent 16550 UARTs.  This means
    that any DOS application which knows how to talk to a standard COM
    port can use a DigiBoard intelligent port.

    Virtual 16550 support may be enabled and configured via the Port Setup
    dialog in the DigiBoard Configuration utility.

    Configuration Hints
    -------------------

	1. Virtual Base Address and IRQ settings should be set to match
	   the address and IRQ which your DOS application uses.

	2. Virtual Base Address and IRQ settings MUST NOT be used by any
	   other device in your system.  For example, if you have a
	   standard COM1 (which uses Base Address 3f8h and IRQ 4), you
	   must not assign a virtual port to the same settings.

	3. Virtual Base Addresses MUST NOT overlap.  For example, you must
	   not assign two DigiBoard ports to the same Virtual Base Address.

	4. Virtual IRQs may overlap.  For example, you may set two virtual
	   ports to use the same Virtual IRQ, without any problems.  But you
	   cannot set a virtual IRQ to one that is already used in your system.

	   Note:  There is no performance penalty associated with assigning
	   multiple virtual ports to the same Virtual IRQ, in fact, it is
	   recommended to conserve IRQs.

	5. Throughput on virtualized ports is typically limited to below
	   38,400 BPS, depending on the application used.



3. WINFAX 3.0 INSTALLATION
--------------------------

    When installing WinFax 3.0, WinFax may ask to change your Windows
    COMM driver back to the standard COMM.DRV.  Do not let it do this.
    This will remove support for your DigiBoard hardware and you will
    no longer be able to access DigiBoard ports.



4. WINDOWS FOR WORKGROUPS INSTALLATION
--------------------------------------

    This version of the DigiBoard Windows driver does not support Remote
    Access (RAS).

    When installing Windows for Workgroups (W4W) or Remote Access for WFW,
    Setup may ask you to change your Windows COMM back to the standard
    COMM.DRV.  If you do this, you will remove support for your DigiBoard
    hardware and will no longer be able to access DigiBoard ports.



5. DETERMINING IF DIGIBOARD PORTS ARE WORKING
---------------------------------------------

    A simple terminal emulation program (TTY.EXE) was copied to your
    DigiBoard directory (the default is C:\WINDOWS\DIGIBRD) to help
    you determine if all your DigiBoard ports are correctly working.

    Before trying this, you must successfully complete the setup and
    configuration process, outlined in your manual.  If you can start
    Windows without any errors, but are unable to communicate through
    the DigiBoard ports, then try the following:

    - Connect one of the ports to a terminal with a "NULL MODEM" cable
      or to a normal modem with a "MODEM" cable.

    - Run the TTY.EXE program supplied on this disk.

    - Select SETTINGS menu, and configure the port (COM1-COM9), the
      settings (baud, stop bit, parity, etc...), and click OK.

    - Select ACTION, and then select the Connect item.

    - If you didn't get any errors, try typing ATDT.  If you have the
      port connected to another terminal, you should see the ATDT
      appear on its screen.  If you have the port connected to a modem,
      and the modem is hooked up to a phone line, then you should
      hear a dial tone.  You may actually see the ATDT appear in the
      screen, but it will depend on what kind of modem you have and what
      default settings are selected in the modem.

    NOTE: It is possible to start two instances of the TTY.EXE program,
    connect them with a NULL modem cable, set each to the same
    baud rate, parity, stop bit and try typing some characters.
    If you see characters appearing in the opposite TTY window,
    then the ports are communicating.

    - If you can not get the port(s) to communicate, please call
      DigiBoard Technical Support for further assistance.  See your
      manual for the current phone number.



6. HISTORY
----------


    Version 1.4.0 - Released 5/25/94

	- Fixed VUARTD interrupt handler problem which caused Int14-Fcn1, 
	  Write Single Char, to generate an invalid page fault (and possibly
	  other Int14 functions, as well).

    Version 1.4.0a (BETA) - Released 4/14/94

	- Added support for two new baud rates: 14,400 and 28,800.

    Version 1.3.0 - Released 2/24/94

	- Corrected handling of MCA boards when REMOVE button is pressed.

	- Added CONTENTS and SEARCH lists to online Help.

	- Fixed problem with Virtual IRQ combo-box not recognizing
	  "default" as a valid setting when tabbing out of the field.

	- Added version information to DBCOMM.DRV (to view, select
	  PROPERTIES from the File Manager FILE menu.

	- Added support for Crosstalk/Win at 115,200 BAUD.  Crosstalk
	  truncates value of 115,200 to 49,664 (115,200 mod 65536)
	  before sending it on to COMM driver, so when we receive this
	  value as a BAUD rate setting, we assume it means 115,200.
	  We can make this assumption because 49,664 is otherwise NOT
	  a valid data rate.

	- Fixed bug which allowed virtual IIR to indicate RX data
	  available without setting the data ready bit in virtual LSR.

    Version 1.3.0b (BETA) - Released 1/31/94

	- Corrected problem with virtual UART not reflecting RX
	  interrupts into application if Interrupt ID Register (IIR)
	  is not read by app.

	- Fixed bug which allowed virtual IIR to indicate RX data
	  available without setting the data ready bit in virtual LSR.

    Version 1.3.0a (BETA) - Released 1/14/94

	- Improved Configuration program.

	- Added support for the PC/4e(8K), PC/8e(8K), MC/4e and MC/8e adapters.

	- Added support for Virtual 16550 UARTs.  This feature allows DOS
	  applications to access DigiBoard intelligent ports as if the
	  ports were non-intelligent 16550 UARTs.

	- Port mapping is now done via the Port Setup dialog, rather than
	  in a separate Map Ports dialog.

	- The Board setting option for IRQ DISABLED is no longer provided
	  since the board cannot communicate with the driver without an IRQ.

	- Micro Channel machines - System crash that occurred when the
	  configuration utility was started a second time has been fixed.

	- Micro Channel machines - To change an installed board type, select
	  the board in the Installed Boards box and click the remove button.
	  A dialog box will pop up asking you to select new board type.

	- EV_ERR events incorrectly included CE_BREAK errors.

	- GetCommError now correctly returns CE_BREAK errors.

	- Fixed problem which occurred when XoffLim+XonLim >= Rx buffer size.

	- Eliminated problem with Compaq 66/M EISA machine locking up in the
	  config program.

     Version 1.2.0 - Released 9/24/93

	- Help has been added to the configuration program in a context-
	  sensitive WinHelp format.

	- Added support for the 2Port and MC/2e adapters.

	- Corrected definition of the Windows constant CBR_14400.

	- The length of a transmitted BREAK was incorrectly set to a
	  constant.

	- EV_ERR events were incorrectly passed on to application programs.

	- When data was received with parity or framing errors, a problem
	  occurred which occasionally caused General Protection Faults.
