INSTALLING THE DRIVER ===================== This file contains the installation procedures for the Auto 16/4 PnP Token-Ring Adapter drivers with various network software. 1. Installing Drivers Under a Novell NetWare Environment 1.1 Installing the NetWare Server LAN Driver ........................... 2 1.2 Installing the ODI Client Driver in DOS ............................ 4 1.3 Installing the ODI Driver in OS/2 .................................. 6 2. Installing Drivers Under a Microsoft Windows Environment 2.1 Installing Drivers in Windows 95 ................................... 7 2.2 Installing NDIS 3.0 MAC Drivers in Windows NT ...................... 8 2.3 Installing NDIS 2.0 and NDIS 3.0 MAC Drivers in Windows for Workgroups .......................................... 9 3. Installing Drivers in IBM OS/2 LAN Server 2.0, 3.0 and 4.0 Server and DOS LAN Requester 3.1 Installing Drivers in IBM OS/2 LAN Server 2.0 Server ...............10 3.2 Installing Drivers in IBM OS/2 LAN Server 3.0 Server ...............11 3.3 Installing Drivers in IBM OS/2 LAN Server 4.0 Server ...............12 3.4 Installing Drivers in IBM OS/2 LAN Server 2.0/3.0 DOS LAN Requester 13 3.5 Installing Drivers in IBM OS/2 LAN Server 4.0 DOS LAN Requester ....15 4. Installing Drivers with LSP and others 4.1 Installing NDIS 2.0 MAC Drivers LSP Custom in DOS, OS/2 with LAPS, Other DOS Stations and Other OS/2 Stations .........................16 4.2 Installing LSP Custom with DXMAID ..................................20 4.3 Installing LSP Custom ..............................................21 5. Solving Driver Installation Problems ..................................22 5.1 Driver Installation Messages .......................................23 5.2 NDIS MAC Driver Messages ...........................................25 5.3 Novell NetWare Server Driver Messages ..............................27 5.4 Novell NetWare Client with DOS Driver Messages .....................28 5.5 Novell NetWare Client with OS/2 Driver Messages ....................30 --Page 1-- 1.1 INSTALLING THE NETWARE SERVER LAN DRIVER ============================================== Driver directory: \NOVELL\NETWARE Note: If this adapter is the first on the Token-Ring, Auto sense must be set to OFF and the correct data rate must be chosen manually. 1. For Novell Netware 3.11; copy the following files from the "Device Drivers" diskette \NOVELL\NETWARE subdirectory to the directory containing the SERVER.EXE file, usually C:\SERVER. LSLENH.NLM MSM31X.NLM PATCHMAN.NLM TOKEN.LAN TOKENTSM.NLM For Novell Netware 3.12 and 4.x; copy the following files from the Disk 2 \NOVELL\NETWARE subdirectory to the directory containing the SERVER.EXE file, usually C:\SERVER.312, C:\NWSERVER. MSM.NLM TOKEN.LAN TOKENTSM.NLM 2. Start the server by typing "SERVER" from the directory containing the SERVER.EXE file. 3. Steps 3 to 7 describe how to configure the server to load the LAN driver automatically each time the server is started. If you don't want to load the LAN driver automatically everytime, you only need to type in the commands listed in step 6 from the NetWare Operating System console prompt (:). 4. From the NetWare Operating System console prompt (:) type "load install" and press . 5. Go to the System Options panel under Installation Options. Select AUTOEXEC.NCF if there is one, otherwise create one. 6. In the AUTOEXEC.NCF file, add the following statements. For NetWare 3.11 the statements are: (The path C:\SERVER can be changed to whatever you actually use.) MOUNT ALL LOAD C:\SERVER\PATCHMAN.NLM LOAD C:\SERVER\LSLENH.NLM LOAD C:\SERVER\TOKEN.LAN PORT=A20 BIND IPX TO TOKEN NET=1 For higher levels of NetWare the statements are: MOUNT ALL LOAD C:\SERVER\TOKEN.LAN PORT=A2O BIND IPX TO TOKEN NET=1 Note: TOKEN.LAN will automatically load the MSM.NLM or MSM31X.NLM and the TOKENTSM.NLM modules. --Page 2-- 7. Restart the server program to load the drivers. Look for messages indicating that the LAN driver, TOKEN.LAN, and the NetWare modules are installed. If the messages indicate that the driver and modules are installed, the adapter is configured. LAN Driver Parameters --------------------- FRAME -- This parameter indicates the Token-Ring frame type to be used by the LAN driver and network adapter. Default value: Token-Ring Valid values: Token-Ring, Token-Ring_SNAP PORT -- The port address for a primary network adapter is hex A20. The port address for an alternate network adapter is hex A24. Default value: A20 Valid values: A20, A24 NODE -- Use this parameter to specify a locally administered address for the Auto 16/4 PnP Token-Ring Adapter. The adapter can be known on the network by its universally administered address (the address encoded in the adapter memory at the factory) or a locally administered address (a unique user-assigned address). The universally administered address can be seen when executing the configuration utility. The value of the locally administered address must be unique among the addresses on the network and contain 12 hexadecimal digits. Default value: Universally administered address. Valid values: X"400000000000" to X"7FFFFFFFFFFF" immediately followed by one of the following address format indicators: M indicates that the address is in Most Significant Bit (MSB) first format. M is the default address format indicator. L indicates that the address is in Least Significant Bit (LSB) first format. --Page 3-- 1.2 INSTALLING THE ODI CLIENT DRIVER IN DOS ============================================== Driver directory: \NOVELL\DOS The following steps describe the incorporation of the driver into an existing ODI workstation. 1. Find the target directory path where the NetWare DOS ODI Shell or the NetWare Requester code is installed, for example,C:\NWCLIENT. 2. Copy all the files to the target directory from the \NOVELL\DOS subdirectory on the disk2 diskette. 3. Find the batch file that initialed the ODI Shell or NetWare Requester, for example, STARTNET.BAT in C:\NWCLIENT, that contains the following commands: LSL ...driver... IPXODI Replace the "...driver..." with TOKEN.COM (copied in Step 2). 4. To change the TOKEN.COM driver parameter default values, edit the NET.CFG file. See the following example, or the NetWare 4.0 Workstation for DOS and Windows, for a sample NET.CFG file. Copy the edited NET.CFG file to the target directory. Link Driver TOKEN FRAME TOKEN-RING PORT A2Oh TOKEN.COM Driver Parameters ---------------------------- NODE ADDRESS -- To set a locally administered address for the adapter type in the local address you want to use. The local address must contain 12 hexadecimal characters and can be specified in either MSB (the default), or LSB (Least Significant Bit) format. To specify an MSB node address, the letter 'M' immediately follows the last digit of the node address. To specify an LSB node address, the letter 'L' immediately follows the last digit of the node address. If a node address is specified in MSB format, the characters must be within the range X"400000000000" -X"7FFFFFFFFFFF". To specify a node address in MSB format, append an'M' to the end of the address (for example, X"400000000001M"). This address specified in LSB format would be X"020000000080L". --Page 4-- PORT -- The port address for a primary network adapter is A20 hex. The port address for an alternate network adapter is A24 hex. This keyword and value are only necessary to identify a particular adapter when using more than one Auto 16/4 PnP Token-Ring Adapter under DOS. It is also necessary to identify an alternate adapter under OS/2. Default Value: A20 Valid Values: A20, A24 FRAME -- This parameter indicates the Token-Ring frame type to be used by the LAN driver and network adapter. Default value: Token-Ring Valid values: Token-Ring, Token-Ring_SNAP MAX FRAME SIZE -- This option sets the maximum number of bytes that can be put on the wire by the Auto 16/4 PnP Token-Ring Adapter. The number must be a multiple of 8 and include a number of bytes for adapter overhead (6 bytes) and for the maximum header (35 bytes LAN header + 5 bytes SNAP header + 74 bytes protocol header). The total number of bytes is 114. If the LAN speed is 16 Mbps, the number must be between 632 and 17960. If the LAN speed is 4Mbps, the number must be between 632 and 4464. If 2 KB packets are desired, calculate the maximum frame size as: 2048 + 6 + 35 + 5 + 74 = 2168 (rounding up to next multiple of 8 gives 2168) An example NET.CFG entry for using 2-KB packets would appear as: LINK DRIVER TOKEN MAX FRAME SIZE 2168 To set frame sizes greater than 1540 bytes, in an OS/2 environment, you must configure LSL buffers equal to or greater than the frame size you desire. To configure the adapter to handle 4210-byte frames, use this statement in your NET.CFG file: LINK SUPPORT BUFFERS 34 4210 --Page 5-- 1.3 INSTALLING THE ODI DRIVER IN OS/2 ======================================== Driver directory: \NOVELL\OS2 To install the driver on an OS/2 workstation, perform the following steps: 1. Copy the TOKEN.SYS file to the directory containing OS/2 requester, e.g. C:\NETWARE. 2. Add the following lines to the CONFIG.SYS file (if not already present): DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE DEVlCE=C:\NETWARE\TOKEN.SYS REM Add ROUTE.SYS only if Source Routing is needed. DEVICE=C:\NETWARE\ROUTE.SYS DEVICE=C:\NETWARE\IPX.SYS 4. If you need to change any TOKEN.SYS driver parameter values from the defaults, edit the NET.CFG file to change only those parameters. Refer to the parameters in "Installing the ODI Client Driver in DOS". --Page 6-- 2.1 INSTALLING DRIVER FOR WINDOWS 95 ====================================== 1. Plug the PnP adapter into an empty slot. 2. Power on Windows 95. 3. A "New Hardware Found" screen will display. "Auto 16/4 PnP Token-Ring Adapter" found. 4. One second later, Another "New Hardware Found" screen will display. "IBM Auto 16/4 ISA Token-Ring Adapter" found. 5. The driver will be loaded automatically. 6. Follow the screen instructions to finish the installation. -Page 7-- 2.2 INSTALLING DRIVERS IN WINDOWS NT ====================================== Driver directory: \NT Refer to the Microsoft Windows NT System Guide, document No. 36327-0593, for the general procedure for installing network drivers in Windows NT. The main points are summarized here: 1. Log on as an administrator. 2. Double click the "Main" Group icon. 3. Double click the "Control Panel" icon. 4. Double click the "Network" icon. 5. Click the "Add Adapter" button. 6. Select " Requires disk from manufacturer", (This should be the last selection) and then click "Continue". 7. A panel prompts you to insert a diskette. Insert Disk 2 in the A: drive. Type A:\NT and then press . Click . 8. Select "IBM Auto 16/4 Token-Ring ISA Adapter". Click . Several work-in-progress panels display, indicating that the driver and its supporting files are being copied to your computer's hard disk. 9. A dialog box will prompt you to enter the network address. If you are using a locally administered address, enter it in this field. If you do not enter a network address, the driver uses the adapter's universally administered address. When you have modified all the required parameter values, click . lO. The Network Setting panel will display again. This time there should be an entry for the adapter you just added in the "Installed Adapter Cards" list box. 11. Click at the top right to complete the installation. You will be prompted to turn OFF and then turn ON the computer. To allow the program to do this for you, respond "YES" to the prompt. Windows NT will automatically restart your computer. When the system has started again, you will be able to log on and use the PnP Token-Ring adapter. --Page 8-- 2.3 INSTALLING NDIS 2.0 AND NDIS 3.0 MAC DRIVERS IN WINDOWS FOR WORKGROUPS ============================================================================ Driver directory: \WFW The NDIS 2.0 or NDIS 3.0 MAC device drivers can be installed in a Microsoft Windows for Workgroups environment. To do so, perform these steps: 1. Open the "network" group and double-click on the "Network Setup" icon. 2. Click on the "Drivers" button at the bottom of the Network Setup dialog box. If the Drivers button is unavailable, click on the Network button and then install the network. 3. Click on "Add Adapters" in the Network Drivers dialog box. 4. Select "Unlisted or Updated Network Adapter" from the "Add Network Adapter" dialog box and click . 5. The Install Driver dialog box is displayed with the A:\ prompt. Insert Disk 2 in A: drive; click . 6. Select either the NDIS 2.0 or NDIS 3.0 device drivers from the list and click . 7. It necessary, click "Setup" in the Network Drivers dialog box to configure the selected device driver. --Page 9-- 3.1 INSTALLING DRIVERS IN THE IBM OS/2 LAN SERVER 2.0 SERVER ============================================================== Driver directory: A:\ 1. Copy the IBMTOK.OS2 and IBMTOK.NIF files from Disk 2 to C:\IBMCOM\MACS. 2. Click the "LAN Services" icon. 3. Select "OS/2 LAN Services Installation/Configuration". The IBM logo should appear. 4. Click . 5. Select "Advance" and press . 6. Select "Install or Configure this Workstation". 7. Select server type then the "install or remove" selections should appear. 8. Select "Configure a Component". 9. Select "LAN Adapter and Protocol Support". Click the "Configure" button. 10. Select "Configure Workstation". 11. Select "IBM T-R Shared RAM Family (UP/SMP, IBMTOK.OS2)" when prompted to identify your Network Adapter. Then click the button. 12. Select IBM OS/2 NETBIOS and IBM IEEE 802.2 protocols from the list and click the button. 13. Select to confirm all selections. 14. Follow the screen instructions to complete the process, clicking to accept default selections. 15. Continue pressing until your screen prompts you to backup the old CONFIG.SYS and AUTOEXEC.BAT and create a new CONFIG.SYS and AUTOEXEC.BAT. Click to confirm this. 16. Installation is now complete. Reset your PC by turning it off and on. --Page 10-- 3.2 INSTALLING DRIVERS IN IBM OS/2 LAN SERVER 3.0 SERVER =========================================================== Driver directory: A:\ 1. Installation 1) Install your LAN Server network system on your hard disk. 2) At the C:\IBMCOM prompt, type "LAPS" and press 3) Select "Install" and insert Disk 2, which includes the NDIS driver for IBM LAN Server 3.x, to any floppy drive, e.g. A:, to install the driver. 4) When prompted to specify the source of the network information file (.NIF files) for the adapter drivers you want to install, type "A:" and click . 5) When the "Installation Complete" window appears, click . 2. Configuration 1) When the main screen appears, click "Configure". 2) When the "Configuration" window is displayed, click "Continue", The "Configure workstation" window will appear. 3) Select "IBM T-R Shared RAM Family(UP/SMP, IBMTOK.OS2)" when prompted to identify your Network Adapter. Click the button. 4) Select IBM OS/2 NETBIOS and IBM IEEE 802.2 protocols from the list and click the button. 5) Click to save changes, or select "Cancel" to exit without saving. 6) Click to return to the main menu. 7) Click to exit. The configuration utility will update your CONFIG.SYS automatically. Follow the screen instructions to complete the process. 8) Installation is now complete. Reset your PC by turning it off and on. --Page 11-- 3.3 INSTALLING DRIVERS IN IBM OS/2 LAN SERVER 4.0 SERVER =========================================================== Driver directory: A:\ 1. In the OS/2 window, Click the "MPTS" icon. 2. The screen will display the IBM Logo, click . 3. Click the "Install" button. 4. Insert Disk 2, specify the driver path "A:" and press . 5. Click the "Install" button, then the "Configure" button. 6. The screen will display the "Configure" dialog box. Select "LAN adapters and protocols" then click the "configure" button. 7. The screen will display the "LAPS Configuration" dialog box. Highlight the "IBM T-R Shared RAM Family (UP/SMP, IBMTOK.OS2)" item in the "Network Adapter" window, and select IBM OS/2 NETBIOS and IBM IEEE 802.2 protocol. Click . 9. Installation is now complete. Reset your PC by turning it off and on. --Page 12-- 3.4 INSTALLING DRIVERS IN IBM OS/2 LAN SERVER 2.0/3.0 DOS LAN REQUESTER ========================================================================== Driver directory: \DOS 1. Insert the IBM LAN Supprot Program (LSP version 1.30 (or later) diskette into floppy drive A: . Make A: the current drive then type "dxmaid" and press . 2. The screen will display the IBM logo. Press twice. The "Environment Information" screen will appear. 3. Respond to the screen prompts, specifying the following values for each field. Use the to toggle between choices: Are you updating an existing configuration? Yes Do you have driver diskettes? Yes Type changes as needed to the information below: Target for LSP: C:\LSP CONFIG.SYS to update: C:\CONFIG.SYS AUTOEXEC.BAT to update: C:\AUTOEXEC.BAT Make sure that the values given above are correct, then press to store your choices. 4. Insert Disk 2 into floppy drive A:, specify the pathname as A:\DOS, then press . 5. Follow the screen instructions to complete the process. Simply pressing for each screen display will select the default options. 6. Press until a screen showing the current configuration detected is displayed. It should show the "IBM T-R Shared RAM Family" and the protocols already selected (i.e., "IBM IEEE 802.2" and "IBM OS/2 NETBIOS"). 7. Press . to save the new configuration. This completes the LSP installation. 8. Save the configuration and reboot your computer. 9. Insert the DOS LAN Requester Installation Diskette 1 into your floppy drive. 10. Type A:\INSTALL --Page 13-- 11. The IBM logo will again appear on the screen. Press to move on to the next screen. 12. Follow the screen instructions, pressing to move from screen-to-screen until you are prompted to indicate the pathname of the DOS LAN Requester directory (C:\DOSLAN ). 13. Specify the pathname (C:\DOSLAN is the default) for the DOS LAN Requester directory . Then press to continue. 14. The program will ask you for the services that you require. 15. Highlight the appropriate option. Select either the "Send messages" or the "Send, View, Edit, and Log message" option. (Normally, the second option "Send, View, Edit and Log message" is selected). 16. Specify the PC's ID and domain ID. 17. Follow the screen prompts to complete the installation. --Page 14-- 3.5 INSTALLING DRIVERS IN IBM OS/2 LAN Server 4.0 DOS LAN Requester ===================================================================== Driver directory: A:\ 1. Insert the "DOS LAN Service" diskette in A: and type "install". 2. Enter the path where the files will be installed. 3. Enter the "Machine IC", "User name" and "Domain name". 4. The screen display some description. If it's correct; move highlight to "The listed options are correct" item, then press . 5. Move highlight to "Network Card", then press . 6. Select "Change driver for network card" item, then press . 7. Select "Network card not shown in list below ...", and then press . 8. Insert Disk 2 and enter path A:\ . 9. When "IBM Token-Ring Network Adapter, NDIS2 only" is displayed, press to continue. 10. Check that the settings are correct and follow the instructions on the screen to complete the installation. --Page 15-- 4.1 INSTALLING NDIS 2.0 MAC DRIVERS FOR LSP CUSTOM WITH DOS, OS/2 WITH LAPS, OTHER DOS STATIONS AND OTHER OS/2 STATIONS ============================================================================== DOS -- Driver directory : \DOS OS/2 -- Driver directory : \ 1. Copy the DOS or OS/2 NDIS 2.0 MAC driver files from Disk 2 to the directory on the computer that contains the files for the computer's network operating system or network application. Those files include an NDIS-compliant protocol driver. Examples of protocol drivers are the LAPS IEEE 802.2 NDIS 2.0 protocol driver (LANDD), and the IBM TCP/IP Version 2.1 for DOS driver (DOSNDIS). - For DOS: copy all the files from the \DOS directory on Disk 2. - For OS/2: copy the following files from the root directory on Disk 2. IBMTOK,OS2 IBMTOK.NIF LT2.MSG LT2H.MSG 2. Edit the CONFIG.SYS file in the root directory. Add a device statement to start the NDIS 2.0 MAC driver, or if you are using two adapters, add two device statements (see "Supporting Two Adapters with IBMTOK.OS2" ). Place the statements after the device statement for the Protocol Manager (PROTMAN.DOS or PROTMAN.OS2: DEVICE=C:\ ..path.. \IBMTOK.DOS DEVICE=C:\ ..path.. \IBMTOK.OS2 3. Verify that the CONFIG.SYS file does not contain the following statement: STACKS= 0,0 Use the system"s default allocation as the minimum. 4. Locate the PROTOCOL.INI file. The file is in the path specified after the /i: parameter in the Protocol Manager (PROTMAN) statement in the CONFIG.SYS file. If there is no /i: parameter in the Protocol Manager statement, check the LANMAN directory for the PROTOCOL.INI file. 5. Edit the PROTOCOL.INI file. See the following examples of PROTOCOL.INI files for DOS or OS/2. See the following explanations of the PROTOCOL.INI parameters supported by the Auto 16/4 PnP Token-Ring Adapter NDIS 2.0 MAC drivers. --Page 16-- [TOK_MOD] Drivername = IBMTOK$ NetAddress = "400001020304" RAM = 0XD400 MaxTransmits = 6 RecvBufs = 2 RecvBufsize = 256 Xmitbufs = 1 Xmitbufsize = 2040 You must bind the protocol drivers to the NDIS 2.0 MAC device driver. Edit the BINDINGS = statement of those protocol drivers. For example: [PROTOCOL_DRIVER] Bindings = TOK_MOD Parameters for the Auto 16/4 PnP Token-Ring Adapter PROTOCOL.INI File ----------------------------------------------------------------------- EarlyRelease -- This parameter specifies the Early Token Release option for Token-Ring adapters. This option allows the adapter to release a new token as soon as it has received the header of its previously sent frame and thus reduces the average time that another adapter must wait to gain access to the network. Adapters that do not support the Early Token Release option ignore this parameter. The default for adapters is to enable Early Token Release. RAM -- This parameter only applies to Auto 16/4 PnP Token-Ring Adapters without the Plug and Play capability. This parameter specifies the physical RAM location on the network adapter if the default location is not adequate. The specified location must not conflict with the address of any adapter configured and installed in the workstation. The recommended RAM addresses for this field are X'D800' for the Primary adapter and X'D400' for the Alternate adapter. MaxTransmits -- This parameter specifies the maximum number of transmit- queue entries for the adapter driver. For a server or gateway station, set this parameter to the result of multiplying the Maximum Transmits Outstanding parameter by the Maximum Sessions parameter (these are NetBIOS parameters). The value must be a decimal number between 6 and 50; the default is 6. RecvBufs -- This parameter specifies the minimum number of receive buffers to be configured in the memory of the adapter. Any memory remaining after other storage requirements have been satisfied will be configured as additional receive buffers. If you specify too many buffers, the adapter will not open. The value specified must be a decimal number between 2 and 60; the default is 2. --Page 17-- RecvBufSize -- This parameter specifies the length of the data portion of each receive buffer adapter memory. The value specified must be a decimal number between 256 and 2040 and must be divisible by 8; the default is 256. XmitBufs -- This parameter specifies the number of transmit buffers to be configured in adapter memory. Configuring a second transmit buffer may improve transmission performance but it reduces the amount of memory available for storing received frames. The value must be a decimal number between 1 and 16; the default is 1. XmitBufSize -- This parameter specifies the length of the transmit buffers in adapter memory and limits the maximum size frame that can be transmitted. Set the parameter to the size of the largest frame that will be transmitted: - If the ring speed is 4 Mbps, the XmitBufSize = 4096. - If the ring speed is 16 Mbps, the XmitBufSize = 17952. If you set the value too high, the adapter will not open. The value specified must be a decimal number between 256 and 17952 and must be divisible by 8; the default is 2040. Adapter -- This parameter identifies the network adapter card (OS/2 only) assignment if more than one Token-Ring network adapter resides in the workstation. A value of PRIMARY denotes the first Token-Ring network adapter. A value of ALTERNATE denotes the second Token-Ring adapter. Alternate -- If two token ring adapters are installed in the same (DOS only) workstation, this parameter identifies the second adapter. If you have only one adapter or are configuring for the first adapter, do not include this keyword in the list of keywords and parameters for this adapter. If you are configuring for the second adapter, include this keyword in the list of keywords and parameters for the second adapter. NetAddress -- This parameter overrides the network address of the network adapter. The value of this parameter is a hexadecimal string of 12 digits (not including the quotes), such as NetAddress = "400000102004". The range is from 400000000000 to 7FFFFFFFFFFF. The address must be unique among all other network adapter addresses on the network. Specify the network adapter address in the token ring network format. --Page 18-- Supporting Two Adapters with IBMTOK.OS2 ---------------------------------------- When two PnP Token-Ring Adapters are installed in the same system there must be one DEVICE = C:\..path..\statement in the CONFIG.SYS file for each PnP Token-Ring Adapter in the computer and two NDIS MAC device driver sections in the PROTOCOL.INI file. See the following examples: - CONFIG.SYS: DEVICE=C:\..path..\IBMTOK.OS2 DEVICE=C:\..path..\IBMTOK.OS2 - PROTOCOL.INI: [TOK_MOD] Drivername = IBMTOK$ NetAddress = "400001020304" [TOK2_MOD] Drivername = IBMTOK2$ [PROTOCOL_DRIVER_ABC] Bindings = TOK_MOD, . . . , TOK2_MOD --Page 19-- 4.2 INSTALLING LSP CUSTOM WITH DXMAID ======================================= Driver directory: \LSP 1. Insert Disk 2 in the diskette drive. Make the diskette drive the current drive and change the directory to the \LSP subdirectory. 2. Type "DXMAID" and press . 3. Select the responses and type in the requested information on the first Installation Aid panel. Press to continue. Note: If you need more information about a field, place the cursor on the field and press for help. To obtain additional help, press F1 from the help panel. For more information, refer to the LSP Custom User's Guide. 4. In the second panel, to add or remove LSP Custom drivers, position the cursor in the field for the driver and press . 5. Press to view or change the driver parameters. If you do not make any changes, default drivers with default parameter values will be installed. Note: To see a description of one of the parameters, select the value of the parameter in the "Parameter Selection" panel and press . 6. To install the drivers and complete the installation of LSP Custom. press . When the installation is complete, you will be returned to DOS. Note: During this process LSP Custom will be copied to your target disk, so that you do not need the original or a backup copy for daily operation. Keep the original diskettes in a safe place in case you need them to change your configuration or reinstall. 7. Press Ctrl+Alt+Del to restart the computer. A copyright statement will display. If there are no messages, or if there are only information messages, LSP Custom is correctly loaded. If any error messages display, LSP Custom may not be installed correctly. If no LSP Custom copyright statement displays, LSP Custom is not installed, or has been removed. In this case, make a new backup copy and reinstall the program. For problem-solving information refer to the LAN Support Program Custom User's Guide. --Page 20-- 4.3 Installing LSP Custom =========================== Driver directory: \LSP If you want to install the LSP Custom Program manually, take the following steps: 1. Insert Disk 2 in drive A:. 2. Create a directory where you want the LSP files to be copied. Copy all the program files for LSP Custom from Disk 2 \LSP directory. E.g. C: MD \LSP COPY A:\LSP\*.* C:\LSP 3. Edit the CONFIG.SYS to load the drivers. Edit the CONFIG.SYS file to include the following lines: DEVICE=\LSP\DXMA0MOD.SYS DEVICE=\LSP\DXMC0MOD.SYS If you plan to use the NetBIOS interface provided by the DXMT0MOD.SYS, include the statement: DEVICE=\LSP\DXMTBMOD. SYS These statements can be listed anywhere in the CONFIG.SYS, but must be listed in the order as shown. 4. Restart the computer to activate LSP Custom. Your application program, such as DOS LAN Requester, should now be able to use LSP for communication. --Page 21-- 5. SOLVING DRIVER INSTALLATION PROBLEMS ========================================== Use this procedure if you are having problems starting the Auto 16/4 PnP Token-Ring adapter drivers. 1. Ensure that you performed the installation procedures correctly. 2. In Table 5-1, locate the row that describes the network operating system or network application on the computer and perform the recommended actions. --Page 22-- 5.1 DRIVER INSTALLATION MESSAGES ================================== Table 5-1 Driver lnstallation Messages ------------------------------------------ Environment Message Type and Action NetWare - Message prefix TOKEN: see "Novell NetWare Server Driver Messages" for messages pertaining to this adapter. Refer to the online manual NetWare System Messages for explanations and recommended actions for any messages not listed. - NetWare messages: refer to the online manual NetWare System Messages to determine the appropriate action. NetWare Client - Message prefix TOKEN: see "Novell NetWare Client with with DOS DOS Driver Messages" for messages relating to this adapter. Refer to the online manual NetWare System Messages for explanations and recommended actions for any messages not listed. NetWare Client - Message prefix TOKEN: see "Novell NetWare Client with with OS/2 OS/2 Driver Messages" for messages relating to this adapter. Refer to the online manual NetWare System Messages for explanations and recommended actions for any messages not listed. LSP Custom - If the LSP Custom copyright statement did not display, with DOS go to "Manually Installing LSP Custom" to repeat the procedure. LSP - If the LSP (standalone) copyright statement did not Standalone display, go to "Manually Installing NDIS Driver" with DOS to repeat the procedure. - Message prefix LT2, go to "NDIS MAC Driver Messages". --Page 23-- Table 5-1 Driver Installation Messages (continue) ------------------------------------------------------- Environment Message Type and Action OS/2 Check LAPSHIST.LOG in the subdirectory OS2\Install, with and LANTRAN.LOG in the subdirectory \IBMCOM for messages. LAPS - Message prefix LT2 or reference to IBMTOK, go to "NDIS MAC Driver Messages". - LAPS messages, refer to the documentation provided with the LAPS program for explanations and appropriate actions. LAN Manager - Check the Microsoft LANManager log, LANMAN\LOGS\NET.EER, with DOS for error messages. Use the LANManager net error or OS/2 command to obtain explanations. - Verify that the Auto 16/4 PnP Token-Ring Adapter has not been configured for both LAN Manager and the LAN Support Program or the LAN Adapter Protocol and Support Program (LAPS). One indication of this condition would be two Device statements for the Protocol Manager (PROTMAN) in the CONFIG.SYS file. If the adapter has been configured for LAN Support Program or LAPS, remove the CONFIG.SYS statements that load the NDIS MAC driver and the protocol drivers for that program. Windows NT - Select "Administrative Tools" and then select the "Event View" icon. Review the Events listing for Error Events and view the Error Event details. Other Refer to the documentation provided with the network DOS Station operating system or network application that you used Other to install the adapter and protocol driver. OS/2 Station --Page 24-- 5.2 NDIS MAC DRIVER MESSAGES ============================== This section contains the DOS NDIS MAC driver messages. LT20022E A failure during initialization of the IBMTOK.DOS driver has occurred. Press any key to continue .... Cause: This is a generic initialization failure message. If the IBMTOK.DOS device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message. Action: Resolve the specific error message that accompanies this message. In addition, ensure that a DEVICE statement for PROTMAN.DOS exists in the CONFIG.SYS file. LT20023E An unrecognized parameter was found in PROTOCOL.INI. Cause: An unrecognized parameter was found while processing the IBM Token-Ring Network Driver section of PROTOCOL.INI. Action: Correct the parameter or remove it from PROTOCOL.INI. LT20024E A value specified for a parameter in PROTOCOL.INI is not valid. Cause: The value provided for the parameter is not the correct type or is not a valid value. Action: Change the value for the parameter in PROTOCOL.INI. LT20025E A configuration error was found in PROTOCOL.INI. Cause: Conflicting parameter Values were found while processing the IBM Token-Ring Network Driver section of PROTOCOL.INI. Action: Examine the configuration parameters and correct the conflicting values in PROTOCOL.INI. --Page 25-- LT20026E The adapter is not responding or was not found. Cause: One of the following conditions has caused this error. - The logical primary/alternate setting in the PROTOCOL.INI file does not map to the physical primary/alternate setting. - The adapter is not responding to a request to start. - The adapter is configured to enable the Plug and Play function but this system is not enabled for Plug and Play. - There is no physical adapter in this machine. Action: If an adapter is already in this system, check the logical primany/alternate setting. Check the cable and ensure that the connection to the Token-Ring Network Addressable Unit (NAU) is functioning correctly. Then run the hardware diagnostics for the Token-Ring adapter to ensure that the adapter and options are correctly installed. Configure the adapter to disable the Plug and Play function. If there is no adapter in this machine, install a Token-Ring adapter or remove the device driver statement from the CONFIG.SYS file. LT20027E The protocol manager could not be opened. Cause: An unexpected error occurred when the program attempted to open the protocol manager. Action: Check the drive and directory to ensure that the protocol manager is located in the specified path. LT20035E A maximum of two Token-Ring Shared RAM device drivers may be active at the same time. Cause: You are attempting to load more than two Token-Ring Shared RAM device drivers. Action: Verify that you are attempting to load no more than two instances of any combination of IBMTOK.DOS or TOK.DOS in your CONFIG.SYS file. --Page 26-- 5.3 NOVELL NETWARE SERVER DRIVER MESSAGES =========================================== This section contains the Novell NetWare Server driver messages. TOKEN-NW-207 NIC Data Rate/Ring Speed Mismatch, Changing NIC Date Rate. Cause: The data rate of the token ring is different from the data rate configured for the Auto 16/4 PnP Token-Ring Adapter. The difference was detected when the adapter attempted to insert into the token ring. Action: None. Auto sense is enabled if this message displays. The Auto 16/4 PnP Token-Ring Adapter automatically changes to the correct ring speed and attempts to reopen. TOKEN-NW-208 NIC Data Rate/Ring Speed Mismatch, Unload driver and reconfigure NIC to match Ring Speed. Cause: The data rate of the token ring is different from the data rate configured for the Auto 16/4 PnP Token-Ring Adapter. The difference was detected when the adapter attempted to insert into the token ring. Action: Auto sense is disabled if this message displays. TOKEN-NW-209 NIC Data Rate Change Unsuccessful. Cause: The NIC was unable to automatically change the data rate when set to Auto sense mode. Action: Reconfigure the NIC to verify it is set for Automatic Ring Speed Detection (Auto sense). TOKEN-NW-210 NIC cannot be opened in Auto sense mode if it is the only station on the ring, or if the cable is disconnected from the wall. Cause: While attempting to open a new Auto 16/4 PnP Token-Ring Adapter with the Auto sense option enabled, the system determined that the adapter is the only station on the ring. The adapter will not be opened to avoid disruptions on the network. Action: Perform one of the following steps: - Reconfigure the Auto 16/4 PnP Token-Ring Adapter Auto sense option to Off and set the data rate to the data rate used by the access unit to which the adapter is connected. - Wait until another station attaches to the network. The Auto 16/4 PnP Token-Ring Adapter will sense the established data rate automatically and connect to the network. - If the cable has been disconnected from the wall or access unit, reconnect it. --Page 27-- 5.4 NOVELL NETWARE CLIENT WITH DOS DIRVER MESSAGES ==================================================== This section contains the DOS driver with Novell NetWare Client messages. TOKEN-DOS-211 NIC Data Rate/Ring Speed Mismatch, Changing NIC Data Rate. Cause: The data rate of the token ring is different from the data rate configured for the Auto 16/4 PnP Token-Ring Adapter. The difference was detected when the adapter attempted to insert into the token ring. Action: None. Auto sense is enabled if this message is displayed. The Auto 16/4 PnP Token-Ring Adapter automatically changes to the correct ring speed and attempts to reopen. TOKEN-DOS-212 NIC Data Rate Change Unsuccessful. Cause: The NIC was unable to automatically change the data rate when set to Auto sense mode. Action: Reconfigure the NIC to verify it is set for Automatic Ring Speed Detection (Auto sense). TOKEN-DOS-207 Initialization Error = 24 - NIC Data Rate/Ring Speed Mismatch. Cause: The data rate of the Token-Ring is different from the data rate configured for the Auto 16/4 PnP Token-Ring Adapter. The difference was detected when the adapter attempted to insert into the Token-Ring. Action: Auto sense is disabled if this message displays. The NIC must be reconfigured to the correct Ring Speed. If there are other stations already on the ring, the adapter can be reconfigured for Auto sense, otherwise leave Auto sense disabled and manually configure the correct data rate. --Page 28-- TOKEN-DOS-207 Initialization Error = 2D - Auto sense and/or RPL Enabled; No other Adapters Present On The Ring Cause: While attempting to open a new Auto 16/4 PnP Token-Ring Adapter with the Auto sense option enabled, the system determined that the adapter is the only station on the ring. The adapter will not be opened to avoid disruptions on the network. OR While attempting to RPL a workstation, no monitor station could be found. Action: Perform one of the following steps: - Reconfigure the Auto 16/4 PnP Token-Ring Adapter Auto sense option to Off, and set the data rate to the rate used by the access unit to which the adapter is connected. - Wait until another station, or the monitor, attaches to the network and then reload the driver. --Page 29-- 5.5 NOVELL NETWARE CLIENT WITH OS/2 DRIVER MESSAGES ===================================================== This section contains the OS/2 driver with Novell NetWare Client messages. TOKEN-OS2-214 NIC Data Rate/Ring Speed Mismatch ... Cause: The data rate of the token ring is different from the data rate configured for the Auto 16/4 PnP Token-Ring Adapter. The difference was detected when the adapter attempted to insert into the token ring. Action: Auto sense is disabled if this message displays. The NIC must be reconfigured to the correct Ring Speed. If there are other stations already on the ring, the adapter can be reconfigured for Auto sense, otherwise, leave Auto sense disabled and manually configure the correct data rate. TOKEN-OS2-215 NIC Data Rate/Ring Speed Mismatch, Changing NIC Data Rate Cause: The data rate of the token ring is different from the data rate configured for the Auto 16/4 PnP Token-Ring Adapter. The difference was detected when the adapter attempted to insert into the Token-Ring. Action: None. Auto sense is enabled if this message displays. The Auto 16/4 PnP Token-Ring Adapter automatically changes to the correct ring speed and attempts to reopen. TOKEN-OS2-216 NIC Data Rate Change Unsuccessful ... Cause: The NIC was unable to automatically change the data rate when set to Auto sense mode. Action: Reconfigure the NIC to verify it is set for Automatic Ring Speed Detection (Auto sense). TOKEN-OS2-217 Auto sense And/Or RPL Enabled; No Other Adapters Present On The Ring Cause: While attempting to open a new Auto 16/4 PnP Token-Ring Adapter with the Auto sense option enabled, the system determined that the adapter is the only station on the ring. The adapter will not be opened, to avoid disruptions on the network. While attempting to RPL a workstation no monitor station could be found. Action: Perform one of the following actions: - Reconfigure the Auto 16/4 PnP Token-Ring Adapter Auto sense option to Off and set the data rate to the data rate used by the access unit to which the adapter is connected. - Wait until another station, or the monitor, attaches to the network and then reload the driver. --Page 30--