NETWORK DRIVER ERROR MESSAGES FOR NDIS DRIVERS

This file contains a list of the error messages you may see from
the NDIS drivers for the HP LAN Adapter/16 Plus cards. 

Included is the text of the message, its meaning, and suggested actions
for you to follow to resolve the problem.

===========================================================================
Message:
HP LAN ADAPTER/16+: Unexpected Protocol Manager error detected.

Meaning:
This message is displayed when an error other than 'file not found' is
returned on the OPEN call to the NDIS Protocol Manager (an NDIS software
module that supplies configuration data and supervises the network software
initialization process).  The driver 'opens' the Protocol Manager in order
to query it for configuration information.  The conditions which would
result in this error are unknown.  Some condition which is impairing the
networking initialization process has occurred.

Action:
It is unlikely that this error will ever be encountered.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: Protocol Manager not installed.

Meaning:
This message is displayed when the error 'file not found' is returned on
the OPEN call to Protocol Manager.  This error occurs when the Protocol
Manager is not present when the driver attempts to open it.  The most
likely cause is an error in CONFIG.SYS.

Action:
There must be a DEVICE statement to cause the Protocol Manager to be loaded
and it must occur before any other LAN Manager drivers are loaded.

Example:
   DEVICE=C:\LANMAN\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN

   (Other LAN Manager drivers should be included here in the
    CONFIG.SYS file.)

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: Protocol Manager failed on configuration call.

Meaning:
Protocol Manager has returned an error on an attempt to read the
configuration database.  The most likely causes are:
- The PROTOCOL.INI file is missing.
- The path to the PROTOCOL.INI file in the PROTMAN device statement (in
  CONFIG.SYS) is incorrect or missing.
- The structured memory image of the configuration image is corrupt (this
  could happen if a program is loaded after the memory image is constructed
  but before the driver attempts to gain access to the memory image)
- A bind occurs before the driver attempts to access the memory image

Actions:
- Make sure the PROTOCOL.INI file is installed and the path in the PROTMAN
  device statement is correct.
- If the structured memory image of the configuration image is corrupt,
  the solution is to ensure that no programs are loaded before the driver
  accesses the configuration information.
- If a bind occurs before the driver attempts to access the memory image,
  the solution is to move the command that performs the bind to a point
  after the driver loads.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: PROTOCOL.INI contains illegal parameter: xxxxx

Meaning:
Displayed when an illegal parameter is found in PROTOCOL.INI.  A keyword
which is not recognized by the driver has been found in the driver's
configuration data.  The most likely cause is a spelling or syntax error
after the user edited PROTOCOL.INI.  The value 'xxxxx' is the offending
keyword.

Action:
Edit the PROTOCOL.INI file and supply a valid keyword.  All PROTOCOL.INI
parameters are documented in the \NDIS\README file on the Support Disk.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: Illegal value in PROTOCOL.INI after parameter: xxxxx

Meaning:
Displayed when an illegal parameter value is found in PROTOCOL.INI.  A
value specified for a driver parameter was illegal or out of range.  The
most likely causes are:
- Spelling error.
- Syntax error.
- Inappropriate value. For example, using a numeric value when a string is
  expected.
- Value is out of range. For example, a range of 1 - 7 is allowed and a
  value of 8 is specified.
The value 'xxxxx' is the offending keyword.

Action:
Edit the PROTOCOL.INI file and supply a valid value.  All PROTOCOL.INI
parameters are documented in the \NDIS\README file on the Support Disk.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: Card not found or not responding.  Run HPLANSET.

Meaning:
Displayed when the card is not found during a backplane scan or the station
address did not checksum correctly.

Action:
Run HPLANSet from the Support Disk and see if that program is able to
locate the card.  If not, it is most likely that the card's base address is
conflicting with another card in the PC. (The factory default base address is
300h.) Remove all non-essential cards from the PC and run HPLANSet again, or 
move the card to another PC and attempt to configure it there. After these
steps have been taken, if HPLANSet still cannot find the card, it may be
defective and should be replaced.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: The configured interrupt channel is not available.

Meaning:
Displayed when the driver attempts to install the interrupt and it fails.
 This error only occurs on OS/2 systems.  The most likely cause is an
interrupt conflict with another hardware device.

Action:
Choose a different interrupt by changing the INTERRUPT parameter in
PROTOCOL.INI.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: No system timer available.

Meaning:
Displayed when the driver attempts to install the timer and it fails.  This
error only occurs on OS/2 systems.  A maximum of 32 timers are available on
OS/2 systems.  This allocation has been exceeded and none are available for
the driver.

Action:
You must change your system configuration to free up a timer handle.  It is
unlikely that this error will ever be encountered.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: Only 4 HPLANP drivers may be loaded.

Meaning:
Displayed when more than four NDIS drivers are loaded.  You have tried to
install more than four LAN adapters in your system.

Action:
Remove the fifth installation of the driver and LAN adapter.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: No configuration section in PROTOCOL.INI for:_______

Meaning:
Displayed when the configuration database has no entry for this driver.
There is no configuration module in PROTOCOL.INI for the driver.  The most
likely causes are:
- You didn't install the driver properly during the installation procedure
  provided by the NOS vendor.
- You didn't edit PROTOCOL.INI and add the driver configuration information
  while attempting a manual installation.
- The keyword 'DRIVERNAME' is missing from the driver configuration
  information in PROTOCOL.INI.
- The value supplied for the keyword 'DRIVERNAME' in the driver
  configuration information in PROTOCOL.INI was not a legal value.

Action:
Identify which of the above errors is causing the problem, and make an
appropriate correction.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: MicroChannel bus is not supported by this driver.

Meaning:
Displayed when the driver detects that it is running on a Microchannel PC.
 You have loaded the driver on a MicroChannel architecture computer.

Action:
Use the appropriate driver for the adapter you have installed.

___________________________________________________________________________
Message:
HP LAN ADAPTER/16+: Cannot register adapter with the Protocol Manager.

Meaning:
Displayed when the driver's attempt to register with Protocol Manager
fails.  This error could occur if another module has previously registered
the same module name as the LAN Adapter/16 Plus driver.  This would most
likely be the result of editing PROTOCOL.INI and accidently assigning the
same name to two modules (one of them being the LAN Adapter/16 Plus'
module).

Action:
Correct the error in the PROTOCOL.INI file.
