-----------------------------------------------------------------------------
	     NETWARE DOS ODI CLIENT INSTALLATION INSTRUCTIONS
-----------------------------------------------------------------------------

The \NOVELL\DOSODI subdirectory contains the following files:

README.TXT - This file which contains four sections:
	     1.  INSTALLING THE NETWARE DOS ODI CLIENT DRIVER
	     2.  HINTS ON SELECTING PROPER FDDI FRAME TYPE
	     3.  SUPPORTED NET.CFG PARAMETERS
	     4.  INSTALLING THE ODI DRIVER WITH WfW 3.11
DEFPA.COM  - Novell NetWare DOS ODI client driver for the DEC 
	     FDDIcontroller/PCI (v2.10)
DEFPA.INS  - Driver installation file used by NetWare 3.12/4.X
	     DOS ODI client installation utility (INSTALL.BAT)
	     to install and configure the NetWare DOS ODI client
	     driver in that environment.
NET.CFG    - Sample ODI driver control and configuration file



			 ***TRADEMARKS***

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

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

Windows is a trademark of Microsoft Corporation.

CompuServe is a registered trademark of CompuServe, Inc.



Section 1  INSTALLING THE NETWARE DOS ODI CLIENT DRIVER
-------------------------------------------------------

The NetWare DOS ODI Client Driver follows standard Novell installation
procedures for DOS ODI client drivers.  

Note: If you are running an Extended Memory Manager (EMM) with the DEC 
FDDIcontroller/PCI, be sure to run the most current version of EMM386.EXE
(v4.49 or later). There is a known problem running previous versions of
EMM386.EXE with many PCI systems.

Perform the following steps to install the NetWare DOS ODI Client Driver:

1.  Verify that the FDDI network interface card (NIC) is properly
    configured and installed.  Refer to "DEC FDDIcontroller/PCI
    User Information" for instructions.

2.  Enter the following command to copy the Novell NetWare DOS ODI 
    client driver to the DOS workstation:

    COPY A:\NOVELL\DOSODI\DEFPA.COM

3.  Copy the Novell NetWare Workstation files to the DOS workstation
    as described in "Novell NetWare ODI Shell for DOS" supplied with 
    your NetWare v3.1X software.

4.  Configure the NET.CFG file for the DEFPA.COM client driver.
 
    [Read Section 2, HINTS ON SELECTING PROPER FDDI FRAME
      TYPE, in this README.TXT file before continuing.]

    The DEFPA.COM client driver and the NetWare workstation files use 
    the NET.CFG file for configuring the driver at load-time.  The 
    \DOSODI subdirectory provides a sample NET.CFG file to help with 
    your driver configuration.

 a. Enter the following command to copy the sample NET.CFG file
    to the same directory as the other driver files:

    COPY A:\NOVELL\DOSODI\NET.CFG

 b. Edit the NET.CFG file to customize it for your system setup.  Refer
    to "Novell NetWare ODI Shell for DOS" and Section 3, SUPPORTED 
    NET.CFG PARAMETERS, for more information on all of the NET.CFG file 
    parameters.

5.  Connect the DEC FDDIcontroller/PCI to the FDDI network as described
    in Chapter 2 of "DEC FDDIcontroller/PCI User Information".

6.  To load the Novell NetWare ODI drivers and the DEC FDDIcontroller/PCI
    ODI client driver, follow the procedure described in "Novell NetWare
    ODI Shell for DOS".  The following commands are examples:

    LSL.COM
    DEFPA.COM
    IPXODI.COM
    NETX.EXE



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

It is important to specify the correct FDDI frame type to interoperate
with Novell NetWare servers.  If the server uses FDDI_SNAP or ETHERNET_II
frame types, configure the FDDI ODI client to use FDDI_SNAP frame type.
If the server uses FDDI_802.2 or ETHERNET_802.2 frame types, configure
the FDDI ODI client to use FDDI_802.2 frame type.  Novell NetWare ODI
client drivers for FDDI do not support connections to servers using only
ETHERNET_802.3 or ETHERNET_SNAP frame types.



Section 3  SUPPORTED NET.CFG PARAMETERS
---------------------------------------

The following parameters are valid under the LINK DRIVER DEFPA heading
in the NET.CFG file.  Precede each parameter with a TAB or white space. 
Refer to your Novell documentation for more information on editing the 
NET.CFG file.

Parameter:   FRAME FDDI_SNAP
Description: Configures the DOS ODI client driver to use the FDDI_SNAP 
	     frame format.  The client can then connect to servers using 
	     the ETHERNET_II or FDDI_SNAP frame types.

Parameter:   FRAME FDDI_802.2
Description: Configures the DOS ODI client driver to use the FDDI_802.2
	     frame format.  The client can then connect to servers using 
	     the ETHERNET_802.2 or FDDI_802.2 frame types.  This is the 
	     default frame type.

Parameter:   PCICARD  (optional)
Description: Selects instance of DEC FDDIcontroller/PCI adapter per PCI
	     bus.  Values = 1 - 4.  Default = 1.
	     This parameter is optional and need not be specified for
	     proper operation of the driver.

Parameter:   TREQ (optional)
Description: Sets the MACTReq MIB object.  Range = 4-165 milliseconds.
	     Default = 8 milliseconds.
	     This parameter is optional and need not be specified for
	     proper operation of the driver.

Parameter:   FULLDUPLEX (optional)
Description: Enables/Disables FDDI Full-Duplex (FDX) operation.
	     Values = ON, OFF.  Default = OFF.
	     This parameter is optional and need not be specified for
	     proper operation of the driver.

Parameter:   MAX FRAME SIZE (optional)
Description: Sets the advertised maximum frame size for this adapter.
	     Normally, the driver advertises the maximum FDDI frame
	     size (4491 bytes), but this parameter can be used to
	     lower the size.  Range = 12-4491 bytes.
	     Default = 4491 bytes.
	     This parameter is optional and need not be specified for
	     proper operation of the driver.

Following is an example NET.CFG file with the DOS ODI client driver 
configured for FDDI_SNAP frame type and a MACTReq value of 10 ms.

LINK DRIVER DEFPA               ; This line must be included in net.cfg
	FRAME FDDI_SNAP
	TREQ 10


Section 4  INSTALLING THE ODI DRIVER WITH WINDOWS FOR WORKGROUPS 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.

2. Install Novell NetWare support on your system by clicking on the NETWORK
   icon in the Program Manager window.  Next, click on NETWORK SETUP, and
   then the NETWORKS... button. 
   
3. Click on INSTALL WINDOW 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.  At this point, the system may prompt you for Novell files from
   WINUP9.EXE.  This file can be obtained from Novell's CompuServe forum.
   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.)

4. Now, you are ready to install the ODI driver.   Exit to the DOS prompt.
   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.

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

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

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

8. Start WfW and open the File Manager.  Connect to your NetWare drive(s).
