home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 20 NDrivers
/
20-NDrivers.zip
/
IBMTRBM.ZIP
/
IBMTRBM.DOC
< prev
next >
Wrap
Text File
|
1991-05-28
|
36KB
|
1,059 lines
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide
(C) Copyright IBM Corp. 1990, 1991.
TRADEMARKS
3Com is a trademark of 3Com Corporation
Microsoft is a trademark of the Microsoft Corporation
Micro Channel is a trademark of the IBM Corporation
OS/2 is a trademark of the IBM Corporation
Page 1
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide
INTRODUCTION
The IBM Token-Ring Network 16/4 Busmaster Server Adapter /A Network
Driver Interface Specification (NDIS) device driver for the OS/2
program provides the interface between the IBM Token-Ring Network 16/4
Busmaster Server Adapter /A and a NDIS protocol stack. The device driver
delivers received frames from the adapter card to the protocol handler
and sends frames from the protocol handler to the adapter card to be
transmitted on the token-ring network. The device driver does not
examine frame contents.
The IBM Token-Ring Network 16/4 Busmaster Server Adapter /A NDIS device
driver supports the NDIS interface specified in the 3COM/Microsoft
LAN Manager Network Driver Interface Specification, version 1.0.2.
INSTALLATION
Device Driver Files
To install the required device driver files:
1. Create a directory on the target machine
2. Obtain the following files from the IBM Bulletin Board:
* IBMTRBM.OS2
* IBMTRBM.286
* LT4.MSG
* LT4H.MSG
3. Copy the files listed in Step 2 into the newly created directory.
4. Copy the following files from the options diskette distributed with
the IBM Token-Ring Network 16/4 Busmaster Server Adapter /A into
the newly created directory:
* WRTRAM.BIN
* MONT400.BIN
NOTE - The IBMTRBM.OS2 file copied from the IBM bulletin board
supports only 80386/80486 processors. If the target machine
contains a 80286 processor, then follow these steps to install the
proper version of the IBM Token-Ring Network 16/4 Busmaster Server
Adapter /A NDIS device driver:
1. Rename IBMTRBM.OS2 to IBMTRBM.386
2. Rename IBMTRBM.286 to IBMTRBM.OS2
Page 2
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
CONFIG.SYS File
Add a "DEVICE =" statement after the Protocol Manager device driver
statement in the CONFIG.SYS file. A single "DEVICE = " statement is
required for the IBM Token-Ring Network 16/4 Busmaster Server Adapter /A
NDIS device driver, even when supporting multiple adapters.
Add the following "DEVICE =" statement to the CONFIG.SYS file to allow
the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A NDIS device
driver to initialize:
DEVICE = d:\pathname\IBMTRBM.OS2
where d:\pathname\ is the drive and path where the IBM Token-Ring
Network 16/4 Busmaster Server Adapter /A NDIS device driver has
been installed.
CONFIGURING THE DEVICE DRIVER
The configuration file for the IBM Token-Ring Network 16/4 Busmaster
Server Adapter /A NDIS device driver is the PROTOCOL.INI file. The
following information describes the configuration parameters
accepted by the IBM Token-Ring Network 16/4 Busmaster Server Adapter
/A NDIS device driver. For more information about the PROTOCOL.INI
file, see the 3COM/Microsoft Lan Manager Network Driver Interface
Specification.
Page 3
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
Default PROTOCOL.INI Configuration
The device driver accepts 10 parameters (see Modifying PROTOCOL.INI
Parameters) in the PROTOCOL.INI file. The PROTOCOL.INI file should
contain a section for each IBM Token-Ring Network 16/4 Busmaster
Server Adapter /A installed in the target machine that will be used
for token-ring communications.
The following is an example of a section in a PROTOCOL.INI file that
provides the configuration parameters to load and initialize an
IBM Token-Ring Network 16/4 Busmaster Server Adapter /A.
The section name (in the following, TOKEN1) must be different for
each adapter's configuration.
[TOKEN1]
DriverName = IBMTRBM$
BootStrap = C:\IBMLAN\DRIVERS\TOKENRNG\WRTRAM.BIN
MicroCode = C:\IBMLAN\DRIVERS\TOKENRNG\MONT400.BIN
AdapBuffSize = 1032
AdapMinTran = 16
AdapMaxTran = 40
MinRcvBuffs = 16
SizWorkBuf = 2048
MaxTransmits = 10
NetAddress = "400000000077"
Page 4
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
The following is a example of a PROTOCOL.INI file that contains two
adapter configuration sections:
[TOKEN1]
DriverName = IBMTRBM$
BootStrap = C:\IBMLAN\DRIVERS\TOKENRNG\WRTRAM.BIN
MicroCode = C:\IBMLAN\DRIVERS\TOKENRNG\MONT400.BIN
AdapBuffSize = 1032
AdapMinTran = 16
AdapMaxTran = 40
MinRcvBuffs = 16
SizWorkBuf = 2048
MaxTransmits = 10
NetAddress = "400000000077"
[TOKEN2]
DriverName = IBMTRBM$
BootStrap = C:\IBMLAN\DRIVERS\TOKENRNG\WRTRAM.BIN
MicroCode = C:\IBMLAN\DRIVERS\TOKENRNG\MONT400.BIN
AdapBuffSize = 1032
AdapMinTran = 16
AdapMaxTran = 40
MinRcvBuffs = 16
SizWorkBuf = 2048
MaxTransmits = 10
NetAddress = "400000000078"
Page 5
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
Modifying PROTOCOL.INI Parameters
Edit the PROTOCOL.INI file to modify the parameters. All the keyword
parameters for the IBM Token-Ring Network 16/4 Busmaster Server Adapter
/A NDIS device driver can be modified except the DriverName parameter.
The following information describes each keyword parameter and dis-
cusses the possible values. When modifying any vaules, use caution
to select a new value close to the defined default. Using the maximum
values for several of the parameters at the same time may cause the
device driver to fail to load. It is difficult to define the upper
bound that is valid. Use values near the accepted default as a
guideline.
PROTOCOL.INI Parameters
DriverName
This required parameter indicates the network adapter driver
name for the module. This parameter must be set to IBMTRBM$.
Numerics before or after the $ are not supported. If omitted,
the IBM Token-Ring Network 16/4 Busmaster Server Adapter /A
NDIS device driver will ignore that section of the PROTOCOL.INI
file.
BootStrap
This parameter specifies the path to the network adapter card
loader program, WRTRAM.BIN. The network adapter card loader
program is downloaded onto the network adapter card. Then
the network adapter card loader program downloads the network
adapter card program onto the IBM Token-Ring Network 16/4 Bus-
master Server Adapter /A. If this parameter is omitted, the
default C:\WRTRAM.BIN is used as the location and name of the
adapter card loader program.
Page 6
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
MicroCode
This parameter specifies the path to the network adapter card
program, MONT400.BIN. If this parameter is omitted, the de-
fault C:\MONT400.BIN is as the location and name of the adap-
ter card program. Refer to the BootStrap parameter for more
information.
AdapBuffSize
This parameter specifies the size of the buffers on the net-
work adapter card. The value of this parameter must be a
multiple of 8. The size of the buffers is actually 8 bytes
less than the amount specified, because there are 8 bytes of
overhead associate with each buffer.
Default value: 1032
Minimum value: 96
Maximum value: 2048
If this parameter is omitted the default value of 1032 is used.
AdapMinTran
This parameter specifies the minimum amount of buffer resources
reserved for transmit buffers.
Default value: 4
Minimum value: 4
Maximum value: 676
If this keyword is omitted the default value of 4 is be used.
AdapMaxTran
This parameter specifies the maximum amount of buffer resources
reserved for transmit buffers.
Default value: 6
Minimum value: 40
Maximum value: 676
By limiting the maximum number of buffer resources used for
transmission, the buffer resources used for receiving frames
is defined. If this parameter is omitted the default value of
40 will be used.
Page 7
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
MaxTransmits
This parameter specifies the maximum number of transmit queue
entries. The network adapter driver allocates approximately
260 bytes for each transmit queue entry. The value of this
parameter should be high enough to accommodate the sum of all
MaxTransmits parameter values for all protocol drivers using
the adapter concurrently.
Default value: 10
Minimum value: 1
Maximum value: 65535
If this keyword is omitted a value of 10 is used.
MinRcvBuffs
This parameter specifies the minimum number of receive buffers
that are allocated. For a 4MB token-ring network, the value
of this parameter must have the following relationship:
minrcvbuffs x sizworkbuf >= 4500 bytes
For a 16MB token-ring network, the value of this parameter
must have the following relationship:
minrcvbuffs x sizworkbuf >= 18000 bytes
If the number of buffers is excessive and the size of the
buffers unusually large (see SizWorkBuf), then the device
driver may fail to load. The values selected for these key-
word parameters should be within close range of the provided
defaults.
Default value: 16
Minimum value: 1
Maximum value: 65535
If this keyword is omitted a value of 16 is used.
Page 8
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
SizWorkBuf
This parameter specifies the size of each receive buffer.
The value of this parameter should be high enough to accomodate
the largest frame of any protocol driver using the network
adapter driver. Refer to the MinRcvBuffs parameter for more
information about the value of this parameter.
Default value: 2048
Minimum value: 1
Maximum value: 65535
If this keyword is omitted a value of 2048 is used.
NetAddress
This parameter overrides the network address of the network
adapter card. Specify this parameter only if there are dup-
licate addresses on the netowrk. The value of this parameter
is a hexadecimal string of 12 digits enclosed in quotes, as
in "400001020304". The address must be unique among all other
network adapter addresses on the network. Specify the network
address in IBM Token-Ring network format. If the protocol
driver specifies a network adapter address for the network
adapter driver, that value becomes the default value for the
network adapter driver.
Default value: Universially administered address (burned-in address)
Minimum value: "400000000000"
Maximum value: "40007FFFFFFF"
Configuring Multiple Adapters
The PROTOCOL.INI parameters for the first DriverName = IBMTRBM$
applies to the adapter in the lowest Micro Channel slot number.
The second DriverName = keyword applies to the adapter card in
the next higher slot, and so on.
Adapters are initialized based on occurrences of the DriverName =
IBMTRBM$ statement in a section in the PROTOCOL.INI file, regardless
of bind specifications.
Resource Allocation
Parameters are processed for each adapter. Resources allocated for
each adapter are reserved for use by only that adapter.
Page 9
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
RESTRICTIONS
Initialization Failure
If a section in the PROTOCOL.INI file is incorrect and a particular
adapter cannot be loaded, the IBM Token-Ring Network 16/4 Busmaster
Server Adapter /A NDIS device driver will not load any of the adap-
ters and will not complete initialization. In this situation, the
IBM Token-Ring Network 16/4 Busmaster Server Adapter /A NDIS device
driver cannot be used by a protocol stack until the PROTOCOL.INI
section is fixed.
If a adapter card cannot be loaded due to a hardware fault, the
adapter should be removed. Otherwise, the faulting adapter will
prevent all the other IBM Token-Ring Network 16/4 Busmaster Server
adapters from being loaded and being used by the protocol stack.
DOS Mode Support
The IBM Token-Ring Network 16/4 Busmaster Server Adapter /A NDIS
device driver will execute in a protect mode system only. The
PROTECTMODE = YES statement should be included in the CONFIG.SYS.
Interrupt Level
All IBM Token-Ring Network 16/4 Busmaster Server adapters must exe-
cute using the same interrupt level. SETUP should be used to change
the rings to use the same interrupt level. By default, SETUP places
adapters on different interrupt levels.
The interrupt level that is chosen may be shared with other devices.
NDIS Restrictions
The following NDIS general requests are not supported by the IBM
Token-Ring Network 16/4 Busmaster Server Adapter /A NDIS device
driver:
* ResetMac
* Interrupt
* StartReset
* EndReset.
The following NDIS general requests are supported but with
restrictions:
* TransmitChain - Only physical addresses are supported
* SetStationAddress - May only be issued before the adapter is
opened using the NDIS OPENADAPTER general request.
Page 10
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
MESSAGES
───────────────────────────────────────────────────────────────
LT40004E The microcode file xxxxxxxx could not be opened.
Cause: An unexpected error occurred when the
program attempted to open the microcode file.
Action: Check the drive and directory to ensure that
the microcode file exists. Check the microcode file name
specified in PROTOCOL.INI to ensure that it is correct.
If the problem persists, reinstall the microcode file in
the proper directory.
───────────────────────────────────────────────────────────────
LT40005E The microcode file xxxxxxxx could not be read.
Cause: An unexpected error occurred when the
program attempted to read the microcode file.
Action: Reinstall the microcode file in the proper
directory.
───────────────────────────────────────────────────────────────
LT40006E The bootstrap file xxxxxxxx could not be opened.
Cause: An unexpected error occurred when the
program attempted to open the bootstrap file.
Action: Check the drive and directory to ensure
that the bootstrap file exists. Check the bootstrap
file name specified in PROTOCOL.INI to ensure that
it is correct.
If the problem persists, reinstall the bootstrap file
in the proper directory.
───────────────────────────────────────────────────────────────
LT40007E The bootstrap file xxxxxxxx could not be read.
Cause: An unexpected error occurred when the
program attempted to read the bootstrap file.
Action: Reinstall the bootstrap file in the proper
directory.
Page 11
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40008E The parameter specified in PROTOCOL.INI for
keyword xxxxxxxxxxxx is not the proper character
type.
Cause: The value provided for the keyword in the
IBMTRBM module in PROTOCOL.INI is not the correct type.
Action: Change the value in PROTOCOL.INI to
the correct type for the parameter.
───────────────────────────────────────────────────────────────
LT40009E
An unrecoverable error occurred in the
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A NDIS
device driver program.
Cause: An internal software error occurred.
Action: Contact your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40010E All IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapters must be set to
the same interrupt level.
Cause: One or more IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapters are set to a different interrupt level.
To function properly, these adapters must all be set to the
same interrupt level.
Action: Use the reference diskette that came with your
computer to ensure that all IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapters are set to the same interrupt level.
───────────────────────────────────────────────────────────────
LT40011E A data-check error occurred while attempting
to load the bootstrap code onto the adapter.
Cause: The bootstrap code was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.
Action: Contact your vendor sales representative.
Page 12
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40012E A checksum error occurred while attempting
to load the bootstrap code onto the adapter.
Cause: The bootstrap code was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.
Action: Contact your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40013E This version of the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A NDIS device
driver will not run on an 80286 machine.
Cause: The 80286 processor is not supported for this
version of the device driver.
Action: Either install the 80286 version of the
device driver on this machine or remove the statement
that installs the device driver from CONFIG.SYS.
───────────────────────────────────────────────────────────────
LT40014E The parameter values have forced the
control-block size to exceed the allowable
limit.
Cause: The parameters specified require more space for
processing than can be handled. The maximum allowable
control-block size is 64KB.
Action: Reduce the value specified for the SIZWORKBUF
or MINRCVBUFFS parameter to change the amount of storage
required for the control-blocks.
───────────────────────────────────────────────────────────────
LT40015E The adapter is not responding.
Cause: The adapter is not responding to a request to load
the bootstrap code.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
Page 13
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40016E A 2KB window error occurred while attempting
to load the bootstrap code onto the adapter.
Cause: The adapter is not responding to a request to load
the bootstrap code.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40017E An error occurred while attempting to run
the bootstrap code.
Cause: The adapter is not responding to a request to run
the bootstrap code.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40018E A parameter error occurred while attempting
to run the bootstrap code.
Cause: The adapter is not responding to a request to run
the bootstrap code.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40019E A write error occurred while attempting
to load the bootstrap code onto the adapter.
Cause: The bootstrap code was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
Page 14
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40020E A checksum error occurred while attempting
to load the microcode onto the adapter.
Cause: The microcode was unable to load properly
onto the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.
Action: Contact your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40021E The microcode encountered a program-status
error while attempting to write to the adapter.
Cause: The microcode was unable to write properly
to the IBM Token-Ring Network 16/4 Busmaster Server
Adapter/A adapter.
Action: Contact your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40022E A reset error occurred while attempting to
initialize the adapter microcode.
Cause: The adapter is not responding to a request to initialize
the microcode.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40023E A parameter error occurred while attempting
to run the microcode.
Cause: The adapter is not responding to a request to run
the microcode.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
Page 15
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40024E The burned-in address could not be found
on the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter.
Cause: The burned-in address on the adapter could not be located.
Action: Either use the set network address (NETADDRESS)
parameter in PROTOCOL.INI to override the burned-in address or
run the hardware diagnostics for the IBM Token-Ring Network
16/4 Busmaster Server Adapter/A adapter and contact your
vendor sales representative.
───────────────────────────────────────────────────────────────
LT40025W Duplicate device driver statements exist
in CONFIG.SYS.
Cause: Only one occurrence of the device driver statement
for the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS MAC device driver is required to support multiple adapters.
Additional instances of the device driver statement in CONFIG.SYS
will be ignored.
Action: Remove the duplicate device driver statements from
CONFIG.SYS.
───────────────────────────────────────────────────────────────
LT40026E The required parameter DRIVERNAME was not
found in PROTOCOL.INI.
Cause: The parameter specifying the driver name (DRIVERNAME) was not
found in PROTOCOL.INI. This parameter is required.
Action: Change PROTOCOL.INI to specify the proper information.
───────────────────────────────────────────────────────────────
LT40027E The protocol manager could not be opened.
Cause: An unexpected error occurred when the
program attempted to open the protocol manager.
The IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS device driver has been removed.
Action: Check the drive and directory to ensure that
the protocol manager is located in the specified path.
Page 16
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40028E An unrecoverable error occurred while
attempting to register the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A NDIS
device driver program with the protocol manager.
Cause: The device driver was unable to register with
the protocol manager.
Action: Reinstall the protocol manager and
try the operation again.
───────────────────────────────────────────────────────────────
LT40029E No physical adapter was found in this machine.
Cause: There was no adapter found in this machine.
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A adapters
are required to run the MAC device driver.
Action: Install an IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A adapter in this machine, or remove the device
driver statement from CONFIG.SYS.
───────────────────────────────────────────────────────────────
LT40030W The unrecognized parameter xxxxxxxxxxxx was
found in PROTOCOL.INI.
Cause: An unrecognized parameter was found
while processing the IBM Token-Ring Network 16/4 Busmaster
Server Adapter/A section of PROTOCOL.INI.
Action: Correct the parameter or remove it from
PROTOCOL.INI.
Page 17
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40031W The value specified for network address
in PROTOCOL.INI is not valid. The burned-in
address will be substituted.
Cause: The value specified for the network address parameter in
PROTOCOL.INI is not valid for one of the following reasons:
1. Invalid local station address
2. Too long
3. Too short
4. Contains non-hexadecimal characters
5. Not enclosed in double quotes
Action: Remove or correct the network address parameter
(NETADDRESS). A valid value for this parameter is 12 characters
long, is enclosed in double quotes, and contains only valid
hexadecimal characters within the range of 400000000000 through
40007FFFFFFF.
───────────────────────────────────────────────────────────────
LT40033E A duplicate network address was found
while inserting onto the ring.
Cause: The network address that the adapter wants to use on the
token-ring is being used by another node.
Action: Either modify PROTOCOL.INI to provide a different
value for the network address (NETADDRESS) parameter, use the
default burned-in address, or remove the other node that is
using this network address from the ring.
───────────────────────────────────────────────────────────────
LT40034E Ring failure or beaconing was encountered
while inserting onto the ring.
Cause: The ring speed is different from the speed of the
node attempting to insert onto the ring.
Action: Use the reference diskette that came with your
computer to ensure that the adapter is configured at the same
speed as the token-ring.
Page 18
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40035E A hardware failure occurred while attempting
to open the adapter.
Cause: When the adapter tried to insert onto the token-ring, a
hardware error occurred on the adapter.
Action: Run the hardware diagnostics for the IBM Token-Ring
Network 16/4 Busmaster Server Adapter/A adapter. Contact
your vendor sales representative.
───────────────────────────────────────────────────────────────
LT40036E A lobe media error has occurred. Ensure
that the token-ring cable is connected
to the adapter.
Cause: While attempting to open the adapter, an indication
was received that the adapter is not properly connected to
the token-ring.
Action: Ensure that the token-ring cable is connected to
the adapter and to the token-ring multistation access unit (MAU).
If the error persists, use a different token-ring cable
and check to ensure that the connection to the MAU is
functioning properly. Then run the hardware diagnostics
for the IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
adapter.
───────────────────────────────────────────────────────────────
LT40037W The version of the installed device driver is not
optimized for the 80386/80486 processor.
Cause: The version of the IBM Token-Ring Network 16/4
Busmaster Server Adapter/A NDIS MAC device driver is
built for an 80286 machine. The version will function
correctly on this 80386/80486 machine, but performance
benefits will not be available.
Action: Install the optimized version on this machine.
Page 19
IBM Token-Ring Network 16/4 Busmaster Server Adapter/A
NDIS Device Driver User's Guide (con't)
───────────────────────────────────────────────────────────────
LT40038E The installed IBM Token-Ring Network 16/4
Busmaster Server Adapter/A NDIS device driver
cannot run on this operating system.
Cause: The device driver installed is designed to run on
a different operating system.
Action: Do the following:
1. Locate the current version of IBMTRBM.OS2 on the machine.
2. Erase IBMTRBM.OS2.
3. Copy IBMTRBM.286 from the installation diskette
into the directory.
4. Rename IBMTBM.286 to IBMTRBM.OS2.
5. Restart your system.
───────────────────────────────────────────────────────────────