

		EtherWORKS 3 TURBO V2.4 README             31-July-1995
		==============================

Thank You for purchasing a Digital EtherWORKS 3 TURBO Network Interface 
Card.  Digital's Network Products Group is committed to providing you 
with updated EtherWORKS 3 TURBO device drivers to ensure that these cards will 
install easily, perform exceptionally well, and operate in all the latest 
network operating systems (NOS).

This file contains important information that was not available when the 
EtherWORKS 3 TURBO User Information manual was printed.  A RELEASE.NOT file,
also included in the root directory of this diskette, contains detailed 
technical information regarding known anomalies in the use of the EtherWORKS 3
TURBO cards.

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


			     Section 1
			     =========

Note: NICSETUP now allows changing EtherWORKS 3 settings via command line
      switches. See the file \NICSETUP.TXT for a full description on how
      to use the switches. Please note that whenever executing any command 
      line switches be sure to include /CMD as one of the switches.

For most network operating environments, the EtherWORKS 3 TURBO Ethernet 
controller card must be configured with the NICSETUP utility 
before the network can be used.  NICSETUP is not required when the
EtherWORKS 3 TURBO card is used in a Microsoft Windows NT environment.

The NICSETUP utility allows you to configure EtherWORKS 3 TURBO Ethernet 
controller cards, and serves as a diagnostic tool for the cards.  NICSETUP 
works in unison with the RAMDIAG.COM file. Make sure that the RAMDIAG.COM file
is in the same directory as NICSETUP to run diagnostics.

To execute the NICSETUP utility, change your disk drive to the top-level 
directory of this distribution diskette (for example, a:\), then enter 
NICSETUP at the DOS prompt.  The utility is completely menu driven and 
contains help for each option shown 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, you may wish to install and 
configure one card at a time.

During execution of the NICSETUP utility, you will have the option of 
changing and storing the EtherWORKS 3 TURBO card 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 that 
you will be using (PROTOCOL.INI for NDIS, NET.CFG for ODI Client). 

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

Refer to the README.TXT files contained within the \NOVELL\DOSODI and 
\NDIS2\DOS subdirectories of this distribution diskette for more details 
on editing the ConFiGuration/INItialization files that affect your operation.

The EtherWORKS 3 TURBO Controller card default settings are as 
follows:

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


RESOLVING A BUS CONFLICT
------------------------
If you realize, before installing the EtherWORKS 3 TURBO controller card, 
that any of these default settings will pose a system conflict, or if you 
install the card and the system will not boot due to a system conflict, 
you have the option to hardstrap the card.  To hardstrap the card, insert
one or both of the jumpers found at the locations marked W1 and W2 on the 
EtherWORKS 3 TURBO card. Hardstrapping the EtherWORKS 3 TURBO card requires 
only that an I/O range is available. When hardstrapped, the EtherWORKS 3 TURBO
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 TURBO 
card, the next step is to run NICSETUP to reconfigure the EtherWORKS 3 card 
to reside where no bus conflict will occur.  Use the NICSETUP Setup menu 
and follow the guiding directions.  After NICSETUP is complete, power down 
the PC, remove the W1 and/or W2 jumpers, then power up the PC.
If a bus conflict persists, determine what the bus conflict is, set the 
jumpers again, then run NICSETUP to resolve the conflict (following the 
previous steps).

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

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


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

When running NICSETUP diagnostics with the DE203 or DE205 cards connected
to a ThinWire network, 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 with a DE203 or DE205 card installed 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 TURBO card is active.  The EtherWORKS 3 TURBO card is 
considered active if a network device driver has been 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 TURBO card.


			     Section 2
			     =========
  
  ***********************************************************************
  *  NOTE: When unZIPping the kit:                                      *
  *                                                                     *
  *         1) Please use the -d switch so that subdirectories are      *
  *            properly created.                                        *
  *         2) Make sure the kit is unZIPped to the ROOT directory of a *
  *            diskette so that the original directory structure is     *
  *            maintained.                                              *
  ***********************************************************************
	   
