1. 45kit260.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (45kit260.zip)

A:\NOVELL\SRVODI\3_12\README.TXT                16-JAN-1997

--------------------------------------------------------------------
Installing the NetWare 3/4 ODI Server Driver on NetWare 3.12 Servers
--------------------------------------------------------------------

This \NOVELL\SRVODI\3_12 subdirectory contains the following 
files:

README.TXT   - This file.
NLM312.EXE   - Self-extracting ZIP file containing NLMs needed for
	       NetWare 3.12.
	       
	       MSM31X.NLM   - Novell Media Support Module for 
			      NetWare 3.12. (v3.18)
	       NBI31X.NLM   - NetWare Bus Interface module that is 
			      used for bus support and is loaded on 
			      NetWare 3.12 servers after loading 
			      MSM31X.NLM. (v1.49)



			 ***TRADEMARKS***

DEC, Digital, and DECpc are trademarks of Digital Equipment 
Corporation. 

Novell, NetWare, and LAN WorkPlace are registered trademarks and 
NetWare Loadable Module, NLM, NetWare MultiProtocol Router, and 
NetWare SFT are trademarks of Novell, Incorporated.



Section 1  
INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER ON NETWARE 3.12
------------------------------------------------------------

You can install and use the NetWare 3/4 ODI server driver on 
NetWare 3.12 file servers by loading some operating system patches and 
driver support files in addition to the driver.

To install the NetWare 3/4 ODI server driver on a NetWare 3.12 file 
server, perform the following steps:

I.   Verify that the network interface card (NIC) is properly
     configured and installed.  Refer to the adapter's user guide
     for instructions.

II.  Copy the NetWare 3/4 ODI server driver files to either a DOS 
     partition (Step IIA.) or a NetWare partition (Step IIB.) of 
     your NetWare server hard disk.

     A. To copy the files to a DOS partition, enter the following 
	commands:

	1. If installing on NetWare 3.12:

	      COPY A:\NOVELL\SRVODI\DE450.LAN C:\
	      COPY A:\NOVELL\SRVODI\ETHERTSM.NLM C:\
	      COPY A:\NOVELL\SRVODI\3_12\NLM312.EXE C:\

	To extract additional required NLMs:

	      C:\> NLM312.EXE

	You may substitute C:\ with another DOS partition and 
	subdirectory.  Running NLM312.EXE will extract MSM31X.NLM
	and NBI31X.NLM.

     B. To copy the files to a NetWare partition, you need to use 
	the NetWare 3.x Command Processor (NWSHELL). Contact Novell 
	for information on acquiring NWSHELL.NLM.  Once you have 
	NWSHELL.NLM, perform the following steps to copy the files:

	1. Load the NetWare 3.x Command Processor (NWSHELL.NLM) by
	   entering the following command at the server System 
	   Console prompt:
	   
	      :LOAD NWSHELL

	2. Change to the SYS:SYSTEM directory by entering the 
	   following command:

	      CD SYS:SYSTEM

	3. Copy the driver files to the current directory by 
	   entering the following commands:

	   a. If installing on NetWare 3.12:

		 COPY A:\NOVELL\SRVODI\DE450.LAN
		 COPY A:\NOVELL\SRVODI\ETHERTSM.NLM
		 COPY A:\NOVELL\SRVODI\3_12\NLM312.EXE

	To extract additional required NLMs:

		 NLM312.EXE

	Running NLM312.EXE will extract MSM31X.NLM and NBI31X.NLM.

	4. Enter "exit" to log out of the session then press any 
	   key to return to the System Console prompt.
				     
III. Perform substeps IIIA. and IIIB. to configure the NetWare 3.12 
     server to use the Digital EtherWORKS PCI server driver.

     A. With the NetWare 3.12 server running, edit the STARTUP.NCF 
	file using the INSTALL Program. 
	 
	1. From the System Console, load INSTALL:

	      :LOAD INSTALL

	2. Select "System Options."
	 
	3. Select "Edit STARTUP.NCF file."
	 
	4. Add the following SET parameter to set the proper packet
	   size.
	
		 set maximum physical receive packet size = 1520
	   
	5. Save the file with the changes.  Answer "Yes" to the 
	   exit prompt.

     B. You can automatically load the server driver by adding the 
	appropriate instructions to the AUTOEXEC.NCF file.  You can 
	also issue these commands directly from the System Console.
     
	1. While still in the INSTALL program, select "Edit 
	   AUTOEXEC.NCF file."  Add the following lines to 
	   AUTOEXEC.NCF to automatically load and bind the new 
	   driver every time the server is brought up:

				     NOTE
	   The "slot" "frame," and "net" values given below 
	   are examples.  The slot number is the location of the
	   controller in the PCI system.  If there is only one 
	   adapter installed, use the suggested value for this 
	   parameter.  The frame type is one of the four supported 
	   frame types "ETHERNET_802.2", "ETHERNET_II", 
	   "ETHERNET_SNAP", or "ETHERNET_802.3" frame types.  
	   The net address is the external network address. 
	   Refer to the Novell NetWare documentation on "Bind" 
	   for more information.
	   
	   a. If you installed the driver files on NetWare 3.12 
	      using Step IIA1., enter the following commands:

		 LOAD C:\DE450 slot=1 frame=ETHERNET_802.2
		 BIND IPX TO DE450 net=00000001

	   b. If you installed the driver files on NetWare 3.12 
	      using Step IIB3a., enter the following commands:

		 LOAD DE450 slot=1 frame=ETHERNET_802.2
		 BIND IPX TO DE450 net=00000001

	   A drive path is not included for the load statements in 
	   the second example. This is because the DE450.LAN driver 
	   files are copied to the SYS:SYSTEM directory, which is 
	   the NetWare 3.12 default server path.
       
	   Loading DE450.LAN auto-loads ETHERTSM.NLM which in turn 
	   auto-loads MSM31X.NLM and NBI31X.NLM.  This allows for 
	   fewer load statements in the AUTOEXEC.NCF file and less 
	   opportunity for driver load errors.

	   c. Save the file with the changes.  Answer "Yes" to the 
	      exit prompt.

IV.  Shut down the server by entering "DOWN" at the system console 
     and then enter "EXIT" to return to the DOS prompt.

V.   Follow the instructions the adapter's user guide for 
     connecting the controller to the network.

VI.  Restart the server.

     Enter the following command at the DOS prompt:

	SERVER

     The changes made to the STARTUP.NCF and AUTOEXEC.NCF files in 
     step III above take effect.