.TOPIC:
Contents
SETUP Help Menu Netware ODI Driver
NDIS Driver Netware Client 32 Driver
LAN Manager Netware Server 4.11 Green River
LAN Server Netware Server Driver
Windows for Workgroups 3.11 LANtastic
Windows NT 3.5x Banyan VINES
Windows NT 4.0 SUN PC-NFS
Windows 95 FTP PC/TCP
SCO UNIX
[TAB]: Forward [SHIFT+TAB]: Backward [C]: Contents [E]: Exit
.TOPIC:
SETUP Help Menu
[ SETUP Help Menu ]
< Function Key >
Software Installation
F1 : S/W Instructions
F2 : Install Driver
F3 : Update Driver
F6 : Dos Shell
F10: Exit
< Control Key >
ALT : Menu
ARROWS : Change parameter
TAB : Move cursor forward
SHIFT+TAB: Move cursor backward
ALT : List parameters
ESC : Exit
-- <THE END> --
.TOPIC:
Netware ODI Driver
SOFTWARE INSTALLATION INSTRUCTIONS
FOR NOVELL ODI DOS CLIENT DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
For NDIS-2 drivers for DOS clients, see the NDIS-2 instructions instead,
or instructions for Microsoft LAN Manager or IBM LAN Server for those
specific NOSs.
(The general NDIS-2 "readme" file is \NDIS2\README.TXT.
For Microsoft LAN Manager, it is \MSLANMAN.DOS\README.TXT.
For IBM LAN Server, it is \IBMLS\IBMDOS.TXT.)
File Description
----------------
Filename Description
------------ ---------------------------------------
LSL.COM This program implements the Link Support Layer for
DOS ODI clients and generally is loaded first upon
booting. The Link Support Layer file enables the
client to communicate over several protocols.
IPXODI.COM This is Novell's protocol stack for DOS ODI clients.
It performs the same functions as IPX.COM, which is
used for DOS clients. However, it is optional and is
loaded after the LAN driver. Other protocols can be
loaded in its place or with it. This is one of the
key features of the ODI environment.
NETX.COM NetWare Network program.
If you use: You need:
------------------------ -----------
Conventional memory NETX.COM
Expanded memory EMSNETX.EXE
(LIM 4.0 EMS compatible)
Extended memory XMSNETX.EXE
(XMS 2.0 compatible)
NETBIOS.EXE The NetBIOS emulation program (INT 5CH interface) allows
you to run NetBIOS application programs based on the
NETBIOS.EXE interface. The running sequence is one of
the following:
a. IPX shell driver
IPX.COM
NETBIOS.EXE ---> NetBIOS emulation interface
...
b. DOS ODI driver
LSL.COM
HPEIOD.COM ---> DOS ODI driver for HP J3239A
IPXODI.COM
NETBIOS.EXE
...
RXMONSTK.COM This is the receive monitor utility for monitor-type
applications (such as LAN Analyzer).
If the monitor-type applications you are using seem to
stop receiving network packets when you install a new
LAN driver on the computer, load the RXMONSTK.COM file.
Load the RXMONSTK.COM file after the LSL.COM driver
but before the LAN driver. RXMONSTK.COM operates as a
TSR and requires 2684 bytes of memory. You can load
only one LAN driver when using RXMONSTK.COM.
The running sequence is:
LSL.COM
RXMONSTK.COM
HPEIOD.COM ---> DOS ODI driver for HP J3239A
IPXODI.COM
...
======================
INSTALLATION PROCEDURE
======================
1. Make sure that your NetWare operating system is properly installed.
2. Specify "LASTDRIVE=Z" in the CONFIG.SYS file. (When you use VLM.)
3. Edit the NET.CFG file to change any parameters as needed.
Sample NET.CFG file: LINK DRIVER HPEIOD
INT 5
PORT 320
:
:
IF more than one HP J3239A ISA adapter is installed, you must
specify the interrupt ("INT") and I/O base address ("PORT") for
each adapter. Use the same settings from the hardware
configuration of each adapter; you can view the settings in
HPEISET.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing,
working adapter. Check its HW configuration again, and
if changed, reinstall the driver.
IF you have a non-Plug-and-Play computer, you must change the
interrupt setting ("INT") and I/O base address setting ("PORT")
to match the hardware configuration for the adapter, as listed
by HPEISET. If you did not make a note of them when configured,
now use the "View Configuration" menu item in HPEISET to note them.
IF using a NetWare 3.11 client and a NetWare 4.x server:
The default frame type for NetWare 3.11 is Ethernet 802.3, while
default frame type for NetWare v4.x is Ethernet 802.2. Therefore,
include protocol binding for Ethernet 802.3 in the server's site.
4. Run one of the following sets of commands in the sequence shown:
lsl OR lsl
hpeiod hpeiod
ipxodi ipxodi
netx vlm
5. Log on to your network.
-- <THE END> --
.TOPIC:
Netware Client 32 Driver
SOFTWARE INSTALLATION INSTRUCTIONS
FOR NOVELL ODI CLIENT 32-BIT DRIVER
FOR WINDOWS 95 OR FOR DOS/WINDOWS 3.1x
HP J3239A DeskDirect EL-10 ISA Combo Adapter
Select the installation procedure for either Windows 95 or for
DOS with/without Windows 3.1x. Also see the HINTS AND TIPS and
SAMPLE CONFIGURATIONS following the two procedures.
===========================
INSTALLATION FOR WINDOWS 95
===========================
PREREQUISITES:
* NetWare Client 32 for Windows 95 archive file and any patch files
* Access to the Windows 95 CD or CAB files, since the installation
procedure will require this
*For a computer with an existing operating system (such as DOS,
Windows For WorkGroups, or Windows 3.x) being upgraded to Windows 95,
the upgrade must have been done BEFORE the adapter hardware was
installed or cabled.
IF Windows 95 has not yet been upgraded from an existing
operating system and the adapter hardware is already installed,
then remove the adapter and then upgrade to Windows 95, before
doing the procedure below.
IF the adapter hardware was installed and then Windows 95 was
upgraded from an existing operating system, then your
installation probably will not operate correctly. Stop this
procedure and go to the Troubleshooting note at the end of
this procedure.
IF Windows 95 is being installed on a computer with no pre-
existing operating system, then the adapter hardware may be
installed before Windows 95 is installed.
1. If the adapter is being installed for the first time when Client 32
is being added, proceed to step 2. If the adapter is already
installed on the Windows 95 system, skip to step 3.
2. When Windows 95 is restarting, it may display the message "Windows
has found new hardware and is installing software for it". Select
the option labeled "Do not install a driver (Windows will not prompt
you again)" then click on OK.
3. Run the SETUP.EXE program for Client 32. It is located in the
\PRODUCT\WIN95\IBM_ENU subdirectory of the Client 32 software.
4. On the NetWare Client 32 Installation screen, make sure the
"Upgrade NDIS driver to ODI, if available" box is checked if you
are replacing the NDIS driver with the ODI driver.
5. On the Recommended NetWare Client 32 properties screen, set the
appropriate settings for the version of NetWare you are using.
6. The Client 32 installation program will copy files. It may ask for
the source of the Windows 95 installation files. Click OK and then
enter the correct path to the files.
7. The Client 32 installation will finish. Restart the computer for
the changes to become effective.
Troubleshooting
---------------
IF You installed the adapter hardware before upgrading/installing
Windows 95, then remove all traces of the previous driver:
1. IF you are already running HPEISET, go to step 2 below.
IF you are not running HPEISET, then boot your computer in native
DOS without loading network drivers. The procedure is found
in your product manual for running HPEISET.
2. In DOS, change to the \INF subdirectory (a hidden subdirectory)
of the \WINDOWS directory on the hard drive:
cd \windows\inf
Delete the WINSETUP.INF file:
del winsetup.inf
3. Change to the "system" subdirectory of the "windows" directory:
cd \windows\system
Find the driver files:
dir hpeind.*
and then delete the one(s) you found:
del hpeind.sys
del hpeind.vxd
4. Restart your computer and enter Windows 95 normally.
5. From the Control Panel (press [Start] and select Settings and
then Control Panel) do the following:
Open "System". The System Properties dialog box appears.
Click on the Device Manager tab to open its dialog box.
Double-click on "Network Adapters".
Select the adapter product that you have installed.
Click on [Remove].
Click [OK] in the Confirm Device Removal dialog box.
Close Device Manager and Control Panel.
6. When you restart the computer, the "New Hardware Found" dialog
box should appear in Windows 95. Re-install a driver for the
adapter, according to the Windows 95 installation instructions
above.
=================================================
INSTALLATION FOR DOS WITH OR WITHOUT WINDOWS 3.1x
=================================================
1. From the Novell NetWare Client 32 software, run INSTALL.EXE
2. Select the NetWare Client 32 products you want to install on your
workstation from the list shown below. Note that "NetWare Client
32 for DOS" and "NetWare Client 32 for Windows" are usually
selected by default. Select others as needed.
[X] NetWare Client 32 for DOS
[X] NetWare Client 32 for Windows
[ ] NetWare TCP/IP protocol stack
[ ] NetWare IP (TCP/IP Required)
[ ] Desktop SNMP
[ ] HOSTMIB for SNMP (SNMP Required)
[ ] NetWare TSA for SMS
3. In the Customize Support for Windows menu, specify if you want
to use multiple country codes or if you want to set the shared
Windows path. The default for both of these is "No".
4. In the Select LAN Driver Type menu, select "32-bit LAN drivers".
5. Copy HPEIOD.LAN and HPEIOD.LDI onto a disk.
6. In the Novell installation process, select "USER SPECIFIED 32 BIT
DRIVER."
7. In the Insert the Driver Disk menu, insert the disk with the
HPEIOD.LAN and HPEIOD.LDI files, and then specify the path to
those files.
8. In the Installation Configuration Summary, verify that the default
settings for Client 32 are correct, or modify as necessary.
9. Modify AUTOEXEC.BAT and CONFIG.SYS [YES]
Client Directory: C:\NOVELL\CLIENT32
Windows Directory: C:\WINDOWS
LAN driver type: 32-bit LAN drivers
LAN driver: HP DeskDirect LAN Adapters
10. Novell NetWare will now copy the files to your workstation and
modify the configuration files to match your selected
configuration.
==============
Hints and Tips
==============
1. If you are using multiple frame types, you will get the following
message when you load the driver:
"Do you want to load another frame type for a previously loaded
board? Y/N "
The way to avoid this is to uniquely identify the card in
STARTNET.BAT as follows:
LOAD C:\NOVELL\CLIENT32\HPEIOD.LAN FRAME=ETHERNET_802.2
PORT=<PORT_NUM>
2. Check for a LASTDRIVE statement in the CONFIG.SYS file. You must
have "LASTDRIVE=Z" in CONFIG.SYS when using Client 32.
3. In the NET.CFG file under the NetWare DOS Requester section, verify
that the setting of "FIRST NETWORK DRIVE" is some letter before "Z".
.
=====================
SAMPLE CONFIGURATIONS
=====================
Below are sample files from a Novell NetWare Client 32 workstation
with an HP EL-10 adapter installed using the default installation:
CONFIG.SYS
----------
DEVICE=C:\WINDOWS\HIMEM.SYS
BUFFERS=30,0
FILES=60
LASTDRIVE=Z
AUTOEXEC.BAT
------------
prompt $P$G
path=C:\WINDOWS;c:\dos;C:\NOVELL\CLIENT32\
SET TEMP=C:\TEMP
@CALL C:\NOVELL\CLIENT32\STARTNET
STARTNET.BAT
------------
SET NWLANGUAGE=ENGLISH
C:\NOVELL\CLIENT32\NIOS.EXE
LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
LOAD C:\NOVELL\CLIENT32\CMSM.NLM
LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM
LOAD C:\NOVELL\CLIENT32\HPEIOD.LAN PORT=300 FRAME=ETHERNET_802.2
LOAD C:\NOVELL\CLIENT32\HPEIOD.LAN PORT=300 FRAME=EHTERNET_802.3
LOAD C:\NOVELL\CLIENT32\IPX.NLM
LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM
IF you are loading multiple frame types, you must UNIQUELY
IDENTIFY the adapter on the load lines. See the "Hints and Tips"
section above for detailed information.
NET.CFG
-------
NetWare DOS Requester
FIRST NETWORK DRIVE F
NETWARE PROTOCOL NDS BIND
Protocol IPX
IPX SOCKETS 40
<End of File>
.TOPIC:
Netware Server 4.11 Green River
SOFTWARE INSTALLATION INSTRUCTIONS
FOR NOVELL NETWARE VERSION 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 version 4.11 Server Driver
\NETWARE\HPEIOD.LDI Installation Information File for
Novell NetWare version 4.11 Server Driver
==============================
GENERAL INSTALLATION PROCEDURE
==============================
1. Install NetWare 4.11.
Complete the software installation procedures for the NetWare 4.11
server. See the Novell documentation for installing NetWare.
2. Update the server with files from the Support Disk for HP J3239A.
NetWare 4.11 provides two different ways to load a new LAN driver.
One method is to copy the new file(s) onto the server and then
either load the driver by typing on the command line or edit
AUTOEXEC.NCF to load the driver. The other method is (1) to load
INSTALL.NLM and use it to select and load your new driver and
(2) to edit AUTOEXEC.NCF.
Manual Loading of Server Driver
===============================
1. Start the server. Load and bind the HP server driver.
2. At the NetWare prompt (indicated by a colon), load the driver:
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.
3. 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.
Using INSTALL.NLM
=================
1. At the NetWare prompt, load the INSTALL.NLM program.
2. Select "LAN Driver Options (Configure/Load/...)" and [ENTER].
3. Press [INSERT] to specify other drivers to install.
4. Press [F3]. Enter the driver path, for example, "a:\netware"
5. Select the HPEIOD.LAN driver in your selection list to start the
driver loading and binding procedure.
==============
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.
NetWare 3.12 allows up to four different frame types, and the adapter
supports all four, as follows:
Ethernet_802.3
Ethernet_802.2
Ethernet_II
Ethernet_SNAP
.
==============
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.
-- <THE END> --
.TOPIC:
Netware Server Driver
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.
-- <THE END> --
.TOPIC:
NDIS Driver
SOFTWARE INSTALLATION INSTRUCTIONS
FOR OS/2 and DOS/WINDOWS CLIENT NDIS 2.01 DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The NDIS-2 drivers contained in the following directories are used
with 3Com 3+Open, Microsoft OS/2 LAN Manager OEM distribution release
1.x or 2.x, and other compatible OEM versions of LAN Manager.
\NDIS2\DOS\HPEIND.DOS
For DOS clients (and Microsoft Windows 3.x)
Use the "readme" instructions below.
\NDIS2\OS2\HPEIND.OS2
For OS/2 clients
Use the "readme" instructions below.
\MSLANMAN.DOS\HPEIND.DOS
For Microsoft LAN Manager DOS clients (and Microsoft Windows 3.x)
Use the LAN Manager "readme" instructions (\MSLANMAN.DOS\README.TXT).
\IBMLS\DOS\HPEIND.NIF
For Microsoft LAN Manager DOS clients (and Microsoft Windows 3.x)
Use the IBM LAN Server DOS "readme" instructions (\IBMLS\IBMDOS.TXT).
\IBMLS\OS2\HPEIND.NIF
For Microsoft LAN Manager OS/2 clients
Use the IBM LAN Server OS/2"readme" instructions (\IBMLS\IBMOS2.TXT).
(For other network operating systems, see the instructions and
directories for the specific NOS.)
These drivers conform to the Network Driver Interface Specification
(NDIS) defined by Microsoft and 3Com.
======================
VERIFYING INSTALLATION
======================
Under DOS, follow the hardware installation instruction to run the
SETUP utility on the support disk to verify adapter installation.
You cannot run SETUP in the OS/2 environment.
========================================
SAMPLE PROTOCOL.INI FILES AND PARAMETERS
========================================
[HPEIND_NIF] Default section of PROTOCOL.INI
drivername = HPEIND$
; irq = 3
; iobase = 0x300
End of sample
Several parameters are included in the HPEIND_NIF section of
PROTOCOL.INI. The "drivername" should always be changed.
You must also change the command lines "irg = 3" and "iobase = 0x300"
to match the adapter's hardware configuration only under the
following circumstances. In all other cases, they are automatically
detected by the driver.
IF more than one HP J3239A ISA adapter is installed, you must
specify the interrupt (irq = ") and I/O base address ("iobase = ")
for each adapter. Use the same settings from the hardware
configuration of each adapter; you can view the settings in
HPEISET.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing,
working adapter. Check its HW configuration again, and
if changed, reinstall the driver.
IF you have a non-Plug-and-Play computer, you must specify the
interrupt (irq = ") and I/O base address ("iobase = ") as
configured in the hardware configuration for the adapter as
listed by HPEISET. If you did not make a note of them when
configured, now use the "View Configuration" menu item in
HPEISET to note them.
Parameters:
irq Specifies the interrupt channel used by the adapter.
Acceptable values are 2, 3, 4, 5, 10, 11, 12 ,and 15.
iobase Specifies the hexadecimal I/O base address used by the adapter.
Acceptable values are 0x200, 0x220, 0x240, 0x260, 0x280, 0x2a0,
0x2c0, 0x2e0, 0x300, 0x320, 0x340, 0x360, 0x380, 0x3a0, 0x3c0,
0x3e0
MaxMultiCast 1-1000 Default 10
Maximum number of MultiCast Addresses: configures the size
of the MultiCast Address Table.
MaxRequests 6-64 Default 8
Maximum number of outstanding General Requests: configures
the size of the General Request Queue.
MaxTransmits 6-64 Default 12
Maximum number of outstanding TransmitChain commands:
configures the size of the TransmitChain Request Queue.
ReceiveChains 6-96 Default 12
Maximum number of outstanding ReceiveChain commands:
configures the size of the ReceiveChain Request Queue.
ReceiveBuffers 6-96 Default 12
Configures the number of the Receive buffers in the Receive
Buffer Pool.
TransmitBufSize 128-1514 Default 1514
Configures the size (in bytes) of buffers in the Transmit
Buffer Pool.
==================================
TROUBLESHOOTING AND ERROR MESSAGES
==================================
Verify any trouble by first running the diagnostics in the HPEISET
utility on the support disk. See the hardware installation
instructions.
Error Messages
--------------
"ERROR: Adapter card not found or I/O port error"
Possible causes:
1. The adapter is not installed correctly in its slot.
2. I/O port failure due to incompatibility between computer
and adapter
Solution: Run "Card Test" in SETUP to determine cause.
"HPEIND-Error-01: Incorrect Media Setting or Bad Transceiver"
Possible causes:
1. Transceiver failure.
2. Cable broken.
3. Loose cable connection.
Solution: Run "Card Test" in SETUP to determine cause.
-- <THE END> --
.TOPIC:
LAN Manager
SOFTWARE INSTALLATION INSTRUCTIONS
FOR MICROSOFT LAN MANAGER DOS CLIENT NDIS 2.01 DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The driver \MSLANMAN.DOS\DRIVERS\ETHERNET\HPEIND\HPEIND.DOS conforms
to the Network Driver Interface Specification (NDIS) defined by
Microsoft and 3Com.
=============================
DRIVER INSTALLATION PROCEDURE
=============================
Use one of the following procedures to match your LAN Manager version,
either 2.0, 2.1, or 2.2. Then refer to the sample configuration file
(following all three procedures) that also corresponds to your version;
some circumstances require you to change settings in those files.
LAN Manager version 2.0
-----------------------
1. Connect to the LAN Manager directory and enter the Setup utility.
2. Select "Import Network Drivers..." in the Action field.
Press [ENTER] to continue.
3. Insert the Support Disk for HP J3239A into the floppy drive.
Press [ENTER] to see the list of Imported Network Drivers.
4. Select the HP J3239A Ethernet Adapter driver, using [SPACE].
Press [ENTER] to confirm.
5. Follow the prompts displayed to complete the process,
until "Network Driver" is displayed.
6. Identify your network adapter if asked. For example, select
"HP J3239A Ethernet Card" for the HP EL-10 ISA adapter.
7. Select the "Add driver" and the "Add protocol" options.
Select "OK" to confirm. The computer's primary parameters should
display.
8. Follow the prompts displayed to complete the process.
9. Save all selections. Select "Save" in the "Action Menu".
10. Press [F3] to exit.
LAN Manager version 2.1
-----------------------
1. Connect to the LAN Manager directory and enter the LMSETUP utility.
The Microsoft LAN Manager Setup screen displays.
2. Select "Network Drivers..." in the "Configuration" field.
Press [ENTER] to confirm.
3. Select "Add New Configs" and press [ENTER] to display a list of
network adapter drivers.
4. Select "Other Driver" and press [ENTER].
5. Insert the Support Disk for HP J3239A into the floppy drive.
Enter the path name of the diskette. Select "OK" to continue.
6. Select the "HP J3239A Ethernet Adapter" driver.
Select "OK" to confirm.
7. Select an appropriate protocol, using [SPACE] to highlight it.
Select "OK" to confirm.
8. The Configuration Complete message should display.
9. Save the configuration; select "Save".
10. Press [F3] to exit.
LAN Manager version 2.2
-----------------------
1. Connect to the LAN Manager directory and enter the Setup utility.
The Microsoft LAN Manager Setup screen displays.
2. Select "Network Drivers..." in the "Configuration" field.
Press [ENTER] to confirm.
3. Select "Add New Config" and press [ENTER] to display a list of
network adapter drivers.
4. Select "Other Driver" and press [ENTER].
5. Insert the Support Disk for HP J3239A into the floppy drive.
Enter the path name of the diskette. Select "OK" to continue.
6. Select the "HP J3239A Ethernet Adapter" driver.
Select "OK" to confirm.
7. Select an appropriate protocol, using [SPACE] to highlight it.
Select "OK" to confirm. If you select the TCP/IP protocol, you
will be prompted for the IP address, the subnet mask, and the
default gateway (router). By default, the workstation number of
the NetBIOS session is set to 6.
See the Microsoft LAN Manager Installation Manual or see the online
help for more details
8. The Configuration Complete message should display.
9. Save the configuration; select "Save".
10. Press [F3] to exit.
All LAN Manager versions
------------------------
NOTE: If you are installing LAN Manager for the first time, you will
be prompted for the default user name and domain of the
workstation, as well as to answer, and for other Windows
environment and memory management information.
You must edit the "[HPEIND_NIF]" section of the PROTOCOL.INI file in
the following cases. See the example at the end of this file.
IF more than one HP J3239A ISA adapter is installed, you must
specify the interrupt (irq = ") and I/O base address
("iobase = ") for each adapter. Use the same settings from the
hardware configuration of each adapter; you can view the
settings in HPEISET.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing,
working adapter. Check its HW configuration again, and
if changed, reinstall the driver.
IF you have a non-Plug-and-Play computer, you must change the
interrupt setting (irq = ") and I/O base address setting
("iobase = ") to match the hardware configuration for the
adapter, as listed by HPEISET. If you did not make a note
of them when configured, now use the "View Configuration" menu
item in HPEISET to note them.
==========================
SAMPLE CONFIGURATION FILES
==========================
Use one of the following to match your LAN Manager version,
either 2.0, 2.1, or 2.2.
LAN Manager version 2.0
-----------------------
AUTOEXEC.BAT file:
@echo off
PROMPT $P$G
PATH=c:\PE2;C:\DOS50;C:\NC;
APPEND=C:\PE2;C:\DOS50;
REM ===== LANMAN 2.0 ==== DO NOT MODIFY BETWEEN THESE LINES
REM ===== LANMAN 2.0 ====
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND
NET START WORKSTATION
REM ===== LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES
REM ===== LANMAN 2.0 ====
CONFIG.SYS file:
LASTDRIVE=Z
BUFFERS = 35
FILES = 35
...
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\HPEIND\HPEIND.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.DOS
PROTOCOL.INI file:
[PROTOCOL MANAGER]
DRIVERNAME = PROTMAN$
[NETBEUI_XIF]
Drivername = netbeui$
BINDINGS = "HPEIND_NIF"
[HPEIND_NIF]
; PROTOCOL.INI for HP J3239A ethernet adapter
drivername = HPEIND$
; irq = 3 (See above note for "All LAN Manager
; iobase = 0x300 versions" for conditions requiring
; End of this sample file you to change these lines!)
LAN Manager version 2.1 or 2.2
-------------------------------
AUTOEXEC.BAT file:
@echo off
PROMPT $P$G
PATH=c:\PE2;C:\DOS50;C:\NC;
APPEND=C:\PE2;C:\DOS50;
@REM === LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
@REM === LANMAN 2.1 ===
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET START WORKSTATION
LOAD NETBEUI
@REM === LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES
@REM === LANMAN 2.1 ===
CONFIG.SYS file:
LASTDRIVE=Z
BUFFERS = 35
FILES = 35
.
.
.
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\HPEIND\HPEIND.DOS
PROTOCOL.INI file:
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
PRIORITY = NETBEUI
[NETBEUI_XIF]
Drivername = netbeui$
SESSIONS = 6
NCBS = 12
BINDINGS = "HPEIND_NIF"
LANABASE = 0
[HPEIND_NIF]
; PROTOCOL.INI for HP J3239A ethernet adapter
drivername = HPEIND$
; irq = 3 (See above note for "All LAN Manager
; iobase = 0x300 versions" for conditions requiring
; End of this sample file you to change these lines!)
-- <THE END> --
.TOPIC:
LAN Server
INSTALLATION INSTRUCTIONS FOR
16-BIT NDIS 2.01 DRIVER FOR IBM LAN SERVER DOS REQUESTER WITH
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The Network Driver Interface Specification (NDIS) 2.01 is a 16-bit driver
used by many DOS networking products to gain access to the LAN.
The HP NDIS 2.01 driver is self-configuring, which means the driver will
automatically locate and read the HP J3239A LAN card's configuration.
Only the DRIVERNAME parameter needs to be present under the [HPEIND]
section in the PROTOCOL.INI file.
The HP NDIS 2.01 drivers for IBM LAN Server DOS clients are located on
this Support Disk:
\IBMLS\DOS\HPEIND.DOS - 16-bit NDIS 2.01 for DOS
IBM LAN Server also requires unique NIF file and OEMSETUP.INF (for IBM LAN
Server 4.0 DOS Services Program only) located on this Support Disk:
\IBMLS\DOS\OEMSETUP.INF - Installation information file for LAN Server
4.0 DOS LAN Services
NOTE: Throughout these instructions, the term 'HP LAN Card' will be used to
refer to the HP J3239A ISA LAN Adapter.
To install Lan Server 4.0 DOS client with the HP LAN card and its NDIS 2.01
driver, follow the procedure under the section labeled "IBM LAN Server 4.0
DOS LAN Services Installation" below.
IBM LAN Server 4.0 DOS LAN Services Installation
================================================
1. Install the HP LAN Card, and optionally, run HPEISET.
Follow instructions in the 'Setting Up Your Card and LAN Connection'
chapter of the Installation Guide.
2. Copy HP NDIS 2.01 driver and an installation file to the hard disk.
Create a directory on the hard disk for the HP driver and installation
file. Insert the HP Support Disk into the floppy drive and enter the
following commands at the DOS prompt:
MKDIR C:\NDIS2
COPY A:\IBMLS\DOS\HPEIND.DOS C:\NDIS2
COPY A:\IBMLS\DOS\OEMSETUP.INF C:\NDIS2
3. Install IBM LAN Server 4.0 DOS Services program.
NOTE: If loading on MS-DOS 6.0 or later with multiple configuration
blocks, replace the CONFIG.SYS and AUTOEXEC.BAT files with a
single simple configuration. After the installation is complete,
incorporate the changes as another configuration in the original
multi-configuration CONFIG.SYS and AUTOEXEC.BAT files.
a) Insert "IBM LAN Server DOS LAN Services Disk 1" diskette into the
floppy disk drive and enter the following commands at the DOS prompt:
A:
INSTALL
b) When the installation program asks where the OEMSETUP.INF file
resides, answer with the path name where the HP driver files were
copied in step 2. In this example, it should be:
C:\NDIS2
c) Then, follow the instructions on the screen and refer to the IBM
LAN Server 4.0 DOS Services Installation Guide, when needed, to
complete the installation procedure.
d) Let the installation program automatically update the CONFIG.SYS
and AUTOEXEC.BAT files to add the necessary commands to invoke the
DOS LAN Services program every time the computer is booted.
4. Reboot the computer.
Reboot the computer to have the changes in the CONFIG.SYS and
AUTOEXEC.BAT take effect.
The IBM LAN Server 4.0 DOS LAN Services installation is complete.
Note: Please refer to the PROTOCOL.TXT file under \NDIS2 directory of
HP Support Disk for more information about "PROTOCOL.INI Parameter
Definitions".
------------------------------------------------------------------------------
INSTALLATION INSTRUCTIONS FOR
16-BIT NDIS 2.01 DRIVER FOR IBM OS/2 LAN SERVER WITH
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The Network Driver Interface Specification (NDIS) 2.01 is a 16-bit driver
used by many OS/2 networking products to gain access to the LAN.
The HP NDIS 2.01 driver is self-configuring, which means the driver will
automatically locate and read the HP J3239A LAN card's configuration.
Only the DRIVERNAME parameter needs to be present under the [HPEIND]
section in the PROTOCOL.INI file.
The HP NDIS 2.01 drivers for IBM LAN Server OS/2 servers and clients
are located on the LAN Adapter/16 Plus Support Disk:
\IBMLS\OS2\HPEIND.OS2 - 16-bit NDIS 2.01 for OS/2
IBM LAN Server also requires unique NIF file located on this Support Disk:
\IBMLS\OS2\HPEIND.NIF - NIF file for LAN Server 3.0 or 4.0 OS/2 Server
and Requester
The installation procedure described below is based on the IBM LAN Adapter
and Protocol Support program that comes with IBM LAN Server ver 3.0/4.0.
For the other versions of LAN Adapter and Protocol Support program, refer
to its "Installation Guide" for details.
NOTE: Throughout these instructions, the term 'HP LAN Card' will be used to
refer to the HP J3239A ISA LAN Adapter.
To install the HP LAN Card and its 16-bit NDIS 2.01 driver under IBM OS/2
as a server or client (requester), follow the instructions below:
1. Install the HP LAN Card, and optionally, run HPEISET.
Follow instructions in the 'Setting Up Your Card and LAN Connection'
chapter of the Installation Guide.
2. Boot IBM OS/2 and install the IBM LAPS program.
a) Make sure the IBM OS/2 operating system is properly installed and
functioning. Insert the IBM LAPS (LAN Adapter and Protocol Support)
disk into the floppy disk drive and type the following commands
from the OS/2 command prompt:
A:
LAPS
b) Select the "INSTALL" button from the IBM LAPS main dialog box.
c) Follow the directions to finish installing the IBM LAPS program
but do not exit the LAPS program.
3. Install, using IBM LAPS, the NDIS 2.01 driver into the system.
a) While still at the LAPS program main dialog in step 2, select the
"INSTALL" button again.
b) Insert the HP Support Disk into the floppy drive and enter the path
to the HP drivers at the prompt:
A:\IBMLS\OS2
and select the "OK" button.
c) The LAPS program will copy the appropriate files from the HP
Support Disk and return the to main dialog box.
4. Configure network drivers.
a) Select "Configure" from the LAPS program main dialog box.
b) Choose "Configure LAN Transport" button in the Configuration dialog
box and select "Continue".
c) Highlight the "HP J3239A Ethernet Adapter" line from the list in
the "Configure Workstation" dialog box and select "Add" to move the
line to the "Current Configuration" list.
d) Highlighting the desired protocols in the 'Protocols' list box and
select "Add" to move them to the 'Current Configuration' list box.
e) To optionally edit the driver's configuration, highlight the
"HP J3239A Ethernet Adapter" line in the "Current Configuration"
list and select "Edit".
NOTE: If more than one HP J3239A adapter is installed in the
computer, a location parameter (i.e. ADAPTERSLOT, ADAPTERTYPE,
or IOADDRESS) must be specified under each [HPEID_NIF] section
of the PROTOCOL.INI file.
f) Select 'OK' button if all the configuration has been completed.
g) Select "Exit" from the LAPS program main dialog box to indicate
configuration parameters are correct. Follow the instructions on
the screen or refer to the "LAPS Installation Guide" to complete
the installation process of LAPS. The LAPS program will update the
CONFIG.SYS file in the IBM OS/2 boot disk and then return to the
OS/2 command prompt.
5. Install IBM OS/2 Requester or the IBM LAN Server software.
Refer to the installation guide for IBM OS/2 LAN Server or OS/2
Requester and follow the instructions to complete the rest of
server/requester program installation.
6. Reboot the computer.
Reboot the computer into OS/2 to have the changes in the CONFIG.SYS
and STARTUP.CMD take effect.
The installation is complete.
Note: Please refer to the PROTOCOL.TXT file under \NDIS2 directory of
HP Support Disk for more information about "PROTOCOL.INI Parameter
Definitions".\
Note: IBM OS/2 2.X needs service pack installed
IBM OS/2 2.0, 2.1, and 2.11 needs a new version of the OS2LDR module
to allow drivers to register shared interrupts. This is documented
in IBM Authorized Analysis Report (APAR) PJ14230. Contact IBM to
order a service pack to update OS2LDR module.
OS/2 Warp (3.X) supports shared interrupts.
This patch is also required for OS/2 2.11 SMP.
-- <THE END> --
.TOPIC:
Windows for Workgroups 3.11
SOFTWARE INSTALLATION INSTRUCTIONS
FOR MICROSOFT WINDOWS FOR WORKGROUPS 3.11
NDIS & ODI DRIVERS
HP J3239A DeskDirect EL-10 ISA Combo Adapter
=========================================
INSTALLATION OF NDIS-2 AND NDIS-3 DRIVERS
=========================================
The drivers on the Support Disk for HP J3239A are:
\WFWG\HPEIND.386 NDIS 3.0 driver for enhanced mode
\WFWG\HPEIND.DOS NDIS 2.0 driver for real mode
1. Run Windows for WorkGroups.
2. Click the Network icon in the Main Program Group.
3. Click the Network Setup icon in the Network window.
4. Check the Drivers button.
IF it is hidden and can't be selected, then proceed with step 5.
IF it is visible and can be selected, skip to step 8.
5. Click the Networks button.
6. Select Install Microsoft Windows Network with no additional network.
7. Click the OK button.
8. Select the "Drivers" item from the Network Setup dialog box.
9. Select the "Add Adapters" item in the Option dialog box.
10. IF you are installing the HP J3239A adapter for the first time:
select "Unlisted or Updated Network Adapter".
IF you have installed the HP J3239A adapter before, just select
"HP J3239A ISA LAN driver" in the drivers list, and skip to
step 13.
11. Insert the support disk into the floppy drive, A for example,
and enter the pathname for the driver as follows:
a:\wfwg
Then the dialog box for the "HP J3239A ISA LAN driver" displays.
12. Use the Setup button to change to change the I/O base address and
the interrupt (IRQ) only under the following conditions:
IF more than one HP J3239A ISA adapter is installed, you must
specify the interrupt and I/O base address for one adapter in
Windows for WorkGroups at a time. Use the same settings from
the hardware configuration of each adapter; you can view the
settings in HPEISET.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing,
working adapter. Check its HW configuration again, and
if changed, reinstall the driver.
IF you have a non-Plug-and-Play computer, you must change the
interrupt and I/O base address to match the hardware
configuration for the adapter, as listed by HPEISET. If you
did not make a note of them when configured in HPEISET, now use
the "View Configuration" menu item in HPEISET to note them.
13. Use the Setup button to set driver type to one of the following.
Real mode and Enhanced mode NDIS
Enhanced mode NDIS
Real mode NDIS
(For ODI driver, use the ODI procedure below instead.)
14. Click [OK]. The Network Drivers dialog box displays.
Click [Close]. The Network Setup dialog box displays.
Click the [Continue] button.
15. IF the Microsoft Windows Network Names dialog box displays, enter
the names appropriate for your computer and network, and click
[OK]. Otherwise, go on to the next step.
16. You may be prompted to insert either or both of the following disks,
any number of times in any order. Whenever you insert the requested
disk, make sure the appropriate path name is entered as follows.
After inserting any Windows for WorkGroups disk, make sure the
path is the root of the floppy drive, for example:
a:\
After inserting the HP support disk, in drive "a" for example,
enter the path:
a:\wfwg
17. After the requested disks have been read, the Network Setup dialog
box says that the CONFIG.SYS, AUTOEXEC.BAT, PROTOCOL.INI, and
SYSTEM.INI files have been modified.
18. Remove the last disk from the floppy drive and click [OK]. The
driver is installed into the Windows for WorkGroups environment.
IF instead of the above result, you are notified of MS-DOS
Multiple Configuration Menus in the CONFIG.SYS file, then
you must make your own modifications to some of those files.
Check the sample files below and make desired modifications.
19. The Windows Setup dialog box says you must restart your computer.
IF Windows for WorkGroups has already been fully installed (that
click [Restart Computer].
IF you were just installing Windows for WorkGroups, click [Continue]
now. Then proceed with the Windows for Workgroup Setup program
until the setup procedure is completed.
Click [OK] or [Close] to complete any changes in the Network
Settings or adapter dialog box.
The installation and/or changes of network configuration will not
take effect until the computer is booted.
20. The first time you start Windows for WorkGroups after installation,
the Welcome to Windows For Workgroups dialog box should request a
password. If you do not want password protection, click [OK] and
then [No]. If you want password protection, enter a password and
click [OK].
SAMPLE CONFIGURATION FILES
--------------------------
AUTOEXEC.BAT file:
C:\WFW311\SMARTDRV.EXE
C:\WFW311\net start
PATH C:\WFW311;
SET TEMP=C:\WFW311\TEMP
CONFIG.SYS File
FILES=30
BUFFERS=30
LASTDRIVE=Z
DEVICE=C:\WFW311\HIMEM.SYS
DEVICE=C:\WFW311\IFSHLP.SYS
STACKS=9,256
PROTOCOL.INI File on Windows for Workgroups 3.11
[network.setup]
version=0x3110
netcard=ms$J3239A,1,MS$J3239A,2
transport=ms$netbeui,NETBEUI
lana0=ms$J3239A,1,ms$netbeui
[MS$J3239A]
DriverName=HPEIND$
INTERRUPT=3
IOBASE=0x300
[J3239A]
adapters=MS$J3239A
[NETBEUI]
BINDINGS=MS$J3239A
LANABASE=0
SESSIONS=10
NCBS=12
SYSTEM.INI
[386Enh]
netcard=HPEIND.386
==================================
INSTALLATION OF NOVELL ODI DRIVERS
==================================
The ODI driver on the Support Disk for HP J3239A is:
\DOS\HPEIND.COM
1. Run Windows for WorkGroups.
2. Click the Network icon in the Main Program Group.
3. Click the Network Setup icon in the Network window.
4. Check the Drivers button.
IF it is hidden and can't be selected, then proceed with step 5.
IF it is visible and can be selected, skip to step 8.
5. Click the Networks button.
6. Select Install Microsoft Windows Network with no additional network.
7. Click the OK button.
8. Select the "Drivers" item from the Network Setup dialog box.
9. Select the "Add Adapters" item in the Option dialog box.
10. IF you are installing the HP J3239A adapter for the first time:
select "Unlisted or Updated Network Adapter".
IF you have installed the HP J3239A adapter before, just select
"HP J3239A ISA LAN driver" in the drivers list, and skip to
step 13.
11. Insert the support disk into the floppy drive, A for example,
and enter the pathname for the driver as follows:
a:\wfwg
Then the dialog box for the "HP J3239A ISA LAN driver" displays.
12. Use the Setup button to change to change the I/O base address and
the interrupt (IRQ) only under the following conditions:
IF more than one HP J3239A ISA adapter is installed, you must
specify the interrupt and I/O base address for one adapter in
Windows for WorkGroups at a time. Use the same settings from
the hardware configuration of each adapter; you can view the
settings in HPEISET.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing,
working adapter. Check its HW configuration again, and
if changed, reinstall the driver.
IF you have a non-Plug-and-Play computer, you must change the
interrupt and I/O base address to match the hardware
configuration for the adapter, as listed by HPEISET. If you
did not make a note of them when configured in HPEISET, now use
the "View Configuration" menu item in HPEISET to note them.
13. Use the Setup button to set driver type to one of the following.
Real mode and Enhanced mode NDIS
Enhanced mode NDIS
Real mode NDIS
(For ODI driver, use the ODI procedure below instead.)
14. Click [OK]. The Network Drivers dialog box displays.
Click [Close]. The Network Setup dialog box displays.
Click the [Continue] button.
15. IF the Microsoft Windows Network Names dialog box displays, enter
the names appropriate for your computer and network, and click
[OK]. Otherwise, go on to the next step.
16. You may be prompted to insert either or both of the following disks,
any number of times in any order. Whenever you insert the requested
disk, make sure the appropriate path name is entered as follows.
After inserting any Windows for WorkGroups disk, make sure the
path is the root of the floppy drive, for example:
a:\
After inserting the HP support disk, in drive "a" for example,
enter the path:
a:\wfwg
17. After the requested disks have been read, the Network Setup dialog
box says that the CONFIG.SYS, AUTOEXEC.BAT, PROTOCOL.INI, and
SYSTEM.INI files have been modified.
18. Remove the last disk from the floppy drive and click [OK]. The
driver is installed into the Windows for WorkGroups environment.
IF instead of the above result, you are notified of MS-DOS
Multiple Configuration Menus in the CONFIG.SYS file, then
you must make your own modifications to some of those files.
Check the sample files below and make desired modifications.
19. The Windows Setup dialog box says you must restart your computer.
IF Windows for WorkGroups has already been fully installed (that
click [Restart Computer].
IF you were just installing Windows for WorkGroups, click [Continue]
now. Then proceed with the Windows for Workgroup Setup program
until the setup procedure is completed.
Click [OK] or [Close] to complete any changes in the Network
Settings or adapter dialog box.
The installation and/or changes of network configuration will not
take effect until the computer is booted.
20. The first time you start Windows for WorkGroups after installation,
the Welcome to Windows For Workgroups dialog box should request a
password. If you do not want password protection, click [OK] and
then [No]. If you want password protection, enter a password and
click [OK].
NOTE: To connect to a Novell server from within Windows for WorkGroups
make sure you are logged on to a NetWare server before starting
Windows. Also make sure that you have setup Windows for Workgroups
to use Novell NetWare.
SAMPLE CONFIGURATION FILES
--------------------------
AUTOEXEC.BAT File
SET TEMP=c:\windows\temp
PATH c:\windows;%PATH%
c:\windows\net start
lsl
HPEIOD
c:\windows\odihlp.exe
ipxodi
netx
CONFIG.SYS File
FILES=30
BUFFERS=30
LASTDRIVE=Z
DEVICE=C:\WFW311\HIMEM.SYS
DEVICE=C:\WFW311\IFSHLP.SYS
STACKS=9,256
PROTOCOL.INI File on Windows for Workgroups 3.11
[network.setup]
version=0x3110
netcard=J3239A,1,J3239A,4
transport=ms$netbeui,NETBEUI
lana0=J3239A,1,ms$netbeui
[net.cfg]
PATH=C:\WINDOWS\net.cfg
[J3239A]
[Link Driver HPEIOD]
[NETBEUI]
BINDINGS=HPEIOD
LANABASE=0
SESSIONS=10
NCBS=12
SYSTEM.INI
[boot]
shell=progman.exe
network.drv=wfwnet.drv
...
[386Enh]
network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386
netheapsize=20
netmisc=ndis.386,msodisup.386
transport=netbeui.386
InDOSPolling=FALSE
...
[Network]
winnet=wfwnet/00025100
multinet=nonet
FileSharing=No
PrintSharing=No
LogonDisconnected=yes
EnableSharing=no
UserName=HP
Workgroup=WORKGROUP
ComputerName=HP
Comment=HP
logonvalidated=no
[network drivers]
devdir=C:\WINDOWS
LoadRMDrivers=No
-- <THE END> --
.TOPIC:
Windows NT 3.5x
SOFTWARE INSTALLATION INSTRUCTIONS
FOR MICROSOFT WINDOWS NT NDIS DRIVERS
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The drivers named "HPEIND.*" conform to the NDIS-3 MiniPort Spec.
File description
----------------
\WINNT\HPEIND .SYS NDIS3 MiniPort driver
\ OEMSETNT.INF Windows NT drivers information file for HP
\WINNT\README .TXT Readme file
==============================================
Installing Driver on Microsoft Windows NT 3.5x
==============================================
1. Double-click the Network icon in the Control Panel.
2. In the Network Settings dialog box, click the Add Adapter button.
The Add Network Adapter dialog box displays.
3. When the Network Adapter Setup dialog box displays, scroll to the
end of the list and select "<Other> Requires disk from manufacturer".
4. Insert the Support Disk for HP J3239A into the floppy drive.
Enter that drive letter and the pathname "A:\" (using your
drive letter), and select OK.
5. When the Select OEM Option window displays with the line:
HP DeskDirect (J3239A) EL-10 ISA LAN Adapter
select that line indicating your adapter.
6. The HP J3239A ISA LAN Card Setup dialog box displays.
IF more than one HP J3239A ISA adapter is installed, you must
specify the "IRQ level" and "I/O port address" of the adapter
you are installing now. Use the same settings from the hardware
configuration of the adapter; you can view the settings in HPEISET.
Do not change them here.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing, working
adapter. Check its HW configuration again, and if changed,
reinstall the driver for NT.
IF you have a non-Plug-and-Play computer, you must specify its "IRQ
level" and "I/O port address" HW configuration, as listed by
HPEISET. If you did not make a note of them when configured, now
use the "View Configuration" menu item in HPEISET to note them.
Do not change them in this NT installation.
IF you have more than one hardware bus, you will be asked for the
bus location of the adapter. Select ISA or EISA, whichever slot
contains the adapter and confirm.
7. The HPEIND.SYS driver is copied from the \WINNT directory on the
support disk to "C:\WINNT\SYSTEM32\DRIVERS\". The "OEMSETNT.INF"
file is copied from the root on the support disk to
"C:\WINNT\SYSTEM32\" and renamed.
You can see "[0x]HP J3239A ISA LAN Adapter" in the Installed Adapter
Cards menu and can see the HP J3239A ISA LAN Adapter Driver in the
Installed Network Software menu.
8. In the Network Setting dialog box, choose the Bindings button,
to bind the adapter to transport drivers.
IF the TCP/IP protocol is installed, the TCP/IP configuration will
start up. Complete its configuration.
9. Select the Restart button and use your network service.
==============================================
Diagnosing Problems by Examining the Event Log
==============================================
If the driver fails to start or appears to be working incorrectly,
examine the Event Log for any driver diagnostic messages.
1. Start the Event Viewer applet in the Administrative Tools group in
Program Manager.
2. Search the Event Log Source column for any entries named "Hpeind".
Double-click the entry to examine the Event Detail dialog box.
In the upper half of the box is a short generic description of the
error. In the lower half of the box is a hexadecimal and ASCII dump
of error data.
3. Scroll through the ASCII error data for any readable strings.
IF a readable string is present, it will describe the problem found
in more detail.
IF no readable string is present, this typically indicates that the
driver failed early in the process of loading -- usually due to
a resource conflict, such as in the I/O port address.
-- <THE END> --
.TOPIC:
Windows NT 4.0
SOFTWARE INSTALLATION INSTRUCTIONS
FOR MICROSOFT WINDOWS NT NDIS DRIVERS
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The drivers named "HPEIND.*" conform to the NDIS-3 MiniPort Spec.
File description
----------------
\WINNT\HPEIND .SYS NDIS3 MiniPort driver
\ OEMSETNT.INF Windows NT drivers information file for HP
\WINNT\README .TXT Readme file
=============================================
Installing Driver on Microsoft Windows NT 4.x
=============================================
1. Double-click the Network icon in the Control Panel.
2. In the Network dialog box, select the Adapter tab and the "Add"
button. The Select Network Adapter dialog box displays.
3. Select the Have Disk button.
4. Insert the Support Disk for HP J3239A into the floppy drive.
Enter that drive letter and the pathname "A:\" (using your
drive letter), and select OK.
5. When the Select OEM Option window displays with the line:
HP DeskDirect (J3239A) EL-10 ISA LAN Adapter
select that line indicating your adapter.
6. The HP J3239A ISA LAN Card Setup dialog box displays.
IF more than one HP J3239A ISA adapter is installed, you must
specify the "IRQ level" and "I/O port address" of the adapter
you are installing now. Use the same settings from the hardware
configuration of the adapter; you can view the settings in HPEISET.
Do not change them here.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing, working
adapter. Check its HW configuration again, and if changed,
reinstall the driver for NT.
IF you have a non-Plug-and-Play computer, you must specify its "IRQ
level" and "I/O port address" HW configuration, as listed by
HPEISET. If you did not make a note of them when configured, now
use the "View Configuration" menu item in HPEISET to note them.
Do not change them in this NT installation.
IF you have more than one hardware bus, you will be asked for the
bus location of the adapter. Select ISA or EISA and confirm.
7. The HPEIND.SYS driver is copied from the \WINNT directory on the
support disk to "C:\WINNT\SYSTEM32\DRIVERS\". The "OEMSETNT.INF"
file is copied from the root on the support disk to
"C:\WINNT\SYSTEM32\" and renamed.
You can see "[0x]HP J3239A ISA LAN Adapter" in the Installed Adapter
Cards menu and can see the HP J3239A ISA LAN Adapter Driver in the
Installed Network Software menu.
8. In the Network dialog box, choose the Close button, and the adapter
will be bound to transport drivers.
IF the TCP/IP protocol is installed, the TCP/IP configuration will
start up. Complete its configuration.
9. Restart the computer and use your network service.
==============================================
Diagnosing Problems by Examining the Event Log
==============================================
If the driver fails to start or appears to be working incorrectly,
examine the Event Log for any driver diagnostic messages.
1. Start the Event Viewer applet in the Administrative Tools group in
Program Manager.
2. Search the Event Log Source column for any entries named "Hpeind".
Double-click the entry to examine the Event Detail dialog box.
In the upper half of the box is a short generic description of the
error. In the lower half of the box is a hexadecimal and ASCII dump
of error data.
3. Scroll through the ASCII error data for any readable strings.
IF a readable string is present, it will describe the problem found
in more detail.
IF no readable string is present, this typically indicates that the
driver failed early in the process of loading -- usually due to
a resource conflict, such as in the I/O port address.
-- <THE END> --
.TOPIC:
Windows 95
SOFTWARE INSTALLATION INSTRUCTIONS
FOR MICROSOFT WINDOWS 95 NDIS DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The Windows 95 drivers information file for HP is "WINSETUP.INF"
in the root directory of the Support Disk for HP J3239A.
PREREQUISITE: Before doing this procedure, Windows 95 must have been
installed BEFORE the adapter hardware was installed or cabled.
IF Windows 95 has not yet been installed or upgraded and the adapter
hardware is already installed, then remove the adapter and then
install or upgrade Windows 95, before doing the procedure below.
IF the adapter hardware was installed and then Windows 95 was
installed and upgraded, then your installation probably will not
operate correctly. Stop this procedure and go to the "xxx"
procedure in the Troubleshooting section below.
=============================================
INSTALLATION ON AN ISA PLUG-AND-PLAY COMPUTER
=============================================
1. When you start Windows 95, the adapter just installed is automatically
detected, and the New Hardware Found dialog box displays.
IF New Hardware Found does NOT display, stop this procedure and go to
the "Recovering from Missing New Hardware Found Dialog Box" in the
Trouble-shooting section below.
2. Select "Driver form disk provided by hardware manufacturer" and click
OK. The Install From Disk dialog box displays.
3. Insert the Support Disk for HP J3239A into the floppy drive. Specify
that drive's path, for example, "a:\", and click OK.
4. Respond to prompts for disks by inserting each one and entering the
path. For "Windows 95 Disk n" you will insert either the Windows 95
CD-ROM with path "d:\win95" (or your CD-ROM drive letter in place of
"d") or the floppy disk number "n" with path "a:\" (or your floppy
drive letter). For "Manufacturer's disk" insert the support disk.
5. After completing the device and driver setup, remove any disk still
in the drive a and restart your computer.
6. You may need to respond to the "Enter Network password" dialog box
before you can proceed.
==========================================
INSTALLATION ON NON-PLUG-AND-PLAY COMPUTER
==========================================
1. From the Control Panel, run the Add New Hardware wizard.
2. Click [Next >]. Select Yes for detection and click [Next >].
3. Click [Next >] and wait for the device to be found. Then click
[Next >] for manual installation.
4. For "Hardware types", click "Network adapters" and [Next >].
5. In the Select Device dialog box, click [Have Disk], and the
Install From Disk dialog box appears.
6. Insert the support disk into the floppy drive. Enter the path:
a:\
(This installs the default driver.)
7. In the Select Device dialog box, click the product name of the
specific LAN adapter you have installed [OK]. Click [Next >].
8. Click [Finish]. Close the Control Panel.
9. Remove the support disk from the floppy drive and restart your
computer.
===============
TROUBLESHOOTING
===============
CASE 1: You installed the adapter hardware before upgrading/installing
Windows 95:
THEN do "REMOVING ALL TRACES OF A PREVIOUS DRIVER" procedure
below. Then follow the normal procedure to install the
software and driver for Windows 95.
CASE 2: You expected the "New Hardware Found" dialog box, but it does
not appear. That is, you have just installed the adapter
hardware into an ISA Plug-and-Play computer and returned to
Windows, but Windows does not give that dialog box.
THEN follow one of the three possibilities below:
IF you are installing the adapter into a computer that is NOT
ISA Plug-and-Play, then this is normal. Follow the
procedure for "INSTALLATION ON NON-PLUG-AND-PLAY COMPUTER"
above.
IF "New Hardware Found" did appear once but you ignored it:
THEN see "Recovering from missing new..." below.
IF you installed the adapter hardware before
upgrading/installing Windows 95:
THEN do "Removing all traces of a previous driver" procedure
below. Then follow the procedure to install the
software and driver for Windows 95.
--------------------------------------------------
Removing all traces of a previous driver procedure
--------------------------------------------------
1. IF you are already running HPEISET, go to step 2 below.
IF you are not running HPEISET, then boot your computer in native
DOS without loading network [software or?] drivers. The procedure
is found in your product manual for running HPEISET.
2. In DOS, change to the \INF subdirectory (a hidden subdirectory) of
the \WINDOWS directory on the hard drive:
cd \windows\inf
Delete the WINSETUP.INF file:
del winsetup.inf
3. Change to the "system" subdirectory of the "windows" directory:
cd \windows\system
Find the driver files:
dir hpeind.*
and then delete the one(s) you found:
del hpeind.sys
del hpeind.vxd
4. Restart your computer and enter Windows 95 normally.
5. From the Control Panel (press [Start] and select Settings and then
Control Panel) do the following:
Open "System". The System Properties dialog box appears.
Click on the Device Manager tab to open its dialog box.
Double-click on "Network Adapters".
Select the adapter product that you have installed.
Click on [Remove].
Click [OK] in the Confirm Device Removal dialog box.
Close Device Manager and Control Panel.
6. When you restart the computer, the "New Hardware Found" dialog box
should appear in Windows 95. Re-install a driver for the adapter,
according to the Windows 95 installation instructions above.
-------------------------------------------------------
Recovering from missing "New Hardware Found" dialog box
-------------------------------------------------------
Possible Cause: Ignoring the first instance of the "New Hardware
Found" dialog box when restarting the computer after installing adapter
hardware. This happens when you select the response "Do not install a
driver (Windows will not prompt you again)".
Solution: Follow the procedure for "INSTALLATION ON
NON-PLUG-AND-PLAY COMPUTER" above.
-- <THE END> --
.TOPIC:
LANtastic
SOFTWARE INSTALLATION INSTRUCTIONS
FOR ARTISOFT LANTASTIC VERSIONS 5.0 & 6.0 NDIS 2.01 DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
==============================
INSTALLATION FOR LANTASTIC 5.0
==============================
You can use HP's NDIS driver \NDIS2\DOS\HPEIND.DOS in place of
AEXNDIS.DOS, the NDIS driver offered by ARTISOFT.
Sample configuration files for 5.0
----------------------------------
AUTOEXEC.BAT / STARTNET.BAT
C:\LANTASTI\AI-NDIS BIND_TO=HPEIND_NIF
C:\LANTASTI\AILANBIO
C:\LANTASTI\REDIR MachineName
CONFIG.SYS
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\HPEIND.DOS ---> NDIS driver for HP J3239A
PROTOCOL.INI
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
[HPEIND_NIF]
DRIVERNAME = HPEIND$
IF you are using PROTMAN.DOS V1.x, you must use the NO_BIND option on
the AI-NDIS command line in STARTNET.BAT, and you must run
NETBIND.EXE V1.x before AILANBIO.EXE.
==============================
INSTALLATION FOR LANTASTIC 6.0
==============================
Two alternative methods:
A. Using the LANtastic 6.0 Install program
------------------------------------------
NOTE: This method is required if LANtastic 6.0 has not yet been
installed.
1. Start the LANtastic 6.0 Install program.
2. Select "NDIS support for network adapters".
3. Insert the Support Disk for HP J3239A and enter the path
"A:\LANTASTI" (for floppy drive A). The Install program will search
for HPEIND.DOS and PROTOCOL.INI (which are in \NDIS2\DOS and
\LANTASTI\, respectively) and copy them files to the target
directory.
B. Using manual installation
----------------------------
NOTE: This method can be used if LANtastic 6.0 has been already
installed.
1. Replace the old NDIS-2 driver (xxx.DOS) with the NDIS-2 driver for
HP J3239A -- \NDIS2\DOS\HPEIND.DOS
2. Edit CONFIG.SYS, AUTOEXEC.BAT, and PROTOCOL.INI as indicated below.
AUTOEXEC.BAT / STARTNET.BAT
@echo ===== Begin LANtastic configuration =====
SET LAN_CFG=C:\LANTASTI
PATH C:\LANTASTI;%PATH%
SET LAN_DIR=C:\LANTASTI.NET
rem Please obtain the NETBEUI.EXE program from Microsoft
NETBEUI
AI-NDIS BIND_TO=HPEIND_NIF
AILANBIO @STARTNET.CFG
REDIR THOMAS @STARTNET.CFG
SERVER C:\LANTASTI.NET @STARTNET.CFG
NET LOGIN \\THOMAS
@echo ===== End LANtastic configuration =====
CONFIG.SYS
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\HPEIND.DOS ---> NDIS driver for HP J3239A
PROTOCOL.INI
[PROTMAN]
Priority=NETBEUI
DriverName = PROTMAN$
Dynamic = Yes
[NETBEUI_XIF]
DriverName = netbeui$
Sessions = 6
NCBS = 12
Bindings = HPEIND_NIF
LANABASE = 1
[HPEIND_NIF]
DriverName = HPEIND$
-- <THE END> --
.TOPIC:
Banyan VINES
SOFTWARE INSTALLATION INSTRUCTIONS
FOR BANYAN VINES CLIENT NDIS 2.01 DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The driver used for Banyan VINES is NDIS2\HPEIND.DOS, which conforms
to the Network Driver Interface Specification (NDIS) defined by
Microsoft and 3Com.
======================
INSTALLATION PROCEDURE
======================
1. Run the PCCONFIG utility. The "Configuring A PC for the Network"
window will display.
2. Select "1 - Network Card Setting," and press [ENTER] to continue.
You will be prompted for the hardware configuration options.
3. Select the "NDIS Ethernet" option and press [ENTER].
4. Enter the interrupt (IRQ) setting, as listed by HPEISET, when
prompted. Enter the text "J3239A" for the "PROTOCOL bindings ="
Statement.
IF you did not make a note of the interrupt setting when
configured, now use the "View Configuration" menu item in
HPEISET to note it. Do not change the setting in this VINES
installation.
5. Press [F10] when process is complete, or press [ESC] to exit
the screen
.
6. Select "2 - Login Environment Settings," and press [ENTER].
7. Select "1 - Select Default Communications Driver," and press
[ENTER].
8. Select "NDIS Ethernet," and press [ESC] to exit this menu.
9. Press [F10] to save all settings.
10. Modify the CONFIG.SYS and the PROTOCOL.INI files as in the
following examples.
==========================
Sample Configuration Files
==========================
CONFIG.SYS file:
device=c:\banyan\protman.dos/i:c:\banyan
device=c:\banyan\HPEIND.dos
PROTOCOL.INI file:
[protocol manager]
DriverName = PROTMAN$
[J3239A]
DriverName = HPEIND$
-- <THE END> --
.TOPIC:
SUN PC-NFS
SOFTWARE INSTALLATION INSTRUCTIONS
FOR SUN PC-NFS NDIS 2.01 DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
The driver \NDIS2\DOS\HPEIND.DOS conforms to the Network Driver
Interface Specification (NDIS) defined by Microsoft and 3Com.
======================
INSTALLATION PROCEDURE
======================
1. Edit the CONFIG.SYS file to include the following
command line, and reboot the computer:
Device=c:\dos\ansi.sys
2. In DOS, insert the PC-NFS Installation diskette into the floppy disk
drive. Run the INSTALL utility on the diskette, and the PC-NFS
installation screen displays.
3. Follow screen prompts to configure your screen display. For example,
press [M] for a monochrome display, or press [C] for a color display,
or press [ESC] to cancel the installation.
4. When the "Install the Basic PC-NFS files" screen displays, select
"Install Full PC-NFS" from the list.
5. Specify the target PC-NFS installation directory, by entering the
appropriate path in the field provided, or example, C:\NFS.
Then press [ENTER] to continue.
6. Respond to each prompt with the selections appropriate to your system.
7. When you reach the prompt "Configure an Ethernet network connection",
select "Ethernet". Press [ENTER] to confirm.
8. Choose the network adapter by entering the driver name "HPEIND.DOS".
Select "NDIS" from the list. Then press [ENTER] to confirm.
9. Continue to follow the prompts. You will be prompted for PC-NFS
distribution diskettes.
10. When prompted to update AUTOEXEC.BAT and CONFIG.SYS, press [Y].
11. You will be notified when the installation is complete:
"PC-NFS installation is complete."
12. Two subdirectories will be created on the destination drive,
namely, \LANMAN and \NFS.
13. Create the NETWORK.BAT, DRIVES,BAT and HOSTS files. Specify the
PC name, IP address, server name, and server IP address in the files.
See Sample Configuration Files below.
14. Copy the NETWORK.BAT, DRIVES.BAT and HOSTS files into the \NFS
directory on your server.
15. Copy the file \NDIS2\DOS\ HPEIND.DOS from the Support Disk for
HP J3239A to the newly created subdirectory (\LANMAN) on your
destination drive.
16. In the CONFIG.SYS file, add the following command line preceding
the NFS_NDIS driver specification:
DEVICE=C:\LANMAN\HPEIND.DOS
17. Make the following changes in the PROTOCOL.INI file in the \LANMAN
directory:
A. Replace the section name [your-mac-module] with "[J3239A]"
B. Replace the command line "drivername = YOURMAC$" with
"drivername = HPEIND$"
C. You must edit the command lines "irg = 3" and "iobase = 0x300"
to match the adapter's hardware configuration only under the
following circumstances:
IF more than one HP J3239A ISA adapter is installed, you must
specify the interrupt (irq = ") and I/O base address
("iobase = ") for each adapter. Use the same settings from
the hardware configuration of each adapter; you can view the
settings in HPEISET.
NOTE: The ISA Plug-and-Play HW configuration of an additional
adapter can change the configuration of an existing,
working adapter. Check its HW configuration again, and
if changed, reinstall the driver.
IF you have a non-Plug-and-Play computer, you must specify the
interrupt (irq = ") and I/O base address ("iobase = ") in
the hardware configuratin for the adapter, as listed by
HPEISET. If you did not make a note of them when configured,
now use the "View Configuration" menu item in HPEISET to note
them.
D. Replace the command line "bindings = YOUR-MAC-MODULE" with
"bindings = HPEIND$"
18. Reboot your computer. Start the application needed. For example:
Execute NFSCONF.EXE to configure mounting a virtual drive "E:".
Execute TELNET.EXE to do terminal emulation.
==========================
SAMPLE CONFIGURATION FILES
==========================
AUTOEXEC.BAT file:
...
SET TZ=PST8
SET path=C:\;C:\NFS;C:\LANMAN
SET NFSDRIVE=D
REM Add the following line to bind NDIS driver
C:lanman\netbind
PRT *
REM Execute application you need, such as NFSRUN
NFSRUN
CONFIG.SYS file:
shell=c:\command.com /P /E:526
dos=high, UMB
rem ----pcnfs install
Device=c:\dos\ansi.sys
DEVICE=C:\NFS\PCNFS.SYS /m
DEVICE=C:\NFS\SOCKDRV.SYS
REM Specify PROTOCOL.INI directory
DEVICE=C:\LANMAN\PROTMAN.SYS /i:C:\LANMAN
REM HP NDIS driver name
device=C:\LANMAN\HPEIND.DOS
DEVICE=C:\LANMAN\NFS-NDIS.SYS
FILES=50
BUFFERS=50
LASTDRIVE=v
STACKS=9,256
\LANMAN PROTOCOL.INI file:
[protocol manager]
drivername = PROTMAN$
[HPEIND]
drivername = HPEIND$
irq = 3
iobase = 0x300
[NFS-NDIS]
drivername = NFSLINK1
bindings = HPEIND
NETWORK.BAT file:
REM stc* is a sample PC-NFS workstation name
REM HP3 is a sample PC-NFS server address
NET START RDR stc*
NET PCNFSD HP3
NET NAME stc*
DRIVES.BAT file:
REM specify connections to remote directory
NET USE l:HP3:/usr2/down
NET USE k:HP3:/mnt
HOSTS file:
REM specify gateway address
192.72.24.201 <gateway # updated>
REM specify workstation's IP address
192.72.24.102 stc
REM specify server's IP address
192.72.24.202 HP3
-- <THE END> --
.TOPIC:
FTP PC/TCP
SOFTWARE INSTALLATION INSTRUCTIONS
FOR FTP PC/TCP VERSION 2.x NDIS 2.01 DRIVER
HP J3239A DeskDirect EL-10 ISA Combo Adapter
======================
INSTALLATION PROCEDURE
======================
1. Install FTP PC/TCP for DOS/Windows software. Follow the
installation manual provided with the FTP PC/TCP. The remainder of
these instructions assume it is installed in C:\FTP.
Select the "DIX Ethernet" driver (ETHDRV) as the PC/TCP kernel.
2. Insert the Support Disk for H3239A into the floppy drive, and copy
the NDIS-2 driver to the directory where the FTP PC/TCP software is
installed. For example:
copy a:\ndis2\dos\hpeind.dos c:\ftp
3. Copy the PC/TCP NDIS support files from the FTP DOS/Windows diskette
to the directory where the FTP PC/TCP software is installed. For
example:
copy a:\protman.dos c:\ftp
copy a:\protman.exe c:\ftp
copy a:\netbind.com c:\ftp
Make sure the PC/TCP packet driver to NDIS driver converter module
DIS_PKT.GUP is also in the same directory (C:\FTP).
4. Update configuration files. For example:
AUTOEXEC.BAT file:
...
SET PCTCP=C:\FTP\PCTCP.INI
C:\FTP\NETBIND
C:\FTP\ETHDRV
...
CONFIG.SYS file:
DEVICE = C:\FTP\PROTMAN.DOS /I:C:\FTP
DEVICE = C:\FTP\HPEIND.DOS
DEVICE = C:\FTP\DIS_PKT.DOS
PROTOCOL.INI file:
[PROTMAN]
DRIVERNAME = PROTMAN$
[PKTDRV]
drivername = PKTDRV$
intvec = 0x60
bindings = HPEIND_NIF <--- Add this line
[HPEIND_NIF]
DRIVERNAME = HPEIND$
5. Reboot the computer.
The FTP PC/TCP software and changes made to PROTOCOL.INI,
CONFIG.SYS and AUTOEXEC.BAT will only then take effect.
-- <THE END> --
.TOPIC:
SCO UNIX
INSTRUCTIONS FOR OBTAINING SCO DRIVERS FOR
HP J3239A DESKDIRECT EL-10 ISA LAN ADAPTER
The HP J3239A DeskDirect EL-10 ISA LAN adapter drivers for Santa
Cruz Operation (SCO) operating systems are available for download from
Hewlett-Packard.
For SCO Open Server 5, the MAC Driver Interface (MDI) driver will be
available from SCO in AHS after June 1, 1997. Hewlett Packard will
provide this driver on HP Electronic Support Services for LAN adapters
until the driver is included in the released SCO Open Server 5 at which
time it will be removed from HP's services.
For SCO Open Server 3, Open Desktop 3, or UNIX 3.2v4.X, the Link Level
Interface Driver (LLI) is available to download from Hewlett-Packard.
Hewlett Packard will provide this driver on HP Electronic Support Services
for LAN adapters until the driver is included on SCO Electronic Support\
Services, at which time it will be removed from HP's services.
This document contains information on the following topics:
1. Downloading the MDI Drivers from SCO (To be included in AHS
June 1997).
2. Downloading the LLI Drivers from SCO
3. Downloading the MDI or LLI Drivers from HP (Available until they
are on SCO's Electronic Services).
=======================================
1. Downloading the MDI Drivers from SCO
=======================================
NOTE: At the time of writing this documentation the MDI driver was
not available at SCO. It should be available from SCO at
their ftp site as a vendor supported driver early 1997 at
ftp://ftp.sco.com/VCD, and as part of the AHS supplement June
1997.
To download the supplement with ftp via World Wide Web:
For AHS, open the URL: ftp://www.sco.com/AHS/5.0/sco
For Release Supplements, open the URL:
ftp://www.sco.com/Supplements
To download the supplement via an anonymous ftp connection:
ftp to ftp.sco.com
Login name: ftp
Password: your email address
AHS Directory: AHS/5.0/sco
Release Supplement Directory: Supplements
NOTE: The wu-ftp software used on ftp.sco.com requires that two
kinds of DNS resource records for your site have been
propagated to SCO's nameserver: a Name-to-address mapping and
a PTR Address-to-name mapping.
The lack of a propagated PTR record for your site is the most
common cause of problems with anonymous ftp to ftp.sco.com.
PTR records are also known as "pointer" records or "reverse"
records. Please contact your Internet provider for more
information.
To download the supplement via an anonymous UUCP connection:
AHS Directory: /usr/spool/uucppublic/AHS/5.0/sco
Release Supplement Directory: /usr/spool/uucppublic/Supplements
For USA, Canada, Pacific Rim, Asia and Latin America customers:
Machine name: sosco
Login name: uusls (fourth character is the letter "l")
No password
List of modems available for UUCP transfer from sosco.sco.com:
V32, V32bis 5@ +408 425-3502
Telebit Trailblazer +408 429-1786
For Europe/Middle East/Africa customers there is a system located
at SCO EMEA (London):
Machine name: scolon
Login name: uusls
Password: bbsuucp
List of modems available for UUCP transfer from
scolon.sco.com:
Dowty Trailblazer +44 (0) 1923 210911
V32 +44 (0) 1923 222681
=======================================
2. Downloading the LLI Drivers from SCO
=======================================
NOTE: At the time of writing this documentation the LLI driver was
not available at SCO. It should be available from SCO at
their ftp site as a vendor supported driver early 1997 at
ftp://ftp.sco.com/VCD.
=============================================
3. Downloading the MDI or LLI Drivers from HP
=============================================
The latest SCO Drivers for the HP J3239A DeskDirect EL-10 ISA LAN
Adapters are available from Hewlett Packard Bulletin Board Service,
Hewlett Packard Internet, and CompuServe.
World Wide Web Site
===================
URL: http://www.hp.com/go/network_city
Click on "Support" for LAN adapter problem-solving information,
or for a path to the software download site that supplies LAN
adapter drivers.
HP BBS
======
The Hewlett-Packard Bulletin Board Library Service is available
24 hours per day, 7 days-per-week.
Phone Number - (208) 344-1691
Baud Rates supported | Parity | Data Bits | Stop Bits
---------------------------------------------------------------
300,1200,2400,4800,9600,14400 | N | 8 | 1
To obtain the updates:
1. Connect to HP BBS and register:
Follow the BBS instructions to add your name to the BBS users
list.
2. At the Main System menu, select "L" for "Libraries".
The Main System Menu (TOP) appears as follows:
A Account Display/Edit
I Information Center
L Libraries
E E-Mail Feedback
X Exit the System (logoff)
3. At the Library menu, select "S" for "Select a Library".
The Library Area Menu appears as follows:
F Find files
D Download a file
S Select a Library
L Download lists of files
P Set your preferences
X Exit File Libraries
4. List all the libraries by entering a ?
Choose the index for the library "HP Network Products Library"
5. Download PC LAN Adapter files
Select "D" for "Download a file" option.
See the above list for the Support Disk Archive file name
for your adapter.
Choose the transfer type.
Initiate the download with your modem program.
6. You have completed the steps necessary to download a file from
the HP BBS.
HP FTP Library Service
======================
Hewlett-Packard Internet services are available 24 hours-per-day,
7 days per week.
Internet FTP Archive - ftp.hp.com
Name - anonymous
Password - Send User Identification
Here is an example of how to obtain HP adapter driver updates using
FTP and the Internet FTP archive.
1. Run FTP and when the "ftp>" prompt appears, open a connection to
the HP Internet archive:
ftp> open ftp.hp.com
2. Log in as user "anonymous". A password is not required but for
tracking purposes enter your internet mail address:
User: anonymous
Password: YourName@YourComputer
3. Change directory to /pub/networking/software
where all the HP adapter support disk archive files are located:
ftp> cd /pub/networking/software
4. Set file transfer mode to binary:
ftp> binary
5. List the HP PC LAN Support Disk archive files available:
ftp> dir
6. Use the "get filename" command to download the file to your local
computer.
7. Quit the FTP session.
ftp> quit
8. You have completed the steps necessary to download a file from
the HP Internet FTP archive.
Updates from CompuServe
=======================
1. After logging in, go to the "hp" service.
2. Select "HP systems, Disks, Tapes, etc."
3. Select "Networking Products" library.
4. Download the filename; then quit.
-- <THE END> --
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.