			INSTALLATION INSTRUCTIONS FOR
	    NOVELL 16-BIT ODI DRIVER WITH DOS REQUESTER (VLM) AND
                        HP DeskDirect LAN ADAPTER

 DOS and Microsoft Windows 3.x computers gain access to Novell servers
 through Novell's client software called the DOS Requester (i.e. VLM.EXE).
 The DOS Requester uses the 16-bit Open Data-Link (ODI) driver to access
 the LAN adapter and the LAN media.
 
 The following versions of Novell DOS software must be used:
     - LSL.COM    v2.11 or later
     - IPXODI.COM v2.20 or later
 
 If any of these files are an earlier version than is supported see the
 note "Obtaining Latest Novell Client Software" below.
 
 The 16-bit ODI driver is self-configuring, which means no additional
 NET.CFG parameters need to be specified beyond the "LINK DRIVER" line.
 The driver will locate the adapter and read in its configuration.

 There are two 16-bit DOS ODI drivers contained in the HP DeskDirect 
 LAN Adapter Support Disk.

     HPFEODIM.COM - bus-master mode 16-bit DOS ODI driver
     HPFEODI.COM  - I/O-memory mode 16-bit DOS ODI driver
 
 The HPFEODIM.COM driver uses the HP DeskDirect LAN adapter's bus-master
 data transfer mode.  Bus-mastering provides the highest performance data
 transfers.  Please refer to your HP DeskDirect LAN adapter's Installation
 Guide to determine if your adapter supports bus-master operation.

 The HPFEODI.COM driver uses the HP DeskDirect LAN adapter's I/O-mapped
 or memory-mapped data transfer modes.  It may be used in the situation
 when the HP DeskDirect LAN adapter is installed in a slot which does
 not support bus-master operations, or if your HP DeskDirect LAN adapter
 does not support bus-master operation.

 NOTE:  Throughout these instructions, the term 'HP LAN Card' will be used
        to refer to the HP DeskDirect LAN Adapter.
 
 To install the HP LAN Card and its 16-bit ODI driver for DOS, follow the
 instructions below:
 
 1.  Install the HP LAN Card and run HPVGSET.
 
     Follow instructions in the 'Setting Up Your Card and LAN Connection'
     chapter of the Installation Guide.
 
 2.  Locate the "NetWare Client for DOS and MS Windows" diskettes.
 
     Locate the Novell DOS Requester installation diskette(s).  These could
     be labeled "WSDOS_1" and "WSWIN_1".  To create these NetWare client 
     installation diskettes from the NetWare CD ROM, follow the NetWare
     documentation included with the CD-ROM.
 
 3.  Run the NetWare client installation program.
 
     Insert the number 1 diskette into the floppy drive and execute the 
     INSTALL program.  For example, if the NetWare diskette is in floppy 
     drive A, then enter:
 
         A:
         INSTALL
 
     Follow Novell's instructions to fill in the first three fields of
     the form.
 
     It is recommended to answer 'Yes' in STEP 2 to allow the Novell install
     utility to modify the startup files.  This will make the NetWare
     client start up automatically and attach to the server every time the
     computer is rebooted.  If 'N' is entered, the commands to start up the
     NetWare client will have to be entered manually.
 
     If Windows is installed on the computer, it is recommended to answer
     'Yes' in STEP 3 to allow the Novell install utility to add Windows
     support.
 
 4.  Specify the driver to use.

     The fourth or fifth step, depending on the NetWare version, selects which 
     ODI driver to use.  Press the ENTER key to bring up the "Network Board" 
     window.  Highlight the "OTHER DRIVERS" at the end of "Network Board" list
     and press the ENTER key to bring up the "Insert the DRIVER Disk" window. 
 
     Remove the Novell diskette and insert the HP Support Disk.  Press the
     ENTER key to bring up the "Network Board" window.  The lines:
 
         Hewlett-Packard DeskDirect Bus Master LAN Adapter
         Hewlett-Packard DeskDirect LAN Adapter
 
     will be displayed in the "Network Board" window. Highlight the appropriate
     line of your choice and then press the ENTER key to select the driver.

     If you choose to use the bus-master mode driver, highlight the 
     "Hewlett-Packard DeskDirect  Bus Master LAN Adapter" line.
     If you choose to use I/O-memory mode driver, highlight the
     "Hewlett-Packard DeskDirect LAN Adapter" line.
 
 5.  Skip the NET.CFG overrides.
 
     The Novell INSTALL utility will display a window with the settings for
     the card.  The following parameters will be shown:
         
         Optional Bus Identifier
         Optional Card Identifier
         Optional EISA/PCI Slot
         Optional Hardware Interrupt    
         Optional ISA Base I/O Port
         Optional LAN Speed
         Optional Media Frame Type(s)   
         Optional Memory-Mapped Address
         Optional Node Address
 
     Press the ESC key without selecting any parmeters and proceed with
     the remainder of the steps in the NetWare DOS Requester INSTALL utility.
 
     NOTE: When the HP LAN Card DOS ODI driver is run, it will locate the
           HP LAN Card and read the resources the card is using.
 
     NOTE: If more than one HP LAN Card is installed, see "Note on NET.CFG 
           Parameters for HPFEODIM & HPFEODI Driver" below.
 
     NOTE: The ODI driver default frame type is ETHERNET_802.2.  NetWare
           286 and 386 servers use frame type ETHERNET_802.3 as their default,
           but NetWare 4.0 uses both ETHERNET_802.2 and ETHERNET_802.3 types.
           The HP LAN Card supports all Ethernet frame types.

 6.  Complete the Netware client software installation.

     Follow the instructions of Netware client software installation utility
     to finish the installation procedure.  All the Netware client software
     files will be copied to your target drive and the appropriate NET.CFG
     file will be created for proper operations.

 7.  Reboot the computer.
 
     After the installation procedure is compeleted, exit from the installation
     utility and windows if you were running windows. Then, reboot the computer
     to have all the changes made to DOS and Windows's configuration files
     take effect.
 
 The installation of the HP ODI driver and NetWare client software is complete.  
 
 Note on NET.CFG Parameters for HPFEODIM & HPFEODI Driver
 ========================================================
 
 The HPFEODIM and HPFEODI DOS ODI drivers support the following optional 
 NET.CFG parameters:

     PORT         "Optional Base I/O Port"        (default: search for card)"
     SLOT         "Optional EISA/PCI Slot         (default: search for card)"
     BUS ID       "Optional Bus Identifier        (default: search for card)"
     CARD ID      "Optional Card Identifier       (default: search for card)"
     LAN SPEED    "Optional LAN Speed             (default: autoselect LAN)"
     FRAME        "Optional Media Frame Type(s)   (default: ETHERNET_802.2)"
     MEM          "Optional Memory-Mapped Address (default: read from card)"
     NODE ADDRESS "Optional Node Address          (default: read from card)"
 
 The default behavior for the HP DOS ODI driver is to search for all the 
 HP LAN Cards that it supports and read the configuration stored onboard.
 Normally, none of these parameters needs to be specified in the NET.CFG file.
 
 There are several reasons to specify one or more of these parameters in
 the NET.CFG file:
 
     1) To add support for additional frame types.
     2) To prevent interference with another card caused by the search
        for any HP LAN Cards.
     3) If there is more than one HP LAN Card installed.
     4) To override the Interrupt Channel (IRQ) used by the HP LAN Card.
     5) To override the Memory-Mapped Address used by the HP LAN Card.
     6) To override the LAN selected.
     
 To add or modify parameters in the NET.CFG file, use a text editor.  Make
 sure the file is saved as a plain text or ASCII file.  All these parameters
 are under the "LINK DRIVER" section of the NET.CFG file for the DOS ODI
 driver loaded (e.g. HPFEODIM or HPFEODI).
 
 NOTE: The "LINK DRIVER" line must start on column one and the other lines 
 must be indented at least two spaces.
 
 PORT  
       When this value is specified, it must match the first address
       in the "I/O Address Range" parameter shown by HPVGSET.  When a
       PORT value is specified, the driver will check for an HP LAN
       Card only at that I/O location.  If no card is present, the driver
       will exit with an error.
           
       For example, using the I/O Address Range of "D000-D0FFh", the PORT
       line should be:
         
           PORT D000
 
 SLOT  
       For EISA and PCI cards, when this value is specified, it must match the
       slot number into which the HP EISA or PCI LAN card is installed.  When
       a SLOT value is specified, the driver will check for a HP EISA or PCI
       card only at that slot.  If no card is present, the driver will
       exit with an error.
 
       The legal values are 1 to 15 for EISA cards and 1 to 255 for PCI cards.
       Please note that for PCI cards, this parameter is valid only when the
       PCI card is installed on the computer with the BIOS conforming to
       PCI BIOS Specification version 2.10 or later.
 
       For example, if the PCI card is located in slot 1, the SLOT line
       should be:
 
       SLOT 1
 
       For ISA cards, this value is ignored.
 
 BUS ID  
       This parameter tells the driver which of the system busses to
       search for an HP LAN Card.  When a BUS ID value is specified,
       the driver will check for an HP LAN Card.  If no card or
       multiple cards are found on the bus, the driver will exit with an
       error.
 
       The legal values are "ISA 0", "EISA 2", and "PCI 4".
 
       For example, to have the driver search the PCI bus, the BUS ID
       line should be:
 
       BUS ID PCI 4
 
 CARD ID  
       This parameter tells the driver to search for an HP LAN Card
       matching the network address specified.  The value entered should
       be the last six hexidecimal digits of the adapter's MAC address.
       When a CARD ID value is specified, the driver will search for an
       HP LAN Card that matches the value specified.  If no card is
       found, the driver will exit with an error.
 
       For example, if the adapter's network address is 080009123ABC, the
       CARD ID line should be:
 
       CARD ID 123ABC
 
       Please note that CARD ID parameter may interfere with the card searching
       process if there are multiple of HP LAN cards installed on the same
       PC. In this case, it is recommended that using PORT or SLOT or BUS ID
       to uniquely specify which card to be used. 
 
 INT   
       For ISA and EISA cards, this value will override the Interrupt
       Channel stored in the card by HPVGSET until the computer is rebooted.
 
       The legal values are: 3, 4, 5, 7, 9, 10, 11, 12, and 15.
 
       For example, to use interrupt channel 3, the INT line should be:
 
       INT 3
 
       For PCI cards, the INT parameter is not allowed.
 
 LAN SPEED  
       This value will override the LAN connector stored in the card by
       HPVGSET until the computer is rebooted.  The value specified
       indicates the speed of the network connected to.  
 
       The legal values are: 10 and 100
 
       For example, to force the adapter to only use the 100 Mbit/s
       network connection, the LAN SPEED line should be:
 
       LAN SPEED 100

       For 10Base-T only cards, this parameter is ignored.

 FRAME  
       This parameter tells the driver which frame types to recognize.
       NetWare 286 and 386 servers use frame type ETHERNET_802.3 as
       their default, but NetWare 4.0 uses both ETHERNET_802.2 and
       ETHERNET_802.3 types.  More than one FRAME line with different
       values can be specified.
 
       The legal values are: ETHERNET_802.2, ETHERNET_802.3, ETHERNET_II,
       and ETHERNET_SNAP.
 
       For example, to use the default frame type of ETHERNET_802.2, the 
       FRAME line should be:
         
           FRAME ETHERNET_802.2
 
 MEM   
       This parameter is only valid with HPFEODI driver. It is not
       required if HPFEODIM driver is used.  This value will override
       the Memory-Mapped Address stored on the adapter until the computer
       is rebooted.
 
       NOTE: If an expanded memory manager (e.g. EMM386) is loaded on
             the computer, refer to the \TECHNOTE\MEMMAP.TXT file on
             the HP Support Disk for the steps necessary to
             configure the memory manager for memory-mapped mode.
 
       The legal values are from A0000 (hex) to EE000 (hex) every 2000 (hex)
       (ie. A0000, A2000, A4000, A6000, A8000, AA000, AC000, AE000, etc).  
       Note all the numbers are in hexidecimal without the trailing "H".
 
       For example, to use the memory-mapped address D0000, the MEM line
       should be:
 
       MEM D0000
 
       NOTE: On computers with multiple PCI busses, the MEM keyword might
             not enable memory-map mode.  See the note "Addressing Issues"
             in the \TECHNOTE\PCI_INFO.TXT file on the HP Support Disk for
             more information.
 
 NODE ADDRESS  
       This value will override the factory station address stored on the 
       adapter.  Use this only if station addresses will be administered 
       locally.
 
       For example, to use a station address of AABBCC123456, the NODE
       ADDRESS line should be:
 
       NODE ADDRESS AABBCC123456
 
       NOTE: The CARD ID is based on the network address set at the
             factory.
 
 Obtaining Latest Novell Client Software
 =======================================
 
 The most currect versions of Novell Client software can be purchased from
 Novell at 1-800-UPDATE1 by ordering "NetWare Client for DOS/MS Windows".  
 
 The most current versions of Novell Client software can be downloaded
 from Novell's Internet system at ftp.novell.com or in Novell's CompuServe
 NOVFILES area.  The self-extracting archives, which contain Novell Client
 software, are currently named:
 
       NET33X.EXE  -  contains NETX.EXE
       VLMUP2.EXE  -  contains LSL.COM, IPXODI.COM, VLM.EXE, and VLMs
       WINDR2.EXE  -  contains NetWare Windows system files (DRV, 386, etc)
       NWDLL2.EXE  -  contains NetWare Windows DLL files
 
 NOTE: The archive names are changed whenever files are updated within them.
       For example, the next update of VLMUP2.EXE will probably be named
       VLMUP3.EXE.
<End of File>
