a:\sco\readme.txt                        9-AUG-1996

This readme.txt file is covers the SCO Unix LLI and MDI device 
drivers for Digital's EtherWORKS PCI/EISA adapters, based on 
Digital's DC21X4 controllers.

This file contains information on the following topics:

	1. Overview
	2. Hardware and Software Requirements
	3. Installation
	4. Parameters
	5. Troubleshooting

************
* OVERVIEW *
************

	These drivers are currently supported for the 
	following devices:
		 
	Digital DE500 Fast EtherWORKS PCI  10/100 Adapter  
	Digital DE450 EtherWORKS TURBO PCI 10 TP/BNC/AUI Adapter
	Digital DE450 EtherWORKS TURBO PCI 10 TP Adapter
	Digital DE435 EtherWORKS TURBO PCI  TP/BNC/AUI Adapter 
	Digital DE434 EtherWORKS TURBO PCI  TP Adapter  
	Digital DE425 EtherWORKS TURBO EISA TP/BNC/AUI Adapter 
		      

	The DE425, DE435 and DE450, with this driver, will 
	autosense whether the adapter is connected to the network
	by the TP, BNC or AUI port at boot time and at run time. 

	If the driver cannot sense a connected port, it will 
	set up the adapter for a TP link. 

	The DE500, with the MDI driver, will autonegotiate a link 
	if an IEEE802.3u auto negotiable partner is available, 
	otherwise it will perform DIGITALs patented 10/100 autosense 
	routine to determine if the Adapter is attached to 10 or 100 
	Mb/s Ethernet.The LLI driver will only perform the autosense 
	routine.  Both drivers will autosense at boot time and at 
	run time.

	If the driver cannot sense a particular line speed, it will 
	assume that the line is not connected, and auto select 
	10Mb/s.

	When connected point to point (DE500 to DE500), the driver 
	will auto select 100Mb/s.  If the DE500 is attached to an 
	N-Way device, the driver will auto select the highest common 
	mode.

	***********************************************************
	Ensure that any 'DC21x4 EISA/PCI Ethernet Adapter' driver
	is removed from the system, before the kernel is re-linked.
	Failure to do so will result in an inoperative adapter.
	***********************************************************

    o MDI Driver
	The SCO MDI Driver is designed to work on the new SCO 
	OpenServer Release 5.0 OS, but is not backwards compatible 
	to the older SCO OpenServer Release 3.0 and earlier operat-
	ing systems.  Installation using the Software Manager is 
	straight forward and should not present any problems nor 
	error messages.

    o LLI Driver
	The SCO LLI Driver is designed to work on the older SCO 
	OpenServer Release 3.0 OS as well as the new SCO OpenServer 
	Release 5.0.  However, DIGITAL does not recommend using the 
	LLI driver with SCO OpenServer Release 5.0. Upgrade to the 
	new MDI driver when running the newer SCO OS.


**************************************
* HARDWARE AND SOFTWARE REQUIREMENTS *
**************************************

   A.  Hardware Requirements:

	 o An IBM-compatible personal computer with 80386 or higher
	   microprocessor and either an EISA bus (if using the 
	   DE425) or a PCI bus with an available bus mastering PCI 
	   slot (if using the DE434, DE435, DE450, DE500).

   B. Firmware Requirements:

	 o Fully compliant Rev. 2.0 or above PCI BIOS must be 
	   supplied with the PC (NOT required if using the DE425).

   C.  Software Revision Requirements:

	 o Operating System:
	       SCO OpenServer Release 3.0 operating system OR
	       SCO OpenServer Release 5.0 operating system
	 o Adapter driver distribution disk if using SCO OpenServer 
	   Release 5.0 or a SCO Unix LLI driver disk for SCO 
	   OpenServer Release 3.0 (see LLI installation instructions 
	   below)

