           INSTALLATION INSTRUCTIONS FOR THE HP DESKDIRECT 32-BIT ODI 
                   DRIVERS WITH NOVELL NETWARE 3.11 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\NW311\HPFEODIM.LAN		bus master driver
	 \NOVELL\NW311\HPFEODI.LAN		programmed I/O and memory-mapped driver
 
 These ODI drivers support sharing interrupts among multiple HP PCI LAN 
 adapters.  
 
 To install either HP 32-bit ODI drivers, follow the instructions below.
 
 
 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.EXE.
 
	 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. 
	  
	 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").  For a PCI card, an address such as "D000" will appear.
	 Record this address.
 
     Exit HPVGSet.               


 2.  Install the NetWare SERVER.EXE on the DOS boot drive.
 
     Complete the software installation procedures for the NetWare 3.11
     server.  See the Novell documentation on how to install NetWare.
 
     
 3.  Copy either the bus master or I/O-memory 32-bit ODI driver from the
     HP Support Disk.

     While still running DOS on the server computer, copy the desired 32-bit
     ODI driver from the HP Support Disk to the DOS directory containing
     the NetWare server.

     To copy the bus master ODI driver from the Support Disk in floppy drive A
     and the server was installed in the directory C:\SERVER.311:
 
 		COPY A:\NOVELL\NW311\HPFEODIM.LAN C:\SERVER.311

     To copy the I/O-memory ODI driver:
 
 		COPY A:\NOVELL\NW311\HPFEODI.LAN C:\SERVER.311

     These HP drivers are based on the 3.2 version of the ODI specification.


 4.  Extract the NetWare Loadable Modules from the Support Disk.
 
     While still running DOS on the server computer, extract all the NetWare
     Loadable Modules from compressed archive on the HP Support Disk to the
     DOS directory containing the NetWare server.  For example, if the Support
     Disk is in floppy drive A and the server was installed in the directory
     C:\SERVER.311:
 
		CD C:\SERVER.311
 		A:\NOVELL\NW311\NLM311.EXE
 
     These .NLM files are required to be loaded with the HP server driver.
     The version, size and timestamp for these files are:
 
 	   	File Name		Version   Size	    Timestamp
 	 	-------------	-------  ------  ---------------
 	 	PATCHMAN.NLM	  2.23    9051   April 16, 1992
 	 	LSLENH.NLM	   	  1.01   11641   November 16, 1992
 	 	MSM31X.NLM	   	  2.50   21308   November 23, 1994
 	 	ETHERTSM.NLM	  2.55    9425   April 18, 1995
 	 	MONITOR.NLM	   	  1.72  117906   June 15, 1992
 
     NOTE: These files are contained in a self-extracting DOS EXE file
 	       named NLM311.EXE.
 
     NOTE: All these .NLM files are written and owned by Novell, Inc.
 	  
     NOTE: MONITOR.NLM is also copied in this step.  See step seven for more
 	       information regarding this file.
 
 
 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".
 
     
 6.  To load and bind the HP server driver from the DOS partition
 
     After starting the NetWare server by running SERVER.EXE, the following
     commands, in order, must be executed on the NetWare 3.11 console to
     load the HP server driver and bind it to NetWare:
 
 		LOAD  C:\SERVER.311\PATCHMAN.NLM
 		LOAD  C:\SERVER.311\LSLENH.NLM
 		LOAD  C:\SERVER.311\ETHERTSM.NLM
 		LOAD  C:\SERVER.311\<driver>.LAN PCI PORT=p FRAME=f
 		BIND IPX to <driver> NET=n
 
     	Where:
        	<driver> is the driver name, HPFEODIM or HPFEODI, copied in step three
 			p is the PORT value obtained from HPVGSET in step one
 			f is the NetWare Frame type
 			n is the NetWare Network number you choose.
 
     For example, to load the HP bus master ODI driver from the DOS partition
     for an HP PCI Card installed at port D000 and using the default frame type
     (Ethernet_802.2), execute the following LOAD command:
    
 		LOAD C:\SERVER.311\HPFEODIM.LAN PCI PORT=D000
 
     NOTE: The driver reads the interrupt channel from the HP PCI Card.
 	       No value needs to be provided on the command line.
 
     NOTE: If other PCI adapters are installed or removed, run HPVGSET to
           ensure the PCI BIOS has assigned the HP PCI Card to the same
	       port (I/O Address Range).
    
     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.11 allows up to four different frame types:
 	       Ethernet_802.3, Ethernet_802.2, Ethernet_II, and Ethernet_SNAP.
 	       The HP PCI cards 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.
 
     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:\SERVER.311" on the LOAD commands.
 
 
 7.  Use MONITOR.NLM version 1.72 or later, if desired.
 
     In order to use the MONITOR program, which shows server and network
     statistics, you need a MONITOR.NLM, version 1.72 or later, instead
     of the MONITOR.NLM supplied on the NetWare 3.11 diskettes.
 
     A version 1.72 MONITOR.NLM is included on the HP Support Disk and
     should have been copied to the DOS boot drive directory in step four
     above.  To load MONITOR from the DOS boot drive directory, use the
     command on the NetWare console:
 
 		LOAD C:\SERVER.311\MONITOR.NLM
 
     The MONITOR.NLM file's version, size and timestamp are:
 
 	   	File Name		Version   Size	    Timestamp
 	 	-------------	-------  ------  ---------------
 	 	MONITOR.NLM	      1.72   117906   June 15, 1992
 
     NOTE: The MONITOR.NLM file is written and owned by Novell, Inc.
 	       Please check with your Novell representative or HP dealer to
 	       check if Novell has released newer version of MONITOR.NLM
 	       and use the newest one that is available.
 
 
 The HP ODI server driver installation is finished.
 
 

 Note on Keywords
 ================
 Both 32-bit ODI drivers recognizes the following keywords on the load line:

 HELP
 
     This will print a help screen summarizing these keywords.  The driver
     will not load if the HELP keyword is used.
 
 NODE <address>
 
     This keyword will temporarily override the adapter's station address
     set at the factory.  Only use this if station addresses will be
     administered locally.  The adapter's address will revert back to the
     factory setting once the driver is unloaded.
 
 PCI
 
     As this driver is a family driver (i.e. supports more than one card)
     the adapter's bus type must be specified on the command line.  Use
     "PCI" for the HP J2585B 10/100VG adapter.
 

 Note on Bus Master Keywords
 ===========================
 The 32-bit ODI bus master driver recognizes these additional keywords on the
 load line:
 
 NOWARN
 
     This keyword will prevent the driver from printing error messages
     whenever the driver detects it is out of Packet Receive Buffers or has
     detected loss of connectivity to the LAN.  See the explanations under
     the statistics "Currently No Rx Buffers Allocated" and "Connected to
     LAN" below.
 
 RX_BUFFERS=<number>
 
     This keyword will override the default number of Packet Receive Buffers
     the driver will allocate when loading.  These buffers are used to
     store newly arrived packets from the LAN.  The default is 1.  The range
     is 1 to 31.  This parameter should only be used under the guidance of
     qualified HP support personnel.
 

 
 Note on Custom Statistics
 =========================
 Both 32-bit ODI drivers collect the following custom statistics.
  
 Lan Speed (Mbit)...........................

     Shows which LAN speed the adapter is configured to operate.  It can be
     either 10 or 100 depending on which LAN connector is used.  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-memory data transfers.  
     One (1) means the driver is using I/O-memory data transfers.

 Always Transmit High Priority..............

     Zero (0) means all packets are transmitted using normal priority on
     100VG LAN.  One (1) means all packets are transmitted using high
     priority on 100VG.  This has no meaning on 10Base-T LANs.  See
     PRIORITY.TXT in the TECHNOTE 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.
 

 Note on Bus-Master Custom Statistics
 ====================================
 The 32-bit ODI bus master driver collects the following additional status
 and statistics:
 
 Tx Packets Dropped Due to Excessive Frags..
 
     The number of transmit packets which are comprised of more than 29
     buffer fragments.  The ODI specification maximum is 17.  This should
     never be above 0.
 
 Current Number Of Rx Buffers Allocated.....
 
     The current number of empty NetWare Packet Receive Buffers the driver
     is holding waiting for new receive packets to arrive.  For 10 Mbit/s
     operation, the default is 10.  For 100 Mbit/s operation, the default
     is 31.  The number should be between 0 and 31.
 
 Currently Less Than Max Rx Buffers..(1=yes)
 
     When the driver is loaded, it will allocate up to the default number
     of Packet Receive Buffers from NetWare depending on which LAN speed is
     operating.	Whenever the number of Packet Receive Buffers the adapter
     is holding ever drops less than this initial number, then this is set
     to one (1).
 
 Allocate Rx Buffer Failure Count...........
 
     This counts the number of times there were no empty NetWare Packet
     Receive Buffers available when the driver asks for a another to
     replace one that was just filled by a newly received packet.  If this
     count is above zero, consider increasing the value of the NetWare
     settable parameter "Minimum Packet Receive Buffers".
 
 Currently No Rx Buffers Allocated...(1=yes)
 
     This will be one (1) whenever the number of Packet Receive Buffers
     the driver is holding is zero.  If this happens briefly, the adapter's
     128K of memory will buffer packets until they are transferring into
     the system.  If this condition persists, then incoming packets will
     be dropped.
 
 No Rx Buffers Allocated Count..............
 
     The count of times the number of Packet Receive Buffers the driver is
     holding is zero.  If this count is above zero, consider increasing the
     value of the NetWare settable parameter "Minimum Packet Receive Buffers".
  
  
 
 Note on Error Messages
 ======================
 There are a few error messages specific to this driver described here.  Common
 messages are described in the file \TECHNOTE\ERRORMSG.TXT on this support 
 disk.
 
 Must use ETHERTSM version ????????.??????? or greater.
 
     This message is produced when the version of MSM31X and ETHERTSM loaded
     on the server is not version 2.32 or later.  Unload these NLMs from the
     server and load these NLMs from the \NOVELL\NLM31X directory.
 
 Allocated only X of Y Receive Buffers needed for best performance.  Add Z to
 the Minimum Packet Receive Buffers setting.
 
     This message is produced only at load time and means the driver was
     unable to pre-allocate enough Packet Receive Buffers.  See step 4 of
     the installation instructions to correctly configure NetWare to 
     provide extra buffers for the driver to use.  
 
 Unable to allocate any receive packet buffers.
 
     This message indicates that NetWare's pool of Packet Receive Buffers is
     empty when the driver tried to allocate an empty one.  Given that enough
     buffers were configured when NetWare was initialized and the driver was
     successfully loaded (see step 4 of the installation instructions), this
     error occurs due to other modules holding buffers.  NetWare will slowly
     increase the number of Packet Receive Buffers to alleviate the shortage.
     Consider increasing the number of buffers in the SET MINIMUM PACKET
     RECEIVE BUFFERS in STARTUP.NCF.  Also, see the "NOWARN" description under
     "Note on Keywords".
 
 
<End of File> 
