T1108 NDIS 2 DOS and OS/2 drivers installation for MS LAN Manager, and IBM LAN Server TR2KNDIS Drivers To use TR2KNDIS.DOS or TR2KNDIS.OS2, install the appropriate network subsystem hardware and execute the following step: 1. Follow the Microsoft LAN Manager or IBM LAPs installation procedures described in the following section. ---------------------------------------------------------------------- Installing TR2KNDIS for LAN Manager ---------------------------------------------------------------------- Microsoft LAN Manager 2.0 Installation Follow the installation instructions in the LAN Manager Installation Guide. The "Importing Additional Network Device Drivers" section describes the process of loading the drivers, and the "Network Drivers Dialog Box" section describes how to specify which drivers to use. Microsoft LAN Manager 1.0 Installation Install LAN Manager as described in the LAN Manager Installation Guide, if you have not already done so. Then perform the following steps to install the T1108 16/4 Token- Ring adapter drivers for LAN Manager. 1. Copy the appropriate driver, TR2KNDIS.OS2 or TR2KNDIS.DOS, from the "T1108 Driver Set" diskette to the desired fixed disk drive and directory. Also copy the message file TR2KNDIS.MSG if installing under OS/2. 2. Add the following line to the CONFIG.SYS. DEVICE=[drive:directory]TR2KNDIS.OS2 or DEVICE=[drive:directory]TR2KNDIS.DOS This line should be entered immediately following the line which installs the PROTMAN.OS2 or PROTMAN.DOS device driver. NOTE: You must specify a DPATH in CONFIG.SYS to the subdirectory containing the TR2KNDIS.MSG file to enable driver error messages and alleviate the "Cannot find message file" error at boot time. 3. Add the following section to PROTOCOL.INI [TR2KNDIS_NIF] DriverName = TR2NDS$ 4. Add TR2KNDIS_NIF to the bindings list of the protocol in the PROTOCOL.INI. An example protocol section follows. [NETBEUI_XIF] DriverName = NETBEUI$ Bindings = TR2KNDIS_NIF ---------------------------------------------------------------------- Installing TR2KNDIS for IBM LAN Server ---------------------------------------------------------------------- Automatic Installation This driver supports the automatic installation procedure defined by the IBM LAN Adapter and Protocol Support (LAPS) module. LAPS is provided by IBM with the following services: IBM OS/2 Extended Services 1.0 IBM OS/2 LAN Server 2.0 IBM OS/2 LAN Requester 2.0 Manual Installation 1. Copy the driver TR2KNDIS.OS2, and the message file TR2KNDIS.MSG from the installation diskette to the desired fixed disk drive and directory. 2. Add the following line to the CONFIG.SYS. DEVICE=[drive:directory]TR2KNDIS.OS2 This line should be entered immediately following the line which installs the PROTMAN.OS2 device driver. NOTE: You must specify a DPATH in CONFIG.SYS to the subdirectory containing the TR2KNDIS.MSG file to enable driver error messages and alleviate the "Cannot find message file" error at boot time. 3. Add the following section to PROTOCOL.INI [TR2KNDIS_NIF] DriverName = TR2NDS$ 4. Add TR2KNDIS_NIF to the bindings list of the protocol in the PROTOCOL.INI. An example protocol section follows. [NETBEUI_XIF] DriverName = NETBEUI$ Bindings = TR2KNDIS_NIF ---------------------------------------------------------------------- PROTOCOL.INI Keywords Supported by TR2KNDIS ---------------------------------------------------------------------- The PROTOCOL.INI file defines the configuration of protocol and NDIS drivers. The following table summarizes the TR2KNDIS keywords. For additional information about the PROTOCOL.INI file and network device drivers, refer to the Microsoft LAN Manager Network Device Driver Guide. 旼컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴쩡컴컴컴컴컫컴컴컴컴커 � Parameter � Range � Default � Default � � � � DOS � OS/2 � 쳐컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴탠컴컴컴컴컵컴컴컴컴캑 � DRIVERNAME � TR2NDS$ or TR2NDSn$ � Required � Required� � PORT � See description. � 0xA20 � 0xA20 � � INT � 2 - 12 � 2 � 9 � � SPEED � 4 or 16 � 16 � 16 � � BIT16 � � - � - � � WS0 � � - � - � � MAXTRANSMITS � 3 - 50 � 3 � 6 � � NUMRECEIVEBUFFERS � 3 - 100 � 3 � 6 � � RECEIVEBUFFERSIZE � 256 - 17960 � 2048 � 2048 � � NOEARLYRELEASE � � - � - � � NETADDRESS � "000000000000"-"7FFFFFFFFFFF"� BIA � BIA � 읕컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴좔컴컴컴컴컨컴컴컴컴켸 DRIVERNAME Identifies the network device driver. The DRIVERNAME is TR2NDS$ for the first driver and TR2NDS2$ for the second, and so on. This parameter is required. PORT If no PORT is specified, the driver will assume the default address. Valid addresses are 0xA20 and 0xA40. This parameter is required when multiple adapter support is desired. INT Selects the interrupt (IRQ) value to use for communication with the adapter. This parameter is required when multiple adapter support is desired. SPEED Sets the speed at which the adapter is to open onto the ring. BIT16 Directs the driver to do 16-bit Pseudo DMA I/O at the base IOADDRESS plus 0x10 register. This provides a performance enhancement. This entry is not followed by an equal sign. BIT16 and WS0 are mutually exclusive. WS0 Directs the driver to do 8-bit Pseudo DMA I/O at the base IOADDRESS plus 0x10 register. This provides a performance enhancement This entry is not followed by an equal sign. WS0 and BIT16 are mutually exclusive. MAXTRANSMITS Sets the number of transmits that can be queued simultaneously by the driver. NUMRECEIVEBUFFERS Sets the number of receive buffers to allocate. RECEIVEBUFFERSIZE Sets the size of buffers used to queue received frames in the driver. Several buffers may be required to queue a large frame. Performance is improved if a received frame fits in one buffer. Use the following formula to determine maximum frame size. MediaMaxSize equals 17960 @ 16 Mbps, or 4490 @ 4 Mbps. MaxFrameSize = min(min(8, NumReceiveBuffers) x ReceiveBufferSize, MediaMaxSize) NOEARLYRELEASE This entry informs the driver to disable early token release. Early token release reduces the average time another network adapter must wait to transmit a frame. This entry is not followed by an equal sign. NETADDRESS This entry allow the driver to override the burned in address (BIA). The entry must be a 12 character string of hexadecimal digits, and must be enclosed in quotes. NOTE: Unpredictable results will occur if adapter hardware settings do not match parameter or default values. Unpredictable results will also occur if parameters are specified on adapters that do not support that particular feature. For example, the following is a sample PROTOCOL.INI file: [TR2KNDIS_NIF] DRIVERNAME = TR2NDS$ PORT = 0xA20 MAXTRANSMITS = 10 NUMRECEIVEBUFFERS = 12 RECEIVEBUFFERSIZE = 1024 NETADDRESS = "400000000312" BIT16 SPEED = 4