a:\wfw\readme.txt                       27-FEB-1997


This README file is for the installation of Digital Equipment 
Corporation's EtherWORKS PCI/EISA adapters in a Windows for 
Workgroup environment.

Supported adapters for enhanced mode (NDIS3): 
	DE425, DE434, DE435
Supported adapters for real mode (NDIS2):
	DE425, DE434, DE435
Supported adapters for 16-bit ODI client:
	DE425, DE434, DE43t5

Device drivers: DC21X4.386, DC21X4.DOS, DE425.COM, and DE43X.COM

This document contains the following sections:

	1. Installation Troubleshooting
	2. Protocol.ini Parameters
	3. Driver Types
	4. Adding the Adapter After WFW 3.11 Installation
	5. Adding the Adapter During WFW 3.11 Installation
	6. Adding the Adapter for NetWare Coexistence with WFW 3.11
	7. Error Messages


********************************
* INSTALLATION TROUBLESHOOTING *
********************************

Important note: If this is not your first network installation in 
WFW, you may have a problem with old information still being in the 
setup files, causing functional problems.  If you are experiencing 
problems, go to Network Setup and select "No Network".  Restart the 
system. Examine the setup files (config.sys, win.ini, protocol.ini, 
system.ini) and make sure that no references to network adapters 
exists.  From the root, type the following command:

	dir \windows\system\oem*

Examine these .inf files and if any of them are pertinent to old
installations of network adapters, delete them. Delete old versions 
of network adapter drivers (DC21x4.DOS and DC21x4.386).  
Then go back into Network Setup and add your network adapters
normally.

***************************
* PROTOCOL.INI PARAMETERS *
***************************

For information on protocol.ini parameters for the NDIS2 driver, 
see the README.TXT in the NDIS2 subdirectory. 

For information on net.cfg parameters for the ODI client driver,
see the README.TXT in the NOVELL\DOSODI subdirectory.

The following are the protocol.ini parameters for the NDIS3 driver.  
A DC21040-based on-board controller would have the same parameter
selections as a DE435.

  BurstLength (range = 1,2,4,8,16,32; default = 16)
    Specifies the length, in dwords, of the DMA transfer within a 
    PCI burst. (1 dword = 4 bytes).  Not applicable for DE425.

    If this keyword is not present in protocol.ini, the driver will 
    default to a value of 16.

    For DE434 and DE435, if the automatic installation files are 
    used, BurstLength will default to a value of 4 in PROTOCOL.INI.  
    This value provides the optimum performance for these adapters.  

  Bus Number (range = 0,1,2; default = 0)
    Specifies the PCI Bus Number the adapter is plugged into.
    Should be modified only for an adapter plugged over a PCI-to-
    PCI bridge.  Not applicable for DE425.

  ConnectionType (range = 0..7; default = 0, AutoSense)
    Specifies the selected media port.  
    
    For DE425, the connection type is selected with the EISA
    configuration utility (ECU).

    DE434 and DE435
    -----------------------------------------------------------
    0 AutoDetect Default for DE435, senses the media port connected
		 at driver load time. Precedence is TP, BNC, and 
		 AUI.  Note that the network must be connected for 
		 this to detect properly. (DE435 parameter only)

    0 AutoSense  Precedence is TP, BNC, and AUI.  For DE435, the 
		 network must be connected to detect properly. 
		 (DE435 parameter only)

    1 BNC - Thinwire     BNC connector. (DE435 only)
	
    2 Twisted_Pair       10BaseT.  Default for DE434.
			   
    3 TP Full_Duplex     To connect to full duplex hubs.
			   
    4 TP No_Link_Test    To connect to hubs not supporting the 
			 Link Integrity Test.
			   
    5 AUI - Thickwire    15-pin connector.
			 (DE435 only)
	
  PciMechanism (range = 0,1,2; default = 0)
    Specifies the mechanism access to the PCI configuration space.

	0       Autodetect      Detect system's PCI mechanism 
				automatically

	1       Mechanism 1     Force PCI mechanism #1 accesses to 
				PCI configuration space

	2       Mechanism 2     Force PCI mechanism #2 accesses to
				PCI configuration space

  MapRegisters (range = 4, 8, 16; default = 8)
    Specifies the number of map registers allocated to the adapter.  
    A smaller number may be needed as more adapters are added.

  ReceiveBuffers (range = 8, 10h, 20h, 30h, 40h; default = 10h)
    Specifies the size of the receive buffer's ring, in hex.

  TransmitThreshold (range= 48h,60h,80h,A0h; default = see below)
    This is a 10Mbit mode parameter only.  Not applicable on DE500 
    in 100Mbit mode.

    Transmission starts when the frame size within the transmit 
    FIFO is larger than the threshold. In addition, full frames 
    with a length less than the threshold are transmitted.
	
    If this keyword is not present in the registry, the value 
    defaults to 96 (60h).  If the automatic installation file on
    this diskette is used, the value defaults to 160 (A0h).

  AdapterCFID (static value)
    Do not modify this value.
	For DE425, DE434 and DE435, value = 00021011

  AdapterType (static value = 5 for PCI, static value = 2 for EISA)
    Do not modify this value.

  BusType (static value = 5 for PCI, static value = 2 for EISA)
    Do not modify this value.

  MediaType (static value = 1)
    Do not modify this value.


