			  EtherWORKS3 README
			  ==================

Section 1:....................................... Notes on NICSETUP utility
Section 2:....................................... Accessing the latest drivers
Section 3:....................................... Diagnostic error messages
Section 4:....................................... V2.2 Kit description

			     Section 1
			     =========
	
	The NICSETUP utility allows you to configure EtherWORKS3/TURBO 
Ethernet controller cards as well as serve as a diagnostic tool for the 
cards.  NICSETUP works in unison with RAMDIAG.COM.  RAMDIAG.COM must be in
the same directory as NICSETUP to run diagnostics.

	To execute the NICSETUP utility change your drive(e.g. cd a:\) to the 
top level directory of this distribution media. Then enter NICSETUP at the 
DOS prompt.  The utility is completely menu driven and contains help for each 
option at the bottom of the screen.  The bottom line of the screen will 
always contain the valid keys needed to execute the options.  

	The NICSETUP utility will allow up to four controller cards to be
configured at a time.  For simplicity sake however, you may wish to install 
and configure one board at a time.

	During execution of the NICSETUP utility, you will have the option
of changing and storing the EtherWORKS 3 board settings.  If any of the 
following settings are changed, you MUST edit (using any standard text editor 
such as EDIT or BRIEF) the corresponding configuration file for the driver 
(PROTOCOL.INI for NDIS, NET.CFG for ODI Client) that you will be using.  

		1.      Base I/O Address
		2.      Memory Base Address
		3.      Memory Mode
		4.      IRQ Value

Please see the README files contained within the \ODI\CLIENT and \NDIS\DOS 
subdirectories of this distribution media for more details on editing the 
ConFiGuration/INItialization files that effect your operation.

	The EtherWORKS3/TURBO Controller cards' default settings are as 
follows:

		Base I/O Address        =       300h
		Memory Mode             =       2K
		Memory Base Address     =       D000h
		IRQ                     =       5


RESOLVING A BUS CONFLICT
------------------------
If before you install the EtherWORKS3/TURBO controller card you realize that
any of these default settings will pose a system conflict or if you install 
the EtherWORKS 3 card and the system will not boot due to a system conflict, 
you have the option to "hardstrap" the card by inserting one or both of the 
jumpers found at the locations marked W1 and W2 on the EtherWORKS 3 board.
Hardstrapping the EtherWORKS 3 card requires only that an I/O range is 
available.  When hardstrapped, the EtherWORKS 3 card does not take up any
memory area or IRQ lines thereby reducing the chance of a bus conflict.

The following table details how the board will be set with one or both of
these jumpers installed:

		I/O Range                 W2     W1
		----------------          --     --
		200h - 21Fh               ON     ON          
		280h - 29Fh               OFF    ON
		EISA mode                 ON     OFF
		normal operation          OFF    OFF

After using the W1 and/or W2 jumpers to hardstrap the EtherWORKS 3 module, 
the next step is to run NICSETUP to reconfigure the EtherWORKS 3 card to 
reside where no bus conflict will occur.  Use the "Setup" menu of NICSETUP
and follow the guiding directions.  After NICSETUP is complete, power down 
the PC, remove the W1 and/or W2 jumpers and power up the PC.
If a bus conflict persists, determine what the bus conflict is, use the 
jumpers again and run NICSETUP to resolve the conflict following the same
steps as above.   

NOTE: W1 and/or W2 cannot be installed for normal operation!

Remember that if you change the EtherWORKS 3 default settings using NICSETUP,
you will have to update the appropriate network files (PROTOCOL.INI for NDIS,
NET.CFG for ODI, CONFIG.SYS, EISA Setup).


				USER NOTES
				----------

When running NICSETUP diagnostics with the DE203 or DE205 on Thinwire, it is
necessary for the BNC (network) connector to be terminated with a T-connector
and two 50 ohm terminators.  If this is not done, NICSETUP will display
a "Loopback Error" message.  Also, full diagnostics including Loopback 
cannot be properly run on a live network.  Running diagnostics while the 
DE203 or DE205 is on a live network may also give "Loopback Error" messages.

