1. j3239a.exe Driver
2. NW.TXT File Contents

NW.TXT Driver File Contents (j3239a.exe)

		  SOFTWARE INSTALLATION INSTRUCTIONS
	 FOR NOVELL NETWARE VERSION 3.12 and 4.X (except 4.11)
			 ODI SERVER DRIVER
	     HP J3239A DeskDirect EL-10 ISA Combo Adapter


 The driver is based on the latest version 3.3 of the ODI specification.

    \NETWARE\HPEIOD.LAN    Novell NetWare 3.12, 4.0, 4.1 Server Driver
    \NETWARE\HPEIOD.LDI    Installation Information File for
			   Novell NetWare 3.12, 4.0, 4.1 Server Driver



 ==============================
 GENERAL INSTALLATION PROCEDURE
 ==============================

 1.  Install NetWare server.

     Complete the software installation procedures for the NetWare
     server.  See the Novell documentation on how to install NetWare.


 2. Copy the HP driver and NetWare Loadable Modules from the Support
    Disk for HP J3239A.

    While running DOS on the server computer, copy the HP NetWare server
    driver (HPEIOD.LAN) and all the NetWare Loadable Modules from the
    support disk to the DOS directory containing the NetWare server.  For
    example, if the support disk is in floppy drive A: and the server
    is in the C:\NWSERVER directory (for NetWare 4.X except NetWare 4.11),
    or is in the C:\SERVER.312 directory (for NetWare 3.12), execute
    the following DOS commands:

    For NetWare 3.12:
    =================

    copy a:\netware\hpeiod.lan c:\server.312
    copy a:\netware\312nlm\ethertsm.nlm c:\server.312
    copy a:\netware\312nlm\msm31x.nlm c:\server.312
    copy a:\netware\312nlm\nbi31x.nlm c:\server.312

    In AUTOEXEC.NCF file, You must add following three lines
    before loading and binding the server driver (HPEIOD.LAN).

    load c:\server.312\nbi31x.nlm
    load c:\server.312\msm31x.nlm
    load c:\server.312\ethertsm.nlm


    For NetWare 4.X (except NetWare 4.11):
    ======================================

    copy a:\netware\hpeiod.lan c:\nwserver
    copy a:\netware\410nlm\ethertsm.nlm c:\nwserver
    copy a:\netware\410nlm\msm.nlm c:\nwserver
    copy a:\netware\410nlm\nbi.nlm c:\nwserver

    In AUTOEXEC.NCF file, You must add following three lines
    before loading and binding the server driver (HPEIOD.LAN).

    load c:\nwserver\nbi.nlm
    load c:\nwserver\msm.nlm
    load c:\nwserver\ethertsm.nlm


    If you can log into the server, copy the files to the SYSTEM
    subdirectory.  If you do this, you won't need to specify a path on
    the load line.  If you copy the files to another subdirectory,
    you'll need to specify the correct path.

    Note: Be sure to obtain other patch files required for 3.12, 4.X
	 (except 4.11) available from Novell:
	     312PTx.EXE, 410PTx.EXE
		("x" is the number indicating the latest
		 revision of the patch or archive file)


 3.  Start the server. Load and bind the HP server driver.


 4. At the NetWare prompt (indicated by a colon), run the driver
    program:

    load D:\hpeiod
    bind ipx to hpeiod net=X

       D is the path to the server driver.
       X is the NetWare Network number you choose.


 5.  Add the load and bind statements to your server's AUTOEXEC.NCF
     file, so that the adapter driver loads automatically each time the
     server starts.



 ==============
 Hints and Tips
 ==============

 1. Installing multiple adapters:

    If installing multiple adapters, each adapter must have a
    different NET number and SLOT number.  Also, it is a good idea to
    name each adapter. Example:

	  load D:\hpeiod slot=3  name=LAN_A
	  bind ipx to LAN_A  net=222
	  load D:\hpeiod slot=5  name=LAN_B
	  bind ipx to LAN_B  net=333


 2. Installing one adapter with multiple frame types:

    When binding multiple frame types to one adapter, enter a LOAD and
    BIND statement for each frame type.  Each LOAD statement uses the
    same SLOT number, but each BIND statement needs a unique network
    number.



 ==============
 ERROR MESSAGES
 ==============

 "The board cannot be found."
    Possible cause: The adapter does not exist or driver does not
		    recognize the adapter.
    Solution: Check that the HP J3239A adapter is fully seated in the
	      correct slot.

 "Board RAM failed the memory test."
    Possible cause: The RAM buffer on the adapter failed.
    Solution: Try a different HP J3239A adapter.

 "The board did not respond to the initialization command."
    Possible cause: The driver recognized the adapter but the adapter
		    fails to respond.
    Solution: Try a different HP J3239A adapter.

 "There is no cable connecting to adapter."
    Possible cause: The adapter is not connected to the network cable,
		    or the adapter's transceiver has failed.
    Solution: Check the cable connections and try again.


<End of File>