**************** 
* DRIVER TYPES *
****************

When installing the adapter, you will have the following choices
for driver type:

	1. Real Mode NDIS driver
	2. Enhanced Mode driver
	3. Real Mode and Enhanced Mode driver
	4. 16-bit ODI driver

Real Mode NDIS driver:

	This chooses the NDIS2 DOS driver.  This is not the best 
	performing driver to use because the NDIS2 driver won't be 
	able to take full advantage of WFW's 32-bit capability.  
	However, in cases where you have other software that does 
	not support the NDIS3 driver (such as PATHWORKS 4.x/5.x 
	coexistence), the NDIS2 driver may be a requirement.

Enhanced Mode driver:

	This chooses the NDIS3 driver, DC21x4.386.  This driver 
	interfaces directly to the WFW software, and should be the 
	best performing driver to use.  However, there is some non-
	WFW software which will not work with the NDIS3 driver, and 
	therefore this driver may not be an option for you.  Refer 
	to the vendor of your software to determine their ability 
	to work with NDIS3.

Real Mode and Enhanced Mode driver:

	First, a word of warning.  This is not a recommended mode
	in which to run this adapter.

	Setup information for both NDIS2 and NDIS3 drivers is 
	loaded into PROTOCOL.INI.  The WFW software chooses which 
	driver to use.  NDIS3 is chosen if all loaded stacks 
	support NDIS3, otherwise NDIS2 is chosen.  Both NDIS2 and 
	NDIS3 keywords are written to PROTOCOL.INI.

	For the case where NDIS2 is chosen, by WFW, when the NDIS2 
	driver loads it will give an invalid keyword warning for 
	every NDIS3 keyword it encounters.  These warnings can be 
	ignored.  The only way to make these warnings disappear is 
	to choose "Real Mode Driver" rather than "Real and Enhanced 
	Mode Driver".

	For the case where NDIS3 is chosen, by WFW, as WFW starts
	a message similar to "Network adapter has not loaded
	properly" may appear on some PCs.  In some cases this is an
	inappropriate error message - the adapter has loaded
	properly, and if you continue the network will function
	properly.  This inappropriate error message is the reason
	that this mode is not recommended.

ODI driver:

	This chooses the ODI DOS client driver.  This is the same 
	driver that is used by a Netware DOS client, and you would 
	choose this driver to acheive Netware coexistence.  This is 
	not the best performing option for WFW because the ODI 
	client driver won't be able to take full advantage of WFW's 
	32-bit capability.

	Skip to the section "Adding the Adapter for Netware
	Coexistence with WFW 3.11" below.


**************************************************
* ADDING THE ADAPTER AFTER WFW 3.11 INSTALLATION *
**************************************************

Make sure your adapter is configured in the system.
Automatic Installation Using the Network Setup Program:

      1. Click on the Network Setup icon.
	 If no network is installed, click on Networks button,
	 choose network type, then click OK.

      2. Click on the Drivers button.

      3. If a driver for this adapter already exists, you must 
	 remove it first by clicking on the driver name to select 
	 the driver, then clicking the remove button.

      4. Click the Add Adapter button and select Unlisted or 
	 Updated Network Adapter.

      5. Insert the driver diskette in the floppy drive and press 
	 <ENTER> to accept the A:\ path.
	      
      6. Choose the appropriate adapter and click OK.  Click the 
	 Setup button.  See the "Driver Types" section of this 
	 readme for information on choosing the appropriate driver 
	 for your application.

      7. Follow the instructions to complete the software 
	 installation and reset or power cycle your computer when 
	 WFW asks you to restart.


***************************************************
* ADDING THE ADAPTER DURING WFW 3.11 INSTALLATION *
***************************************************

The installation kit for Windows for Workgroups comprises eight 
diskettes.  Continue with the WFW3.11 installation of disks 1-6.  
During the installation of diskette #7, the network environment 
will be configured.  At this point you will be asked to select a
Network Adapter to install.

Below is a sample of an installation.
							
	1. Select the Bullet "Install Microsoft Windows Network"
	   Click OK
	   Click Continue

	2. From the Add Network Adapter Screen...
	   Select "Unlisted or Updated Network Adapter" , click OK

	3. From Install Driver Screen...
	   - Remove disk #7
	   - Insert the network adapter driver diskette
	     NOTE:  DO NOT INCLUDE THE FILENAME AS PART OF THE PATH
	   Click OK to accept the A:\ path

	4. From Unlisted or updated Network Adapter Screen...
	   Select the appropriate adapter and click OK.  Click the 
	   Setup button.  See the "Driver Types" section of this 
	   readme for information on choosing the appropriate 
	   driver for your application.

	5. From Microsoft Windows Network Name screen...
	   Enter your site specific information and click OK

	6. From Install Driver Screen...
	   - Remove network adapter driver diskette
	   - Insert Disk #7 an click OK
	   - Remove Disk #7
	   - Insert Disk #8

	7. From Install Driver Screen...
	   - Remove Disk #8
	   - Insert network adapter driver diskette

	8. From Networks Screen...
	   Enter A:\
	   - Remove network adapter driver diskette
	   - Insert Disk #8

	9. From Install Driver Screen...
	   Click OK

	10. Finish Installation 