To obtain the latest EtherWORKS 3 TURBO software from the Internet:

 1. Perform an ftp connect to ftp.digital.com.  Your login name is anonymous.
 
 2. Enter your password.  (Use your Internet address as your password.)
  
 3a. To obtain the currently RELEASED (shipping) EtherWORKS 3 kit 
     (matching upper/lowercase lettering) change your directory as follows: 

	cd /pub/DEC/adapters/ethernet/ewrk3/release 
 

 3b. To obtain the latest drivers prior to a major release of an EtherWORKS 3 
     kit. We maintain an interim kit. This kit is the currently released 
     (shipping) kit plus any drivers that were released/completed thereafter. 
     (Matching upper/lowercase lettering) change your directory as follows: 

	cd /pub/DEC/adapters/ethernet/ewrk3/interim

 4. List all the files in the directory to determine the kit number. Released
    and Interim kits will have the following syntax e3kitn. Where "n" is a
    version number. For example for a released kit "n" could be 22(meaning
    V2.2). For an Interim kit "n" could be 226(meaning V2.26).

	ftp> ls


 5. Select ftp image mode:

	ftp> i

 
 6. Perform a get command on the e3kitn.zip file. (where "n" is the kit
    number determined in step 4.)

	ftp> get e3kitn.zip

 
 7. Type quit to exit ftp:

	ftp> quit

				  
To obtain the latest EtherWORKS 3 TURBO software from CompuServe:
 
 1. Type GO DECPCI to select the depci forum and enter the LAN Controllers
    library.

 2. Select the Browse option to scroll through the library titles.

 3. Click on the EtherWORKS title, then press Return to display the 
    description of the EtherWORKS 3 TURBO card.

 4. Select the Retrieve option to copy the file to your system.

For information on obtaining a CompuServe account in the U.S., 
call (800)848-8990.

To obtain the latest EtherWORKS 3 TURBO software from the Network Product 
Business BBS:

 1. Using a modem connect to one of the following numbers: 
	    
    USA:    Network Product Business BBS 1-(508)-486-5777 (open 24hrs)
    Europe: (33)92-96-03-12, select network products / area 23.

 2. Follow the screen's menu-driven instructions to download the driver 
    files.


			     Section 3
			     =========

