Messages and errors
The tables below list common messages and errors and the
conditions under which they occur. Message and error types
include:
- Sign on / successful join messages
- Pre-join ring process messages
- Join ring errors
- NDIS specific errors
- ODI specific errors
Join ring errors display additional error codes that help you
determine when and where the error occurred in the join ring
process.
Sign on / successful join messages
==================================
Condition Message
--------- -------
Sign on Intel TokenExpress(TM) PRO network adapter.
Driver version... Download MAC microcode...
While joining Joining Token Ring. Please wait.
ring
Successfully Joined Token Ring successfully.
joined
Pre-join ring process messages
==============================
Condition Message
--------- -------
Adapter not Can't find a token ring adapter in this computer.
found Make sure the adapter is installed.
Reseat the adapter in slot.
Try moving the adapter to another slot.
Reconfigure the adapter.
Failed self- The adapter failed self-test.
test Reconfigure the adapter with a different I/O address.
Run TokenSet and test the adapter.
EEPROM check- Information in the EEPROM hardware is incorrect.
sum error Run TokenSet, and the view current configuration.
Test the adapter.
Using 16-bit The IRQ assigned to the adapter does not work for
IRQ in 8-bit 8-bit slots.
slot Move the adapter to a 16-bit slot, or
configure the adapter with an IRQ less than 8.
Plug and Play This computer has a Plug and Play BIOS but
BIOS but no doesn't have a configuration manager.
configuration Run TokenSet to disable Plug and Play support.
manager
I/O conflict The I/O address assigned to adapter is used
by another device in this computer.
Reconfigure the adapter with a different I/O address.
Join ring errors
================
Join ring error codes consist of a four digit hex number.
The syntax is as follows:
"Error xxjk"
where x = internal use only, disregard
j = shows where in the process the error occurred
k = shows what the specific error was
If j = 0, the error occurred BEFORE the join ring process.
To find out what the specific error was, use your k value
and table 1.
Table 1. Finding specific error (j = 0)
=========================================================
k Specific Error Description
--- -------------- -----------
1 Not configured Host issued Join Ring command
before issuing configure command.
Call Customer Support.
2 Already joined Adapter is already joined on the ring.
Call Customer Support.
3 Already joining Adapter is already in the process of
joining the ring.
Call Customer Support.
4 Close command Close command from host stopped join.
Retry join ring.
5 Bad individual Host passed a group address for a node
address address.
If using a node address override
(locally administered address),
try a different address.
6 Ring speed not First station on the ring with auto ring
established speed selected.
Retry join ring.
Run TokenSet and manually select a ring
speed (4 or 16 Mbps).
Contact your LAN administrator.
7 Can not detect Ring Speed detection failure.
ring speed Retry join ring.
Run TokenSet and manually select a ring
speed (4 or 16 Mbps).
Contact your LAN administrator.
8 Bad individual The Individual Address registers
address initiali- are not set to the same value as
zation the Individual Address passed in
the Join Ring command.
Call Customer Support.
========================================================
If j = 1, 2, 3, 4, or 5, the error occurred DURING the join
ring process. To find out which join ring process was active
when the error occurred, use your j value and table 2. To
determine the specific error, use your k value and table 3.
Table 2. Finding location of error (j = 1, 2, 3, 4, or 5)
=========================================================
j Join Ring Process Description
--- ----------------- -----------
1 Lobe Media Test Insures that your adapter can send and
receive frames to itself correctly
2 Detect Active Involves the adapter waiting to receive
Monitor a frame that indicates the presence of an
active monitor on the ring.
3 Duplicate Address Insures that the network address assigned
Test to your adapter is unique to the ring.
4 Neighbor Notifi- Determines who your upstream neighbor is
cation and alerts your downstream neighbor that
it has a new neighbor.
5 Request Parameters Requests ring initialization information
from the configuration report server
(if present).
=========================================================
Table 3. Finding specific error (j = 1, 2, 3, 4, or 5)
=========================================================
k Specific Error Description
--- -------------- -----------
1 Function Failure Specific join ring function failed to
complete.
Contact your LAN administrator.
2 Signal Loss Signal loss occurred during the join ring
process.
Contact your LAN administrator.
5 Time-out A specific process timer expired before
completion.
Retry join ring.
Contact your LAN administrator.
6 Ring Failure Adapter unable to successfully complete
ring recovery.
Retry join ring.
Contact your LAN administrator.
7 Ring Beaconing Adapter detected beaconing or was forced
into a beaconing state during join ring
process.
Retry join ring when beaconing stops.
Contact your LAN administrator.
8 Duplicate Address Another station on the ring has the same
node address.
If using a node address override (locally
administered address), try a different
address (contact your LAN administrator);
otherwise, Call Customer Support.
9 Parameter Request A parameter server is present, but does
not respond.
Retry join ring.
Contact your LAN administrator.
A Remove Received A remove station MAC frame was received.
Contact your LAN administrator.
D No Monitor RPL join ring did not detect an active
Detected monitor.
Retry join ring.
Contact your LAN administrator.
E RPL Insertion Ring failure while trying to insert onto
Failure the ring.
Retry join ring.
Contact your LAN administrator.
========================================================
NDIS specific errors
====================
Condition Message
--------- -------
Initial NDIS environment invalid, driver not loaded.
failure Reseat the card.
Make sure card is in ISA/EISA slot.
Failure OS/2 can't allocate a Global Descriptor
allocating Table Entry for the TokenExpress PRO adapter.
GDT Make sure OS/2 is operating correctly.
NDIS Can't establish communication between Token-
environment Express PRO adapter and NDIS environment.
invalid If PCMCIA card, run LANINIT before binding.
Run TokenSet, test the adapter.
Check your network software settings.
Multiple When more than one adapter is present,
adapters TokenSet must be used to set each IO address;
IO address parameter in PROTOCOL.INI is
required for each configured adapter;
TokenSet values must match IOADDRESS values.
PROTOCOL.INI The PROTOCOL.INI file doesn't have an entry for the
doesn't have TokenExpress PRO adapter driver.
DRIVERNAME= Review the installation instructions.
TPRO Check PROTOCOL.INI configuration,
insert DRIVERNAME=TPRO statement.
PROTOCOL.INI Adapter not found at PROTOCOL.INI IOADDRESS.
IO address Use TokenSet to set hardware to PROTOCOL.INI value,
or edit PROTOCOL.INI to match TokenSet value.
Protocol Protocol Manager did not accept LAN Card driver.
Manager Run Tokenset and configure hardware settings.
Check your PROTOCOL.INI IOADDRESS=xxxh statement.
If above doesn't work, call Customer Support.
ODI specific errors
====================
Condition Message
--------- -------
Adapter not Didn't find adapter at address specified in
at address in NET.CFG. The adapter is at I/O address xxxx.
NET.CFG
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.