*** Note POWER OFF/ON your PCI based PC after the install.


************************************************************
* ADDING THE ADAPTER FOR NETWARE COEXISTENCE WITH WFW 3.11 *
************************************************************

1. Install Windows for Workgroups v3.11 on your system if it is not 
   already installed.  For more information about setting up and 
   installing Windows for Workgroups 3.11, see your Windows 
   documentation.  Choose "No Network" during this installation.
   If the network has already been installed, remove it by choosing 
   "No Network" in the Windows network setup.

2. WFW assumes that you will have an ODI client running before you
   initiate Windows.  Set up an ODI subdirectory with your client 
   software, your client driver, and a net.cfg file, as you would
   for any ordinary odi client installation.

3. Edit autoexec.bat to add the following lines at the top of the 
   file.  If these files are located in a subdirectory, specify 
   their path in the autoexec.bat as well. 

	lsl.com 
	dc21x4.com
	ipxodi.com
	netx.exe  ( or vlm.exe )

4. Restart your system (to start the Novell client software), and
   enter Windows. Install Novell NetWare support on your WFW system 
   by clicking on the NETWORK icon in the Program Manager window.  
   Next, click on NETWORK SETUP, and then the NETWORKS... button. 
   
5. Depending on the variety of network protocols you may want to 
   run, you may choose:

	Microsoft Network AND Additional Network: other

		OR

	Install Windows support for the following network only

   Then, choose Novell NetWare Workstation Shell.  If you are using 
   VLM to connect to the NetWare Server, you should choose Novell 
   NetWare Workstation Shell 4.0 and above.  If you are using NETX, 
   you may choose either the 3.x or the 4.0 and above versions of 
   NetWare.  Click on OK and then click on OK again (to choose
   IPXODI.COM and LSL.COM).  At this point, the system may prompt 
   you for Novell files from WINUP9 (see note). You may also be 
   prompted for files from the WFW 3.11 installation kit. You will
   be told that various initialization files are being updated.
   
   NOTE: Some earlier manufactured versions of the WFW V3.11 
	 install diskettes may not contain all the Novell files 
	 asked for when inserting disks 7 and/or 8. In these cases 
	 you may need a more recently produced version of the WFW 
	 V3.11 kit. Alternatively, the files can be obtained on 
	 Novell's CompuServe Forum.

   NOTE: To obtain WINUP9.TXT, which explains which files should be  
	 used for a WFW 3.11 NetWare installation ...

	    From WWW, open the location 
	    ftp://ftp.novell.com/pub/netwire/novfiles

	    From CompuServe, execute "go novfiles"

	    From FTP, FTP into the "ftp.novell.com" site and login
	    as follows:
		User name: anonymous
		Password: <user@return_address>
	    Now enter "cd /pub/netwire/novfiles"

6. Re-boot the system.  The ODI client driver should load and you 
   should login to the network drives on your server.  At this 
   point, it is best to log on to your NetWare Server before 
   starting Windows.  This will allow all NetWare mapped drives to 
   automatically appear in your WFW File Manager.

7. Start WFW and open the File Manager.  You should see your NetWare 
   drive(s).


If you have the NetWare 4.1 Client install disk for DOS/Windows,
an alternate way to install the network would be as follows:

1. Make certain that WFW does not have a network installed.
   Exit from windows to the DOS prompt.

2. Insert disk one, type in install then <ENTER> and follow the 
   prompts.  When selecting the driver for your network board enter 
   the path a:\novell\dosodi

3. When the install is complete, reboot the system.  You should see 
   your NetWare drives from File Manager.


******************
* ERROR MESSAGES *
******************

For NDIS2 and ODI, the error messages will appear on the screen as 
the driver loads.  See the README.TXT files in the appropriate 
subdirectories for more information.

For NDIS3, the error messages are logged in the entry log.  Each 
error message has a standard NDIS error code and a driver's 
additional code.  The additional codes are:

0x01    Interrupt initialization failed.

0x02    Ethernet filter initialization failed.

0x03    Not enough memory to allocate space for the adapter data 
	block.

0x04    Initialization failure.

0x05    Not enough memory to allocate space for the open binding.

0x06    No readable burnt-in or software configured station 
	address.

0x07    System error interrupt (bus parity error).

0x08    Transmit Jabber timer expired.

0x09    Not enough memory to allocate space for the Ethernet 
	filter.

0x0A    No board matching the AdapterCFID Registry's key value was 
	found plugged into the PCI bus.

0x0B    DC21x4 CAM initialization failed.

0x0C    Serial ROM format error.