****************
* INSTALLATION *
****************

   To install the SCO Unix MDI Device Driver:

    -   Run the Software Manager, select the 'Softare->Install New' 
	menu item and follow the on-screen popup dialog boxes for 
	instructions.  The distribution media is the floppy disk 
	supplied with the adapter.

    -   Run the Network Configuration Manager, select 
	'Hardware->Add New LAN Adapter' menu item and follow the 
	on-screen popup dialog boxes for instructions. Relink the 
	kernel on exiting this utility.

    -   To activate the adapter, you must reboot. When the system 
	boots, you should see a message similar to the following 
	message among the other configuration messages:


    %dcx0  0x2000-0x2200  5 - type=DE500-AA addr=12:34:56:78:9a:bc

	with the appropriate I/O addresses, IRQ, adapter type and 
	IEEE address.



   To install the SCO Unix LLI Device Driver:

   Copying the distribution files
   ------------------------------

   -  The compressed distribution file (DEXXX_DD.Z) can be copied
      to DExxx_DD.Z on a SCO Unix machine.

	  From the unix prompt enter DOS
	  COPY A:\SCO\DEXXX_DD.Z .
	  QUIT
	  mv dexxx_dd.z dexxx_dd.Z

   -  Uncompress dexxx_dd.Z to dexxx.dd, using:

	  uncompress dexxx_dd

   -  Copy the file to a NEW diskette.
	  To create a 3.5" floppy in drive 0, place a clean, 
	  (DOS) formatted, floppy in the 3.5" drive and enter:

	      dd if=dexxx_dd of=/dev/rfd0135ds18

      Mark the diskette:
	  "DIGITAL EtherWORKS PCI/EISA LLI driver, Rel.2.2.7"

   -  Run custom. From the menu select:
      Custom -> Install -> A New Product -> Entire Product

   -  Put the distribution diskette in the drive and select 
      continue.

   -  When prompted for distribution floppy 1, just press enter.

   -  When custom has completed, remove the diskette and quit 
      custom.

   -  Run netconfig. Add the desired chain. The LLI drivers 
      are called: dcx0, dcx1, dcx2 and dcx3. Remember that dcx0 
      must be configured first, before any other dcx device is 
      configured.

	 NOTE: For SYSTEMS with more than one adapter in them, only 
	       one driver should be installed, but each active board
	       must be "netconfig'd". 

   -  When the chain has been configured, select 'q' from the 
      netconfig menu.  If you don't wish to modify the space.c file 
      relink the kernel at the prompt.

   -  If you wish to change parameters in the space.c file, edit
      /etc/conf/pack.d/dcx0/space.c and make the required changes.
      The changes will apply to all the installed boards. Then 
      change to the /etc/conf/cf.d directory and invoke 'link_unix' 
      to link the new kernel.

   -  To activate the adapter, you must reboot. When the system 
      boots, you should see a message similar to the following 
      message among the other configuration messages:


      %dcx0  0x2000-0x2200  5 - type=DE500-AA addr=12:34:56:78:9a:bc

      with the appropriate I/O addresses, IRQ, adapter type and 
      IEEE address.

**************
* PARAMETERS *
**************

   The space.c file contains the different parameters that can be 
   modified.
   
   1. Driver tuning parameters:
	 DCX_MEDIA_SENSE
	 DCX_FULL_DUPLEX
	 DCX_AUTOSENSE_MS
	 DCX_CHK_SS_ID

   2. Driver diagnostics control:
	 DCX_DEBUG

   The meaning of each is explained in detail in the space.c file, 
   including allowed values for each parameter. The values in 
   space.c apply to ALL the installed boards.

   Space.c is NOT the place to modify the board's slot number line.
   This must be modified in netconfig, by running the 
   reconfiguration script.

*******************
* TROUBLESHOOTING *
*******************

  o MDI Driver

      No problems reported to date with this latest release (V4.1.5).


  o LLI Driver

     [ NOTE: Please upgrade to the new MDI driver if you are      ]
     [       using the new SCO OpenServer Release 5.0 operating   ]
     [       system. Instructions for upgrading can be found in   ]
     [       your adapter manual.                                 ]

   1. Driver binds to wrong PCI board (network):

      When multiple PCI boards are installed, the chains are bound 
      to the adapters in the order that the adapters are found on 
      the PCI bus by the PCI BIOS. Thus, dcx0 will bind to the 
      first adapter found by the PCI BIOS and supported by DEXXX, 
      dcx1 to the second etc.  
      
      Removing or adding boards without changing the configuration 
      in netconfig can cause a shift in the order that chains are 
      bound. Also, mis-identifying the order in which the adapters 
      are found by the BIOS can cause wrong bindings. This is 
      especially true when using boards with PCI-PCI bridges. The 
      adapters on such boards are located on a PCI bus with a 
      number higher than 0 (bus #1, #2 etc.) and will be found by 
      the PCI BIOS after all the devices on bus zero.

   2. Driver recognizes adapter at boot time, no network connection:

      Check that there is not a 'DC21x4 EISA/PCI Ethernet Adapter'
      driver installed in the system.  The DEXXX (dcx) driver will 
      not work with the DC21X4 driver.

   3. Attempting to FTP a large file (more than 4096 bytes) causes
      the FTP process to hang after transferring 2920 bytes under 
      SCO OpenServer Release 5.0:

      Upgrade to the latest MDI driver (V4.1.5).
