InfoMagic Internet Tools 1995 April

home *** CD-ROM | disk | FTP | other *** search

/ InfoMagic Internet Tools 1995 April / Internet Tools.iso / dos_win / lanman / drivers / os2 / IBMTRDB / IBMTRDBO.ZIP / README.OS2 < prev

Wrap

Text File | 1993-04-26 | 15.2 KB | 406 lines

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 --------------------------------- One IBM Network Driver Interface Specification (NDIS) device driver is supplied with the IBM LANStreamer adapter. This NDIS driver supports OS/2 (version 1.3 or 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 options 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, 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. Examples of a DEVICE= statement for the CONFIG.SYS file are: for OS/2: 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 = This 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" RECEIVEBUFSIZE = The receivebufsize parameter defines the size of the receive buffers. A receive buffer can be from 1500 to 4500 bytes long. The default receive buffer size is 1500 bytes. The size of the receive buffers contributes directly to the amount of system memory required for the IBM LANStreamer NDIS Device Driver. EXAMPLE: RECEIVEBUFSIZE = 1500 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_MOD] 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_MOD 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_MOD, IBMTRDB1_MOD [IBMTRDB_MOD] Drivername = IBMTRDB$ NetAddress = "400001020304" [IBMTRDB1_MOD] 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. EXPLANATION: The value provided for the keyword in the IBMTRDB module in the PROTOCOL.INI file is not the correct type. ACTION: Correct 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. EXPLANATION: An internal software error occurred. ACTION: Contact your vendor sales representative. ----------------------------------------------------------------------------- LT60010E: ALL IBM LANSTREAMER ADAPTERS MUST BE SET TO THE SAME INTERRUPT LEVEL. EXPLANATION: 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. 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'. EXPLANATION: The universally administered address of the adapter installed in the computer is displayed in this message. ACTION: None. ----------------------------------------------------------------------------- LT60012I: THE IBM LANSTREAMER ADAPTER IS USING A LOCALLY ADMINISTERED ADDRESS OF 'ADDRESS'. EXPLANATION: The locally administered address for the IBM LANStreamer adapter installed in the computer is displayed in this message. ACTION: None. ----------------------------------------------------------------------------- LT60014E: THE PARAMETER VALUES HAVE FORCED THE CONTROL-BLOCK SIZE TO EXCEED THE ALLOWABLE LIMIT. EXPLANATION: 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 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) + (32 * MINRCVBUFFS) The control-block work area must be less than 64KB. ----------------------------------------------------------------------------- LT60015E: THE ADAPTER IS NOT RESPONDING. EXPLANATION: The adapter is not responding to a request to initialize. ACTION: Run the hardware diagnostics for the IBM LANStreamer Adapter. Contact your vendor sales representative. ----------------------------------------------------------------------------- LT60025W: DUPLICATE DEVICE DRIVER STATEMENTS EXIST IN CONFIG.SYS. EXPLANATION: 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. ACTION: Remove the duplicate device driver statements from CONFIG.SYS. ----------------------------------------------------------------------------- LT60026E: THE REQUIRED PARAMETER DRIVERNAME WAS NOT FOUND IN PROTOCOL.INI. EXPLANATION: 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. ----------------------------------------------------------------------------- LT60027E: THE PROTOCOL MANAGER COULD NOT BE OPENED. EXPLANATION: An unexpected error occurred when the program attempted to open the protocol manager. The IBM LANStreamer Adapter NDIS MAC device driver has been removed. 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. EXPLANATION: The device driver was unable to register with the protocol manager. ACTION: Reinstall the protocol manager and try the operation again. ----------------------------------------------------------------------------- LT60029E: NO PHYSICAL ADAPTER WAS FOUND IN THIS MACHINE. EXPLANATION: There was no adapter found in this machine. An IBM LANStreamer Adapter is required to run the MAC device driver. 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. EXPLANATION: An unrecognized parameter was found while processing the IBM LANStreamer Adapter section of PROTOCOL.INI. 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. EXPLANATION: 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 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#'. EXPLANATION: The version of the IBM LANStreamer device driver that is loaded into memory is displayed in this message. ACTION: None. ----------------------------------------------------------------------------- LT60033E: A DUPLICATE NETWORK ADDRESS WAS FOUND WHILE INSERTING ONTO THE RING. EXPLANATION: 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. ----------------------------------------------------------------------------- LT60034E: RING FAILURE OR BEACONING WAS ENCOUNTERED WHILE INSERTING ONTO THE RING. EXPLANATION: 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. ----------------------------------------------------------------------------- LT60035E: A HARDWARE FAILURE OCCURRED WHILE ATTEMPTING TO OPEN THE ADAPTER. EXPLANATION: 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 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. EXPLANATION: 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). ----------------------------------------------------------------------------- LT60039I: INITIALIZATION STARTING FOR SECTION 'SECTION NAME' IN PROTOCOL.INI. EXPLANATION: The IBM LANStreamer NDIS device driver is processing the named section of the PROTOCOL.INI file that is displayed in this message. ACTION: None. ----------------------------------------------------------------------------- LT60044E: THE CONFIGURATION VALUES HAVE FORCED THE CONTROL-BLOCK SIZE TO EXCEED THE AVAILABLE MEMORY. EXPLANATION: The configuration parameters specified require more space for for processing than can be handled with the available system memory. 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 SIZWORKBUFF The control block area for each adapter can be computed using the following formula and must be less than 64KB. ALLOCSIZECB = 1698 + (190 * MAXTRANSMITS) + (32 * MINRCVBUFFS) ------------------------------------------------------------------------------- IBM is a trademark of IBM, Inc. Novell is a trademark of Novell, Inc. Netware is a trademark of Novell, Inc. "IBM LANStreamer MC 32 Adapter" is a trademark of IBM, Inc.