For information on ERROR messages, consult the ERROR.TXT file, located 
in the root directory of this distribution diskette. 


			     Section 4
			     =========

		     [Changes from V2.3 to V2.4]


 Fixes from V2.36 to V2.37
 -------------------------
 
 o Changes to README.TXT and RELEASE.NOT. 


 Fixes from V2.35 to V2.36
 -------------------------
 
 o Updated NDIS2 OS/2 driver V3.03.
   
	- Fixes a problem with OS/2 Warp.

 o Updated (WFW) NDIS3 driver.
   
	- Fixes a problem where under certain conditions data corruption
	  could occur.


 Fixes from V2.34 to V2.35
 -------------------------
 
 o Updated NDIS2 DOS and OS/2 drivers V3.02
 
	- Fix for hang with 80286 machines

 
 Fixes from V2.33 to V2.34
 -------------------------

 o Updated OEMSETNT.INF file for Windows NT V3.5 which will now work properly
   with Windows NT V3.51
 
 o Remove Windows NT V3.1 drivers

 o Updated NDIS2 DOS driver V3.01
	
	- Multiple Adapter Support
	- Reduced program size
	- Passes Microsoft Certification Test


 Fixes from V2.32 to V2.33
 -------------------------
 
 o New Novell OS2 ODI driver

 o Updated Windows NT 3.5 drivers(V2.7) which fixes a problem with SMP 
   systems.
 

 Fixes from V2.31 to V2.32
 -------------------------

 o Updated Windows NT drivers which has the following enhancements:
    
    - Fixes a problem with Windows NT PathWORKS(network unavailable)

    - Card now supports IO Only mode.

    - Gateway 2000 system hang fix by placing the card in IO Only mode.

    - Performance improvement

 o Updated Packet driver V1.02

    - Support for multiple cards in a PC. See the \PKT_DRVR\README.TXT 
      file for configuration information



 Fixes from V2.3 to V2.31
 ------------------------

 o Fix to "interrupt" PROTOCOL.INI keyword in WFW OEMSETUP.INF file
 
 

 Fixes from V2.2 to V2.3
 -----------------------

 o New WFW's NDIS3 driver V1.19 (Note: supports 32K and 64K MemoryModes only)
	
	- Improved performance.
	- Fixes disconnect and hang problems.
 
 o New Novell IPX device driver, V1.0 added to the software distribution kit.

 o New Univel driver, V1.0, added to the software distribution kit.

 o New Linux driver. The driver is now distributed with the Linux kernel 
   V1.1.61 or later. Instructions are included in the \LINUX directory
   for obtaining the code that will run in kernels after V1.1.33(approx).
   but before V1.1.61.......

 o New EtherWORKS 3 Packet driver V1.01 added to the software distribution kit.

 o Updated Native PathWORKS DLLEWRK3.EXE driver V5.0.25.

     This fixes a problem where the driver was not processing MULTICAST 
     messages.
   
 o \IBMCOM directory structure added to facilitate installation under
   IBM LAN Requestor.

 o Updated NICSETUP.EXE V2.6.7. Many commands performed from NICSETUP menus 
   can now be executed through command switches. For a brief description
   invoke the utility as follows:

			   c:\> NICSETUP/?

   For a complete description please reference the file NICSETUP.TXT in the 
   root directory of this distribution media.

     Note: When executing a command from a switch, /CMD must be included on 
	   the command line.
      
 o Updated SCO UNIX driver V1.3:

     - Fixed intermittent spurious interrupt/hang problem.

     - Fixed minimum/maximum PDU size to be consistent with TCP/NFS/IPX 
       requirements.

     - Fixed transmit bug that caused NFS write timeouts under heavy load.

 o Updated NDIS2 EWRK3.DOS driver version V2.81:

     - Changed PROTOCOL.INI parameters.  See README.TXT in the \NDIS2\DOS
       directory for a further description.

     - Fixed bug that caused a hang when the driver was loaded but an
       EtherWORKS 3 TURBO card was not installed.

     - Driver will ignore ADAPTERS keyword in protocol.ini, rather than
       abort the loading of the driver.

 o Updated OS/2 driver EWRK3.OS2 driver, V1.03: 

     - EEPROM checksum error on some PCs
     - Trap D after binding on some PCs running IBM's TCP/IP

 o Updated NetWare ODI Server driver, V2.02, which passes the NetWare 
   "Yes, NetWare Tested and Approved" tests for NetWare V3.12 and NetWare 
   V4.01. The bulletin number is L-2273. This driver will be included with
   the soon to be released Netware V4.10.

 o Updated NetWare ODI Client driver, V3.03, which passes the NetWare 
   "Yes, NetWare Tested and Approved" tests for NetWare V3.12 and NetWare 
   V4.01. The bulletin number(s) are: 
   
			Card            Bulletin
			====            ========
			DE203           L-2458
			DE204           L-2459
			DE205           L-2460
   
   This driver will be included with the soon to be released Netware V4.10. 
   Changes for the Netware ODI Client driver V3.03 include:

     - Support for Promiscuous mode
     - Support for Novell Workstation ODI Revision B specification

 o Updated Windows NT (V3.5/3.51) device drivers for Intel and Alpha 
   AXP systems.

     - Windows NT V3.5/3.51 (Intel and Alpha AXP) driver V2.07. 
     
		o Supports 2K MemoryMode
		o Supports PIO Mode (Programmed I/O)
  
 o New setup utility (V1.17) for Windows NT on Alpha AXP systems has been
   included in the kit. \WINNT\NICAXP.EXE. This utility runs under the
   arc console.
