	       NDIS2(specification V2.0.1) DOS DRIVER README         
	       =============================================

ewrk3.dos       38056   7-29-94        3:46p   V2.81
		(size after a successful initialization is 4608 bytes)

	This README is for the NDIS2 DOS device driver of Digital Equipment
Corporation's EtherWORKS 3/Turbo Ethernet Controller Cards.  There are been
significant changes in the protocol.ini entries for this version of the
driver.

	Before proceeding with the installation, it is recommended that the
NICSETUP utility (found in the root directory of this distribution media) be 
executed, particularily if this is the first time you are installing the
controller card and/or NDIS driver.  Read the README file in the root 
directory of the distribution media for details on the execution of NICSETUP.

			PROTOCOL.INI PARAMETERS
			-----------------------

DRIVERNAME      *** REQUIRED
		Example: DRIVERNAME = EWRK3$

IOADDRESS       *** OPTIONAL.  Default = EtherWORKS 3 hardware settings.
		    If present, this value must match the hardware settings.
		Base IO address.  (example: 0x300)

		If IOADDRESS is not specified, this driver autosenses the 
		EtherWORKS 3 board location by reading certain IO locations.  
		It is possible that some PC hardware may be sensitive to 
		this probing.  If the board is not found or the PC exhibits 
		unexpected behavior, IOADDRESS should be specified.

INTERRUPT       *** OPTIONAL.  Default = EtherWORKS 3 hardware settings.
		    If present, this value must match the hardware settings.
		Possible values: 5, 10, 11, or 15. 

RAMADDRESS      *** OPTIONAL.  Default = EtherWORKS 3 hardware settings.
		    If present, this value must match the hardware settings.
		Base memory address of network buffers.  (example: 0xD000)

MEMORYMODE      *** OPTIONAL.  Default = EtherWORKS 3 hardware settings. 
		    If present, this value must match the hardware settings.
		Possible values: 2, 32, or 64.
		
		For this driver, 2K mode is always the best choice when
		using local boot.  This is due to the architectures chosen 
		for the implementation of both the EtherWORKS 3 hardware and 
		this driver.  For 2K mode, remote boot is only supported
		with the RPL protocol, and ctl-alt-del will not cause a
		remote boot.

		32K or 64K modes are the choices for MOP remote boot,
		and for all remote boot protocols where it is desired
		that ctl-alt-del cause a remote boot to occur.

		 2K mode has 63 network buffers.
		32K mode has 15 network buffers.
		64K mode has 31 network buffers.

DIAGNOSTIC      *** OPTIONAL.  Default = 1.
		0 = don't run diagnostics.  
		1 = run diagnostics during initialization.

NETADDRESS      *** OPTIONAL.  Default = hardware address.
		Change current station address.
		(example: AAbbccddeeff or aa-BB-cc-dd-ee-ff)

		Per NDIS 2.0.1 specification, the NETADDRESS parameter
		affects the current address field in the service-specific
		table, and affects the address the board responds to.  
		The permanent address field in the service-specific table 
		remains equal to the original hardware address.

FLAGS           *** OPTIONAL.  Default = 0.
		bit 0 = 0 --->  follow the NDIS 2.0.1 specification for
				the NETADDRESS parameter, as defined above.
				(example: FLAGS = 0)
		bit 0 = 1 --->  Set the permanent address field in the
				service-specific table equal to the address
				specified by NETADDRESS.
				(example: FLAGS = 1)
		other bits undefined.

MINRLBUFFERS \    
MINTXBUFFERS  \     These parameters are no longer supported.  Due to the
MAXRCBUFFERS   -->  architecture of the EtherWORKS 3 board, their use would
MAXTRANSMITS  /     not increase the performance or stability of ewrk3.dos.
IGNOREROM    /      


		Procedure for an NDIS installation
		----------------------------------

1.)  Run NICSETUP to change and/or note the system resources (Memory range,
     I/O range, IRQ line) required by the EtherWORKS 3 module.  It is a good 
     idea to run diagnostics to confirm the installation.

