IBM TOKEN-RING PCI FAMILY ADAPTER, Manual

Page: 81 / 113

LA10045 Could not find the PROTOCOL.INI file image.
Explanation: An unexpected error occurred when the program attempted to read the PROTOCOL.INI file image
through interaction with the Protocol Manager.
User Action: Check the drive and directory to ensure that the Protocol Manager is located in the path specified in the
CONFIG.SYS file. Verify that a valid PROTOCOL.INI file exists in the proper location. If this error persists, consider
reinstalling the NDIS 2.0 network support software.
LA10046 The required DRIVERNAME parameter was not found in PROTOCOL.INI.
Explanation: The parameter specifying the driver name (DRIVERNAME) was not found in the PROTOCOL.INI file.
This parameter is required.
User Action: Change PROTOCOL.INI to specify the proper information.
LA10047 The NetAddress value in PROTOCOL.INI is invalid and will be ignored.
Explanation: The value specified for the network address parameter in PROTOCOL.INI is not valid for one of the
following reasons:
¹
Invalid local station address
¹
Too long
¹
Too short
¹
Contains non-hexadecimal characters
¹
Not enclosed in double quotation marks
User Action: Remove or correct the NetAddress configuration parameter value. A valid value for this parameter is 12
characters long and must be enclosed in double quotation marks. For Token-Ring adapters, the locally administered
address must be within the hex range 400000000000 to 7FFFFFFFFFFF.
Make sure not to set the corresponding group address bit, which is the high-order bit in Token-Ring addressing
notation.
LA10048 An unrecognized parameter xx was found in PROTOCOL.INI.
Explanation: An unrecognized parameter was found while processing a section of the PROTOCOL.INI file defined for
this device driver.
User Action: Correct the parameter name or remove it from PROTOCOL.INI. Refer to the installation manual that
came with your adapter for more information on the configuration parameters.
LA10049 The configuration parameter xx was specified incorrectly. Its default value will be used.
Explanation: An invalid value was specified for a configuration parameter in the PROTOCOL.INI file. A default value
has been substituted.
User Action: Change the PROTOCOL.INI file to specify a valid value for the configuration parameter that is in error.
Refer to the installation manual that came with the adapter for more information on the allowable settings for this
particular parameter.
The device driver has proceeded with its initialization using a predetermined default value for this parameter.
LA10050 The NDIS 2.0 device driver was not able to register with the Protocol Manager.
Explanation: An unexpected error occurred when the program attempted to register a adapter with the Protocol
Manager.
User Action: Check the drive and directory to ensure that the Protocol Manager is located in the path specified in the
CONFIG.SYS file. If this error persists, consider reinstalling the NDIS 2.0 network support software.
LA10051 The configuration parameter values have forced the internal data blocks to exceed the allowed limit.
Explanation: The combination of configuration parameters being used requires more than the 64-KB memory area
that is available for this adapter instance to hold its internal control information.
User Action: Lower the value of the MaxTransmits or MinRcvBuffs parameters in the PROTOCOL.INI file to reduce
the amount of control block storage required by the device driver. Shut down and restart the computer to activate this
configuration change.
Appendix D. NDIS 2 Device Driver Messages
D-5