This README file contains the following information: 1.0 NDIS Device Driver Overview 2.0 NDIS Device Driver Installation 3.0 NDIS Device Driver Configuration 4.0 NDIS Device Driver Support For Multiple Adapters 5.0 NDIS Device Driver Messages Print Instructions: This is a flat ASCII file and has no printer controls. If you want to print this file, you may want to edit it and add any printer control characters or page breaks that are needed. 1.0 NDIS Device Driver Overview --------------------------------- An IBM Network Driver Interface Specification (NDIS) OS/2 device driver is supplied with the IBM LANStreamer adapter. This NDIS OS/2 driver supports OS/2 versions 1.3 and 2.0. The device driver as defined in the NDIS specification, functions as a Media Access Control (MAC) driver. MAC drivers are device drivers that interface directly to the adapter but do not handle communications protocols. The device driver supports Version 2.01 of the NDIS and includes IBM NDIS extensions. The IBM NDIS extensions are used by the device driver to support the IEEE 802.2 CCB Interface through the NDIS interface. The device driver indicates that the IBM NDIS extensions are available by setting the Minor NDIS Version to an 02 in the Common Characteristics Table. The IBM LANStreamer NDIS device driver appears as an 802.5 type of MAC driver. 2.0 NDIS Device Driver Installation ------------------------------------- This driver diskette has been set up to work correctly with IBM LAPS installation and configuration program, IBM LAN Support Program installation program (DXMAID), and Microsoft LAN Manager installation program (SETUP). The files that make up the support for the LANStreamer adapter are duplicated in different directories on this diskette to make installation in each of these environments as easy as possible. When the LAPS installation program is not used in OS/2, the DEVICE= statement must be manually inserted in CONFIG.SYS. The DEVICE= statement for the NDIS device driver must be after the DEVICE= statement for the Protocol Manager. Copy the OS/2 NDIS device driver from the Driver diskette to the desired target directory. Then add a DEVICE= statement into the CONFIG.SYS file to start the NDIS device driver during system initialization. An example of a DEVICE= statement for the CONFIG.SYS file is: DEVICE=C:\..path..\IBMTRDB.OS2 Also remember to remove any device statements for adapters you are replacing with the IBM LANStreamer adapter. 3.0 NDIS Device Driver Configuration -------------------------------------- The NDIS device driver can be configured using the LAPS installation Program for OS/2 or by manually editing the PROTOCOL.INI file. A detailed description of configurable parameters follows: NETADDRESS = The NetAddress parameter overrides the network address of the network adapter card. The value of this parameter is a hexadecimal string of 12 digits and must be enclosed in double quotation marks. The characters must be within the range X'400000000000' through X'7FFFFFFFFFFF'. If you do not assign a locally administered address, the adapter uses the universally administered address. The address must be unique among all other network adapter addresses on the network. EXAMPLE: NETADDRESS = "400100001234" MAXTRANSMITS = The MaxTransmits parameter specifies the maximum number of transmit queue entries to be used by the adapter driver. 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 Maximum Number of Queued Transmits parameter values specified for all protocol drivers using the adapter concurrently. A value from 2 to 512 queues may be specified. If the parameter is not specified, a value of 31 is used. EXAMPLE: MAXTRANSMITS = 32 SIZWORKBUF = The SizWorkBuf parameter specifies the size of the receive buffers. A receive buffer can be from 96 to 18000 bytes long. The default receive buffer size is 2048 bytes. Please refer to the MinRcvBuffs parameter to understand the relationship between these two parameters. EXAMPLE: SIZWORKBUF = 4096 MINRCVBUFFS = The MinRcvBuffs parameter specifies the minimum number of receive buffers that are allocated by the network adapter driver. The value specified for MinRcvBuffs multiplied by the value specified for SizWorkBuf must be greater than the size of the largest frame to be received from the network. For a 4Mbps network the maximum length frame size is 4500 bytes. For a 16Mbps network the maximum length frame size is 18000 bytes. From 2 to 512 receive buffers may be specified. A default of 20 buffers will be used if the parameter is not specified. EXAMPLE: MINRCVBUFFS = 32 MULTICASTNUM = The MulticastNum parameter specifies the maximum number of group addresses to be supported by the network adapter driver. The network adapter driver can support from 1 to 256 group addresses. If this parameter is not specified, a default of 1 will be used. EXAMPLE: MULTICASTNUM = 256 ENABLETXEOFINT = The EnableTxEofInt parameter specifies whether the transmit end of frame interrupt should be enabled. A value of 1 indicates that transmit end of frame interrupt will be recognized by the interrupt handler. A value of 0 indicates that the transmit end of frame should not be recognized by the interrupt handler. A value of 0 may be desireable in some environments (such as a server) to reduce the number of times the interrupt handler is invoked. If this parameter is not specified, the transmit end of frame interrupt is enabled. EXAMPLE: ENABLETXEOFINT = 0 LOOPBACK = The LoopBack parameter is used to determine whether loopback is to be supported by the adapter or handled by the protocol stack. If this parameter is set to 0, then frames transmitted by this station, that would have been received by this station, must be looped back by the protocol stack. If this parameter is set to 1, then loopback will be handled by the adapter and frames transmitted by this station, addressed to this station, will be received. If not specified, loopback will be set by the driver to a 1 unless the adapter is operating in a 16 bit bus slot, or is a 16 bit adapter, and is operating at 16 Mbps. A value of 0 is used in this situation because some machines do not have sufficient bus bandwidth to handle 16Mbps doing simultaneous transmits and receives. EXAMPLE: LOOPBACK = 1 When the LAPS installation program is not used to configure the NDIS device driver, the NDIS device driver section of PROTOCOL.INI can be created manually. An example of a PROTOCOL.INI section for the NDIS device driver follows. [IBMTRDB_NIF] Drivername = IBMTRDB$ NetAddress = "400001020304" The desired protocol driver(s) must be "bound" to the NDIS device driver by manually editing the BINDINGS= statement of those protocol drivers. An example follows: [PROTOCOL_DRIVER_ABC] Bindings = IBMTRDB_NIF 4.0 NDIS Device Driver Support For Multiple Adapters ------------------------------------------------- When more than one adapter is installed in the same system, a single device statement is used in CONFIG.SYS. CONFIG.SYS: DEVICE=C:\..path..\IBMTRDB.OS2 Multiple incidences are created within PROTOCOL.INI. If you are manually configuring, example PROTOCOL.INI entries follow: PROTOCOL.INI: [PROTOCOL_DRIVER_ABC] Bindings = IBMTRDB_NIF, IBMTRDB1_NIF [IBMTRDB_NIF] Drivername = IBMTRDB$ NetAddress = "400001020304" [IBMTRDB1_NIF] Drivername = IBMTRDB$ NetAddress = "400001020305" 5.0 NDIS Device Driver Messages --------------------------------- ----------------------------------------------------------------------------- LT60008E: THE PARAMETER SPECIFIED IN PROTOCOL.INI FOR KEYWORD 'KEYWORD' IS NOT THE PROPER CHARACTER TYPE. CAUSE: The value provided for the keyword in the IBMTRDB module in the PROTOCOL.INI file is not the correct type. USER ACTION: Change the value in PROTOCOL.INI to the correct type for the parameter. ----------------------------------------------------------------------------- LT60009E: AN UNRECOVERABLE ERROR OCCURRED IN THE IBM LANSTREAMER ADAPTER NDIS DEVICE DRIVER PROGRAM. CAUSE: An internal software error occurred. USER ACTION: Contact your vendor sales representative. ----------------------------------------------------------------------------- LT60010E: ALL IBM LANSTREAMER ADAPTERS MUST BE SET TO THE SAME INTERRUPT LEVEL. CAUSE: One or more IBM LANStreamer adapters are set to a different interrupt level. To function properly, these adapters must all be set to the same interrupt levels. USER ACTION: Use the reference diskette that came with your computer to ensure that all IBM LANStreamer adapters are set to the same interrupt level. ----------------------------------------------------------------------------- LT60011I: THE UNIVERSALLY ADMINISTERED ADDRESS OF THE IBM LANSTREAMER IS 'ADDRESS'. CAUSE: The universally administered address of the adapter installed in the computer is displayed in this message. USER ACTION: None. ----------------------------------------------------------------------------- LT60012I: THE IBM LANSTREAMER ADAPTER IS USING A LOCALLY ADMINISTERED ADDRESS OF 'ADDRESS'. CAUSE: The locally administered address for the IBM LANStreamer adapter installed in the computer is displayed in this message. USER ACTION: None. ----------------------------------------------------------------------------- LT60014E: 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. USER ACTION: Reduce the value specified for the MAXTRANSMITS or MINRCVBUFFS parameter to change the amount of storage required for the control-blocks. The control-block area can be computed using the following formula: 1698 + (190 * MAXTRANSMITS) + (256 * MINRCVBUFFS) The control-block work area must be less than 64KB. ----------------------------------------------------------------------------- LT60015E: THE ADAPTER IS NOT RESPONDING. CAUSE: The adapter is not responding to a request to initialize. USER ACTION: Run the hardware diagnostics for the IBM LANStreamer Adapter. Contact your vendor sales representative. ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- LT60016I: THE IBM LANSTREAMER ADAPTER IS OPERATING AT A DATA RATE OF 4 MBPS. USER ACTION: None ----------------------------------------------------------------------------- LT60017I: THE IBM LANSTREAMER ADAPTER IS OPERATING AT A DATA RATE OF 16 MBPS. USER ACTION: None ----------------------------------------------------------------------------- LT60025W: DUPLICATE DEVICE DRIVER STATEMENTS EXIST IN CONFIG.SYS. CAUSE: Only one occurrence of the device driver statement for the IBM LANStreamer Adapter NDIS MAC device driver is required to support multiple adapters. Additional instances of the device driver statement in CONFIG.SYS will be ignored. USER ACTION: Remove the duplicate device driver statements from CONFIG.SYS. ----------------------------------------------------------------------------- LT60026E: 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. USER ACTION: Change PROTOCOL.INI to specify the proper information. ----------------------------------------------------------------------------- LT60027E: THE PROTOCOL MANAGER COULD NOT BE OPENED. CAUSE: An unexpected error occurred when the program attempted to open the protocol manager. The IBM LANStreamer Adapter NDIS MAC device driver has been removed. USER ACTION: Check the drive and directory to ensure that the protocol manager is located in the specified path. ----------------------------------------------------------------------------- LT60028E: AN UNRECOVERABLE ERROR OCCURRED WHILE ATTEMPTING TO REGISTER THE IBM LANSTREAMER ADAPTER NDIS DEVICE DRIVER PROGRAM WITH THE PROTOCOL MANAGER. CAUSE: The device driver was unable to register with the protocol manager. USER ACTION: Reinstall the protocol manager and try the operation again. ----------------------------------------------------------------------------- LT60029E: NO PHYSICAL ADAPTER WAS FOUND IN THIS MACHINE. CAUSE: There was no adapter found in this machine. An IBM LANStreamer Adapter is required to run the MAC device driver. USER ACTION: Install an IBM LANStreamer Adapter in this machine, or remove the device driver statement from CONFIG.SYS. ----------------------------------------------------------------------------- LT60030W: THE UNRECOGNIZED PARAMETER 'PARAMETER NAME' WAS FOUND IN PROTOCOL.INI. CAUSE: An unrecognized parameter was found while processing the IBM LANStreamer Adapter section of PROTOCOL.INI. USER ACTION: Correct the parameter or remove it from PROTOCOL.INI. ----------------------------------------------------------------------------- LT60031W: 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 correct for one of the following reasons: - Invalid local station address - Too long - Too short - Contains non-hexadecimal characters - Not enclosed in double quotes USER 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 7FFFFFFFFFFF. ----------------------------------------------------------------------------- LT60032I: IBM LANSTREAMER ADAPTER NDIS DEVICE DRIVER VERSION 'VERSION#'. CAUSE: The version of the IBM LANStreamer device driver that is loaded into memory is displayed in this message. USER ACTION: None. ----------------------------------------------------------------------------- LT60033E: 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. USER 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. ----------------------------------------------------------------------------- LT60034E: 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. USER 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. ----------------------------------------------------------------------------- LT60035E: 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. USER ACTION: Run the hardware diagnostics for the IBM LANStreamer Adapter. Contact your vendor sales representative. ----------------------------------------------------------------------------- LT60036E: 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. USER 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 LANStreamer Adapter. ----------------------------------------------------------------------------- LT60039I: INITIALIZATION STARTING FOR SECTION 'SECTION NAME' IN PROTOCOL.INI. CAUSE: The IBM LANStreamer NDIS device driver is processing the named section of the PROTOCOL.INI file that is displayed in this message. USER ACTION: None. ----------------------------------------------------------------------------- LT60044E: THE CONFIGURATION VALUES HAVE FORCED THE CONTROL-BLOCK SIZE TO EXCEED THE AVAILABLE MEMORY. CAUSE: The configuration parameters specified require more space for for processing than can be handled with the available system memory. USER ACTION: Reduce the value specified for the MAXTRANSMITS or MINRCVBUFFS parameter to change the amount of storage required. The following formula can be used to compute the maximum value: H(i) = RCVAREA(i) + ALLOCSIZECB(i) A H(i) value should be computed for each IBM LANStreamer Adapter and the sum of all H(i) values must be less than 1 MB. The receive area for each adapter can be computed: RCVAREA = MINRCVBUFFS x SIZWORKBUF The control block area for each adapter can be computed using the following formula and must be less than 64KB. ALLOCSIZECB = 1698 + (190 * MAXTRANSMITS) + (256 * MINRCVBUFFS) ------------------------------------------------------------------------------- IBM is a trademark of IBM, Inc. IBM LANStreamer Adapter is a trademark of IBM, Inc.