			INSTALLATION INSTRUCTIONS FOR
	    16-BIT NDIS 2.01 DRIVER FOR DOS/WINDOWS AND OS/2 WITH
                     THE HP DESKDIRECT LAN ADAPTER (J2973A)

 
 The Network Driver Interface Specification (NDIS) 2.01 is a 16-bit driver
 used by many DOS and OS/2 networking products to gain access to the LAN.
 
 The HP NDIS 2.01 drivers are self-configuring, which means the driver will
 automatically locate and read the HP DeskDirect LAN Adapter's configuration.
 Only the DRIVERNAME parameter needs to be present under the [HPFEND]
 section in the PROTOCOL.INI file.
 
 The 16-bit NDIS 2.01 drivers are located on the HP Support Disk:
 
     \IBMLS\DOS\HPFEND.DOS - 16-bit NDIS 2.01 driver for DOS and Windows
     \IBMLS\OS2\HPFEND.OS2 - 16-bit NDIS 2.01 driver for OS/2
 
 
 To install the HP DeskDirect LAN Adapter and its 16-bit NDIS 2.01
 DOS or OS/2 driver, follow the instructions below:
 
 
 1.  Install the HP DeskDirect LAN Adapter, and optionally, run HPVGSET.
 
     Follow instructions in the printed manual.
 
 2.  Install the networking product onto the PC.
 
     Completely install the networking product.
 
     NOTE: If the product requires that a driver be given and it cannot
           read the HP NDIS 2.01 driver off this disk, then pick any other
           driver to install.  In steps 4 and 5 below, when editing the
           PROTOCOL.INI and CONFIG.SYS files, change all occurances of that
           driver's name to HPFEND.
 
 3.  Copy the NDIS 2.01 driver from the HP Support Disk.
 
     Create a directory on the computer.  For example,
 
         C:
         MKDIR \NDIS2
 
     Copy the NDIS 2.01 driver file from HP Support Disk this directory.
     For DOS computers with the HP Support Disk in floppy drive A:
 
         COPY A:\IBMLS\DOS\HPFEND.DOS C:\NDIS2

     For OS/2 computers with the HP Support Disk in floppy drive A:
 
         COPY A:\IBMLS\OS2\HPFEND.OS2 C:\NDIS2
 
 4.  Edit the PROTOCOL.INI file with a text editor.
 
     Locate the PROTOCOL.INI file within the networking product's directory
     created in step two.
 
     The PROTOCOL.INI file must include a section describing the LAN adapter
     (i.e. a [HPFEND] section) and a section describing each of the network
     products being run.  Each network product section must include a
     a BINDINGS statement.
 
     For a complete description of all the parameters used by the
     HP DeskDirect LAN Adapter NDIS 2.01 driver, refer to the PROTOCOL.TXT
     file under \NDIS2 directory of the HP Support Disk.
     
     Here is an example section for the HP DeskDirect LAN Adapter shown below:
 
         ; HP DeskDirect LAN Adapter
         [HPFEND_PCI]
                 drivername = HPFEND$
         ;       adaptertype = 3
         ;       adapterslot = 
         ;       ioaddress = 
         ;       memorymapbase = 
         ;       maxhwtrans = 10
         ;       maxswtrans = 2
         ;       maxmulticast = 5
         ;       maxicnest = 1
         ;       priority = no
         ;       usebootrom = no
         ;       busmaster = yes
         ;       netaddress = "080009010203"
 
     All the optional parameters have been commented out (using the ';'
     character) and are shown here only to illustrate the defaults.
     Only the DRIVERNAME parameter is mandatory. 
  
     The PROTOCOL.INI file must be merged with the networking product's
     PROTOCOL.INI.  BINDINGS statements must be created to identify the
     HP DeskDirect LAN Adapter NDIS 2.01 driver to the networking
     product's protocol modules.
 
     An example PROTOCOL.INI file that supports FTP PC/TCP might look like
     the following:
 
          ; FTP's software
          [PKTDRV]
          drivername = PKTDRV$
          intvec = 0x65
          bindings = HPFEND                         <--- Add this line
 
          ; HP DeskDirect LAN Adapter
          [HPFEND]                                  <--- Add this line
          DRIVERNAME = HPFEND$                      <--- Add this line
 
 5.  Edit the CONFIG.SYS file.
 
     The CONFIG.SYS file must be modified to include DEVICE statements
     for the PROTMAN.DOS (or PROTMAN.OS2) driver, for the HPFEND driver,
     and any of the drivers for the networking product being used.
     An example portion of a DOS CONFIG.SYS file that supports the
     HP DeskDirect LAN Adapter and FTP PC/TCP version 2.2 is shown below:
 
         REM************************************************
         REM   FTP software, run startftp after bootup   ***
         REM************************************************
         DEVICE = C:\FTP\PROTMAN.DOS /I:C:\FTP
         DEVICE = c:\FTP\DIS_PKT.GUP
         REM*************************************************
         REM  HP DeskDirect LAN Adapter NDIS 2.01 DRIVER  ***
         REM*************************************************
         DEVICE = C:\NDIS2\HPFEND.DOS
 
     Please refer to FTP PC/TCP's Installation Manual for details.
 
     Notes on the PROTMAN driver:
 
     - PROTMAN must be loaded before the adapter driver and the networking
       drivers; that is, the DEVICE statement for the PROTMAN driver must be
       located before the other network DEVICE statement.
 
     - The "/I:" parameter in the DEVICE statement for the PROTMAN driver
       identifies the path to the PROTOCOL.INI file.  In the example above,
       PROTOCOL.INI is located in the directory C:\FTP.
 
 6. Reboot the computer and execute NETBIND.EXE
 
      To activate the modified PROTOCOL.INI and CONFIG.SYS files, reboot
      the computer.  When the boot process is complete, run NETBIND.EXE.
      This file is included with the networking product software.  NETBIND
      must be run each time the system is booted, so it is recommended
      NETBIND.EXE be added to the AUTOEXEC.BAT file.
 

<End of File>
 
