![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM) Adapter: Driver Error Codes for NDIS Driver
DRIVER ERROR CODES FOR NDIS DRIVER
Driver Error Codes for the NDIS Driver
This file contains information specific to the Intel TokenExpress
adapter NDIS driver and the types of error codes you may encounter when
installing the NDIS driver. These codes apply to IBM OS/2 2.x and LAN
Manager v2.x.
These error codes result from errors during driver initialization or
when attempting to open the TokenExpress adapter. The error code may
appear in either of two places:
* As a code at the end of error message 352 (as described in "The
Complete Guide to Installing the Intel TokenExpress Adapter"):
TokenExp 0 352E MAC Driver not Installed -
Adapter initialization error, CC=
or
* In the OMACSTAT utility's "Configuration Status Display." Refer to
OMACSTAT.DOC file for additional information.
1. Adapter Reset Errors
Adapter reset errors indicate an adapter-detected self test error
during an adapter reset.
F100 Initial test error
F101 Adapter ROM CRC error
F102 Adapter RAM error
F103 Instruction test error
F104 Context/interrupt test error
F105 Protocol handler hardware error
F106 System interface register error
2. Adapter Initialization Errors
Adapter initialization errors indicate an adapter-detected self test
error during initialization.
F200 Timeout waiting for initialization to finish
F201 Invalid initialization block
F202 Invalid options
F203 Invalid receive burst count
F204 Invalid transmit burst count
F205 Invalid DMA abort threshold
F206 Invalid SCB
F207 Invalid SSB
F208 DIO parity error
F209 DMA timeout
F20A DMA parity error
F20B DMA bus error
F20C DMA data compare error
F20D Unrecoverable hardware error
F2FF DMA test pattern error
3. Adapter Open Errors
Adapter open errors indicate an adapter-detected error when trying
to open the adapter. These errors result in problems during
"Netbind" or "start" on a LAN Manager workstation.
If the resultant error code has the form:
F3xy
"x" indicates that the error occurred during the open phase and "y"
indicates the type of error that occurred. These errors are
displayed under "Diagnostics Results" by the OMACSTAT utility.
Note: Adapter open errors will not occur during driver
initialization.
F31? Lobe media test
F32? Physical insertion
F33? Address verification
F34? Participation in ring poll
F35? Request initialization
F3?1 Function failure
F3?2 Signal loss
F3?5 Time out
F3?6 Ring failure
F3?7 Ring beaconing
F3?8 Duplicate node address
F3?9 Request parameters
F3?A Remove received
Error F311 indicates a problem with the cable between the computer
and the MAU, while F327 indicates that the adapter's speed setting
is wrong for the ring.
F408 Adapter RAM configuration error
F440 Error in burnt-in or configured node address
4 . Adapter Download Errors
Adapter download errors indicate an error was detected while the
adapter was attempting to download its runtime code from the
computer.
F700 Adapter download failed
F705 Download code file access denied (OS/2)
F718 Download code file not found (OS/2)
F742 Download code file garbled (OS/2)
F743 Download code file EOF
F76E Download code file open failed (OS/2)
F7B1 Adapter ROM CRC error
F7B2 Adapter RAM error
F7B3 Instruction test error
F7B4 Context/interrupt test error
F7B5 Protocol handler hardware error
F7B6 System interface register error
5. . Fatal Ring Status
These error codes indicate that the TokenExpress driver detected a
non-recoverable problem on the ring.
F801 Remove command received from Network Management.
F804 Adapter detected internal error and removed itself.
F808 Lobe wire fault
Trademark information