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

ewrk3.dos       39944   12-16-93        1:48p   V2.77

	This README is for the NDIS2 DOS device driver of Digital Equipment
Corporation's EtherWORKS3/Turbo Ethernet Controller Cards.  

	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.  Please make careful note of any
configuration changes made during the NICSETUP process as any changes will
also need to be made to the PROTOCOL.INI file (using any standard text editor
such as EDIT or BRIEF).  Please read the README file in the root directory of 
the distribution media for details on the execution of NICSETUP.

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

MINRLBUFFERS    Used to determine when to reject a transmit (out of resource)
		rather than put it in the ewrk3 transmit queue, so as not to 
		use up all the buffers for transmit and leave none for 
		receives.  Default = 2.

MEMORYMODE      2, 32, or 64.  Default = 2.
		For this driver, 2K mode is always the best choice.
		This is due to the architectures chosen for the implementation
		of both the etherwork 3 hardware and this driver.
		 2K mode has 63 network buffers.
		32K mode has 15 network buffers.
		64K mode has 31 network buffers.

RAMADDRESS      Base memory address of network buffers.  Default = 0xD000

IOADDRESS       Base IO address.  Default = 0x300

INTERRUPT       5, 10, 11, 0r 15.  Default = 5.

DIAGNOSTIC      0=don't run diagnostics.  1=run diagnostics.
		Default = 1.

NETADDRESS      Change station address.

		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:\NDIS\DOS\EWRK3.DOS
     -  When prompted for the full pathname of the PROTOCOL.INI stub file,
	enter A:\NDIS\DOS\PATHWRKS
     
     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: 
     
     - Copy A:\NDIS\DOS\EWRK3.DOS to your network directory.
     - Copy the text of A:\NDIS\DOS\PROTOCOL.STB into your existing 
       PROTOCOL.INI file.  If you have no existing PROTOCOL.INI file you 
       can copy A:\NDIS\DOS\PROTOCOL.INI into your network directory.
     - Edit your CONFIG.SYS file to install PROTMAN.SYS and EWRK3.DOS device
       drivers.  Examples are:    
       
		DEVICE=C:\DECNET\PROTMAN.SYS 
		DEVICE=C:\DECNET\EWRK3.DOS
       
       Your non-PathWORKS NOS may have other requirements.

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.  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 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
