           INSTALLATION INSTRUCTIONS FOR THE HP DESKDIRECT 32-BIT ODI 
                   DRIVERS WITH NOVELL NETWARE 3.12 SERVERS
   
 This HP DeskDirect adapter comes with two 32-bit Open Data-Link Interface 
 (ODI) drivers designed specially for high performance use in Novell 
 NetWare servers.  The HPFEODIM.LAN driver provides high performance bus
 mastering for those HP DeskDirect adapters that support bus mastering.
 The HPFEODI.LAN driver provides programmed I/O or memory-mapped data 
 transfers for use with the HP DeskDirect adapters that are not bus 
 master capable or for use in slots that do not support bus mastering.
 
 These ODI drivers are self-configuring, which means that only the location 
 of the adapter (i.e. slot or base I/O address) needs to be specified.	 The 
 driver will read the adapter's configuration (for example, interrupt channel 
 or memory-map address) from the onboard memory.
 
 These drivers support sharing interrupts among multiple HP 10/100VG PCI 
 LAN adapters.  
 
 The 32-bit ODI drivers are located in the HP support disk directories:
 
     \NOVELL\HPFEODIM.LAN			bus master driver
	 \NOVELL\IOMEM\HPFEODI.LAN		programmed I/O and memory-mapped driver
 
 To install the HP LAN adapter and its 32-bit ODI driver, follow the
 instructions below:
 
 1.  Install the adapter into the computer and run HPVGSet.
 
	 Follow the instructions in your documentation for installing the
	 adapter hardware.  If you are installing a PCI LAN adapter, see the 
	 note on "Interrupt Sharing" in the A:\TECHNOTE\PCI_INFO.TXT file. 
	  
	 If you are installing the HP DeskDirect J2573A ISA adapter, run
     HPVGSET.EXE.  The second column heading across the top of the
     screen will be "I/O Address Range".  Below this heading will be the
     address range of the LAN adapter.  Write down the first number shown
     for use in step 4 (that is, if the address shown is "300-31F", write
     down "300").
 
     Exit HPVGSet.               


 2.  Install the NetWare SERVER.EXE on the DOS boot drive.
 
     Complete the software installation procedures for the NetWare 3.12
     server.  See the Novell documentation on how to install NetWare.
 
     
 3.  Copy the HP driver and NetWare Loadable Modules from the HP support disk.
 
     While running DOS on the server computer, copy the HP NetWare server 
     driver (HPFEODIM.LAN or HPFEODI.LAN) and all the NetWare Loadable 
     Modules from the HP support disk to the DOS directory containing the 
     NetWare server. For example, if the HP Support Disk is in floppy drive A 
     and the server is in the C:\NWSERVER directory, execute the following 
     DOS commands:
 
         COPY A:\NOVELL\HPFEODIM.LAN C:\NWSERVER
						or
		 COPY A:\NOVELL\IOMEM\HPFEODI.LAN C:\NWSERVER
						and
         COPY A:\NOVELL\NLM\ETHERTSM.NLM C:\NWSERVER
		 COPY A:\NOVELL\NLM\MSM31X.NLM C:\NWSERVER
		 COPY A:\NOVELL\NLM\NBI31X.NLM C:\NWSERVER

     Note: ETHERTSM.NLM will attempt to autoload MSM.NLM and NBI.NLM.  Since
	       those modules only work with Netware versions 4.X they will fail
		   to load.  In failing they will print a message about unresolved
		   external procedures.  After failing they will autoload MSM31X.NLM
		   and NBI31X.NLM.  These are the versions needed for Netware 3.12.
		   If you desire, you can overwrite MSM.NLM with MSM31X.NLM and
		   NBI.NLM with NBI31X.NLM.  This will prevent the unresolved external
		   procedure error messages from displaying. Even when the error
		   messages are displayed everything is working fine.  As long as the
		   driver loads you can be sure the needed support modules loaded also.

	 Note: When NBI31X.NLM loads, you may see the following message displayed:

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

		   If you see this message it means you need to install the latest Netware
		   3.12 patches available from Novell from their World Wide Web page.  In
		   general you should always have installed the most current patches
		   available from Novell.  		             
 
     The HP driver is based on the latest version of the ODI specification.
     The .NLM files are required to be loaded with the HP server driver.
     The version, size and date of these files are:
 
            File Name    Version    Date
          -------------  ------- ----------
          MSM31X.NLM      3.17    07/01/96
          ETHERTSM.NLM    3.11    07/03/96
		  NBI31X.NLM	  1.44    07/02/96
 
     NOTE: All these .NLM files are written and owned by Novell, Inc.
 
 
 4.  To load and bind the HP server driver
 
     Loading the driver can take one of several forms depending up the
     boards installed.  This driver makes use of Novell's Netware Bus
     Interface (NBI).  Using NBI, the driver locates all PCI and EISA
     cards supported by this driver.  The HPFEODI.LAN driver also scans 
     and finds the first legacy ISA card (if any) supported.

     If only one card supported by this driver is found, the driver will
     automatically try and load using that card.  No parameters are 
     required on the load line in this case (unless you want a different
     frame type than the 802.2 default).

	 Your load line would be one of the following:
	   LOAD HPFEODIM 
	   LOAD HPFEODI

	 The HPFEODIM.LAN bus master driver may require that a slot number be 
	 supplied.  If more than one HP DeskDirect EISA and/or PCI adapter
	 is installed, then a slot number must be supplied to identify the 
	 card for which the driver is being loaded.

	 Two examples are: 
	    LOAD HPFEODIM SLOT=5	   ;for a card in physical slot 5 (EISA
			           			   ;  or PCI 2.1 bios)
        LOAD HPFEODIM SLOT=10001   ;PCI card in a PCI 2.0 bios machine

     Slot numbers on PCI 2.0 bios machines are different from slot numbers
	 on PCI 2.1 bios machines.  The PCI 2.0 bios understands physical slot
	 numbers.  Thus you can load the driver using the physical slot number
	 (for example, slot 5).  However, the PCI 2.0 bios does not understand 
	 physical slot numbering.  On PCI 2.0 bios machines, Netware provides 
	 arbitrary slot numbers beginning with 10001.  These slot numbers do 
	 not correspond to any physical slot number on your server.  On some 
	 PCs you can have two slots with the same number.  For example, you may 
	 have a PCI slot 5 and an EISA slot 5.  In this case Netware will identify 
	 the one slot as slot 5 and the other as slot 501.

	 When the HPFEODIM.LAN driver loads, it will display the adapters found
	 and their slot numbers.  Use this information to determine the slot 
	 number to use.  If you have more than one of the same HP DeskDirect 
	 adapter installed in the computer, then you will have to manually 
	 determine which card corresponds to which slot.  One technique
	 is to only connect one card to a hub.  The driver will only load the
	 card that is connected to the hub.  Once the driver loads, you can type
	 "config" at the Netware server prompt and see the slot number for which
	 the driver loaded.  By repeating this technique you can determine the
	 proper slot numbers on PCI 2.0 bios machines.

	 The HPFEODI.LAN programmed I/O and memory mapped driver operates identical
	 to the HPFEODIM.LAN bus master driver with one exception.  The HPFEODI.LAN
	 driver also supports the HP DeskDirect J2573A legacy ISA adapter.

     If the ISA adapter is desired, you must load the driver using the ISA and 
     PORT keywords.  NBI does not support legacy ISA. Therefore the driver must 
     handle legacy ISA differently.  To load the driver for a legacy ISA card 
     when one or more EISA or PCI adapters supported by the driver are installed, 
     type:

        LOAD HPFEODI ISA PORT=p
		   Where p is the I/O Base Address found when running HPVGSET.EXE.
           ISA is a custom keyword needed by the driver.

     Follow the load command with the BIND command:

         BIND IPX to HPFEODI{M} NET=n
           Where n is the NetWare Network number you chose.

     Optionally, a frame type can be provided using the FRAME keyword:

         LOAD HPFEODI{M} SLOT=10001 FRAME=f
     	   Where f is the NetWare Frame type.

     These commands can be optionally added to the AUTOEXEC.NCF file used
     by the SERVER.EXE program.  This file can be edited by running the
     INSTALL.NLM utility from a server console and then choosing the
     "System Options".  From there choose the "Edit AUTOEXEC.NCF file"
     option.
 
     NOTE: You must LOAD and BIND the driver for each frame type desired.
           NetWare 3.12 allows up to four different frame types:
           Ethernet_802.3, Ethernet_802.2, Ethernet_II, and Ethernet_SNAP.
           The adapter supports all Ethernet frame types.
 
     NOTE: There is no LOAD command for the MSM31X.NLM because the 
           ETHERTSM.NLM will automatically load the MSM31X.NLM file.
	   	   Likewise NBI31X.NLM will be autoloaded.
 
     NOTE: It is good practice to copy the HP server driver and the
           associated NLMs to their own directory on a NetWare volume,
           preferably the SYSTEM volume.  This allows updating these files
           without bringing the NetWare server down.  Use the path to the
           Novell directory instead of the "C:\NWSERVER" on the LOAD
           commands.

 5.  Increase the number of Packet Receive Buffers in STARTUP.NCF.

	 NOTE: This step only applies if you are using the HPFEODIM.LAN bus
	       master driver.  Skip if not.
 
     A NetWare SET MINIMUM PACKET RECEIVE BUFFERS command must be placed in
     the STARTUP.NCF file.  Using a DOS editor, add the following line to
     the STARTUP.NCF file.  If a SET MINIMUM PACKET RECEIVE BUFFERS command
     is already there, add the amount below to what is allocated.
 
     For 100 Mbits/sec operation, add:
         SET MINIMUM PACKET RECEIVE BUFFERS = 100
 
     NOTE: STARTUP.NCF is the only place where this set command can be given.
 
     The driver pre-allocates empty Packet Receive Buffers for arriving
     packets.  The driver will print error messages if it cannot pre-allocate
     a buffer from NetWare.  See "Note of Error Messages" below for a
     description of these messages.  Also, see the description of "Allocate
     Rx Buffer Failure Count" under "Note on Custom Statistics".
 

 The HP ODI server driver installation is finished.
 
 
 Note on Custom Statistics
 =========================
 
 Lan Speed (Mbit)...........................
 
     Shows which LAN speed the adapter is configured to operate.  It can be
     either 10 or 100.  This will not change once the driver is loaded.
 
 Connected to LAN...........................
 
     Zero (0) means not connected to a LAN.  One (1) means connected.
     This statistic is not tracked in real time.  It is only updated 
     whenever the transmit queue goes full.
 
 Using Ethernet Frames......................
 
     Always one (1).  This driver only supports Ethernet frame types.
 
 Using Memory Mapped Transfers..............
 
     Zero (0) means the driver is using I/O-mapped data transfers.  
     One (1) means the driver is using memory-mapped data transfers.
 
 Always Transmit High Priority..............
 
     Zero (0) means all packets are transmitted using normal priority on
     a 100VG LAN.  One (1) means all packets are transmitted using high
     priority on 100VG.  This has no meaning on 10-MBit/s (10Base-T) LANs.  
     See PRIORITY.TXT in the ADAPTER directory of the HP support disk for
     more information on 100VG priority support.
 
 Currently In Promiscuous Mode..............
 
     One (1) means the driver is receiving all packets from the LAN not
     just ones addressed to it.  Some network management applications will
     enable the driver's promiscuous mode.
     
 Number of Times Tx Queue Full..............
 
     The number of times all the adapter's transmit resources were full
     awaiting transmission.
 
 Currently Tx Queue Full....................
 
     One (1) means all the adapter's transmit resources are full awaiting
     transmission.  This can happen briefly, especially on 10-Mbit/s LANs,
     when more packets are being produced than the LAN can transmit them.
     If it stays one, then loss of LAN connectivity might have occurred.
     See "Connected to LAN" statistic.
 