NICSETUP will not allow diagnostics to be run when it detects that the
EtherWORKS 3 module is 'active'.  The EtherWORKS 3 module is considered 
active if a network device driver was loaded.  It may be necessary to 
remove the statement that loads the device driver in CONFIG.SYS or other
file and power cycle (cold boot) the PC to 'deactivate' the EtherWORKS 3 
module.

			     Section 2
			     =========

To obtain EtherWORKS driver files on the Internet perform the following:
========================================================================

 o Perform an ftp connect to gatekeeper.dec.com. Password is anonymous.
 o Enter Logon ID (It does not matter what is selected for your Logon ID)
 o Change (cd) your directory to: /pub/micro/msdos/network (*lowercase*)
 o Select "ftp> i" for image mode
 o Perform an "ftp> get" on the file ethwrks3.zip (contains all driver files)

				   *OR*

 o Perform an "ftp> get" on the file etherworks3.dd.Z (contains SCO/UNIX driver
									 files)


To obtain EtherWORKS driver files from CompuServe perform the following:
========================================================================

 o Select Conference DECPCI(GO DECPCI) and enter the LAN CONTROLLERS
   library. RETRIEVE the latest version of the EtherWORKS 3 ZIP file.

   To get information on obtaining a CompuServe account call (800)848-8990


			     Section 3
			     =========

For information on ERROR messages please consult the file ERROR.TXT located 
in this directory.

			     Section 4
			     =========

 o OS/2 driver (EWRK3.OS2) V1.01. (/MSLANMAN.OS2 directory) 
   (New) Official release OS/2 driver. 

 o Windows NT (EWORKS3.SYS) FT1.4 (/WIN_NT/FIELDTST/ALPHA directory)
                                  (/WIN_NT/FIELDTST/I386 directory)
   (New) Field Test Windows NT drivers for Alpha and Intel platforms.

 o Novell CLIENT driver (EWRK3.COM) V3.00 (/ODI/CLIENT/FIELDTST directory) 
   (New) Novell CLIENT driver currently undergoing V4.0 certification testing.
   Promiscuous mode support.

 o Novell SERVER driver (EWRK3.LAN) X1.41 (/ODI/SERVER/FIELDTST directory)
   (New) Novell SERVER driver currently undergoing V4.0 certification testing.

 o Native PathWORKS driver (DLLEWRK3.EXE) V1.25 (/PATHWRKS directory)
   Added support for EISA PC's, 802.3 Frame format, user defined 802 mode.

 o NDIS DOS Driver (EWRK3.DOS) V2.77 (/PATHWRKS directory)
   Fix for hang condition in eisa mode if protocol.ini had the entry 
   DIAGNOSTIC=0.
   Fix for problems with multiple protocol stacks and with some single 
   protocol stacks (lanman 2.1a tcp/ip for example), exhibited by hangs in 
   netbind and at other times after booting the driver. The following changes 
   for V2.77 fixed these problems:
	* broadcast is enabled at ALL times (some stacks assume this)
	* SetStationAddress bug fix

 o SCO UNIX driver V1.1 (/SCO directory)
   Removed TCP/IP dependencies(No longer have to have TCP/IP installed)
   Changed minimum PDU size to 46. This bug prevented IPX from starting.
   Fixed bug in LLI protocol engine.
   LED toggles to show network activity.
   Checksum EEPROM at initialization and report errors on failure.

 o NICSETUP V2.6.2 (/ directory)
   Fixes problem when switching from certain ISA mode 2K addresses to EISA mode

 o OEMSETUP.INF files for Windows for Workgroups (/WINWGRP/ISA directory)
                                                 (/WINWGRP/EISA directory)
   Fixes installation problem with WFW V3.11 and PathWORKS

 o Updated README.TXT files.
