Release Notes 93000305_A
                                 for
                       Digi DataFire Sync 2000
                          UnixWare 7 Package
                            Release v1.0.0
                       Release Date: 10/14/98

	Please reference the following number(s) when searching the Digi
	International FTP/WWW site for the latest software package:

	Software Image P/N 400001831_A

	These numbers are for informational purposes only:

	CD-ROM Software Image P/N  400001625_A

	This Digi software package includes device drivers for the
	DataFire Sync 2000 product supported under UnixWare 7.0.1.
	This release includes support for multiple Host Adapters per 
	system, and a Graphical software configuration interface that
	operates under the X-Windows environment.

	The following Host Adapters are supported on this release:

	DataFire Sync 2000 + 4P PCI  P/N  77000641
	DataFire Sync 2000 4P PCI    P/N  77000642
	DataFire Sync 2000 + 2P PCI  P/N  77000643
	DataFire Sync 2000 2P PCI    P/N  77000644

	The following SCO Unixware patch(es) must be applied to the 
	Unixware 7.0.1 Operating System in order to support this
	package:

	erg710613 - Fixes DDI8 I_LINK bug
		  - Fixes DDI8 Autopush bug

	Software limitations:

		* More then 20 DLCI's per system require UnixWare 7
		  to allow more then 20 stream links (slink).
			 
		* Dlci's greater then 991 are not supported. Unless the dlci
		  is being used for LMI (Line Management Interface).

	Additional Notes: 

		* For SNA support, DataFire Sync 2000 for UnixWare 7 
		  uses the IBM C/S Communications package.

		* When configuring X.25 over SNA, if you do not set
		  "Call User Data Matching" to your SNA CUD in the
		  "QLLC port" Advanced screen, then X.25 over IP will
		  fail as SNA is in a mode to attempt to receive
		  all packets, which will include any sent from a
		  different CUD.  The current CUD can be determined
		  from the "QLLC link station" Advanced screen.

		* An effort has been made to automate the Frame
		  Relay configuration process. If problems exist
		  when trying to connect to other hosts on the
		  network, the user should be familiar with network
		  trouble shooting methods. An example of this is 
		  the use and understanding of the following utilites: 

		* (TCP/IP ONLY ) ping, netstat, route, ifconfig, slink, strcf

		* (IBM C/S) Refer to the SNA user's manual.

		* Your Frame Relay/X.25 network will attempt to come up on
		  reboot. If this is undesirable, disable the start
		  scripts via wancfg (GUI).

		* After removing an adapter from NETCFG, the O.S. must
		  be rebooted to complete the adapter's removal process.
		  The networks will still be operational until after the
		  reboot. 

	Known Problems: 

		* Under certain circumstances, such as adding a new adapter
		  to the PCI bus, the resmgr entry of existing configured
		  adapters may be changed.  Due to a UnixWare 7 bug, some
		  information stored within the old resmgr key can be lost.
		  The current work around to this problem would be to remove
		  any all but one of the resmgr entries of MODNAME "dgsdlc" 
		  with the UNIT number "0" and rebooting the system.

		* On some non-SCSI platforms, NETCFG will abort with Tcl
		  errors when switching to the WAN view.  This is caused
		  by a SCO UnixWare 7 bug.  To work around this problem,
		  remove the following files from the /etc/inst/nd/mdi path
		  that do not have installed adapters present.  These files
		  can be saved off to a temporary location.

		  /etc/inst/nd/mdi/5ess/5ess-isa.bcfg
		  /etc/inst/nd/mdi/atel/atel-isa.bcfg
		  /etc/inst/nd/mdi/etsi/etsi-isa.bcfg
		  /etc/inst/nd/mdi/japan/japan-isa.bcfg
		  /etc/inst/nd/mdi/ni1/ni1-isa.bcfg