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

This \NOVELL\SRVODI\312 subdirectory contains the following files:

README.TXT   - This file.
NBI31X.NLM   - NetWare Bus Interface Module for NetWare 3.12 servers (v1.49)
MSM31X.NLM   - Novell Generic Media Support Module for NetWare 3.12
	       servers (v3.18).

Product Requirements:

Oper. Sys.   - Novell NetWare 3.12 with 312PTx.EXE and LANDRx.EXE installed


			 ***TRADEMARKS***

CompuServe is a registered trademark of CompuServe, Incorporated.

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

Novell, NetWare, and LAN WorkPlace are registered trademarks and 
NetWare Loadable Module, NLM, 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 installing 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 FDDI network interface card (NIC) is properly
     configured and installed.  Refer to "DEC FDDIcontroller/PCI
     User Information" for instructions.

II.  The following NetWare 3.12 patch file must be installed
     prior to using the new driver modules:

       312PTx.EXE   Where "x" is A or higher (312PTA.EXE or higher).
       This file can be obtained from the following places: 

       Novell's anonymous FTP server at:

		ftp://ftp.novell.com/pub/updates/nwos/nw312/

       Novell's WWW server at:

		http://support.novell.com/search

       and on CompuServe.

				     NOTE
	   When NBI31X.NLM is loaded on NetWare 3.12 and the message

		"Warning: This version of NetWare does not
		 support protected mode BIOS accesses.
		 Without a loader patch some PCI drivers
		 may fail."

	   is displayed, the LOADER.EXE patch in 312PTx.EXE needs
           to be applied.

III. The following NetWare 3.12 patch file must be installed
     prior to using the new driver modules:

       LANDRx.EXE   Where "x" is 9 or higher (LANDR9.EXE or higher).
       This file can be obtained from the following places: 

       Novell's anonymous FTP server at:

		ftp://ftp.novell.com/pub/updates/nwos/nw312/

       Novell's WWW server at:

		http://support.novell.com/search

       and on CompuServe.

				     NOTE
	   This driver kit includes the most current FDDITSM.NLM,
	   MSM31X.NLM, and NBI31X.NLM modules available at the
	   time the kit was built.  These modules may equal,
	   supercede, or be older than the modules provided by
	   Novell in the current LANDRx.EXE patch kits.  It
	   is recommended that the user install the latest
	   released versions of these modules unless otherwise
	   indicated.

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

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

	      COPY A:\NOVELL\SRVODI\DEFPA.LAN C:\
	      COPY A:\NOVELL\SRVODI\FDDITSM.NLM C:\
	      COPY A:\NOVELL\SRVODI\312\MSM31X.NLM C:\
	      COPY A:\NOVELL\SRVODI\312\NBI31X.NLM C:\

	You may substitute C:\ with another DOS partition and 
	subdirectory.

     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:

		 COPY A:\NOVELL\SRVODI\DEFPA.LAN
		 COPY A:\NOVELL\SRVODI\FDDITSM.NLM
		 COPY A:\NOVELL\SRVODI\312\MSM31X.NLM
		 COPY A:\NOVELL\SRVODI\312\NBI31X.NLM

	4. Enter "exit" to log out of the session then press any key to 
	   return to the System Console prompt.
				     
V.   Perform substeps VA. and VB. to configure the NetWare 3.12 server 
     to use the DEC FDDIcontroller/PCI NetWare 3/4 ODI 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 FDDI packet
	   size:
	
		 set maximum physical receive packet size = 4500
	
	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 physical slot number where the controller
	   is installed or a unique number generated by NetWare.  On PCI
	   systems that adhere to PCI Specification Revision 2.1 or
	   later, the slot number will be the actual slot number assigned
	   by the vendor.  On older systems, the physical slot number is
	   not available, so NetWare will generate a unique number starting
	   at 10000.  You may wish to load the driver without specifying
	   a slot parameter and select among the list presented on the
	   System Console.  The frame type is either of the two supported
	   frame types "FDDI_SNAP" or "FDDI_802.2".  Read Section 2,
	   HINTS ON SELECTING PROPER FDDI FRAME TYPE, in this file for
	   more information on choosing the frame type.  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 using Step IVA., enter
              the following commands:

		 LOAD C:\DEFPA slot=2 frame=FDDI_SNAP
		 BIND IPX TO DEFPA net=00000001

	   b. If you installed the driver files using Step IVB3., enter
              the following commands:

		 LOAD DEFPA slot=2 frame=FDDI_SNAP
		 BIND IPX TO DEFPA net=00000001

	   A drive path is not included for the load statement in the
	   second example.  This is because the DEFPA.LAN driver 
	   files are copied to the SYS:SYSTEM directory, which is the 
	   NetWare 3.12 default server path.
       
	   In the above examples, note that loading DEFPA.LAN auto-loads
	   FDDITSM.NLM which in turn auto-loads MSM31X.NLM which in
	   turn auto-loads 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.

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

VII. Follow the instructions in Chapter 2 of "DEC FDDIcontroller/PCI
     User Information" for connecting the controller to the FDDI network.

VIII.Restart the server with the DEC FDDIcontroller/PCI server driver.

     Enter the following command at the DOS prompt:

	SERVER

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

Section 2  HINTS ON SELECTING PROPER FDDI FRAME TYPE
----------------------------------------------------

It is important to specify the correct FDDI frame type to interoperate
with Novell NetWare clients.  If the DOS clients use FDDI_SNAP or
ETHERNET_II frame types, configure the driver to use FDDI_SNAP frame type.
If the clients use FDDI_802.2 or ETHERNET_802.2 frame types, configure the
driver to use FDDI_802.2 frame type.  For Appletalk clients using the
ETHERNET_SNAP frame type, configure the driver to use FDDI_SNAP.  NetWare 
3/4 ODI server drivers for FDDI do not support connections to clients 
using the ETHERNET_802.3 frame type, unless the frames are translated into 
proper FDDI_SNAP or FDDI_802.2 frames.

To allow client connections from all supported frame types, you can load the
server driver twice, once for each frame type.  You must bind a protocol for 
each instance.  See the NetWare documentation for information on how to do 
this.