2a.) PathWORKS 4.x users: Insert your Client Setup diskette and run NETSETUP 
     to automate the network installation procedure.  
     
     -  When prompted for the Network adapter type, choose 'Other NDIS'.
     -  When prompted for the full pathname of the NDIS driver, enter
	A:\NDIS2\DOS\EWRK3.DOS
     -  When prompted for the full pathname of the PROTOCOL.INI (stub file),
	enter A:\NDIS2\DOS
     
     NETSETUP will show you the configuration parameters read from the
     PROTOCOL.INI file.  Make sure they match the EtherWORKS 3 module 
     configuration.  By default the parameters shown will match those of
     the EtherWORKS 3 module unless you ran NICSETUP and changed a module 
     setting.

     NETSETUP will update your CONFIG.SYS, AUTOEXEC.BAT, PROTOCOL.INI and 
     network specific files automatically.

     Note: PathWORKS V5.0 or greater will include a menu option to allow 
	   selection of the EtherWORKS 3 card in PWSETUP. For those 
	   versions the selection of OTHER NDIS is inappropriate.

2b.) Non-PathWORKS users: 
     
     -  When prompted for the Network adapter type, choose 'Other NDIS'.
     -  When prompted for the full pathname of the NDIS driver, enter
	A:\NDIS2\DOS\EWRK3.DOS
     -  When prompted for the full pathname of the PROTOCOL.INI (stub file),
	enter A:\NDIS2\DOS
       
3.)  If you are using a memory manager such as EMM386 or QEMM, you must      
     exclude the memory space that the EtherWORKS 3 is using from being
     mapped as high memory.  The following is example text that must be 
     added to your CONFIG.SYS file if you are running a memory manager:

	       DEVICE=C:\DOS\EMM386.EXE x=D000-D07F frame=E000
     
     This line would be used to exclude the default memory space of the
     EtherWORKS 3 at D000:0 - D07F:F in 2K mode.  If the EtherWORKS 3 is
     configured for 32K mode at the same Memory Base Address, the CONFIG.SYS
     line would be: 

	       DEVICE=C:\DOS\EMM386.EXE x=D000-D7FF frame=E000
     
     Consult your memory manager document for specifics.

4.)  Read the USER NOTES below.

5.)  After steps 1,2,3 have been done, turn off your PC and turn it back        
     on for the modifications to take effect.


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

1.  If DIAGNOSTIC = 1, during the initialization of the EWRK3 device driver
    you will notice a message stating that diagnostics are being executed.  
    If an error is detected, an appropriate message is displayed.  A 
    description of EtherWORKS 3 diagnostic error messages can be found in 
    the file ERROR.TXT which can be found in top level directory of this 
    distribution media. Please consult this document and correct the error 
    specified. If the error cannot be corrected contact your local DIGITAL 
    representative for further assistance.

2.  If during the execution of the diagnostic you experience an EtherWORKS 3 
    error such as 'Memory Queue Test Failed', make sure you remembered to 
    exclude the EtherWORKS 3 memory region from your extended memory manager 
    in CONFIG.SYS.

3.  If you do not wish to execute the diagnostics each time the driver is 
    loaded, edit PROTOCOL.INI such that DIAGNOSTIC = 0.


		    CHANGES FROM V2.74 TO V2.77
		    ---------------------------

1. V2.74 hung in eisa mode if protocol.ini had the entry DIAGNOSTIC=0.
   This has been fixed and DIAGNOSTIC=0 may now be used with eisa mode.

2. V2.74 had 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


		    CHANGES FROM V2.77 TO V2.79
		    ---------------------------

1. Changed protocol.ini parameters.  See new descriptions above.  Added
   support for lower case (previously entries had to be all upper case).


		    CHANGES FROM V2.79 TO V2.80
		    ---------------------------

1. Fixed bug that caused a hang when the driver was loaded but an ewrk3
   board was not present.
		   

		    CHANGES FROM V2.80 TO V2.81
		    ---------------------------

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