1. HPDeskDirectJ2573AJ2577AJ2585AJ2585BJ2970AJ2973ALANAdapters.zip Driver
2. README File Contents

README Driver File Contents (HPDeskDirectJ2573AJ2577AJ2585AJ2585BJ2970AJ2973ALANAdapters.zip)

                       INSTALLATION INSTRUCTIONS FOR
        16-BIT NDIS 2.01 DRIVER FOR FTP PC/TCP v2.X FOR DOS/WINDOWS WITH
                    HP DeskDirect 10/100 PCI LAN Adapter
 
 This document contains the information for installing the HP DeskDirect 
 10/100 PCI LAN Adapter with FTP PC/TCP v2.X networking software.
 
 The HP NDIS 2.01 driver is self-configuring, which means the driver will
 automatically locate and read in the HP DeskDirect 10/100 PCI LAN card's 
 configuration. Only the DRIVERNAME parameter needs to be present under 
 the [HPFEND] section in the PROTOCOL.INI file.
 
 The 16-bit NDIS-2 driver is contained in the HP Support Disk NDIS2 directory:
 
         \NDIS2\HPFEND.DOS - 16-bit NDIS 2.01 driver
 
 NOTE: Throughout these instructions, the term 'HP LAN Card' will be used to
       refer to the HP DeskDirect 10/100 PCI LAN Adapter.
 
 To install the HP LAN Card and its 16-bit NDIS 2.01 driver with FTP PC/TCP,
 follow the instructions below:
 
 1.  Install the HP LAN Card, and optionally, run HPVGSET.
 
     Follow instructions in the 'Setting Up Your Card and LAN Connection'
     chapter of the Installation Guide.
 
 2.  Install the FTP PC/TCP for DOS/Windows software.
 
     Follow the installation guide manual provided with the FTP PC/TCP for
     DOS/Windows to install it on your computer.
 
     Select the "DIX Ethernet" driver (ETHDRV) as the PC/TCP kernel.
 
 3.  Copy the NDIS 2.01 driver from the HP Support Disk to the same
     directory where the FTP PC/TCP software is installed.
 
     Insert the HP Support Disk into the floppy drive, and enter the
     following command at the DOS prompt:
 
         COPY A:\NDIS2\HPFEND.DOS C:\FTP
 
     NOTE:  This assumes that PC/TCP is installed in the C:\FTP directory.
 
 4.  Copy the PC/TCP NDIS support files from the FTP DOS/Windows diskette
     to the same directory where the FTP PC/TCP software is installed.
 
     Insert the FTP DOS/Windows diskette into the floppy drive and enter
     the following commands at the DOS prompt:
 
         COPY A:\PROTMAN.DOS C:\FTP
         COPY A:\PROTMAN.EXE C:\FTP
         COPY A:\NETBIND.COM C:\FTP
 
     NOTE:  This assumes that PC/TCP is installed in the C:\FTP directory.
 
     Make sure the PC/TCP packet driver to NDIS driver converter module
     DIS_PKT.GUP is also in the same directory (eg. C:\FTP).
 
 5.  Edit the PROTOCOL.INI file with an ASCII text editor.
 
     Use the PROTOCOL.FTP file located in the directory where PC/TCP is
     installed as a template and reference to the example shown below to
     create a customized PROTOCOL.INI for the computer.
 
         [PROTMAN]
         ; Protocol manager
         drivername = PROTMAN$
 
         [PKTDRV]
         drivername = PKTDRV$
         intvec = 0x60
         bindings = HPFEND_NIF           <--- Add this line
 
         [HPFEND_NIF]                    <--- Add this line
         ; HP DeskDirect 10/100 PCI LAN Adapter   <--- Add this line
         DRIVERNAME = HPFEND$            <--- Add this line
         ; adaptertype = 3
	 ; adapterslot = 
         ; ioaddress = 
         ; memorymapbase = 
         ; maxhwtrans = 10
         ; maxswtrans = 2
         ; maxmulticast = 5
         ; maxicnest = 1
         ; priority = no
         ; usebootrom = no
         ; busmaster = yes
         ; netaddress = "080009010203"
 
     The PROTOCOL.INI file must include a section describing the LAN adapter
     (the HPFEND section) and a section describing each of the network
     products being run.  Each network product section (eg. NFS-NDIS) must
     include a BINDINGS statement.
 
     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. 
 
     NOTE: Refer to the PROTOCOL.TXT file in the \NDIS2 subdirectory on the
           HP Support disk for the definition of each PROTOCOL.INI parameter.
 
     NOTE: The file \PCTCP\PROTOCOL.HP is an example of the PROTOCOL.INI
           file for using HP LAN Card in the FTP PC/TCP environment.
 
 6.  Edit the CONFIG.SYS file with an ASCII text editor.
 
     The CONFIG.SYS file must be modified to contain the DEVICE statements
     that load the needed drivers (eg.  Protocol Manager, HP NDIS 2.01, and
     and packet driver converter).  Add the following statements near the
     end of the CONFIG.SYS file:
 
         DEVICE = C:\FTP\PROTMAN.DOS /I:C:\FTP
         DEVICE = C:\FTP\HPFEND.DOS
         DEVICE = C:\FTP\DIS_PKT.DOS
 
     NOTE:  This assumes that PC/TCP is installed in the C:\FTP directory.
 
     Please refer to the FTP PC/TCP for DOS/Windows Installation Guide
     manual for more information about how to customize the CONFIG.SYS file
     for FTP PC/TCP software.
 
     NOTE: This assumes that PC/TCP is installed in the C:\FTP directory.
 
     NOTE: The DEVICE statement for the PROTMAN driver must be before the
           other network driver DEVICE statements.
 
     NOTE: The "/I:" parameter in the DEVICE statement for the PROTMAN file
           identifies the path to the PROTOCOL.INI file.
 
 7.  Edit the AUTOEXEC.BAT file with an ASCII text editor.
 
     Before running any network application (eg. FTP, TELNET, etc), PC/TCP
     must be started.  Add the following lines near the beginning of the
     AUTOEXEC.BAT file:
 
         SET PCTCP=C:\FTP\PCTCP.INI
         C:\FTP\NETBIND
         C:\FTP\ETHDRV
 
     NOTE:  This assumes that PC/TCP is installed in the C:\FTP directory.
 
 8.  Reboot the computer.
 
     The changes made to the PROTOCOL.INI, CONFIG.SYS and AUTOEXEC.BAT will
     not take effect until your computer is rebooted.  Reboot your computer
     in order to activate the FTP PC/TCP software.
 
 
 The installation of FTP PC/TCP is complete.

<End of File>