![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM) EISA/32: IBM - OS/2 EE v1.3 Driver Error Messages
EISA/32 IBM-OS/2 EE V1.3 DRIVER ERROR MESSAGES
These instructions apply to Release 4.0 of the software.
You'll always find the most current version of the driver instructions
are available through Intel's online services. If the driver software
has changed, you can get the latest drivers and instructions from
Intel's online services. Always check the revision date of the document
to make sure you have the most updated copy.
Error messages are listed in numerical order and appear in this format:
TokenExp ISA 0 302E: Attach to LANDD failed
____________ _ _____ _________________________
| | | |
| | | |
| | | |- message
| | |
| | |- message number (see entries below)
| |
| |- *0 = only Token Ring adapter in this computer
| 1 = second Token Ring adapter in this computer
| 2 = third Token Ring adapter in this computer
| 3 = fourth Token Ring adapter in this computer
|
| *Order number specified in device driver line
|
|- adapter identification
Error 301E
Message:No adapters found. Driver not installed.
Action: The driver didn't install because it couldn't find the adapter
you specified.
* Make sure you've installed the adapter correctly. Check that the
adapter is seated firmly in its expansion slot.
* Run the diagnostics to make sure the adapter is working.
Error 302E
Message:Attach to LANDD failed
Action: Look at the CONFIG.SYS file. Make sure the LAN driver line
("DEVICE=LANDD.SYS") precedes the adapter driver line
("DEVICE=TRNETDD.SYS").
Error 303E
Message:GDT or UVirt Allocation Problems.
Action: Your system doesn't have enough extended memory to allocate to
the adapter driver.
* Make sure you specify the right amount of extended memory when you
set up OS/2.
* Try reconfiguring your system to free up some extended memory.
Error 304W
Message:Adapter initialization failed. Error: <code>.
Action: The adapter failed for one of the reasons below. (Find the
reason corresponding to the code displayed on your screen.)
Code Description
F000x Bring-up diagnostic error. x may be any value from 1 to
6.
F10x Adapter initialization error.
F101-F107 The adapter reports that the initialization parameters
received from the driver are invalid.
F108 Parity error during I/O operation.
F109-F10C DMA error.
F10D Adapter check. The adapter encountered an unrecoverable
hardware error.
F20 DMA error during initialization.
Run the diagnotics program. If your adapter
malfunctions, call your dealer or Intel's Technical
Support.
Error 305W
Message:Adapter open failed. Error: <code>
Action: The driver couldn't open the adapter. For a description of the
error code, refer to the Open Error Codes section of the "IBM
Local Area Network Technical Reference" manual.
Error 306E
Message:Adapter work area overflow
Action: Use the Communication Manager program to reduce the number of
queue elements specified under the IEEE 802.2 LAN Profile.
Error 320E
Message:Cannot open the file specified in the DEVICE= statement.
Default values used. The file is: <name>
Action: Look at the CONFIG.SYS file. Check the file name you typed in
the device driver line. Make sure you use this form:
drive:\path\file_name
Make sure you specify the path containing the driver file.
Error 321E
Message:Cannot read the file specified in the DEVICE= statement.
Default values used. The file is: <name>
Action: Look at the CONFIG.SYS file. Check the attributes of the file
you specified in the device driver line. The file must have a
READ attribute.
Error 322E
Message:Cannot access the file specified in the DEVICE= statement.
Default values used. The file is: <name>
Action: Look at the workstation's CONFIG.SYS file. Check the Intel
device driver line for errors or typos.
Error 323E
Message:The file specified in the DEVICE= statement, is not a proper CM
*.CFG file. The file is: <name>
Action: Check that the file you specified in the DEVICE= statement is a
.CFG file created and verified by the Communication Manager
(CM). To do this, start CM and browse through the specified
file. When you exit and save the file, it will have the correct
format.
Error 324I
Message:An error was encountered during close of the file specified in
the DEVICE= statement. The file is: <name>
Action: The file you specified may contain corrupted data. Contact your
dealer or Intel's Technical Support.
Error 325E, 326E, 327E
Message:See messages and suggested actions for 323E.
Error 328E
Message:Configuration file error. Use CM to correct and verify. Illegal
keyword: <keyword>
Action: Start the Communication Manager (CM) and select "Change
configuration" for the specified file. Run "verify" before you
exit. For more information about the error, refer to the 802.2
LAN Profile under CM.
Error 329E
Message:Configuration file error. Use CM to correct and verify. Syntax
error near: <string>
Action: See the suggested action for Error 328E.
Error 330E
Message:Configuration file error. Use CM to correct and verify. Illegal
value: <value>
Action: See the suggested action for Error 328E.
Error 331E
Message:Configuration file error. Use CM to correct and verify. Syntax
error near: <string>
Action: See the suggested action for Error 328E.
Error 350E
Message:The DEVICE= statement in CONFIG.SYS is not readable.
Action: Look at the CONFIG.SYS file. Make sure there are no errors in
the device driver line. As a last resort, try retyping the
device driver line.
Error 351E
Message:Syntax error in DEVICE= statement in CONFIG.SYS. Parameters
must be defined as: <keyword>=<value>. Spaces are used to
separate parameters.
Action: Look at the CONFIG.SYS file. Make sure there are no errors in
the device driver line. Make sure you've put spaces between
parameters, and put equal signs (=) between keywords and their
values.
Error 352E
Message:The DEVICE= statement in CONFIG.SYS contains an unknown keyword.
The keyword: <word> is ignored.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 354E
Message:The DMA value specified in the DEVICE= statement in CONFIG.SYS
is illegal. Default value used.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 355E
Message:The interrupt value specified in the DEVICE= statement in
CONFIG.SYS is illegal. Default value used.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 356I
Message:Configuration file not specified in DEVICE= statement. Default
values are used.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 357I
Message:Resource computation error. Check that the configuration file is
OK using the CM verify utility. Default values are used.
Action: Start the Communication Manager (CM) and select "Change
configuration" for the specified file. Run "Verify" before you
exit.
Error 358E
Message:Transmit buffer size invalid. 4/16Mbit adapters have max. sizes:
2048/(4460, 17960) at (4, 16Mbps) respectively.
Action: Use the Configuration Manager (CM) "Change configuration"
utility to change the transmit buffer size to a valid value.
For more information about the transmit buffer, refer to the
802.2 LAN Profile under CM.
Error 359I
Message:Interrupt level specification in DEVICE= statement is applicable
only to the 4MB AT adapter. Parameter ignored.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 360I
Message:DMA level specification in DEVICE= statement is applicable only
to the 4MB AT adapter. Parameter ignored.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 361E
Message:Multiple definition of configuration file in DEVICE= statement.
Parameter ignored.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 362E
Message:Multiple definition of interrupt level in DEVICE= statement.
Default value used.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 363E
Message:Multiple definition of DMA in DEVICE= statement. Default value
used.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 364E
Message:Multiple definition of trace level in DEVICE= statement. Trace
not enabled.
Action: Edit the CONFIG.SYS file and correct the error in the device
driver line.
Error 371E
Message:Cannot open ACSLAN.LOG (Dos-Open error)
Action: Check the attributes of the file ACSLAN.LOG. They must allow
the file to be read.
Error 372E
Message:Cannot access ACSLAN.LOG (DosChgFilePtr error)
Action: The ACSLAN.LOG file may contain corrupt data. Try restarting
the workstation.
Error 373E
Message:Interrupt conflict
Action: The driver has detected an interrupt conflict. Make sure none
of the other devices in this computer use the interrupt this
adapter uses. If you discover a conflict, change the interrupt
setting for the Intel adapter or for the other device.
Error 379E
Message:Resulting receive frame size too large. Default values are used.
Action: Use the Configuration Manager "Change configuration" utility to
reduce the link station or SAP count.
Trademark information