Business Machines 35H3636 IBM Turbo 16/4 Token-Ring PC Card 2 User Manual ANO35H3636 with Compliance Statements

International Business Machines Corporation IBM Turbo 16/4 Token-Ring PC Card 2 ANO35H3636 with Compliance Statements

ANO35H3636 User Manual with Compliance Statements

Turbo 16/4 Token-Ring PC Card 2User’s Guide
Turbo 16/4 Token-Ring PC Card 2User’s Guide
NoteBefore using this information and the product it supports, be sure to read the general information under “Appendix G. Noticesand Warranty” on page 95.Eighth Edition (July 1999)© Copyright International Business Machines Corporation 1997, 1999. All rights reserved.US Government Users Restricted Rights – Use duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.The following paragraph does not apply to the United Kingdom or anycountry where such provisions are inconsistent with locallaw: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.This publication could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvements and/orchanges in the products and/or programs described in this publication at any time.It is possible that this publication may contain reference to, or information about,IBM products (machines and programs), programming, or services that are notannounced in your country. Such references or information must not be construedto mean that IBM intends to announce such IBM products, programming, orservices in your country.Requests for technical information about IBM products should be made to your IBMAuthorized Dealer or your IBM Marketing Representative.A form for readers’ comments appears at the back of this publication. If the formhas been removed, address your comments to:Department CGFADesign & Information DevelopmentIBM CorporationPO Box 12195RESEARCH TRIANGLE PARK NC 27709-9990USAWhen you send information to IBM, you grant IBM a nonexclusive right to use ordistribute the information in any way it believes appropriate without incurring anyobligation to you.
ContentsPreface ........................... viiWho Should Read This Manual .................. viiHow This Manual Is Organized .................. viiRelated Information .......................viiiSafety Information ....................... ixChapter 1. Introduction ..................... 1Auto Ring Speed ........................ 1Stealth Mode ......................... 2Chapter 2. Installation ..................... 3Checklist ........................... 3Kit Contents ......................... 3Installation Tips ........................ 3Chapter 3. Inserting and Removing the PC Card ........... 5Inserting the PC Card ...................... 5Removing the PC Card ..................... 6Hot-Pluggability and Suspend/Resume Issues ............. 7Windows 95 and Windows 98 .................. 7DOS ODI Hot-Pluggability and Suspend/Resume ........... 8DOS NDIS Hot-Pluggability ................... 8OS/2 NDIS Hot-Pluggability and Suspend/Resume .......... 8Chapter 4. Software Installation ................. 9Novell Installation .......................10Novell NetWare Server Driver and PCMCIA Bus Support ........10Novell NetWare 3.12 Server...................11Novell NetWare 4.11 Server...................14Novell NetWare 5.0 Server ...................17Novell Client DOS/Windows 3.1x .................19Novell NetWare Client32 for Windows 95 ..............19Novell NetWare Server Driver Parameters .............20Windows Installation ......................23Windows 95 and Windows 98 ..................23Windows NT 3.51 ......................24Windows NT 4.0 .......................25Windows 2000........................25Remote Unattended Install for Windows 95, Windows 98, and NT 4.0 . . . 25OS/2 Installation ........................26OS/2 NDIS 2 Device Driver Using MPTS ..............26OS/2 NDIS 2 Device Driver Using Other Installation Programs ......27DOS Installation ........................27Microsoft Windows for Workgroups/NDIS 2 .............27ODI 16–bit Client.......................28ODI 16–bit Client Parameters ..................29Chapter 5. LANAID.......................33About LANAID.........................33The Net Address .......................33Installing LANAID .......................33Using LANAID to Configure the PC Card ...............34© Copyright IBM Corp. 1997, 1999 iii
Command Line Invocation of LANAID ................35Bypassing Startup Files .....................35Chapter 6. Point Enablers and Card Services ............37Relationship Between the Interfaces.................37Point Connectivity Enablers ....................37Advantage .........................38Disadvantages........................38Socket Services ........................38Card Services .........................38Advantages.........................39Disadvantage ........................39Card Services Enabler......................39Card and Socket Services versus Point Enablers ............39Autoset Mode ........................40Using a Memory Manager in DOS Environments ............40Memory Managers with Point Enablers...............40Memory Managers with Card and Socket Services ..........41Expanded Memory Specification .................42Appendix A. CD-ROM Content and Software Packages ........45Software Packages .......................45Diskette Images ........................46Product Documentation .....................47Appendix B. Problem Determination ................49Questions, Problems? ......................50World Wide Web .......................50IBM Product Support .....................50Troubleshooting and Error Codes..................50Novell NetWare Server Driver Messages ..............50Windows 95 and Windows 98 ..................60Windows NT ........................61Windows 2000........................61OS/2 NDIS Error Codes ....................62DOS NDIS Error Codes ....................76ODI 16-bit Client Error Codes ..................77Appendix C. Running the Diagnostics Program ...........81Test Options .........................81Diagnostics Error Codes and Suggested Actions ............81Initialization Error Codes ....................81Open Errors ........................82Open Error Codes ......................83Transmit Error Codes .....................86Appendix D. LANAIDC Parameter Information ............87Using LANAIDC to Duplicate Configurations ..............87LANAIDC Parameters ......................88Appendix E. Token.lan and LAN Client Driver Parameters .......89Custom Keywords .......................89Keywords with Parameters ...................89Appendix F. Parts Information ..................93iv Turbo 16/4 Token-Ring PC Card 2
Appendix G. Notices and Warranty ................95Notice to Users in the United Kingdom................95Electronic Emission Notices ....................95Federal Communications Commission (FCC) Statement ........95Industry Canada Class B Emission Compliance Statement .......96Avid de conformité aux normes d’Industrie Canada ..........96European Community (EC) Mark of Conformity Statement .......96Japanese Voluntary Control Council for Interference (VCCI) Statement . . . 96Trademarks..........................97Product Warranty........................97Glossary of Terms and Abbreviations ...............101Index ............................105Contents v
vi Turbo 16/4 Token-Ring PC Card 2
PrefaceThis manual contains the information you need to install and use your PC Card.Unless specified, all references in this book to the PC Card apply to the IBM Turbo16/4 Token-Ring PC Card 2.On this CD-ROM are the installation aids, device drivers, and documentation for thePC Card.Who Should Read This ManualThis manual is intended for use by network administrators and other end users ofthe IBM Turbo 16/4 Token-Ring PC Card 2.How This Manual Is Organized“Chapter 1. Introduction” on page 1 describes the features of the IBM Turbo 16/4Token-Ring PC Card 2.“Chapter 2. Installation” on page 3 describes the PC Card covered in this manualand gives a checklist for installation of the PC Card.“Chapter 3. Inserting and Removing the PC Card” on page 5 describes theprocedure for installing the PC Card into your computer.“Chapter 4. Software Installation” on page 9 describes the procedure for softwareinstallation for a number of network operating environments.“Chapter 5. LANAID” on page 33 describes the LANAID product.“Chapter 6. Point Enablers and Card Services” on page 37 describes how to usethe PC Card with these programs.“Appendix A. CD-ROM Content and Software Packages” on page 45 describes theCD-ROM content and how the software packages work.“Appendix B. Problem Determination” on page 49 describes troubleshootingprocedures and fixes that might be needed for your environment.“Appendix C. Running the Diagnostics Program” on page 81 describes thediagnostics program, how to use it, and the error codes associated with it.“Appendix D. LANAIDC Parameter Information” on page 87 lists the keywords usedin the LANAIDC program.“Appendix E. Token.lan and LAN Client Driver Parameters” on page 89 describesthe keywords used in the token.lan file.“Appendix F. Parts Information” on page 93 lists the parts involved in this kit.“Appendix G. Notices and Warranty” on page 95 lists the legal notices required forthe IBM Turbo 16/4 Token-Ring PC Card 2.© Copyright IBM Corp. 1997, 1999 vii
Related InformationRefer to these publications for additional information:vBOF for LAN Technical Reference Adapter Interfaces, SBOF-6221vIBM Token-Ring Network Architecture Reference, SC30-3374vLAN Technical Reference IEEE 802.2 and NETBIOS, SC30-3587vCredit Card Adapter Technical Reference, SC30-3585vNTS/2 LAN Adapter and Protocol Support Configuration Guide, S96F-8489vLAN Technical Reference: Token-Ring Network Shared-RAM, SC30-3588vIBM Token-Ring Adapter Features, available on the IBM Turbo 16/4 Token-RingPC Card 2 CD-ROMvIBM Networking home page on the World Wide Web:www.networking.ibm.comvYou will need the manuals that were shipped with your network operating system.Note: SBOF-6221 and SC30-3587 replaceLocal Area Network TechnicalReference, SC30-3383.viii Turbo 16/4 Token-Ring PC Card 2
Safety InformationDanger: Before you begin to install this product, read the safety information inCaution: Safety Information—Read This First, SD21-0030. This booklet describessafe procedures for cabling and plugging in electrical equipment.Varning — livsfara: Innan du börjar installera den här produkten bör du läsasäkerhetsinformationen i dokumentetVarning: Säkerhetsföreskrifter— Läs dettaförst,SD21-0030. Där beskrivs hur du på ett säkert sätt ansluter elektriskutrustning.Fare: Før du begynner å installere dette produktet, må du lesesikkerhetsinformasjonen iAdvarsel: Sikkerhetsinformasjon — Les dette først,SD21-0030 som beskriver sikkerhetsrutinene for kabling og tilkobling av elektriskutstyr.Fare! Før du installerer dette produkt, skal du læse sikkerhedsforskrifterne iNB:Sikkerhedsforskrifter—Læs dette førstSD21-0030. Vejledningen beskriver denfremgangsmåde, du skal bruge ved tilslutning af kabler og udstyr.Gevaar: Voordat u begint met de installatie van dit produkt, moet u eerst deveiligheidsinstructies lezen in de brochurePAS OP! Veiligheidsinstructies—Lees diteerst,SD21-0030. Hierin wordt beschreven hoe u electrische apparatuur op eenveilige manier moet bekabelen en aansluiten.Gevaar Voordat u begint met het installeren van dit produkt, dient u eerst deveiligheidsrichtlijnen te lezen die zijn vermeld in de publikatieCaution: Safety© Copyright IBM Corp. 1997, 1999 ix
Information - Read This First, SD21-0030. In dit boekje vindt u veilige proceduresvoor het aansluiten van elektrische appratuur.Vorsicht: Bevor mit der Installation des Produktes begonnen wird, dieSicherheitshinweise inAchtung: Sicherheitsinformationen—Bitte zuerst lesen,IBMForm SD21-0030. Diese Veröffentlichung beschreibt die Sicherheitsvorkehrungenfür das Verkabeln und Anschließen elektrischer Geräte.Danger : Avant d’installer le présent produit, consultez le livretAttention :Informations pour la sécurité — Lisez-moi d’abord, SD21-0030, qui décrit lesprocédures à respecter pour effectuer les opérations de câblage et brancher leséquipements électriques en toute sécurité.Danger: Avant de procéder à l’installation de ce produit, lisez d’abord les consignesde sécurité dans la brochureATTENTION: Consignes de sécurité—A lire aupréalable,SD21-0030. Cette brochure décrit les procédures pour câbler etconnecter les appareils électriques en toute sécurité.Pericolo: prima di iniziare l’installazione di questo prodotto, leggere le informazionirelative alla sicurezza riportate nell’opuscoloAttenzione: Informazioni di sicurezza— Prime informazioni da leggerein cui sono descritte le procedure per il cablaggioed il collegamento di apparecchiature elettriche.xTurbo 16/4 Token-Ring PC Card 2
Perigo: Antes de iniciar a instalação deste produto, leia as informações desegurançaCuidado: Informações de Segurança — Leia Primeiro, SD21-0030. Estedocumento descreve como efectuar, de um modo seguro, as ligações eléctricasdos equipamentos.Peligro: Antes de empezar a instalar este producto, lea la información deseguridad enAtención: Información de Seguridad — Lea Esto Primero,SD21-0030.Este documento describe los procedimientos de seguridad para cablear y enchufarequipos eléctricos.Perigo: Antes de começar a instalar este produto, leia as informações desegurança contidas emCuidado: Informações Sobre Segurança—Leia IstoPrimeiro,SD21-0030. Esse folheto descreve procedimentos de segurança para ainstalação de cabos e conexões em equipamentos elétricos.VAARA: Ennen kuin aloitat tämän tuotteen asennuksen, lue julkaisussaVaroitus:Turvaohjeet—Lue tämä ensin, SD21-0030, olevat turvaohjeet. Tässä kirjasessa onohjeet siitä, miten sähkölaitteet kaapeloidaan ja kytketään turvallisesti.Safety Information xi
Vigyázat: Mielôtt megkezdi a berendezés üzembe helyezését, olvassa el a“Caution: Safety Information— Read This First,SD21-0030 könyvecskében leírtbiztonsági információkat. Ez a könyv leírja, milyen biztonsági intézkedéseket kellmegtenni az elektromos berendezés huzalozásakor illetve csatlakoztatásakor.xii Turbo 16/4 Token-Ring PC Card 2
Safety Information xiii
xiv Turbo 16/4 Token-Ring PC Card 2
Chapter 1. IntroductionThe IBM Turbo 16/4 Token-Ring PC Card 2 (referred to asPC Card)isacredit-card-sized adapter that provides an interface between computers andToken-Ring networks. It is part of the shared RAM family of adapters. The PC Cardis designed for computers with slots that comply with the standards for the PersonalComputer Memory Card International Association (PCMCIA) Release 2.1, Type IIslots.Features include:vRemote Program Load (RPL)vFull-duplex-ready.vSupports the Desktop Management Interface (DMI).vEasy to install — variable interrupt levels and I/O address choices.vIncludes RJ-45 cable and STP media access adapter for easy connection toeither UTP or STP cables.vMobile computing possible because the PC Card does not have to be removed;simply disconnect the cable and reconnect when you are in the new location.See “Stealth Mode” on page 2.vCompliance with PCMCIA Revision 6.2 and IEEE 802.5 standards. This allowsuse of the PC Card with a variety of application programs.vAuto Ring Speed, a configurable option that permits the PC Card device driver todetect and operate at the data rate of the ring.vSupport for a variety of network operating systems and network applications.Auto Ring SpeedThe Auto Ring Speed function avoids problems due to manual configuration of anincorrect data rate. The function also eliminates the need to reconfigure the PCCard if the data rate of the ring is changed.You should not select Auto Ring Speed if you might be the first one to attach toyour ring. The PC Card will not allow you to connect in this case. You will have totry to connect again after another Token-Ring user is on the ring.When using the PC Card in Auto Ring Speed mode, it is important to be aware oftransmit buffer limitations that may cause problems. A 16-Mbps Token Ring cansupport transmit buffer sizes up to 17 960 bytes. A 4-Mbps Token Ring can supporttransmit buffer sizes up to 4464 bytes. This is a restriction due to the speed of themedia. This might affect your application.If your software is configured to try 16-Mbps ring operation first and you plan toutilize Auto Ring Speed, use a transmit buffer size less than or equal to 4464 bytes.This will ensure that you will not have any open PC Card errors due to impropertransmit buffer size if your PC Card must change ring speed.© Copyright IBM Corp. 1997, 1999 1
Stealth ModeThe device drivers for Turbo 16/4 Token-Ring PC Card 2 are fullybackward-compatible with all of the previous versions of IBM Token-Ring CreditCards, however there have been improvements in the hardware with theintroduction of the Turbo PC Cards. That new hardware feature is referred to asStealth Mode and can be used in the Turbo 16/4 Token-Ring PC Card 2 to removepower from the card by removing only the cable. The operating system will notsense the presence of the card in the slot with the cable detached.With previous IBM Token-Ring Credit Cards, with the exception of the IBM Turbo16/4 Token-Ring PC Card, the card and cable had to be removed from thecomputer to remove power to the slot and the detection of the adapter from theoperating system.When removing the cable from the PC Card while the system is running orconnected to the network or both, stop the PC Card before you remove the cable orcard, just as you normally would when removing any adapter from the system.Note: If the cable is disconnected at boot time under a Plug and Play operatingsystem, the operating system will not be aware of the PC Card’s presenceand will not try to load the device drivers for the PC Card. However, underan operating system which is not Plug and Play compliant, the operatingsystem will try to load the PC card device drivers anyway and as a result theoperating system will generate an error message referring to the adapter orthe device drivers or both.2Turbo 16/4 Token-Ring PC Card 2
Chapter 2. InstallationChecklistThe PC Card cannot be installed without a network operating system on thecomputer. Ensure that a network operating system has been installed, or useLCINST to install IBM LAN Client as described inIBM Token-Ring AdapterFeatures.To install this PC Card, complete the following steps in order.1. Read the information in Chapter 1, “Introduction.”2. Check the shipping package contents list and tips that begin on page 3.3. Insert the PC Card; see page 5 .4. Connect the cable to the PC Card and to the network. The cable must connectto the PC Card, or the system will not recognize the PC Card.5. Install the new driver according to the operating system on your computer. See“Chapter 4. Software Installation” on page 9.6. Installation is now complete. You must reboot your system for the changes totake effect. If you have not inserted the PC Card already, insert it beforerebooting the system. “Hot-Pluggability and Suspend/Resume Issues” on page 7gives information about hot-plugging the PC Card.Kit ContentsYour kit contains the following items:vIBM Turbo 16/4 Token-Ring PC Card 2 (also calledPC Card)vToken-Ring PC Card cable, P/N 38H7044. (The standard cable uses an RJ-45connector for use with UTP network wiring.)vOne IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.vAn STP connector for connection to STP network wiring, P/N 73G8314. See“Chapter 3. Inserting and Removing the PC Card” on page 5 for information oninstalling the PC Card, the cable, and, if needed, the STP connector.Note: If you are connecting to a standard Token-Ring cable that uses a D-shellconnector (P/N 6339098), you should order PC Card cable P/N 38H7046.vAdapter Support Information cardvRegistration card.Installation TipsThis section provides references to other sections of this book, telephone numbers,and tips about the PC Card.1. Check to see if there is a newer level of the driver available. See “Chapter 4.Software Installation” on page 9.2. If you have problems with your computer or PC Card or you need assistance,contact your IBM representative or call the IBM Help Center. See “Questions,Problems?” on page 50.© Copyright IBM Corp. 1997, 1999 3
3. If you plan to use Card and Socket Services software, Version 2.0 or higher,install it and reboot your computer. The software might have been provided withyour computer or operating system. See page 38 for a description of theseservices.Return to page 3 to continue. Step 2 of the Installation Checklist is now complete.4Turbo 16/4 Token-Ring PC Card 2
Chapter 3. Inserting and Removing the PC CardInserting the PC CardNote: If you are using Card and Socket Services, you might be able to usehot-pluggabilityfeatures with your PC Card. See “Hot-Pluggability andSuspend/Resume Issues” on page 7.1. Switch OFF (O) the power to the computer.2. Determine which type of network cabling you will be using as shown inthe following figures, and connect the PC Card cable to the network asdescribed.vIf your network uses UTP cabling, attach the RJ-45 (8-pin modular)connector on the PC Card cable (P/N 38H7044) to the RJ-45telecommunications outlet.vIf your network uses STP cabling, attach the RJ-45 connector on thePC Card cable (P/N 38H7044) to the RJ-45 end of the STP connector(P/N 73G8314). Attach the STP connector to the STPtelecommunications outlet.The STP connector has been specifically designed to work with theIBM Token-Ring PC Cards.Note: Verify that you are using the correct STP connector. The correctSTP connector and PC Card cable have the code number 100 onthe connectors that attach to each other.© Copyright IBM Corp. 1997, 1999 5
3. To attach the cable to the PC Card, move the latching button (thehalf-circle in the center of the PC Card connector) toward the cable. Thecable cannot be connected or disconnected unless the latch is retracted.Attach the cable to the PC Card with the part number on the bottom.The connector is keyed to attach to the PC Card only one way. If youfeel any resistance, remove the connector, turn it over, and reattach it.Part Number(on bottom)Latching ButtonPC Card4. To lock the cable securely, move the latching button in toward the PCCard. In some cases, you might want to leave the PC Card cable latchretracted. If the PC Card cable is pulled, it will disconnect from the PCCard, possibly saving your computer from being pulled off a table.5. Insert the PC Card in the slot. If you are using a point enabler, notewhich slot you use.PC CardPC Card SlotThe PC Card is keyed to go in only one way. If you feel resistancebefore the PC Card is fully inserted, remove the PC Card, turn it over,and reinsert it.6. Switch ON (|) the power to the computer.7. Return to page 3 to continue. Step 3 of the Installation Checklist is nowcomplete.Removing the PC CardNote: If you are using Card and Socket Services, you may be able to usehot-pluggabilityfeatures with your PC Card. See “Hot-Pluggability andSuspend/Resume Issues” on page 7 for more information.Follow these steps to remove the PC Card:6Turbo 16/4 Token-Ring PC Card 2
1. Switch OFF (O) the power to the computer.2. With the cable still attached to the PC Card, pull the PC Card from thecomputer.3. To detach the cable from the PC Card, retract the latching button (the half-circlein the center of the connector) by moving it toward the cable.4. Grasp the connector and unplug it from the PC Card.5. Store the PC Card.Note: When the cable is removed from the PC Card, the PC Card appears tothe system as if it has been physically removed from the socket.Hot-Pluggability and Suspend/Resume IssuesThe DOS ODI, DOS NDIS, OS/2 ODI, OS/2 NDIS, Card Wizard 4.1 and 5.0 onWindows NT, Windows 95 and Windows 98 (NDIS 3) drivers support a level ofhot-pluggabilityand Suspend/Resume. Hot-pluggability refers to the ability toremove and insert your card at any time while the machine is running. If you followthese guidelines, no damage will occur to either your PC Card, machine, orsoftware. Hot-plugging has the advantage of allowing you to remove your cardwhen you are using battery power, thus reducing the drain on your battery. It alsoprovides greater freedom in using portable computers in a portable manner. TheIBM Turbo 16/4 Token-Ring PC Card 2 appears to be removed physically from asystem when the cable is removed. The PC Card appears to the system to beinserted when its cable is reattached to the PC Card. This makes it possible tohot-plug the PC Card without physically removing it from the socket. Attach orremove your cable instead of physically removing the PC Card.To use the hot-plugging features of this card, you must:vUse Card and Socket Services. If you are using a point enabler,do notattemptto unplug your card while the machine is powered on. You might damage bothyour card and the machine in this case.vUse the Windows 95, DOS ODI environment, DOS NDIS environment, OS/2 ODIenvironment, or OS/2 NDIS environment. At the present time the DOS Nativeenvironment does not support hot-pluggability. Removing your card while usingthis environment might result in a system failure or the inability to access yourLAN applications.vDo not hot-plug a card when in a Windows for Workgroups environment. Yourcard does not have to be present when NET START is run. If you plan to accessyour network in your Windows session, insert your card before starting Windows.If you plan to pull out your card, shut down Windows before doing so. It issuggested that you include your Network Address in the protocol.ini if youexecute NET START without a card present. This ensures that the system hasyour card’s address even if the card is not present.The following sections describe, in more detail, the exact procedure to follow foreach of the supported hot-plugging environments.Windows 95 and Windows 98Windows 95 and Windows 98 have built-in support for hot plugging andsuspend/resume. They recognize the PC Card when it is inserted into a PCMCIAsocket (or the cable is attached to an inserted PC Card) and load the correct driverand configured protocol stack for the PC Card.Chapter 3. Inserting and Removing the PC Card 7
If you plan to disconnect from your network, click the PC Card icon on the statusbar. A message box appears with a message to stop the PC Card. Click this box.When the Safe to remove message appears, you can either remove the cable orphysically remove your PC Card.DOS ODI Hot-Pluggability and Suspend/ResumeIt is recommended that you use the NetWare Event Service Layer program(NESL.COM) for hot-plugging to work in this environment. Without this support, youshould use the following procedure.To remove the card or go into a suspend mode, you must first unload all thedrivers. This is done by removing them in the reverse order they were installed.This can be accomplished by typing the following commands at the DOS prompt:netx u (or vlm u)ipxodi utokencs ulsl uAt this point, you can remove the card from your machine. Once the card isremoved, you can enter and exit suspend mode as often as you like beforereinstalling the card. It is best to reinstall the card while the machine is not insuspend mode.After reinserting the card or resuming, you can restart your network software bytyping the following commands at the DOS prompt:lsltokencsipxodinetxDOS NDIS Hot-PluggabilityYou can insert and remove your card before and after using Windows forWorkgroups. You cannot hot-plug the card while using Windows for Workgroups.Insert the card before starting the software. Remove the card only after exiting theWindows for Workgroups environment.OS/2 NDIS Hot-Pluggability and Suspend/ResumeYou can remove the card or go into suspend mode at any time as long as you arenot running any applications that use shared resources. After you reinsert the cardor resume, you should have all of your LAN shared resources connected. If you useCM/2 to connect to the host, you will have to log on again.One scenario that does not work is suspending and then removing the card. Thecard will not be recognized when it is reinserted. If you want to do something likethis, you must first remove the card and then suspend. You can then resume laterand reinsert the card later.8Turbo 16/4 Token-Ring PC Card 2
Chapter 4. Software Installation1. Get the latest level of LAN driver updates for your operating system to ensurethat your code is at the latest level.2. Be sure that your IBM Turbo 16/4 Token-Ring PC Card 2 has already beeninstalled in your computer. If it has not, follow the instructions in “Chapter 3.Inserting and Removing the PC Card” on page 5.3. Get the driver for your environment. There are three places to find the driver. Ifyou have a Web connection, we recommend the first one listed here. All threemethods will place the driver in a directory according to the structure in Table 1.vMethod A: Get the driver from a software package on the IBM NetworkingHardware Division home page on the Web. This will ensure that you get thelatest driver. Go to x:\startcd.htm (where x is your CD-ROM drive). SelectIBM Networking Web site — product support. Select Downloads andchoose the appropriate software package for your environment. Run thepackage to expand the files.Note: You can also access the Web site directly atwww.networking.ibm.com/supportvMethod B: Use the driver shipped on this CD-ROM directly with your networkoperating system’s installation software.vMethod C: Get the driver from a software package shipped on this CD-ROM.Point your Web browser to x:\startcd.htm (where x is your CD-ROM drive).Select CD-ROM — product support. Select Downloads and choose theappropriate software package for your environment. Run the package toexpand the files.4. Install the driver. Use Table 2 and Table 3 on page 10 to find the location of theinstallation instructions for your environment. It is recommended that you installthe latest service pack for your operating environment before installing the PCCard software.Table 1. Driver File Directory StructureOperating System DirectoryWindows 9x \ (root)Windows NT \ (root)Windows 2000 \ (root)Novell NetWare Server and Client \NOVELL\NETWARENovell NetWare DOS Requester (16-bit) \NOVELL\DOSOS/2 \ (root)DOS \DOSWindows for Workgroups \WFWIf you are using one of the environments listed in Table 2, you will not use LANAID.Where to Find the Installation Instructions for Your EnvironmentTable 2. Do not use LANAID to configure your machineNovell NetWare 3.12 Server page 11Novell NetWare 4.11 Server page 14Novell NetWare 5.0 Server page 17© Copyright IBM Corp. 1997, 1999 9
Table 2. Do not use LANAID to configure your machine (continued)Novell Client DOS/Windows 3.1x page 19Novell NetWare Client32 for Windows 95 page 19Windows 95/Windows 98 page 23Windows NT 3.51 page 24Windows NT 4.0 page 25Windows 2000 page 25Remote Unattended Install for Windows 95, Windows 98,and NT 4.0 page 25OS/2 NDIS 2 Device Driver Using MPTS page 26OS/2 NDIS 2 Device Driver Using Other InstallationPrograms page 27ODI 16-bit Client page 28If you are using the environment listed in Table 3, you will use LANAID to configureyour machine. Even though the network operating system appears to fully installand configure the device driver, it is highly recommended that you run LANAID toensure that the PC Card is appropriately configured.Table 3. Use LANAID to configure your machineMicrosoft Windows for Workgroups/NDIS 2 page 27Note: If you are operating in a server environment, you might not get support fromyour hardware or network operating system manufacturers.Novell InstallationNovell NetWare Server Driver and PCMCIA Bus SupportCard Services and Point Enablers: What Works and What DoesNotIBMTOKEN.LAN is used in both the NetWare Server and Client environments. Inorder to use this driver, your system must enable the card by loading: SocketServices, Card Services, and CS20TOK.EXE. POINTTR.EXE is not supported withIBMTOKEN.LAN.If Card Services on your system is earlier than version 5.00, enter the followingparameter when you load the driver: MEM1=<SRAM Address>LOAD IBMTOKEN.LAN FRAME=TOKEN-RING MEM1=C8000If you do not put this parameter on the driver load line, you will be prompted for thisparameter every time you load the driver.If your Card Services is version 5.00 or higher, you do not need to worry about thisparameter.CS20TOK.EXE ConfigurationCS20TOK.EXE is a small software program that configures the PC Card socketcontroller to allocate resources (memory, I/O Ports, interrupts, DMA channels, and10 Turbo 16/4 Token-Ring PC Card 2
power) to PCMCIA cards. Once CS20TOK.EXE has run successfully, the PCMCIAToken-Ring card is ready to operate and looks much like any ISA Token-Ringadapter.Generally, enabling a card is done by loading CS20TOK.EXE in CONFIG.SYS,AUTOEXEC.BAT, or at a DOS prompt.For a complete list of CS20TOK.EXE parameters, you can enter the following at aDOS prompt:CS20TOK /? or CS20TOK /hExamples:In autoexec.bat:cs20tok sa mmio=d000 sram=d000,4 rs=16 irq=a io=0a20In config.sys:device=c:\cs20tok.exe sa mmio=d000 sram=d000,4 rs=16 irq=a io=0a20Both set the card in slot 1 (sa) to an 8-KB memory region based at X'0D0000', withthe card operating in enhanced mode. The card is assigned port X'0A20', interruptvector X'A' (10 decimal), and Token-Ring speed (rs) will be 16 Mbps. The programruns, then sounds two ascending beeps indicating successful operation. The card isnow enabled and ready for the driver to be loaded.Here is an example of using CS20TOK.EXE with two adapters:cs20tok sa mmio=d000 sram=d000,4 rs=16 irq=a io=0a20 prics20tok sb mmio=c800 sram=c800,4 rs=16 irq=9 io=0a24 altNovell NetWare 3.12 ServerBefore you start this installation, get the latest level of patches for NetWare 3.12from Novell. The current level is IntraNetWare Support Pack Version 5.0 from theNovell support Web site at support.novell.com. You will install the patches duringthe following procedure.If the Novell NetWare server is not on your computer, use the following instructions.If it is on your computer, go to the instructions on page 13.Server Driver Installation in New NetWare 3.12 ServerChanges from the usual NetWare installation are necessary because this driver iswritten to a new specification level that requires new NetWare loadable modules(NLMs). The installation program is not aware of this, though, and these NLMs mustbe loaded during installation of the server device driver and after the serverinstallation.1. Create a diskette containing the extracted files from the NETWARE.EXEpackage file on the IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. Refer to Novell’sInstallation and Upgrademanual for installation instructions.Follow the procedure for the installation of Novell NetWare 3.12 until thesection titled ″Load LAN Drivers″is next.3. Insert the diskette that you created in step 1 into drive A. Enter the followingcommands at the server prompt:LOAD A:\NOVELL\NETWARE\NBI31X.NLMLOAD A:\NOVELL\NETWARE\MSM31X.NLMLOAD A:\NOVELL\NETWARE\TOKENTSM.NLMChapter 4. Software Installation 11
Note: A message referring toprotected-mode BIOS accessmight appearbefore installation of Novell patches. It is for information only and canbe ignored.4. Load the server device driver. Enter the following command at the serverprompt:LOAD X:\NOVELL\NETWARE\IBMTOKEN.LAN DATARATE=M16In server environments, the DataRate should be set to M16 or M4, and clientsshould be set to Auto. The default is Auto.Note: See “Novell NetWare Server Driver Parameters” on page 20 for acomplete list of parameters that can be specified in the LOADIBMTOKEN command in the AUTOEXEC.NCF file.5. Follow the instructions in the Novell manual, beginning with ″Bind the Protocolto the LAN Driver″and continue until you are in the File Server STARTUP.NCFFile panel.6. In addition to the instructions in the Novell manual, add the following line toSTARTUP.NCF:Set Minimum Packet Receive Buffers = 48Note: Increase the minimum packet receive buffers by 48 for each additionaladapter that is installed.7. Perform the instructions in ″Create an AUTOEXEC.NCF file″in the Novellmanual. Add the following lines to the AUTOEXEC.NCF file immediately afterthe IPX INTERNAL NET statement (replace C:\SERVER.312\ with the locationof the NetWare server program):LOAD C:\SERVER.312\NBI31X.NLMLOAD C:\SERVER.312\MSM31X.NLMLOAD C:\SERVER.312\TOKENTSM.NLMLOAD C:\SERVER.312\IBMTOKEN.LAN NAME=IBMLS1 DATARATE=M16BIND IPX TO IBMLS1 NET=<unique net number>Make sure that the line containing IBMTOKEN.LAN has the complete pathname.Notes:a. See “Novell NetWare Server Driver Messages” on page 50 for a completelist of parameters that you can specify on the LOAD IBMTOKEN commandin the AUTOEXEC.NCF file.b. If you experience any problems after loading the Novell NLM files, contactNovell to ensure that you have the current version of these files.Press Esc and answer Yes to save the new file to disk. Press Esc again toreturn to the server console.8. Shut down your server by entering down and then entering exit from the serverprompt.9. Make sure that the diskette that you created in step 1 is inserted in drive A.Enter the following commands at the server prompt. You might be prompted toperform a file overwrite; it is OK to overwrite these files.COPY A:\NOVELL\NETWARE\NBI31X.NLM C:\SERVER.312COPY A:\NOVELL\NETWARE\MSM31X.NLM C:\SERVER.312COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\SERVER.312COPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\SERVER.312COPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\SERVER.31212 Turbo 16/4 Token-Ring PC Card 2
10. Go to the Novell server directory and enter server at the DOS prompt torestart the server.11. Install the patches obtained earlier now. Make sure to select the v3.31 ODILAN Updates for Hardware if given the opportunity.12. Installation is now complete.Check for the following conditions to determine whether the adapter is workingcorrectly and whether installation is complete:vThe device driver files are loading successfully.vThere are no error messages.If you experience problems, go to “Appendix B. Problem Determination” onpage 49.For information concerning NetWare server error messages, see “NovellNetWare Server Driver Parameters” on page 20.Server Driver Installation in Existing NetWare 3.12 ServerIf Novell NetWare is on your computer, perform the following steps to install theadapter server device driver.1. Create a diskette containing the extracted files from the NETWARE.EXE file onthe IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. Install the patches obtained earlier now. Make sure to select the v3.31 ODILAN Updates for Hardware if given the opportunity. Return to the serverconsole when the installation is complete.3. Make sure that the diskette you created in step 1 has been inserted in drive A.Enter the following commands at the server prompt. You might be prompted toperform a file overwrite; it is OK to overwrite these files.COPY A:\NOVELL\NETWARE\NBI31X.NLM C:\SERVER.312COPY A:\NOVELL\NETWARE\MSM31X.NLM C:\SERVER.312COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\SERVER.312COPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\SERVER.312COPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\SERVER.312Note: If you experience any problems after loading the Novell NLM files,check the Novell Web site to ensure that you have the current versionof these files.4. In the directory where Novell is installed on your hard disk, enter server at theDOS prompt to start the server.5. At the server console prompt, enter load install.6. From the Installation Options menu, select System Options and press Enter.7. Select Edit STARTUP.NCF File and press Enter. Add the following line to theSTARTUP.NCF file:Set Minimum Packet Receive Buffers = 48Note: Increase the minimum packet receive buffers by 48 for each additionaladapter that is installed.8. Press Esc and then answer Yes to save changes to the STARTUP.NCF file.9. Select Edit AUTOEXEC.NCF File and press Enter. Edit this file and, after theIPX internal net statement, include the following statements. (ReplaceC:\SERVER.312\ with the location of the NetWare server program.)In a server environment, set the DataRate to M16 or M4, and clients to Auto.The default is Auto.Chapter 4. Software Installation 13
LOAD C:\SERVER.312\NBI31XLOAD C:\SERVER.312\MSM31XLOAD C:\SERVER.312\TOKENTSMLOAD C:\SERVER.312\IBMTOKEN NAME=IBMLS1 DATARATE=M16BIND IPX TO IBMLS1 NET=<unique net number>See “Novell NetWare Server Driver Parameters” on page 20 for a complete listof parameters that can be specified on the LOAD IBMTOKEN command in theAUTOEXEC.NCF file.Press Esc and then answer Yes to save the new file to disk. Press Esc againto return to the server prompt.10. Shut down your server by entering down and then entering exit from theserver prompt.11. Enter server to restart the server.12. Installation is now complete. Shut down and restart your computer for allchanges to take effect.Check for the following conditions to determine whether the adapter is workingcorrectly and whether installation is complete:vThe device driver files are loading successfully.vThere are no error messages.If you experience problems, go to “Appendix B. Problem Determination” onpage 49.For information concerning NetWare server error messages, see “NovellNetWare Server Driver Messages” on page 50.Novell NetWare 4.11 ServerBefore you start this installation, get the latest level of patches for NetWare 4.11Server from Novell. The current level is IntraNetWare Support Pack Version 5.0from the Novell support Web site at support.novell.com. You will install the patchesduring the following procedure.If Novell NetWare is not on your computer, use the following instructions. If it is onyour computer, follow the instructions on page 16.Server Driver Installation in New NetWare 4.11 ServerChanges from the usual NetWare installation are necessary because this driver iswritten to a new specification level that requires new NetWare loadable modules(NLMs). The installation program is not aware of this, though, and these NLMs mustbe loaded during installation of the server device driver and after the serverinstallation.Note: A message referring to protected-mode BIOS access might appear beforeinstallation of Novell patches. It is for information only, and can be ignored.1. Create a diskette containing the extracted files from the NETWARE.EXEpackage file on the IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. When you see INSTALL Found the following: IBM Turbo 16/4 Token-Ring PCCard 2xxxx xxxx xxxx, press Enter. The actual numbers vary by product.Then press the Insert (INS) key to install the unlisted driver.14 Turbo 16/4 Token-Ring PC Card 2
3. Press ALT-ESC to toggle to the server console, and enter the following LOADstatements (make sure that the diskette that you created in step 1 is insertedin drive A):LOAD A:\NOVELL\NETWARE\MSM.NLMLOAD A:\NOVELL\NETWARE\TOKENTSM.NLM4. Press ALT-ESC to toggle back to the INSTALL panel.5. Press F3 on the next panel to specify A:\NOVELL\NETWARE as the directorypath.Press Enter, then follow the instructions on the panel to complete theinstallation of the driver. If you need to make any custom configurationchanges to the driver, do so at this time.6. Follow the instructions in the Novell manual toCreate an AUTOEXEC.NCF file.In addition to the instructions in the manual, add the following lines to theAUTOEXEC.NCF file immediately after the IPX INTERNAL NET statement (ifnecessary, replace C:\NWSERVER with the location of the SERVER.EXEexecutable):LOAD C:\NWSERVER\NBI.NLMLOAD C:\NWSERVER\MSM.NLMLOAD C:\NWSERVER\TOKENTSM.NLMLOAD C:\NWSERVER\IBMTOKEN.LAN NAME=IBMLS1 DATARATE=M16Note: There will be existing LOAD and BIND IPX statements in theAUTOEXEC.NCF. Delete the LOAD statement (we have replaced it withstated LOAD C:\NWSERVER\IBMTOKEN.LAN statement). Also, makeany needed modifications to the existing BIND IPX statement (refer totheBind the Protocol to the LAN Driversection of the Novell manual foradditional information).See “Novell NetWare Server Driver Parameters” on page 20 for a complete listof parameters that can be specified on the LOAD IBMTOKEN command in theAUTOEXEC.NCF file.7. Press ESC and answer YES to save the new file to disk. Press ESC again toreturn to the server console.8. Type the following commands from the server prompt to shut down the serverand exit to DOS: down, then exit.9. Perform the following COPY commands, making sure that the diskette that youcreated in step 1 is inserted in drive A. Note that it will prompt you at each ofthe following files to ask if you want to perform a file overwrite; it is OK tooverwrite these files.COPY A:\NOVELL\NETWARE\NBI.NLM C:\NWSERVERCOPY A:\NOVELL\NETWARE\MSM.NLM C:\NWSERVERCOPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\NWSERVERCOPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\NWSERVERCOPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\NWSERVER10. Go to the Novell server directory and enter server at the DOS prompt torestart the server.11. Install the latest available Novell patches for NetWare 4.11 now. Make sure toselect the Version 3.31 ODI LAN Updates for Hardware if given the opportunity.12. Issue the following commands from the server prompt to bring the serverdown, then restart it: down, then restart server.13. Installation is now complete. Check for the following conditions to determinewhether the adapter is working correctly and whether installation is complete:vThe device driver files are loading successfully.vThere are no error messages.Chapter 4. Software Installation 15
If you experience problems, go to “Appendix B. Problem Determination” onpage 49 .For information concerning NetWare server error messages, see “NovellNetWare Server Driver Messages” on page 50.Server Driver Installation in Existing NetWare 4.11 ServerIf Novell NetWare is in your computer, perform the following steps to install theadapter server device driver.Note: If you are altering the configuration of a previously-loaded adapter, unloadthat adapter before proceeding with these instructions.1. Create a diskette containing the extracted files from the NETWARE.EXE file onthe IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. Be sure that your IBM Turbo 16/4 Token-Ring PC Card 2 is already in yourcomputer. If it is not, follow the instructions in “Chapter 2. Installation” onpage 3.3. Install the latest available Novell patches for NetWare 4.11. Make sure toselect the Version 3.31 ODI LAN Updates for Hardware if given theopportunity. Return to the server console when the installation is complete.4. Down and restart server from the server prompt to bring the server down,then restart it again.5. Check to see if the device driver is loaded. If it is, unload it using the followingcommand: unload token or unload ibmtoken6. Type load install on the server.7. Select Driver Options.8. Select Configure Network Drivers.9. Select Select Drivers.10. On the next panel, press the Insert (INS) key to install the unlisted driver.11. Insert the diskette that you created in step 1; press F3 on the next panel andspecify the path A:\NOVELL\NETWARE.12. Follow the instructions on the panels to complete the installation of the driver.If you need to make any custom configuration changes to the driver, do so atthis time.13. Follow the instructions in the Novell manual toCreate an AUTOEXEC.NCF file.In addition to the instructions in the manual, add the following lines to theAUTOEXEC.NCF file, immediately after the IPX INTERNAL NET statement. Ifnecessary, replace C:\NWSERVER with the actual location of theSERVER.EXE executable.LOAD C:\NWSERVER\NBI.NLMLOAD C:\NWSERVER\MSM.NLMLOAD C:\NWSERVER\TOKENTSM.NLMLOAD C:\NWSERVER\IBMTOKEN.LAN NAME=IBMLS1 DATARATE=M16Note: There will be existing LOAD and BIND IPX statements in theAUTOEXEC.NCF. Delete the LOAD statement (we have replaced it withthe stated LOAD C:\NWSERVER\IBMTOKEN.LAN statement).Also, make any needed modifications to the existing BIND IPX statement.Refer to theBind the Protocol to the LAN Driversection of the Novell manualfor additional information.16 Turbo 16/4 Token-Ring PC Card 2
See “Novell NetWare Server Driver Parameters” on page 20 for a complete listof parameters that can be specified on the LOAD IBMTOKEN command in theAUTOEXEC.NCF file.14. Press ESC and answer YES to save the new file to disk. Press ESC again toreturn to the server console.15. Type the following commands from the server prompt to shut down the serverand exit to DOS: down, and then exit.16. Perform the following COPY commands, making sure that the diskette that youcreated in step 1 is inserted in the diskette drive. Note that it will prompt you ateach of the following files to ask if you want to perform a file overwrite; it is OKto overwrite these files.COPY A:\NOVELL\NETWARE\NBI.NLM C:\NWSERVERCOPY A:\NOVELL\NETWARE\MSM.NLM C:\NWSERVERCOPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\NWSERVERCOPY A:\NOVELL\NETWARE\IBMTOKEN.LAN C:\NWSERVERCOPY A:\NOVELL\NETWARE\IBMTOKEN.LDI C:\NWSERVER17. Go to the Novell server directory and enter server at the DOS prompt torestart the server.18. Installation is now complete. Check for the following conditions to determinewhether the adapter is working correctly and whether installation has beencompleted successfully:vThe device driver files are loading successfully.vThere are no error messages.If you experience problems, go to “Appendix B. Problem Determination” onpage 49.For information concerning NetWare server error messages, see “NovellNetWare Server Driver Messages” on page 50.Novell NetWare 5.0 ServerServer Driver Installation During NetWare 5.0 Server InstallationInstallation of the network board and its device driver occurs during the combinedstorage device and network board installation step. Use the following instructions toinstall the network board and its driver during a new NetWare 5.0 server installation.1. Create a device driver installation diskette.Create a diskette containing the extracted files from the NETWARE.EXEpackage file on the IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. During the installation program, when you get to Select a Storage Device and aNetwork Board:vSelect and configure the storage devicevSelect and configure the network boardvLoad a NetWare Loadable Module TM program (if required)3. Select a Storage DeviceStorage devices such as hard disks, CD-ROMs, and tape devices require asoftware driver to communicate with the storage adapter. The software driver forthe storage device is called a custom device module (CDM). Each type ofstorage device requires a CDM.The installation program auto-detects many types of storage devices such asIDE drives, SCSI drives, CD-ROM drives, and tape drives. If your storageChapter 4. Software Installation 17
device is not detected, choose the appropriate driver from the list of availabledrivers provided with NetWare 5.0. You can also add a new driver from adiskette. CDMs can be obtained from the storage device manufacturer.4. Select a Network BoardThe software driver for a network board is called a LAN driver.The installation program auto-detects many types of network boards. If yournetwork board is not detected, choose the driver for the network board from thelist provided with NetWare 5.0. You can also use a new or updated driver fromthe diskette that you created in step 1.The network board must be installed and configured correctly. For servers, it isrecommended that DATARATE is set to M16 or M4, and clients be set to Auto.You might be able to influence certain network board properties by configuringthe system and the network board or both.5. Load a NetWare Loadable Module (if required)Certain server and network configurations might require you to load a NetWareLoadable Module (NLM) before you can complete the server installation. Anexample is loading ROUTE.NLM for a Token-Ring environment that requires it.Server Driver Installation in Existing NetWare 5.0 ServerThe following procedure explains how to use NWCONFIG to load a LAN driver andbind a protocol.1. Create a diskette that contains the extracted files from the NETWARE.EXEpackage file on the IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. At the server console prompt, enter NWCONFIG3. Select Driver Options > Configure network drivers.4. To select a driver from all of the available drivers, choose Select a driver. Thescreen will display a list of all available drivers.5. Press Insert. Follow the instructions on the panels. Use the diskette that youcreated in step 1 when you are prompted to supply an unlisted driver. Thedirectory is A:\NOVELL\NETWARE.Note: For some drivers, a message might appear indicating that the drivermust be loaded manually (at the console prompt). To load a drivermanually, follow the screen prompts or press F1 for more information.6. Set protocols. When the window containing protocol choices is displayed,select the protocol that you want to use and press the spacebar. If you selectTCP/IP, enter the IP address and the IP mask.7. Set parameters. Use the down arrow key to move the cursor to the parameterwindow. Enter parameter values as needed. Press F1 for help. It isrecommended for servers that the Data Rate is set to 4 Mbps or 16 Mbps, andclients be set to Automatic.In some cases, the system displays a pop-up list of values for the field fromwhich you select the desired value. In other cases, you must type in a valueand press Enter to move to the next field.8. To specify a particular frame type for a Token-Ring driver, press F3 to display alist of frame types. Use the arrow keys to move up and down the list. PressEnter to select a frame type. When finished, press F10. If you do not specify aparticular frame type, all frame types are loaded automatically, but only thosefound on the network are actually bound to the driver.9. Select Save parameters and load driver.10. Confirm bindings of the protocol with the driver and the network number.18 Turbo 16/4 Token-Ring PC Card 2
11. Driver installation is now complete. To add another adapter, down the server,power off the server, and insert the additional adapter. NetWare will load theappropriate driver automatically. Then repeat step 10.Novell Client DOS/Windows 3.1x1. Download Novell Client DOS/Windows 3.1x Version 2.5 or higher from theNovell Web site (support.novell.com). Unzip the downloaded file to a directoryon your computer.2. Exit Windows.3. From a DOS prompt, go to the driectory where you put the file. RunINSTALL.EXE.4. Select Yes or No to respond to the Novell License Agreement.5. Select Novell Client Windows Support and Work Station Manager 3.X.Press F10 to save and continue.6. Select 32–bit LAN Drivers and press F10 to save and continue.7. Select USER SPECIFIED 32–Bit Driver and press Enter. Insert the CD-ROMor the diskette that contains the device drivers into the appropriate drive. Enterthe path to the 32–bit ODI driver: x:\novell\netware where x is your CD-ROMdrive letter. The panel should sayIBM Token-Ring PCMCIAPress Enter, configure the parameters, and press F10 to save and continue.8. At the Installation Configuration Summary panel, confirm that the values arewhat you selected, and press F10 to save and continue.9. The files will be copied at this point.10. Installation is now complete.11. Reboot your computer and start Windows to connect to and login to yourserver.12. Check for the following conditions to determine whether the adapter is workingcorrectly and whether installation has been completed successfully:vThe device driver files are loading successfully.vThere are no error messages.If you experience problems, go to “Appendix B. Problem Determination” onpage 49.Novell NetWare Client32 for Windows 95(Previous version is IntranetWare Client for Windows 95.)Note: You will need the Windows 95 diskettes or CD-ROM to complete thisinstallation.If you are installing on a workstation that already has Windows 95 installed usingNovell IntranetWare Client Version 2.2 for Windows 95, use the following procedure.Note: IntranetWare Client Version 2.2 for Windows 95 or Novell Client Version 2.5for Windows 95 can be downloaded from Novell on the Web atsupport.novell.comChapter 4. Software Installation 19
If you are upgrading from the NetWare DOS Requester (VLM) client or if you do nothave any network client installed, you need to have the Windows 95 CD-ROM ordiskettes or the Windows 95 .CAB files.1. If the NDIS driver is not already installed, install it using the instructions in“Windows Installation” on page 23.2. After downloading the code, run the installation program (SETUP.EXE) forNovell IntranetWare Client Version 2.2 for Windows 95 or Novell Client Version2.5 for WIndows 95.3. Select Yes or No to respond to the Novell License Agreement.4. Select Start to begin the installation.If you are prompted to select an adapter, select one that matches yourhardware. This step might not be necessary, as you should have alreadyselected the adapter in the first step.5. If you do not need to customize your installation, select Reboot.6. If you want optional features or need to configure your workstation, selectCustomize. Then select Reboot.Novell NetWare Server Driver ParametersFor the Novell NetWare server, the parameters are set on the command line or onthe load IBMTOKEN line in the AUTOEXEC.NCF file.Table 4. Novell NetWare Driver ParametersParameter ExplanationDATARATE= Configures the Token-Ring data rate for the PC Card. It isrecommended for servers that the DATARATE be set to M16 or M4,and clients be set to AUTO.Valid values:AUTO AutoSense – automatic ring-speed detection.Note: The PC Card will not function with AutoSense if it isthe first one on the ring. AutoSense is not designed forchanging ring speed while the PC Card is operational. It isusually necessary to reload the driver.M16 16-Mbps ring speed operation.M4 4-Mbps ring speed operation.The default is AUTO.Note: If using Novell NetWare SFTIII, M16 or M4 must be selectedfor the DATARATE parameter on both of the SFTIII machines. Donot use AUTO.FRAME= This string defines the frame type to be used with the PC Cardwhen loading the IBMTOKEN LAN driver.Token-Ring drivers can add most-significant bit (MSB) orleast-significant bit (LSB) following the frame type designation. LSBforces canonical addresses to be passed between the MLID andthe upper layers. The MSB designation forces non-canonicaladdresses to be passed (this is the default for Token-Ring media).Valid values:TOKEN-RING or TOKEN-RING_SNAPThe default is TOKEN-RING.20 Turbo 16/4 Token-Ring PC Card 2
Table 4. Novell NetWare Driver Parameters (continued)Parameter ExplanationFULLDUPLEX= This keyword permits the IBMTOKEN LAN driver to activateToken-Ring full-duplex operation supported by the PC Card and theNetWare server environment.Valid values:YES, NOThe default is YES.MEM1= The MEM1 keyword is needed if you are using a Card Servicesversion earlier than version 5.00. This value is the base sharedRAM address that your adapter is configured to use. If it is notspecified, you will be prompted for this parameter when the driverloads. If you are using a version of Card Services which is 5.00 orhigher, this parameter is not needed..Valid values:C0000, C4000, C8000, CC000, D000, D4000, D8000,DC000There is no default for this parameter.NODE= This keyword is used to set a locally administered address for thePC Card. A local address must contain 12 hexadecimal charactersand can be specified in either most-significant bit (MSB) orleast-significant bit (LSB) format.To specify an MSB node address, the letter M immediately followsthe last digit of the node address. To specify an LSB node address,the letter L immediately follows the last digit of the node address. Ifneither an M nor L is specified after the last digit of the nodeaddress, MSB will be assumed.If a node address is specified in MSB format, the value must bewithin the range X'400000000000' to X'7FFFFFFFFFFF' (forexample, X'400000000002'M). This same address specified in LSBformat would be X'020000000080'L with an L optionally appendedto the end.Notes:1. Do not assign the same local address to two or more stations.Severe station communication or network failures can occurwhen two or more stations are assigned the same address.2. If you do not assign a locally administered address, the PCCard uses the universally administered address permanentlyencoded in its memory.SLOT= This keyword defines the slot number of the corresponding PCCard in the computer. To avoid being prompted to enter a slotnumber when the IBMTOKEN LAN driver is loaded, specify thiskeyword. One SLOT number is required for each NIC if you areusing more than one.Chapter 4. Software Installation 21
Table 4. Novell NetWare Driver Parameters (continued)Parameter ExplanationRT= Route Switching Mode. This parameter indicates whether the drivershould enable code that attempts to send routable traffic directly toa destination rather than through the router. This can improve theperformance of these connections and reduce the workload at therouter. If the value is Disable, all routable frames will be sentthrough the router.Valid values:AAutomatically determines whether to use Peer or Clientmode.PCommunicates with a peer destination station to establisha direct path.CUses an MSS server to determine the direct path.DDeactivates the route switching function for this PC Card.The default is D.RTTS= Route Switching Table Size. This parameter specifies the number ofentries allowed in the route table kept for Route Switching support.This should be set equal to or greater than the number of remotestations this station will send data to using routable IP frames. If itis set too low, some of the traffic that could be sent directly willinstead be sent through the router.Valid values: 16-1024The default is 1024.RTSM= Route Switching IP Subnet Mask. This parameter contains acharacter string specifying the IP subnet mask for the IP subnet towhich this PC Card will attach. This value is entered as an IPdotted-decimal value (for example, 255.255.255.0). This is amandatory parameter when the RTSWMode parameter is set toAuto or Peer.Valid values:xxx.xxx.xxx.xxxA dotted-decimal IP network number (15 charactersmaximum).Disable When not in use.The default is Disable.RTHT= Route Switching Holding Time. This parameter specifies the RouteSwitching information holding time value. This determines how oftena remote station must refresh its Route Switching information whichpertains to this station.Valid values:2to20The default is 20.22 Turbo 16/4 Token-Ring PC Card 2
Table 4. Novell NetWare Driver Parameters (continued)Parameter ExplanationTPRn= TCP Port Range. This represents a set of parameters whichdesignate the transmit frame priority value for a specified TCP portrange. n is 1, 2, 3, 4, or 5. The format of this 9-digit hexadecimalstring is:<PortNumber><PortNumber><PriorityValue>where each PortNumber is a four-character hex value andPriorityValue is a one-character hex value. The two PortNumberfields define a starting and ending value that make up a range, withthe starting value less than or equal to the ending value.Valid values:PortNumber0x0000 to 0xFFFFPriorityValue1to6There is no default for this parameter.UPRn= UDP Port Range. This represents a set of parameters whichdesignate the transmit frame priority value for a specified UDP portrange. n is 1, 2, 3, 4, or 5. The format of this 9-digit hexadecimalstring is:<PortNumber><PortNumber><PriorityValue>where each PortNumber is a four-character hex value andPriorityValue is a one-character hex value. The two PortNumberfields define a starting and ending value that make up a range, withthe starting value less than or equal to the ending value.Valid values:PortNumber0x0000 to 0xFFFFPriorityValue1to6There is no default for this parameter.Windows InstallationWindows 95 and Windows 981. Insert the IBM Turbo 16/4 Token-Ring PC Card 2 in your computer and switch iton. When Windows loads, it will alert you to the fact that new hardware wasfound in your computer. If it does not, see “Troubleshooting and Error Codes” onpage 50.2. When the Update Device Driver Wizard (Windows 95) or the Add NewHardware Wizard (Windows 98) appears, insert the CD-ROM or diskette thatcontains the driver files.3. Follow the instructions on the panels to install the driver files for the IBM Turbo16/4 Token-Ring PC Card 2. During installation, you might be prompted to insertthe diskette labeled IBM Shared RAM Token-Ring Adapter NDIS 3/4/5 DeviceDrivers. At this point, click OK and select the path to the driver diskette orCD-ROM in the copy files from box. You might also be prompted to insert theChapter 4. Software Installation 23
diskette labeled Windows 95/98. At this point, click OK and select the path tothe diskettes, CD-ROM, or hard disk where the Windows installation files arelocated in the copy files from box.4. When driver installation is complete, Windows will prompt you to reboot yourcomputer. The IBM Turbo 16/4 Token-Ring PC Card 2 will not function until youdo so.Using the IBM Turbo 16/4 Token-Ring PC Card 2 with TexasInstruments Cardbus Controllers and Windows 95 OSR2Some portable PCs that have support for Cardbus PC Cards use the TexasInstruments Cardbus socket controller. Windows 95 OSR2 (build 4.00.950B)includes support for the chipset. IBM Token-Ring PC Cards will not functioncorrectly if:vYour portable PC uses the Texas Instruments Cardbus controller chipset andvYour installation of Windows 95 OSR2 uses the Cardbus drivers that shippedwith Windows 95 OSR2If you are having problems getting your IBM Token-Ring PC Card to function andyou suspect that you have the Windows 95 Cardbus socket controller driversinstalled, follow the procedures below to determine if you need the Windows 95Cardbus socket controller driver patch.1. Right-click My Computer on the desktop and select Properties. This will bringup the system control panel.2. Check the version of Microsoft Windows 95. If the version is 4.00.950B, you arerunning OSR2 and should continue reading; otherwise, you do not need thepatch.3. Click the Device Manager tab in the system control panel and check to see ifyou have the Cardbus Socket Controller devices installed by expanding thePCMCIA socket section. If you do not have this device listed, then you do notneed the patch.4. Click Start and select Find — Files or folders...5. Search for the file cbss.vxd on the drive that contains your Windows installation(usually C). When you find it, right-click the cbss.vxd file and select Properties.6. Click the Version tab and check the version of the file. If the version is4.00.1111, then you are using the Cardbus socket controller drivers that shippedwith Windows 95 OSR2. Contact the computer manufacturer to obtain a patchfor the Cardbus controller for Windows 95 OSR2.Windows NT 3.511. Insert the IBM Turbo 16/4 Token-Ring PC Card 2 in your computer and switch iton. When Windows NT loads, login to the computer and open the control panel.Double-click Network.2. Click Add Adapter and select <Other> Requires disk from manufacturer.Atthis point, Windows NT will prompt you for your driver files. Select the path toyour driver diskette or CD-ROM and click OK.3. When prompted to choose the adapter, select IBM Turbo 16/4 Token-Ring PCCard 2. After installation is complete, the adapter should appear in the InstalledAdapter Cards window.4. Select OK to close the network control panel. You might be prompted toconfigure your protocols. Consult the documentation that came with your24 Turbo 16/4 Token-Ring PC Card 2
operating system if you need help doing this. You will also be prompted toreboot your computer. The IBM Turbo 16/4 Token-Ring PC Card 2 will notfunction until you do so.Windows NT 4.01. Insert the IBM Turbo 16/4 Token-Ring PC Card 2 in your computer and switch iton. When Windows NT loads, login to the computer and open the control panel.Double-click the Network icon.2. Click the Adapters tab, then click Add.... Click Have Disk and specify thelocation to the driver files.3. When prompted to choose the adapter, select IBM Turbo 16/4 Token-Ring PCCard 2. After installation is complete, the adapter should appear in the NetworkAdapters list.4. Close the Network Control Panel. You might be prompted to configure yourprotocols. Consult the documentation that came with your operating system ifyou need help doing this. You will also be prompted to reboot your computer.The IBM Turbo 16/4 Token-Ring PC Card 2 will not function until you do so.Windows 2000Windows 2000 includes built-in support for your IBM Turbo 16/4 Token-Ring PCCard 2. Windows 2000 will automatically install its built-in driver for you. However,the driver that comes with the adapter includes support for some features that arenot supported in the driver that is included with Windows 2000. You might want toupdate the driver to take advantage of the latest features.1. Click Start,Settings, and Control Panel.2. Double-click System, select the Hardware tab, and select Device Manager.3. Expand the network adapters, double-click IBM Turbo 16/4 Token-Ring PCCard 2, and select the Driver tab.4. Select Update Driver, and follow the instructions on the panels in the wizard.5. When the system sayssearch for a suitable driver for my device, insert thediskette, and specify the diskette drive (a:\). Press OK.6. Follow the instructions on the panels until the installation is complete. You mightbe alerted to the fact that the device driver has not been digitally signed byMicrosoft. Choose Yes to continue installation. If your system is set up to blockinstallation of unsigned drivers, contact your system administrator forassistance.7. Restart your computer.8. Installation of the driver is now complete.Remote Unattended Install for Windows 95, Windows 98, and NT 4.0Instructions are on the adapter CD-ROM and can be read with your Web browser.See “Appendix A. CD-ROM Content and Software Packages” on page 45.Chapter 4. Software Installation 25
OS/2 InstallationOS/2 NDIS 2 Device Driver Using MPTSIf your OS/2 network operating system has not yet been installed on your computer,install it now and follow its instructions for installing device drivers. If an OS/2network operating system has previously been installed, follow the instructions herefor using MPTS to install device drivers.1. Start MPTS by performing either of the following actions:vFrom the OS/2 desktop, double-click the MPTS icon.vFrom an OS/2 window, go into the IBMCOM subdirectory and enter mpts atthe OS/2 prompt.2. Select OK on the MPTS logo panel.3. Select Install. You will be prompted for the source of the .NIF file. Put theCD-ROM in the drive. Enter x: where x is the letter of your CD-ROM drive.Select OK once the Installation Complete message appears. You will return tothe main menu.4. Select Configure in the MPTS dialog box.5. On the Configure panel, make sure that LAN adapters and protocols ispreselected and then select Configure at the bottom of the panel.6. In the Configuration panel, in the Network Adapters group box, select IBMTurbo 16/4 Token-Ring PC Card 2 and select ADD.Note: You can edit parameter settings for this PC Card. Highlight this adapterin the Current Configuration list box and select Edit. When you havefinished with the parameter settings, select OK.7. In the Protocols list box, select the protocols used by your network application.Highlight each protocol and select ADD. If you are not sure which ones to use,select IBM IEEE 802.2 and IBM OS/2 NetBIOS protocol drivers or ask yournetwork administrator.The protocol drivers you have selected will appear under the adapter drivername in the Current Configuration list box.Note: You can edit parameter settings for the protocols. Highlight a protocoland select Edit.8. Select OK when you have finished selecting and editing protocols in theConfiguration panel.9. Select Close on the Configure panel.10. Select Exit in the MPTS dialog box.11. Select Exit on the Update CONFIG.SYS panel to update the CONFIG.SYS file.12. Select OK when you get the message that the CONFIG.SYS has beensuccessfully updated.13. Select Exit on the Exiting MPTS panel.14. Shut down OS/2 and restart your computer to let the changes take effect.Installation is now complete.15. At system startup, check for the following conditions to determine whether theadapter is working correctly and whether installation has been completedsuccessfully:vThe device driver files loaded successfully. There are no error messages.vYou are able to log on and communicate with the network.26 Turbo 16/4 Token-Ring PC Card 2
If you experience problems go to “Appendix B. Problem Determination” onpage 49 .OS/2 NDIS 2 Device Driver Using Other Installation ProgramsIBM TCP/IP for OS/2 is an example of a product that provides driver installationprograms.1. Insert the CD-ROM in the drive.2. Use your product documentation to install the driver (IBMTOKCS.OS2).3. Change the parameters if needed.4. Installation is now complete. Shut down and restart your computer for allchanges to take effect.5. Check for the following conditions to determine whether the adapter is workingcorrectly and whether installation has been completed successfully:vThe device driver files load successfully.vThere are no error messages.If you experience problems go to “Appendix B. Problem Determination” onpage 49.DOS InstallationMicrosoft Windows for Workgroups/NDIS 2Perform the following installation steps for the PC Card to install a real mode driverwhen using Microsoft Windows for Workgroups:1. Follow the setup instructions included with Windows for Workgroups.If Windows for Workgroups is not already installed, you will be prompted toinstall a network PC Card during the Windows for Workgroups installationprocess.If you are installing the PC Card in a computer that already has Windows forWorkgroups installed, refer to theMicrosoft Windows for Workgroups User’sGuidefor instructions on how to install and configure a third-party device driver.Note: If you have Windows for Workgroups Version 3.11, perform the followingsteps before proceeding with step 1.a.vWhen you get to the Network Setup window, select Networks, andthen Install Microsoft Windows Network.vChange any other items for your environment, and select OK andContinue.a. When prompted to install a new PC Card, select Unlisted orupdated network adapter. You will be asked to provide the networkdriver. Insert the CD-ROM, check the path, and select OK.b. Follow the instructions as they appear on the window to install theIBMTOKCS.DOS device driver.c. Accept the defaults for Interrupt, MMIO, and SRAM. You will be givena chance to update these later, if necessary.d. Exit the Windows for Workgroups setup.Do notreboot your computerat this time. Exit to the DOS prompt.Chapter 4. Software Installation 27
2. Configure the PC Card.Memory management notesvIf you are using Card and Socket Services, the program will default toAutoset mode, which allows the LAN driver to negotiate with Card and SocketServices for available resources. LANAID will allow you to select values forresources to be used by your PC Card such as Interrupt, memory, and I/OBase Address.vIf you are not using Card and Socket Services in Autoset mode, you mustensure that the values that you select for Interrupt, MMIO, and SRAM do notconflict with those for other PC Cards and resources installed in yourcomputer (such as video, sound, COM port).vIf you are using EMM386, in most cases the memory exclusions will beautomatically handled by LANAID. If you are using a memory manager, youmust exclude the memory ranges being used by your PC Card (8-KBdefault).a. If LANAID is not already installed, install it as described in “InstallingLANAID” on page 33.b. After LANAID is installed, continue with “Using LANAID to Configure the PCCard” on page 34. When you get to the panel that asks for the existingnetwork operating system, select Microsoft Windows for Workgroups.3. Step 5 of the Installation Checklist is now complete. Continue with the next stepon page 3.ODI 16–bit ClientNote: It is recommended that you use LAN Client (Client32) whenever possible asan efficient solution.The 16–bit DOS Novell NetWare Requester environment supports access to serversrunning Novell NetWare 3.11 or higher.To install the TOKENCS.COM ODI driver on a DOS computer, perform the followingsteps. Consult your Novell NetWare documentation for instructions regarding how tocreate the NetWare Client for DOS and MS Windows diskettes.1. Create a diskette containing the extracted files from the DOSODI.EXE file onthe IBM Turbo 16/4 Token-Ring PC Card 2 CD-ROM.2. Insert the NetWare Client for DOS and MS Windows Disk 1 into theappropriate drive.3. At the command prompt, type a:, where a is your drive letter, and then pressEnter.4. Type install and then press Enter.5. Follow the instructions as they appear. In step 5 of the instructions, pressEnter and select Other Drivers.6. Insert the CD-ROM or the diskette that you created in step 1 into theappropriate drive. When prompted, specify the location to the chosen mediaand press Enter. Specify the path as a:\novell\dos (or x:\novell\dos for theCD-ROM version).7. Highlight your adapter and press Enter.8. At this time you can change the default parameters. When you finish makingany desired changes, press F10. “ODI 16–bit Client Parameters” on page 29contains the parameters that can be configured in the NET.CFG file.28 Turbo 16/4 Token-Ring PC Card 2
9. Follow the instructions presented to finish the installation.Note: If source routing is required, edit the STARTNET.BAT file that is in theclient directory (usually c:\nwclient) and add the following line after theIPXODI statement.c:\nwclient\route10. Shut down and restart your computer for all changes to take effect.11. Check for the following conditions to determine whether the adapter is workingcorrectly and whether installation has been completed successfully:vThe device driver files loaded successfully. There are no error messages. Iferror messages are displayed or if you do not see messages that indicatethat the drivers have been installed, see “Troubleshooting and Error Codes”on page 50.vThe adapter LEDs indicate normal operation: green ON, amber OFF.If you experience problems go to “Appendix B. Problem Determination” onpage 49.ODI 16–bit Client ParametersTable 5. ODI 16–bit Client ParametersParameter ExplanationNODE ADDRESS To set a locally administered address for the adapter, type in thelocal address that you want to use. The local address must contain12 hexadecimal characters and can be specified in either MSB (thedefault), or LSB format. To specify an MSB node address, the letter″M″immediately follows the last digit of the node address. Tospecify an LSB node address the letter ″L″immediately follows thelast digit of the node address.This keyword is specified as NODE ADDRESS in NET.CFG forDOS and OS/2 workstations.If a node address is specified in MSB format, the characters mustbe within the range X'400000000000' — X'7FFFFFFFFFFF'. Tospecify a node address in MSB format, add an ″M″to the end ofthe address (for example, X'400000000000M'). This addressspecified in LSB format would be X'020000000080L'.Notes:1. Do not assign the same local address to two or more stations.Severe station communication or network failures might occurwhen two or more stations are assigned the same address.2. If you do not assign a locally administered address, the adapteruses the universally administered address (the addressencoded in the adapter memory at the factory). The universallyadministered address appears on a label on the adapter.PORT The port address for a primary network adapter is X'A20'. The portaddress for an alternate network adapter is X'A24'.Valid values:X'A20' and X'A24'Default value:X'A20'Chapter 4. Software Installation 29
Table 5. ODI 16–bit Client Parameters (continued)Parameter ExplanationNIC UAA This parameter can be used to specify which physical networkadapter is to be associated with this load of the LAN driver. Theparameter value can be a 1–digit ordinal value or a 12–digit,hexadecimal, universally administered address (MAC address).With ordinal type parameter usage, an ordinal value of 1 indicatesthe adapter with thelowestuniversally administered address value.An ordinal value of 2 indicates the adapter with the next lowestuniversally administered address, and so on. If there are twoadapters, the one with the higher MAC address has an ordinalvalue of 2.This parameter is not required for a single network adapter;however, this parameter is necessary if the system contains morethan one network adapter and at least one of them is a Turbo 16/4Token-Ring PC Card 2. Otherwise, system or network errors arelikely to result.NOFULLDUPLEX This parameter disables full-duplex ring insertion.MAX FRAME SIZE This option sets the maximum number of bytes that can be put onthe wire by the Turbo 16/4 Token-Ring PC Card 2. The numbermust be a multiple of 8 and include the number of bytes for thedata packet for adapter overhead (6 bytes) and for the maximumheader (35 bytes LAN header + 5 bytes SNAP header + 74 bytesprotocol header). The total number of bytes is 114.If the LAN speed is 16 Mbps, the number must be between 632and 17 960. If the LAN speed is 4 Mbps, the number must bebetween 632 and 4 464. If 2 KB packets are desired, calculate themaximum frame size as:2048+6+35+5+74=2168 (rounding up to next multiple of 8gives 2168)An example NET.CFG entry for using 2–KB packets would appearas:LINK DRIVER TOKENMAX FRAME SIZE 2168In an OS/2 environment, to set frame sizes greater than 1540bytes, you must configure LSL buffers equal to or greater than theframe size you desire. To configure the adapter to handle4210–byte frames, use this statement in your NET.CFG file:LINK SUPPORTBUFFERS 14 4210Refer to the section that discusses NET.CFG options inNovellNetWare Workstation 4.0 for OS/2for information about configuringlink suport layer buffers.FRAME This parameter indicates the token-ring frame type to be used bythe LAN driver and network adapter.Default value:Token ringValid values:Token ring, token-ring_SNAPNOSHALLOWMODE This parameter disables adapter shallow mode operation.30 Turbo 16/4 Token-Ring PC Card 2
Table 5. ODI 16–bit Client Parameters (continued)Parameter ExplanationRECEIVEBUFFERSIZE This parameter can be set to a value from 192 to 2048, inclusive.Any value smaller than 192 is changed to 192. Any value largerthan 2048 is changed to 2048. Numbers between 192 and 2048that are not on an eight-byte boundary are rounded up to the nexthigher eight-byte boundary.EXPRESSMODE For DOS only, this parameter enables adapter fast-path receiveexpress mode.ENHANCEDMODE Causes the adapter to operate in fast-path receive mode and in the4–KB paging mode of fast-path transmit operation. The Auto 16/4Credit Card can not function in Enhanced Mode (Enhanced=NO).BUS ID PCMCIA 3 This keyword must be present in the NET.CFG file.PCMCIA This keyword must be present in the NET.CFG file forconfigurations that use Card Services to enable the adapter. Thiskeyword must not be used in configurations that enable the adapterby way of a Point Enabler.AUTORINGSPEED This keyword will cause the adapter to save the speed of the ringthat it is opening into and use that ring-speed value as its speedthe next time that it is initialized.Chapter 4. Software Installation 31
32 Turbo 16/4 Token-Ring PC Card 2
Chapter 5. LANAIDAfter you have inserted the PC Card, you must configure the PC Card software tooperate with your computer and network operating system. You will need themanuals that were shipped with your network operating system.If your computer does not have a hard disk, contact your network administrator.About LANAIDLANAID is a software tool that is shipped on the IBM Turbo 16/4 Token-Ring PCCard 2 CD-ROM. Use LANAID to automatically configure the appropriate systemfiles for the IBM Turbo 16/4 Token-Ring PC Card 2 to work with any of the networkoperating systems that are listed below.LANAID requires that Card Services or an Intel socket controller that is compatiblewith the point enabler is installed.LANAID detects the following network operating systems and changes parametersin the PC Card configuration in order to work with them:vIBM LAN ClientvDOS Novell NetWare Client-16vOS/2 Novell NetWare ClientvArtisoft LANtastic 6.0, 7.0vBanyan VINES 6.xvMicrosoft LAN ManagervWindows for Workgroups\NDIS 2vOther DOS NDIS environmentsFor all other environments, you will use your network operating system to changeparameters in the PC Card configuration.The Net AddressLANAID identifies the PC Card to be configured by its universally administeredaddress. The universally administered address, or net address, of the IBM Turbo16/4 Token-Ring PC Card 2 was assigned at the factory and is on the back of thecard. Ensure that the address shown by LANAID is the same as the address on thePC Card. It may be necessary to remove one or more PC Cards to allow LANAIDto find the PC Card to be configured.Installing LANAIDThe LANAID graphical user interface operates under DOS or in afull-screenDOSsession of OS/2. (A DOSwindowof OS/2 will not work correctly.) You need at least1.5 MB of free, extended memory and 300 KB of conventional memory to run theprogram. At a DOS prompt, enter mem to find out about the memory availability onyour system.You can select LANAID options in several ways. You can click with a mouse orother pointing device, or you can make selections by tabbing to your selection and© Copyright IBM Corp. 1997, 1999 33
pressing Enter. (If you will be using a mouse with LANAID, make sure that youhave a mouse driver installed.) You can also select push buttons withhot keys. Thehot keys are the letters that correspond to the underlined characters on the pushbutton. Press Alt plus the hot-key letter.You can get help on each LANAID panel by selecting the Help button at the bottomof the panel. You can get context-sensitive help by placing your mouse pointer onany part of the panel and pressing F1.1. Install LANAID on your hard disk:a. At the DOS prompt, insert the CD-ROM in the drive and enter install fromthe x:\lanaid directory, wherexis your CD-ROM drive. The files willautomatically decompress and copy to the target directory. When this iscomplete, the LANAID program will be automatically invoked.b. Type the drive, path, and directory you want to use for LANAID. You can letit default to C: for the drive and \LANAID for the directory, or you can enternew values. Press Enter for each entry.2. OR, extract the package file LAIDPKG.EXE to the drive, path, and directory thatyou want to use for LANAID. See “Appendix A. CD-ROM Content and SoftwarePackages” on page 45. The files will automatically decompress and copy to thetarget directory. When this is complete, type lanaid from the directory to whichthe package was expanded.Using LANAID to Configure the PC CardThis section explains how to run LANAID to configure the PC Card for operationwith a previously installed network operating system and device driver. See“Chapter 4. Software Installation” on page 9 for information on installing networkoperating systems and device drivers.If you are using Card and Socket Services, LANAID will default to Autoset mode,which allows the LAN driver to negotiate with Card and Socket Services foravailable resources. If you do not use Autoset mode, LANAID will allow you toselect values for resources, such as Interrupt and I/O Address, to be used by yourPC Card.1. From the LANAID main panel, select Network Software. On the NetworkOperating System Choices panel, select Identify Existing Network OperatingSystem.2. On the Network Operating System Selection panel, LANAID identifies a networkoperating system and the directory in which the network operating system isinstalled. It is important to confirm these choices or manually identify the actualinstalled operating system and directory. When the information is correct, pressthe Continue push button.3. From the LANAID main panel, select View Adapter Configuration. On the nextpanel, there are two folders. The Configurable folder shows all the parametersyou can set along with their current values. Parameters that are in conflict withother settings are noted. Use the Suggest push button to have LANAID suggestnon-conflicting values.If you are not using Card and Socket Services in Autoset mode, you mustensure that the values that you select for Interrupt and I/O address do notconflict with those for other PC Cards installed in your computer. Use the34 Turbo 16/4 Token-Ring PC Card 2
Change push button to select from the allowable values yourself. The Hardwarefolder shows parameters of the computer system that you cannot set, but thatmight be useful.Select the Store push button.When you finish with the panels, press the Done button and you will bereturned to the main panel. Installation is then complete. See “Appendix C.Running the Diagnostics Program” on page 81 if you want to use thediagnostics.4. Reboot your computer.Command Line Invocation of LANAIDNote to LAN administrators: If you want to do automated installations of LANClient, use the LANAIDC tool. Enter lanaidc /h from the directory on your harddrive where you installed LANAID. You can also boot the Diagnostics and LANAIDCdiskette that you create from the DIAGDISK.EXE diskette image (see “Appendix A.CD-ROM Content and Software Packages” on page 45). The diskette will boot to amenu that allows you to select either Diagnostics or LANAIDC. See Appendix D.LANAIDC Parameter Information for more information.Bypassing Startup FilesIf startup configuration files are bypassed, LANAID or LANAIDC does not have theinformation to determine the resources used; therefore, it will not allow you to setany parameters. Do not bypass the startup configuration if you want to configureyour system. (A typical way to bypass startup files is by pressing the F5 key duringthe DOS boot phase.)Chapter 5. LANAID 35
36 Turbo 16/4 Token-Ring PC Card 2
Chapter 6. Point Enablers and Card ServicesComputers that support PC Cards have one or more PC Card slots, known as A, B,C... or 1, 2, 3.... The slots are controlled by integrated circuit chips such as theTI1130, TI1131, and TI1250 (Cardbus) controller chip sets, and many more.In order for communications programs to use a PC Card, interface software ofsome sort is needed. At present, several interfaces are available and each has itsadvantages and disadvantages. The two most important interfaces are thoseprovided by Point Connectivity Enablers and Card Services; both are availableunder DOS, but OS/2 requires you to use Card Services.If you decide to use Card Services, you must install and enable it before runningLANAID.A third type of interface is Socket Services.Relationship Between the InterfacesThe following diagram shows how the interfaces relate to each other:Credit Card Software ConfigurationsLAN DeviceDriverLAN DeviceDriverCard ServicesEnabledPoint ConnectivityEnabledCard ServicesEnablerPointEnablerCardServicesSocketServicesSocketControllerSocketControllerLAN DeviceDriverLAN DeviceDriverPCMCIA 2.1Socket ServicesEnabledCardServicesSocketServicesEnablerSocketServicesSocketServicesSocketControllerSocketControllerPoint Connectivity EnablersThese are small programs that provide an interface directly to the PC Cardcontroller; therefore, they must be written to support a particular type of controller.© Copyright IBM Corp. 1997, 1999 37
In the DOS environment only, you have the option of using these point connectivityenablersinsteadof Card and Socket Services.One point enabler is supplied for this PC Card:POINTTR.EXEFor computers with Intel 32365SL PCMCIA controller chip sets or anycontroller that is designed to be compatible. These include the IBMThinkPad, Toshiba 4500 and later, and many other makes.Notes:1. When using the point connectivity enabler, it is vitally important that you makecertain that the system resources used by the PC Card are different from anddo not conflict with the system resources and any other PC Cards installed inyour computer.2. Windows NT currently uses a point enabler called PCMCIA.SYS, whichcurrently ships with Windows NT.AdvantagevEnablers consume no memory — they remove themselves after configuring thePC Card.DisadvantagesvYou must specify the slot; the point enabler will enable only that slot. Therefore,the PC Card must always be in a specific slot.vIn some computers, the slot may not be switched off when the computer is insuspend mode, so the PC Card will continue to consume power.vWhen configuring two or more PC Cards, you must allocate memory andinterrupt resources manually under DOS.Socket ServicesThis is a BIOS-type interface that provides a way to gain access to the PC Cardsockets (slots) of a computer. It identifies how many sockets your computer has anddetects the insertion or removal of a PC Card while the computer is switched on. Ithas an interface to Card Services. Socket Services is part of the PCMCIASpecification.The Socket Services device driver is usually provided by the manufacturer of thecomputer, because the driver must understand the computer’s BIOS and PCMCIAcontroller.Card ServicesThis is a software management interface that allows system resources (such asmemory, interrupts, slots, and I/O ports) to be allocated automatically when SocketServices has detected that a PC Card has been inserted.Client drivers call Card Services to allocate and de-allocate system resources.When Socket Services detects an insertion or removal of a PC Card, it sendsnotification to Card Services. Card Services then notifies its registered client drivers,such as IBMTOKCS.OS2, that they should allocate or de-allocate resources.38 Turbo 16/4 Token-Ring PC Card 2
If the installation program detects Card and Socket Services in your computer, it willdefault to Autoset mode. Autoset mode allows your LAN driver to negotiate withCard Services for memory space and interrupts. This helps to prevent conflicts withother PC Cards that are installed in your computer; however, you will not knowexactly what memory addresses and interrupts have been given to you. It willdefault to Autoset mode if the driver supports it.Card Services requires Socket Services. The Card Services interface will usually beprovided with the operating system.AdvantagesvAbility to insert and remove PC Cards without computer reconfiguration andwithout damaging the electrical contacts.vAutomatic allocation of system resources.vWhen used with your Token-Ring software in Autoset mode, automaticconfiguration of your PC Card occurs.DisadvantageStay-resident program that uses system memory. The amount varies according tothe type of PC Card support and the drivers used.Card Services EnablerIf you want to use a Token-Ring device driver that does not have built-in CardServices support on a system that uses Card Services, CS20TOK.EXE is supplied.This program is a Card Services Enabler that uses Card and Socket Services toconfigure the IBM Turbo 16/4 Token-Ring PC Card 2. As with other enablers, youmust specify the resources desired for the PC Card, and they must agree with thesettings of the Token-Ring device driver for the system to work correctly.The DOS Card Services 2.00 interface enabler shipped on the CD-ROM isCS20TOK.EXE.CS20TOK.EXEDOS Card Services 2.00 interface enabler. It uses the Card Servicesinterface to configure the socket and the PC Card. It is used when theToken-Ring device driver is not a Card Services client driver and a CardServices environment is desired. It works with DOS Card Services 2.00 andhigher.Card and Socket Services versus Point EnablersThere is much debate about this. In principle, Card and Socket Services is thebetter method of connection because it allows you to insert or remove PC Cardsfrom any socket, even while the computer is switched on; and it automaticallyallocates resources like memory, I/O ports, interrupt levels, and slots.Point Enablers, of which two are provided with the PC Card, are popular becausethey remove themselves from memory after having been loaded—as opposed tothe 30–40 KB needed for Card and Socket Services.For point enablers, you have to specify the slot in which a particular PC Card willbe used and you have to specify memory locations, interrupt levels, and otherChapter 6. Point Enablers and Card Services 39
parameters. This is not difficult unless you use several PC Cards at different times,in which case you need to make certain that what you specify does not conflict withany other PC Cards installed in your computer.Autoset ModeCard and Socket Services turns out to be most helpful when you have a number ofPC Cards installed in your computer. If the installation program detects Card andSocket Services in your computer, it will default to Autoset mode. Autoset modeallows your LAN driver to negotiate with Card and Socket Services for memoryspace and interrupts every time you switch on your computer. This helps to preventconflicts with other PC Cards that are installed in your computer; however, you willnot know exactly what memory addresses and interrupts you are using.Using a Memory Manager in DOS EnvironmentsIf your computer comes with a memory manager preinstalled, or if you would like touse one, you must configure your computer so that the memory manager does notuse the same memory as your PC Card. If you have more than one PC Card, youmust reserve the memory needed for all of them. One PC Card cannot use thesame memory ranges as another.To determine whether or not your computer has a memory manager, edit yourCONFIG.SYS file and look for the memory manager driver name. For example,when using EMM386, look for:DEVICE=C:\DOS\EMM386.EXE ......When using a memory manager, considerations for your PC Card environment(Point Enabler or Card and Socket Services) are required. Listed here areexplanations for handling these environments with a memory manager. It is notintended to be all-inclusive. To understand completely your memory manager andyour configuration files, refer to your computer’s operating system manual.Memory Managers with Point EnablersvTo prevent duplicate use of a memory location, the area used by your PC Cardmust be excluded from the memory manager. To do this, you must edit yourCONFIG.SYS file. In certain environments, LANAID will add the excludestatement automatically.If you are using enhanced mode, 8 KB of memory must be excluded. If you areusing compatibility mode, 24 KB of memory must be excluded.vFor the point enabler, the required exclusions are shown in the example below(using EMM386, this is done using the X= parameter):For enhanced mode:DEVICE=C:\POINTTR.EXE SA RS=4 MMIO=D000 IRQ=9 SRAM=D000,4 WS=0..DEVICE=C:\DOS\HIMEM.SYS..DEVICE=C:\DOS\EMM386.EXE 1024 RAM X=D000-D1FFFor compatibility mode:40 Turbo 16/4 Token-Ring PC Card 2
DEVICE=C:\POINTTR.EXE SA RS=4 MMIO=D000 IRQ=9 SRAM=D800,16 WS=0..DEVICE=C:\DOS\HIMEM.SYS..DEVICE=C:\DOS\EMM386.EXE 1024 RAM X=D000-D1FF X=D800-DBFFNotice that the EMM386 line excludes the ranges that the POINTTR.EXE enableruses.Memory Managers with Card and Socket Services1. To prevent duplicate use of a memory location, the area used by your PC Cardmust be excluded from the memory manager. To do this, you must edit yourCONFIG.SYS file. In certain environments, the installation program will add theexclude statement automatically.If you are in enhanced mode, 8 KB of the MMIO range must be excluded.If you are in compatibility mode, 8 KB of the MMIO range (MMIO base addressdefault of D000) and 16 KB of the Shared RAM (SRAM) range (SRAM baseaddress default of D800) must be excluded.In addition, Card Services needs at least 4 KB excluded for its use. Remember,if you are using more than one PC Card, the memory locations for the other PCCards must also be excluded.2. Card Services and memory managers typically do not talk to each other. Youmust tell them what areas can be used. For example, with IBM Card Servicesthe /MA option is used to tell Card Services what memory range it can use forPC Cards. It also uses some of this area for itself. That same /MA range mustbe excluded from the memory manager line. This will prohibit the memorymanager from also using that same space.For IBM CS, the /MA is used to specify the range of memory the PC Cards andCard Services use. The parameter is added to the Resource Map Utility line inyour CONFIG.SYS. For example:vUsing IBM Card Services:On a computer using memory range C0000–CFFFFDEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-CFFF..DEVICE=C:\DOS\DICRMU02.SYS /MA=C000-CFFFThe Resource Map Utility driver name may be slightly different for the variouscomputers. Consult your operating manual.vUsing Phoenix Card Services with the /ADDR option:For some versions of Phoenix Card Services, the /ADDR parameter is usedto specify the 4-KB memory range used by Card Services. The memoryrange chosen for the PC Cards must not conflict with this range. The /ADDRparameter is placed on the Phoenix device driver line in the CONFIG.SYSfile. Consult your operation manual as to the version you have and whetherthe /ADDR option is needed.Note: The /ADDR needs only the starting address of the Card Servicesmemory area.On a computer using memory range D0000–DFFFFChapter 6. Point Enablers and Card Services 41
DEVICE=C:\DOS\EMM386.EXE NOEMS X=D000-DFFF..DEVICE=C:\PCMPLUS\PCMCS.EXE /WAIT=12 /ADDR=D0 /IRQ=93. General Rules:IBM Card Servicesa. The memory area used by PC Cards must fall within the range specifiedby /MA.b. The memory area used by Card Services itself (4 KB) must be includedin the /MA range.c. All of the /MA range must be excluded from your memory manager line.Phoenix Card Servicesa. The memory used by Card Services starting at the /ADDR address andthe memory used by the PC Card should be excluded from the memorymanager line.b. If the /ADDR line is not used, the driver will use the first availableaddress on a 4-KB boundary for Card Services. The memory managerline must exclude this area and the PC Card memory area.Expanded Memory SpecificationExpanded memory specification (EMS) requires 64 KB (one page frame) ofcontiguous memory. This may cause you to move your PC Card memory range.With EMM386 you set the page frame base address using the FRAME= option onthe memory manager line in the CONFIG.SYS. If the FRAME= option is not used,EMM386 will find the first 64-KB block of contiguous memory. For example:1. Using a point enabler with the PC Card at D0000–DBFFF, the C0000–CFFFFrange is free for the EMS page. A sample enhanced mode memory managerline in your CONFIG.SYS is:DEVICE=C:\DOS\EMM386.EXE RAM 1024 X=D000-D1FF FRAME=C000Note: The Token-Ring PC Card uses D0000–D1FFF for 8-KB MMIO. TheFRAME= parameter sets the base address of the EMS page frame (thepage frame uses C0000–CFFFF). So, no PC Cards should be set to usememory in the range C0000–CFFFF.2. Using a point enabler with the PC Card at D0000–DBFFF, the C0000–CFFFFrange is free for the EMS page. A sample compatibility mode memory managerline in your CONFIG.SYS is:DEVICE=C:\DOS\EMM386.EXE RAM 1024 X=D000-D1FFX=D800-DBFF FRAME=C000Note: The Token-Ring PC Card uses D0000–D1FFF for 8-KB MMIO andD8000–DBFFF for 16-KB SRAM. The FRAME= parameter sets the baseaddress of the EMS page frame (the page frame uses C0000–CFFFF).So, no PC Cards should be set to use memory in the rangeC0000–CFFFF.3. Using IBM Card Services, you can set the /MA option such that a 64-KB blockis free for the EMS page frame. A sample memory manager line in yourCONFIG.SYS is:DEVICE=C:\DOS\EMM386.EXE RAM 1024 X=D000-DBFF FRAME=C000..DEVICE=C:\DICRMU01.SYS /MA=D000-DBFF42 Turbo 16/4 Token-Ring PC Card 2
Note: Because of the /MA option, IBM CS will use memory in the rangeD0000–DBFFF only. The FRAME= parameter sets the base address ofthe EMS page frame (the page frame uses C0000–CFFFF). So, no PCCards should be set to use memory in the range C0000–CFFFF.Chapter 6. Point Enablers and Card Services 43
44 Turbo 16/4 Token-Ring PC Card 2
Appendix A. CD-ROM Content and Software PackagesThe CD-ROM contains PC Card drivers, supporting applications, publications,technical tips, and frequently asked questions related to the IBM Turbo 16/4Token-Ring PC Card 2. A nagivational tool is provided to assist in accessing thecontents of the CD-ROM. This tool can be launched by opening the filex:\startcd.htm (where x is the letter of your CD-ROM drive) in a Web browser.Release date information can be obtained from the CD-ROM by selecting CD-ROM— product support. However, the IBM Networking Web site might offer morecurrent information. If you have a Web connection, you can obtain the most currentdrivers and information by selecting IBM Networking Web site — productsupport.vUser’s GuideandToken-Ring Adapter Featuresin HTML and PDF format. See“Product Documentation” on page 47.vDevice Drivers that can be installed directly from the CD-ROM during the devicedriver install process. They are located in the following directories:Operating System DirectoryWindows 9x \ (root)Windows NT \ (root)Windows 2000 \ (root)Novell NetWare Server and Client \NOVELL\NETWARENovell NetWare DOS Requester (16–bit) \NOVELL\DOSOS/2 \ (root)DOS \DOSWindows for Workgroups \WFWvLAN Client files that can be installed directly from the CD-ROM during the LANClient installation process.vSelf-expanding software package and diskette image files.Software PackagesTable 6 lists packages that are available on the Web and on the CD-ROM. Table 7on page 46 lists diskette images that are available on the Web and on theCD-ROM. They can be obtained using the navigation tool already mentioned. Selectthe Web link for the latest version of the file, or select the CD-ROM link to copy thefile directly from the CD-ROM. The files are located on the CD-ROM at x:\download(where x is your drive letter).Run the self-extracting package file to expand to a hard drive (or you can expand toa diskette where noted with an asterisk (*)). The directory structure is maintained asit exists on the CD-ROM.Table 6. Software PackagesPackage Description ExecutableCD-ROM Complete CD-ROM content CDIMAGE.EXE© Copyright IBM Corp. 1997, 1999 45
Table 6. Software Packages (continued)Package Description ExecutableDevice Drivers (*) vDOS and Windows 3.1x (NDIS 2)vNovell NetWare DOS Requester (16–bit)vNovell NetWare Server and ClientvOS/2vWindows 95/98/NT/2000vWindows for WorkgroupsvDOSNDIS.EXEvDOSODI.EXEvNETWARE.EXEvOS2NDIS.EXEvWIN32PCC.EXEvWFWPKG.EXEDocumentation —HTML and PDF vUser’s GuidevToken-Ring FeaturesvUSERGUID.EXEvFEATURES.EXEIBM LAN Client IBM LAN Client — Complete package LCPKG.EXELAN AdapterManagement Agents vOS/2vWindows NT and Windows 9xvDMIOS2.EXEvDMIWIN.EXETivoli ManagementAgents (*) vWindows 3.xvWindows 9xvWindows NTvOS/2vNetWare 3.xvNetWare 4.x and 5.xvTMAW3X.EXEvTMAW9X.EXEvTMAWNT.EXEvTMAOS2.EXEvTMANW3X.EXEvTMANW4_5.EXELANAID (*) LAIDPKG.EXEDiskette ImagesRun these diskette image files to create diskettes. Each image file will create asingle diskette.Table 7. Diskette ImagesImage Description ExecutableLAN AdapterManagement Agents vOS/2 — Diskette 1vOS/2 — Diskette 2vWindows 95/98/NT — Diskette 1vWindows 95/98/NT — Diskette 2vWindows 95/98/NT — Diskette 3vDMIOS2A.EXEvDMIOS2B.EXEvDMIWINA.EXEvDMIWINB.EXEvDMIWINC.EXEIBM LAN Client vIBM LAN Client — Diskette 1vIBM LAN Client — Diskette 2vIBM LAN Client — Diskette 3vIBM LAN Client — Diskette 4vLCDISK1.EXEvLCDISK2.EXEvLCDISK3.EXEvLCDISK4.EXERUI vRemote Unattended Install diskette forWindows 9x and Windows NT for NetBEUIvRemote Unattended Install diskette forWindows 9x and Windows NT for IPvRUIPCCNB.EXEvRUIPCCIP.EXE46 Turbo 16/4 Token-Ring PC Card 2
Product DocumentationComplete product documentation is available for downloading from the CD-ROMand the Web in both PDF and HTML formats. The HTML version can also beviewed directly from your Web browser. Two documents are provided. TheUser’sGuideincludes hardware and software installation instructions, troubleshooting tips,device driver parameters and error messages.Token-Ring Adapter Featuresprovides detailed information about Remote Program Load, LAN Client, LANAdapter Management Agent, Route Switching, Class of Service, and the TivoliManagement Agent.To access the product documentation, insert the CD-ROM into the CD-ROM drive ofyour computer and point your Web browser to x:\startcd.htm (where x is yourCD-ROM drive letter). Select IBM Networking Web Site or CD-ROM and thenDownloads. Select Target Operating System and then select theUser’s GuideorToken-Ring Adapter Features. Select the package name that appears. You might beprompted to select an ftp site from which to download the package. In the Saveas... dialog box, choose the path to the directory where you want to copy thepackage file. Select OK to download the package file. Go to the directory where thepackage was stored and run the package file to expand the files.TheUser’s Guidein PDF format is stored in the file userguid.pdf.Token-RingAdapter Featuresin PDF format is stored in the file feature.pdf. The correspondingHTML versions are in userguid.htm and feature.htm.To view the documentation directly from the CD-ROM, insert the CD-ROM into theCD-ROM drive of your computer and point your Web browser to x:\startcd.htm(where x is your CD-ROM drive letter). Select CD-ROM — product support, selectyour PC Card and then the documentation that you want to view.Appendix A. CD-ROM Content and Software Packages 47
48 Turbo 16/4 Token-Ring PC Card 2
Appendix B. Problem DeterminationCheck this list of possible error conditions if problems occur.1. Make sure that the PC Card is in the socket and that the cable is connected tothe PC Card.2. You are using EMM386.EXE or another memory manager.EMM386 is the source of many problems with PC Cards. The problem occurswhen EMM386.EXE and the LAN device driver are using the same memory.This is calledmemory contention. The PC Card will not function correctly if thiscontention occurs. If you are using Card Services, check to be sure that thememory that Card Services controls is excluded by the memory manager. If youare using a point enabler, be sure that the memory that you use is excluded bythe memory manager. As a quick test, you may want to comment outEMM386.EXE in your CONFIG.SYS, reboot, and try the PC Card again.If the PC Card functions, you will have to edit the EMM386.EXE command toexclude some memory. The PC Card uses 8 KB of memory in two separateareas. These memory areas may be consecutive. See Using a MemoryManager in DOS Environments for more information.3. You are using Card Services.During reboot, you hear four alternating tones. This indicates that Card Serviceswas unable to give you one or more resources that your program requested.Resources are I/O ports, interrupt level, and memory locations.Note: The items in the following paragraph are performed by the installationprogram.If you are using the NDIS driver (IBMTOKCS.DOS), edit the PROTOCOL.INI fileand see whether you have specified a particular value for the interrupt level ormemory locations. This would be indicated by the keywords INTERRUPT=X,MMIO=0xXXXX, or RAM=0xXXXX. If you are using the ODI driver(TOKENCS.COM), edit the NET.CFG file and see whether you have specified aparticular value for the interrupt level or memory locations. This would beindicated by the keywords INT X, MEM #1 XXXXX, or MEM #2 XXXXX.These keywords specify a particular value for these parameters. If you find oneor more of these keywords, comment them out by placing a semicolon in frontof the keyword. Save the file and reboot your computer. If all three arecommented out or are not in PROTOCOL.INI or NET.CFG, the driver is inAutoset mode and lets Card Services determine what values are used by thedriver. If you reboot and still receive the alternating beep alarm, there is aproblem with Card Services. Check your level of Card Services and ensure thatit is the latest available.4. You are using a point enabler.When you use a point enabler, it is essential that the I/O ports, interrupt,memory areas, and slot number that are chosen by the enabler agree with whatthe LAN device driver is expecting. Problems occur when the enabler has setup certain resources and the LAN device driver is expecting others. Typically,the LAN driver will not initialize. Look at the default values for the interrupt,whether the PC Card is a primary or secondary PC Card (this affects the I/Oports), and where the MMIO memory and the SRAM memory are located. Besure that the enabler settings and the settings of the LAN driver coincide. By theuse of parameters on the command line of the enabler and the parameters for© Copyright IBM Corp. 1997, 1999 49
the LAN device driver (in PROTOCOL.INI, NET.CFG, or LSP.INI), you should beable to configure your PC Card to function.5. If you believe that you have a hardware problem with the PC Card, run the PCCard diagnostics. See “Appendix C. Running the Diagnostics Program” onpage 81.6. Check “Troubleshooting and Error Codes” if your computer displays an errorcode. If you do not find your error code, use the following information to contactIBM.Questions, Problems?World Wide WebYou can download the latest code from the World Wide Web.On a Web browser:www.networking.ibm.com/supportIBM Product Support1-800-772-2227 IBM HelpCenter1-800-565-3344 HelpPC (Canada)1-800-237-5511 IBM Support ServicesTroubleshooting and Error CodesNovell NetWare Server Driver MessagesError Code Explanation and ActionIBMTOKEN-xx-201 IBM Token-Ring Shared RAM Adapter, Version xxxExplanation:Information only.User Action:None.IBMTOKEN-xx-202 The IBM Token-Ring Shared RAM Adapter UAA (BIA)isxxx.Explanation:Information only.User Action:None.IBMTOKEN-xx-203 The IBM Token-Ring Shared RAM Adapter is using anLAA ofxxx.Explanation:Information only.User Action:None.50 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionIBMTOKEN-xx-204 Revision levelxxxof the IBM Token-Ring Shared RAMAdapter is incompatible with this driver version.Explanation:The Revision ID of the IBM Token-RingShared RAM Adapter is not one that issupported by this version of the device driver.This correlation is enforced to ensure anappropriate match between the adapterhardware and the device driver software.User Action:Contact your customer service center forassistance. You might need to upgrade youradapter, use a different version of the devicedriver, or both.IBMTOKEN-xx-205 A device driver initialization error occurred (failure codexxx).Explanation:An unexpected error occurred duringinitialization of the device driver.User Action:Properly shut down the computer and switchoff the power to the machine. Restart thecomputer by switching it on again. If the errorpersists, contact your customer servicecenter.IBMTOKEN-xx-206 The configuration parameterxxxwas specifiedimproperly. Its default value will be used.Explanation:The value of a configuration parameter wasimproperly specified.User Action:Edit the configuration file (or rerun theconfiguration program) to specify a value thatis of the correct type and within the allowedrange. Check the adapter installationinstructions for additional information.Appendix B. Problem Determination 51
Error Code Explanation and ActionIBMTOKEN-xx-207 The configuration parameter values have forced theinternal data blocks to exceed the allowed limit.Explanation:The combination of configuration parametersbeing used requires more than the 64–KBmemory area that is available for this adapterinstance to hold its internal controlinformation.User Action:Lower the value of the MaxTransmits orMinRcvBuffs parameters from their currentsetting to reduce the amount of control blockstorage required by the device driver. Shutdown and restart to activate this configurationchange.IBMTOKEN-xx-208 Unable to register interrupt levelxxxfor this adapter.Explanation:The hardware interrupt level assigned to thisadapter was not able to be registered (orhooked) by the device driver.User Action:Check the configuration of your computer,looking for other devices that are assignedthe same interrupt level as this adapter. Tryremoving the conflicting device from themachine and restart the computer to see ifthe problem goes away. If so, then determineif he conflicting device can be left out of themachine, or if the machine can bereconfigured to resolve the conflict. Note thatin most machines, the BIOS assigns certainsystem resources to the devices found in thecomputer, including the interrupt level.IBMTOKEN-xx-210 A hardware failure occurred while attempting to openthe adapter.Explanation:An adapter hardware error was detectedwhen opening the adapter for networkoperation.User Action:Run the adapter diagnostics program toisolate the problem and contact yourcustomer service center. If no problem wasidentified by the diagnostics, check that thecable is attached securely to both the adapterand the network interface (wall plate). Turnthe computer off and then on again to restartthe machine. If the problem persists, contactyour customer service center.52 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionIBMTOKEN-xx-211 A possible lobe wire failure was detected whileattempting to insert into the network.Explanation:The adapter is not correctly connected to theToken-Ring network.User Action:Check that the cable is securely attached toboth the adapter and to the Token-Ringnetwork. You might need to contact your localnetwork administrator to ensure that thecabling in the building is intact and that thenetwork concentrator to which you areattached is operational. If the error persists,try using a different cable.IBMTOKEN-xx-212 A signal loss condition was detected while attemptingto insert into the network.Explanation:The Token-Ring network is not functioningcorrectly.User Action:Contact your local network administrator todetermine the status of your network, or tryconnecting again at a later time.IBMTOKEN-xx-213 The lobe wire connected to the adapter is not attachedto the network.Explanation:The adapter is not correctly connected to theToken-Ring network.User Action:Check that the cable is securely attached toboth the adapter and to the Token-Ringnetwork. You might need to contact your localnetwork administrator to ensure that thecabling in the building is intact and that thenetwork concentrator to which you areattached is operational. If the error persists,try using a different cable.Appendix B. Problem Determination 53
Error Code Explanation and ActionIBMTOKEN-xx-214 The configured data rate for the adapter does notmatch that of the network.Explanation:The operational speed of the Token-Ringnetwork does not match the configured speedof the adapter.User Action:Change the setting of the DataRateconfiguration parameter to match the speed ofthe network to which the adapter is attached.Your local network administrator should beable to tell you which speed to use. Settingthe DataRate parameter value to AUTO willallow the adapter to automatically determinethe correct speed setting to use whenconnecting to the network, provided that thisis not the only adapter active on the TokenRing. Consult the adapter installationinstructions for additional information onsetting the DataRate parameter.IBMTOKEN-xx-215 An adapter timeout occurred while attempting to insertinto the network.Explanation:The Token-Ring network is not functioningcorrectly.User Action:Contact your local network administrator todetermine the status of your network, or tryconnecting again at a later time.IBMTOKEN-xx-216 A ring failure condition was detected while attemptingto insert into the network.Explanation:The Token-Ring network is not functioningcorrectly.User Action:Contact your local network administrator todetermine the status of your network, or tryconnecting again at a later time.IBMTOKEN-xx-217 A ring beaconing condition was detected whileattempting to insert into the network.Explanation:The Token-Ring network is not functioningcorrectly.User Action:Contact your local network administrator todetermine the status of your network, or tryconnecting again at a later time.54 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionIBMTOKEN-xx-218 A duplicate network address was detected whileattempting to insert into the network.Explanation:The address specified for the NetAddressconfiguration parameter is being used byanother adapter (or ring station) on thenetwork.User Action:Modify the configuration file to change theNetAddress parameter value being used forthis adapter, or remove the NetAddressparameter to allow the adapter’s burned-inaddress (universally administered address) tobe used. Contact your local networkadministrator for assistance with choosing anew NetAddress parameter value, or topossibly have the conflicting adapter removedfrom the same Token-Ring network as thisadapter.IBMTOKEN-xx-219 A ring parameter failure occurred while attempting toinsert into the network.Explanation:The Token-Ring network is not functioningcorrectly.User Action:Contact your local network administrator todetermine the status of your network, or tryconnecting again at a later time.IBMTOKEN-xx-220 The adapter was forced to remove itself whileattempting to insert into the network.Explanation:The Token-Ring network rejected the attemptby this adapter to connect to it.User Action:Contact your local network administrator todetermine the status of your network, or tryconnecting again at a later time.Appendix B. Problem Determination 55
Error Code Explanation and ActionIBMTOKEN-xx-221 A hardware failure occurred while attempting to openthe adapter.Explanation:An adapter hardware error was detectedwhen opening the adapter for networkoperation.User Action:Run the adapter diagnostics program toisolate the problem and contact yourcustomer service center. If no problem wasidentified by the diagnostics, check that thecable is attached securely to both the adapterand the network interface (wall plate). Turnthe computer off and then on again to restartthe machine. If the problem persists, contactyour customer service center.IBMTOKEN-xx-222 A hardware failure occurred while attempting to openthe adapter.Explanation:A hardware error was detected when openingthe adapter for network operation.User Action:Run the adapter diagnostics program toisolate the problem and contact yourcustomer service center. If no problem wasidentified by the diagnostics, check that thecable is attached securely to both the adapterand the network interface (wall plate). Turnthe computer off and then on again to restartthe machine. If the problem persists, contactyour customer service center.56 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionIBMTOKEN-xx-223 The adapter cannot be opened in AutoSense mode if itis the only active station on the network.Explanation:The DataRate configuration parameter is setto AUTO (which is also the default value if theparameter is not specified), but the adapter isthe first station to open on the Token-Ringnetwork.User Action:This adapter is designed to not open onto theattached Token-Ring network if it is configuredto use AutoSense detection and if it wouldhave been the first active ring station.The possible remedies are to try connectingagain at a later time when at least one otherring station is active on the network (such asa network server), or to change theconfiguration value so that the DataRateparameter is set to a specific ring-speed valueof M16 or M4 and restart the computer.Note that setting a specific value of M16 orM4 for the DataRate parameter will cause thisadapter to establish the operational speed ofthe Token-Ring network if it is still the firstactive ring station, so consult with your localnetwork administrator if necessary.Check the adapter installation instructions foradditional information on setting the DataRateparameter.IBMTOKEN-xx-224 Portxxx: The adapter attempted to perform a RemoteProgram Load but failed monitor contention.Explanation:The adapter was opened as a RemoteProram Load (RPL) client, but was unable tolocate an RPL server on the network.User Action:Make sure that there is an active RemoteProgram Load server on the network and thatit is configured to recognize this adapter’snetwork address.Appendix B. Problem Determination 57
Error Code Explanation and ActionIBMTOKEN-xx-225 A network protocol error occurred while attempting tooperate the adapter in full duplex mode.Explanation:The adapter was unable to successfullycommunicate with a Token-Ring switch whenattempting to open for full-duplex operation.User Action:Check that your full-duplex switch isfunctioning correctly and that the adapter iscorrectly connected to it. If this problempersists, contact your customer servicecenter.IBMTOKEN-xx-226 The adapter failed to open during an enhanced modeopen sequence.Explanation:The adapter failed during some phase of anenhanced mode open sequence.User Action:Restart the computer. If the problem stilloccurs run diagnostics. If the diagnosticsindicates that the adapter is not defective thenrecord this message number and contact yourcustomer service center.IBMTOKEN-xx-227 The IBM Token-Ring Shared RAM Adapter opened atxxxMbps, half duplex.Explanation:Information only.User Action:None.IBMTOKEN-xx-228 The IBM Token-Ring Shared RAM Adapter opened atxxxMbps, full-duplex.Explanation:Information only.User Action:None.IBMTOKEN-xx-229 The adapter is configured for full duplex, but could onlybe opened in half duplex mode.Explanation:Information only.User Action:None.58 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionIBMTOKEN-xx-233 Adapter analysis code isxxx.Explanation:Information only.User Action:None.IBMTOKEN-xx-234 Adapter full-duplex operation has now been activated.Explanation:Information only.User Action:None.IBMTOKEN-xx-240 IBM Token-Ring Shared RAM AdapterExplanation:Information only.User Action:None.IBMTOKEN-xx-301 ODI 3.3 and Above HSMExplanation:Information only.User Action:None.IBMTOKEN-xx-304 Adapter is disconnected from the media.Explanation:The media network is not functioningcorrectly.User Action:Check that the cable is securely attached toboth the adapter and the Token-Ring network.Run adapter diagnostics if problems persist.You might need to contact your localadministrator to ensure that the cabling in thebuilding is intact and that the networkconcentrator to which you are attached isoperational. If the error persists, try using adifferent cable.IBMTOKEN-xx-305 Condition restored. The adapter is connected to themedia.Explanation:Information only.User Action:None.Appendix B. Problem Determination 59
Error Code Explanation and ActionIBMTOKEN-xx-312 Insufficient memory for minimum number of receivebuffers.Explanation:The HSM driver was not able to allocate theminimum number of receive buffers.User Action:Increase the number of buffers that theserver’s operating system can allocate byediting the STARTUP.NCF file on the server.Increase the Minimum Packet Receive Buffersparameter in this file by the total number oftransmit (TxBuffers =) and receive (RxBuffers=) that the HSM driver is using. Down andrestart the Novell NetWare server.IBMTOKEN-xx-401 NetWarexxx xxxExplanation:Information only.User Action:None.IBMTOKEN-xx-402 Unable to find a supported board in this machine.Explanation:Information only.User Action:None.IBMTOKEN-xx-403 Unable to acquire the configuration parameters for thePCMCIA adapter.Explanation:Needed parameters have not been correctlyconfigured.User Action:Make sure that your computer is loading Cardand Socket Services. You must also beloading the Token-Ring 16/4 PC CardConnectivity Enabler (CS20TOK.EXE) inCONFIG.SYS to configure your adapter.Windows 95 and Windows 98Windows 95 sometimes has trouble selecting available resources for the PC Card,causing the PC Card not to function. If you find that your PC Card is notfunctioning, follow this procedure.1. Click Start.2. Go to the Settings menu selection and click Control Panel.3. Click System.4. Click the Device Manager tab.60 Turbo 16/4 Token-Ring PC Card 2
5. Go to the icon for Network Adapters. You might see a yellow or red circle withan exclamation point inside beside an entry for the IBM Turbo 16/4 Token-RingPC Card 2. If you see this, click the entry. This will take you to the propertiesdialog for the PC Card.6. Click the Resources tab of the dialog box. There are three resources that mustbe correct before the IBM Turbo 16/4 Token-Ring PC Card 2 will functioncorrectly. Acceptable values for the input/output range include any fourconsecutive values beginning at 0300. The interrupt request value should be avalue between 3 and 15 that does not conflict with any other devices. Thememory range is often set incorrectly by Windows 95. It is recommended thatthe memory range be set in the 000D0000 to 000DC000 in a non-conflictingmemory region. The memory range 000C0000 to 000CFFFF is often used forvideo caches and Windows 95 does not always exclude memory regions thatare already in use.7. If EMM386.EXE is in your CONFIG.SYS, comment it out.Windows NTWindows NT 3.51 and 4.0 use a point enabler called PCMCIA.SYS that is suppliedwith Windows NT. PCMCIA.SYS configures the Intel compatible socket controllerwith settings gleaned from the registry entry for the PC Card. Windows NT willindicate resource conflicts only after an attempt is made to configure a device. Aswhen using a DOS enabler, you must manually choose your PC Card resources. Bylooking at the event viewer in the administrative tools, you might find that there isan I/O, IRQ, or memory conflict. A program called WINMSD is included withWindows NT which allows you to see the resources of your machine and determineif there are any conflicts. Make a note of your configured resources and comparethem to the settings indicated by WINMSD. Make corrections to your configurationas needed. This is done by the following procedure:1. Right-click Network Neighborhood.2. Select Properties.3. Select the Adapter tab.4. Select IBM Turbo 16/4 Token-Ring PC Card 2 and click Properties.You can now change your configuration as needed.Windows 2000Windows 2000 sometimes has trouble selecting available resources for the PCCard, causing the PC Card not to function. If you find that your PC Card is notfunctioning, follow this procedure:1. From the Control Panel, double-click the System icon. Select the Hardwaretab, and click the Device Manager button.2. From the Device Manager, look for a yellow or red circle with an exclamationpoint beside an entry for the IBM Turbo 16/4 Token-Ring PC Card 2. If you seethis, then double-click the adapter. The properties dialog for the adapter will nowbe displayed.3. The device status window will tell you why the device is not functioning. Youmight choose to try to resolve the problem yourself based on the problemdescription, or Windows 2000 will help you solve the problem if you click theTroubleshooter button.Appendix B. Problem Determination 61
OS/2 NDIS Error CodesThe following sections provide messages that can be received from the NDIS driverfunction. The messages are logged to a file. The NDIS driver signals the user whena Card Services call fails; the error signal is an alternating beep. If you hear thissound, and you are running OS/2, a problem is occurring during configuration of thePC Card and you must review the LANTRAN.LOG file in your \IBMCOMsubdirectory to determine what is wrong. Depending on the error, you may see oneor more of the following error codes.Error Code Explanation and ActionLTG0022E A failure during initialization of te IBMTOKCS devicedriver has occurred. This is a genericExplanation:This is a generic initialization failure message.If the IBMTOKCS device driver encountersany errors during initialization, the specificmessage related to the error will accompanythis generic message.User Action:Resolve the specific error that accompaniesthis message. In addition, ensure that theProtocol Manager device driver,PROTMAN.OS2, is located in the \IBMCOMdirectory, and that a DEVICE statement forPROTMAN.OS2 exists in the CONFIG.SYSfile.LTG0023I An unrecognized parameter was found inPROTOCOL.INI.Explanation:The parameter displayed was found while theinstallation program wa sprocessing the IBMToken-Ring Network Driver section ofPROTOCOL.INI. The parameter is not valid.User Action:Correct the parameter or remove it fromPROTOCOL.INI.LTG024I A value specified for a parameter in PROTOCOL.INI isnot valid.Explanation:The value provided for the parameter is notthe correct type or is not a valid value.User Action:Change the value for the parameter inPROTOCOL.INI.62 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0025I A configuration error was found in PROTOCOL.INI.Explanation:Conflicting parameter values were found whilethe installation program was processing theIBM Token-Ring Network Driver section ofPROTOCOL.INI.User Action:Examine the configuration parameters andcorrect the conflicting values inPROTOCOL.INI.LTG0026I The PC Card is not responding or was not found.Explanation:One of the following conditions has causedthis error:vThe logical primary or alternate setting inthe PROTOCOL.INI file does not map tothe physical primary or alternate setting.vThe PC Card is not responding to arequest to start.vThere is no physical PC Card in yourcomputer.User Action:If there is already a PC Card in this system,check the logical primary or alternate setting.Check the cable and ensure that theconnection to the token-ring networkaddressable unit is functioning correctly. Then,run the hardware diagnostics for thetoken-ring PC Card to ensure that the PCCard and options have been installedcorrectly.If there is no PC Card in your computer,install a token-ring PC Card or remove thedevice driver statement from theCONFIG.SYS file.LTG0027I The protocol manager could not be opened.Explanation:An unexpected error occurred when theprogram attempted to open the protocolmanager.User Action:Check the drive and directory to ensure thatthe protocol manager is located in thespecified path.Appendix B. Problem Determination 63
Error Code Explanation and ActionLTG0029I The PC Card encountered a lobe wire fault.Explanation:The PC Card will be closed.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and theMultistation Access Unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, refer tothe documentation that was shipped withyour PC Card to run diagnostics; then, trythe operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.LTG0030I There are not adequate receive bufers for the PC Cardto open.Explanation:The requested DIR.OPEN.ADAPTERparamaeter has not allowed enough receivebuffer space in the PC Card shared-RAMarea.User Action:Reduce the RAM requirements byreconfiguring the parameters inPROTOCOL.INI. The parameters that willreduce the space requirements for the receivebuffer are the transmit buffers (if more thanone is specified).LTG0032I An invalid node address error occurred when theprogram attempted to open the PC Card.Explanation:The node address defined is not valid.User Action:Specify a valid node address. Refer to theIBM Token-Ring Network ArchitectureReference(SC30–3374) for node addressrestrictions.64 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0033I The receive buffer length defined is not valid.Explanation:The PC Card was not opened. The receivebuffer length defined in PROTOCOL.INI is notvalid. The value specified must be greaterthan the allowable maximum, less than theallowable minimum, or not a multiple of 8.User Action:Specify a valid receive buffer length.LTG0034E The PC Card transmit buffer length defined is notvalid.Explanation:The PC Card was not opened. The PC Cardtransmit buffer length defined inPROTOCOL.INI is not valid. The valuespecified must be greater than the allowablemaximum, less than the allowable minimum,or not a multiple of 8.User Action:Specify a valid PC Card transmit bufferlength.LTG0037I An unexpected error caused the Open AdapterCommand in the IBMTOKCS.OS2 device driver.Explanation:The PC Card was closed because of anunexpected error condition.User Action:See the message log, LANTRAN.LOG, foradditional information about this error. Theerror must be corrected before you can usethis PC Card.Appendix B. Problem Determination 65
Error Code Explanation and ActionLTG0038I An auto-removal error has been detected.Explanation:The PC Card will be closed. The PC Cardhas either detected a monitor contentionfailure or received a beacon frame from thering. The problem might be that your PC Cardspeed is different from the speed at which theLAN is running.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.LTG0039I A remove medium access control (MAC) frame hasbeen received.Explanation:The PC Card will be closed. A commandforcing the PC Card to remove itself from thering has been received.User Action:Contact your LAN administrator to determinewhy the REMOVE command was issued foryour computer.LTG0041I An open error occurred during the lobe media testphase.Explanation:The PC Card has detected a problem on yourlocal lobe between the PC Card and themultistation access unit (MSAU).User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and the MSAU.Correct any related problems and try theoperation again.2. If there are no related problems, run thediagnostics; then, try the operation again.66 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0042I An open error occurred during the physical insertionphase.Explanation:The PC Card has detected one of thefollowing open errors while trying to insert intothe LAN:vRing failurevRing beaconingvTimeoutUser Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.LTG0043I An open error occurred during the address verificationphase.Explanation:The PC Card has detected one of thefollowing open errors during the addressverification phase of the PC Card openprocess:vSignal lossvTimeoutvRing failurevRing beaconingvDuplicate nodevREMOVE command receivedUser Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.Appendix B. Problem Determination 67
Error Code Explanation and ActionLTG0044I An open error occurred during the roll-call poll phase.Explanation:The PC Card has detected one of thefollowing open errors during the roll-call pollphase of the PC Card open process:vSignal lossvTimeoutvRing failurevRing beaconingvREMOVE command receivedUser Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.LTG0045I An open error occurred during the request parameterphase.Explanation:The PC Card has detected one of thefollowing open errors during the requestparameter phase of the PC Card openprocess:vSignal lossvTimeoutvRing failurevRing beaconingvParameter requestvREMOVE command receivedUser Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.68 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0051I The open error type is function failure.Explanation:The PC Card has detected a lobe mediafailure while trying to open the PC Card.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.LTG0052I The open error type is signal loss.Explanation:The PC Card has detected a signal lossfailure while trying to open the PC Card.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.Appendix B. Problem Determination 69
Error Code Explanation and ActionLTG0055I The open error type is timeout.Explanation:The PC Card has detected an insertion timerexpiration while trying to open the PC Card.This condition indicates that the ring might becongested, experiencing a high bit-error rate,or is losing an unusually high number oftokens or frames.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.LTG0056I The open error type is ring failure.Explanation:The PC Card has detected a ring failure whiletrying to open the PC Card.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.70 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0057I The open error type is ring beaconing.Explanation:The PC Card has detected a monitorcontention failure or has received a beaconframe from the ring while trying to open thePC Card.User Action:Perform the following steps:1. Check and secure all cable connecetionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, run thediagnostics; then, try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.LTG0058I The open error type is duplicate node address.Explanation:The PC Card has detected that anotherstation on the ring has a PC Card addressequal to the address specified for your PCCard.User Action:Note the identification number of thismessage and then contact your LANadministrator.LTG0059I The open error type is parameter request.Explanation:The PC Card has detected a parameterrequest error while trying to open the PCCard.User Action:Perform the following steps:1. Check and secure all cable connectionsbetween your PC Card and themultistation access unit (MSAU). Correctany related problems and try the operationagain.2. If there are no related problems, refer tothe documentation that was shipped withyour PC Card to run the diagnostics; then,try the operation again.3. If the problem persists, print or save theLANTRAN.LOG file and contact your LANadministrator.Appendix B. Problem Determination 71
Error Code Explanation and ActionLTG0060I The open error type is REMOVE received.Explanation:While attempting to insert into the ring, yourcomputer received a command forcing thisPC Card to remove from the ring.User Action:Contact your LAN administrator to determinewhy the REMOVE command was issued foryour computer.LTG0063I Your computer is the first attempting to insert onto thering in AUTORINGSPEED mode.Explanation:User Action:Either remove the AUTORINGSPEEDkeyword from PROTOCOL.INI or make surethat another computer is on the network andhas set the ring speed. If the problempersists, print or save the LANTRAN.LOG fileand contact your LAN administrator.LTG0064I Physical insertion of your computer onto the ring failed.Explanation:User Action:Check the PC Card configuration and retrythe open request. If the problem persists,refer to the documentation that was shippedwith your PC Card to run diagnostics; then,try the operation again.LTG0070I A problem was detected on microcode level 00 00 00C2 45 50.Explanation:User Action:Request and install engineering changeECA0066, P/N 92F9122, on your system, oruse the configuration feature of the LANAdapter Protocol Support installation programto change the value for the number oftransmit buffers to be greater than 1.LTG0083E Token-Ring Credit Card Request I/O failed.Explanation:Card Services would not give IBMTOKCSaccess to the I/O ports it requested.User Action:Make sure that no other PC Cards are usingthe range of I/O ports that the adapter needs.For a primary PC Card the range is A20–A23.For a secondary PC Card the range isA24–A27.72 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0084E Token-Ring Credit Card Request IRQ failed.Explanation:Card Services would not give IBMTOKCSaccess to the interrupt request (IRQ) line itrequested.User Action:Make sure that no other PC Cards are usingthe IRQ requested. IBMTOKCS defaults toIRQ 9. To change the IRQ that IBMTOKCSuses, add the line INTERRUPT=X to yourPROTOCOL.INI file. X can be any one of thefollowing values: 3, 4, 5, 7, 9, 10, or 11. TheIRQ chosen should not be used by any otherdevice.LTG0085E Token-Ring Credit Card RAM Request Window failed.Explanation:Card Services would not give IBMTOKCSaccess to the memory window that itrequested.User Action:Make sure that no other PC Cards are usingthe memory window requested. IBMTOKCSdefaults the MMIO memory window to CC00for the primary PC Card ot DC00 for thealternate PC Card. It also defaults the SRAMmemory window to D800 for the primary PCCard or D400 for the alternate PC Card. Tochange the MMIO memory window, add theline MMIO=XXXX to your PROTOCOL.INI file.XXXX can be any unused 8–KB, 16–KB,32–KB, or 64–KB region in the rangeC000–DC00. You might also have to asjustthe RAMSIZE keyword accordingly.LTG0086E Token-Ring Credit Card Request Configuration failed.Explanation:Card Services would not give IBMTOKCS theconfiguration that it requested.User Action:Try a different interrupt line by using theINTERRUPT=X statement in yourPROTOCOL.INI file. X can be any unusedinterrupt line in the range 3–15.Appendix B. Problem Determination 73
Error Code Explanation and ActionLTG0087E Token-Ring Credit Card RAM MapMemPage failed.Explanation:Card Services would not map theshared-RAM memory on the PC Card to therequired memory window.User Action:Try changing the memory window.IBMTOKCS defaults the MMIO memorywindow to CC00 for the primary PC Card orDC00 for the alternate PC Card. It alsodefaults the SRAM memory window to D800for the primary PC Card or D400 for thealternate PC Card. To change the MMIOmeory window, add the line MMIO=XXXX toyour PROTOCOL.INI file. XXXX can be anyunused 8–KB region in the rangeC000–DE00. To change the SRAM memorywindow, add the line RAM=XXXX to yourPROTOCOL.INI file. XXXX can be anyunused 8–KB, 16–KB, 32–KB, or 64–KBregion in the range C000–DC00. You mightalso have to adjust the RAMSIZE keywordaccordingly.LTG0090E Token-Ring Credit Card Register Client failed.Explanation:Card Services would not register the PC Cardcallback handler.User Action:Make sure that you have Card Services 2.0(PCMCIA.SYS) correctly installed.LTG0091E Card Services could not be found.Explanation:User Action:Add the appropriate statements to yourCONFIG.SYS file so that Card Services willbe installed.74 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionLTG0093E No sockets were found by Card Services.Explanation:The Card Services functionGetCardServicesInfo reported that there areno sockets in your computer. This can be forany of the following reasons:1. Socket Services is not installed or isinstalled incorrectly.2. There are no physical sockets on yourcomputer.3. No PC Card with sockets is installed or isinstalled incorrectly.User Action:Perform the following steps:1. Make sure that you have Socket Servicesinstalled correctly.2. Make sure that your computer hasphysical sockets.3. Make sure that you have installed the PCCard correctly.LTG0094I A Token-Ring Auto 16/4 Credit Card Adapter was notfound in any socket in your computer.Explanation:User Action:Insert the PC Card in a socket.LTG0095E A NETADDRESS must be specified to boot without thePC Card present in a socket.Explanation:You attempted to boot your computer withouta Token-Ring Auto 16/4 Credit Card Adapterinserted in a socket and without aNETADDRESS.User Action:Either insert the PC Card in a socket andreboot your computer or add theNETADDRESS= parameter toPROTOCOL.INI and reboot your computer.By adding the NETADDRESS parameter youcan insert the Token-Ring Auto 16/4 CreditCard Adapter after the reboot. Make sure thatthe address you use is either a locallyadministered address or the universallyadministered address on your PC Card. Tofind out your universally administeredaddress, run the diagnostics program that ison the diskettes that came with your adapter.Appendix B. Problem Determination 75
Error Code Explanation and ActionLTG0097E Token-Ring Credit Card MMIO RequestWindow failed.Explanation:Card Services would not give IBMTOKCSaccess to the MMIO memory window itrequested.User Action:Make sure that no other PC Cards are usingthe memory window requested. IBMTOKCSdefaults the MMIO memory window to CC00for the primary PC Card or DC00 for thealternate PC Card. To change the MMIOmemory window, add the line MMIO=XXXX toyour PROTOCOL.INI file. XXXX can be anyunused 8–KB region in the rangeC000–DC00.LTG0098E Token-Ring Credit Card MMIO MapMemPage failed.Explanation:Card Services would not map the MMIOmemory on the PC Card to the requestedmemory window.User Action:Try changing the MMIO memory window.IBMTOKCS defaults the MMIO memorywindow to CC00 for the primary PC Card orDC00 for the alternate PC Card. To changethe MMIO memory window, add the lineMMIO=XXXX to your PROTOCOL.INI file.XXXX can be any unused 8–KB region in therange C000–DC00.LTG0099E PROTOCOL.INI did not have a section with aDriverName=IBMTCS$ keyword.Explanation:A common cause of this is not using LAPS toinstall new drivers.User Action:Use LAPS to install the new PC CardToken-Ring Driver.DOS NDIS Error CodesError Code Explanation and ActionLTG0022E A failure during initialization of the IBMTOKCS device driver hasoccurred. This is a generic initialization failure message. If theIBMTOKCS device driver encounters any errors during initialization,the specific message related to the error will accompany this genericmessage.Resolve the specific error message that accompanies this message.In addition, ensure that the Protocol Manager device driver,PROTMAN.DOS, exists, and that a DEVICE statement for it exists inthe CONFIG.SYS file.76 Turbo 16/4 Token-Ring PC Card 2
ODI 16-bit Client Error CodesError Code Explanation and ActionTOKENCS-DOS-32 Driver registered as a NESL Suspend Class producer.Explanation:This is an informational only message.User Action:No action is required.TOKENCS-DOS-33 Driver registered as a NESL Resume Class producer.Explanation:This is an informational only message.User Action:No action is required.TOKENCS-DOS-34 Driver registered as a NESL Service Change Classproducer.Explanation:This is an informational only message.User Action:No action is required.TOKENCS-DOS-36 NetWare Event Service Layer (NESL) is Loaded.Explanation:This is an informational only message.User Action:No action is required.TOKENCS-DOS-50 The board cannot be found or the cable is notattached.Explanation:The PC Card has not been inserted in thePCMCIA socket.User Action:Insert your PC Card in the socket and tryagain.TOKENCS-DOS-204 The shared RAM is on incorrect boundary.Explanation:User Action:Change the Shared RAM base address andplace it on a 16–KB boundary (C0000,C4000, C8000, CC000, D0000, D4000,D8000, DC000).Appendix B. Problem Determination 77
Error Code Explanation and ActionTOKENCS-DOS-205 The PC Card did not reset during initialization.Explanation:During initialization, no interrupt occurred.User Action:This can happen if you are using an enablerand it is setting an interrupt level that isdifferent from the interrupt levelTOKENCS.COM is using. Check to makesure that both interrupts are the same.TOKENCS-DOS-206 An interrupt failed to occur during initialization.Explanation:During initialization, no interrupt occurred.User Action:This can happen if you are using an enablerand it is setting an interrupt level that isdifferent from the interrupt levelTOKENCS.COM is using. Check to makesure that both interrupts are the same.TOKENCS-DOS-226 The ROM and shared RAM address ranges overlap.Explanation:The ROM and RAM memory areas areoverlapping.User Action:Check the settings in NET.CFG for MEM #1and MEM #2. MEM #1 determines the ROM(MMIO) base address. MEM #2 determinesthe Shared RAM base address. If you areusing an enabler, check where it is placingthe ROM (MMIO) and the RAM address.ROM is 8 KB in size. RAM is usually 16 KB insize.TOKENCS-DOS-228 The MAX FRAME SIZE in NET.CFG file is too large(Max=17 960)Explanation:The maximum frame size has beenexceeded.User Action:Change the maximum frame size to a validvalue.TOKENCS-DOS-229 The MAX FRAME SIZE in NET.CFG file is too small(Min=632).Explanation:The maximum frame size is too small.User Action:Increase the maximum frame size to a validvalue.78 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation and ActionTOKENCS-DOS-230 The specified MAX FRAME SIZE in NET.CFG is not amultiple of 8.Explanation:The maximum frame size has been set to avalue that is not valid.User Action:Change the MAX FRAME SIZE to a multipleof 8.TOKENCS-DOS-231 The MAX FRAME SIZE in NET.CFG is too big for thisPC Card.Explanation:The maximum value at this speed for this PCCard isxx.User Action:Change the MAX FRAME SIZE to a validvalue.TOKENCS-DOS-233 Card Services could not be found.Explanation:TOKENCS.COM could not find Card Services.User Action:Check your CONFIG.SYS and ensure thatCard Services is loading. If Card Servicessupport is not wanted, take the PCMCIAkeyword out of NET.CFG.TOKENCS-DOS-235 A Card Services error has occurred.Explanation:You have heard an alternating tone and thismessage is posted to the panel. Thisindicates that Card Services was unable toprovide the resources requested.User Action:Check your NET.CFG parameters INT, MEM#1, MEM #2. If they are not in NET.CFG,Card Services has a problem. If they arespecified in NET.CFG, comment (REM) themout and try again.TOKENCS-DOS-237 PCMCIA Token-Ring MLID Loaded, but PC Card is notin socket.Explanation:This is an informational only message.User Action:No action is required.Appendix B. Problem Determination 79
Error Code Explanation and ActionTOKENCS-DOS-246 The DATA RATE specified in NET.CFG must be either4 or 16 Mbps.Explanation:You have specified an incorrect ring speed. Itmust be either 4 or 16 Mbps. The DATARATE keyword is used to set the speed.User Action:(no message) Please insert an IBM Turbo 16/4 Token-Ring PC Card2 or press Esc to avoid loading the driver.Explanation:This message occurs when you have notinserted an IBM Turbo 16/4 Token-Ring PCCard 2 in the computer and have startedTOKENCS.COM.User Action:Insert an IBM Turbo 16/4 Token-Ring PCCard 2 at this time or press Esc to leave.80 Turbo 16/4 Token-Ring PC Card 2
Appendix C. Running the Diagnostics ProgramImportantTo avoid potentially erroneous results, you should always perform a power-onreboot of your computer before running the diagnostics.The Diagnostics and LANAIDC diskette must be created before you run thefollowing procedure. See “Appendix A. CD-ROM Content and Software Packages”on page 45 for instructions.Use the diagnostics program on the Diagnostics and LANAIDC diskette to test thehardware components of the PC Card. Different operating systems will showresources differently.The diagnostics program performs a series of tests and displays the results of eachone by showing success or failure. An error during any test will end the test inprogress and display an error message and error code. See the following tables fora description of error codes and recommended actions.Note: The testing process might run as long as 3 minutes and can be exited at anytime by pressing Enter or by removing the Diagnostics and LANAIDCdiskette and pressing Esc. Pressing Esc will cause the computer to reboot.Pressing Enter will end the test in progress and allow the user to selectanother test option.1. Insert the Diagnostics and LANAIDC diskette.2. Switch ON the power to the computer.3. At the DOS Menu, select 2, IBM Turbo 16/4 Token-Ring PC CardExtended Diagnostics.4. Follow the instructions as they appear. You will be prompted to select atest option. See “Test Options” for descriptions.Test OptionsThere are two test options: the wrap test and the on-ring test. The on-ring test willnot function on a 4–MB token-ring network.The wrap test ensures that the adapter and cable hardware are functioningproperly. For this test, connect the adapter and cable to the network to perform awrap test through the hub or concentrator, or insert a wrap plug (no wrap plug isrequired if you have an STP cable connection) to help isolate a failure to theadapter, the cable, or the wiring to the hub or concentrator.Diagnostics Error Codes and Suggested ActionsInitialization Error CodesFailure during adapter initialization usually indicates a hardware error on the PCcard. Reboot your computer using the diagnostics on the Diagnostics and LANAIDCdiskette, and run the diagnostic program again. If the PC card continues to fail,replace it and the cable.© Copyright IBM Corp. 1997, 1999 81
One of the following codes will be shown to indicate the results of the initializationtest. The error codes are displayed in hexadecimal format and represent theBRING_UP_CODE set by the adapter.0000 Initialization success0014 No microcode0020 Diagnostics could not be executed0022 ROM diagnostics failed0024 Shared RAM diagnostics failed0026 Processor instruction test failed0028 Processor interrupt test failed002A Shared RAM interface register diagnostics failed002C Protocol-handler diagnostics failed0040 PC Card’s programmable timer for the computer failed (set by themicrocode)0042 Cannot write to shared RAM (set by microcode)0044 Reading from shared RAM read-only area caused an incorrect errorindication (interrupt)0046 Writing into shared RAM read-only area did not cause an error indication(interrupt)0048 Initialization timed outOpen ErrorsFailure during the adapter open test might indicate that the adapter is not properlyconfigured to run on the network it is trying to open onto or that the adapter is notproperly configured for the system. The open test provides a return code and anopen error code. If the return code is 07, then see “Open Error Codes” on page 83for a more accurate description of the failure and suggested actions. If the returncode is a value other than 00 or 07, problem determination of the PC Card and thediagnostics is necessary. Record the error and contact your network administrator.00 Open completed successfully01 Incorrect command code03 Adapter open, should be closed05 Required parameters not provided07 Command cancelled, unrecoverable failure (see open error codes to isolateproblem)30 Inadequate receive buffers32 Incorrect MAC address33 Incorrect adapter receive buffer length34 Incorrect adapter transmit buffer length82 Turbo 16/4 Token-Ring PC Card 2
Open Error CodesIf the open provides a return code of 7, there will be a corresponding error code.The open errors are returned in 2 bytes. The high-order byte is always 0 and thelow-order byte contains the following information:1. The phase of testing in which the error was encountered is in the high-ordernibble (half-byte) of the low-order byte.2. The error condition is in the low order nibble of the low-order byte.PhasesValue Meaning1n Lobe media test2n Physical insertion3n Address verification4n Roll call poll (neighbor notification)5n Request parametersErrorsValue Meaningn1 Function failuren2 Signal lossn3 Reservedn4 Frequency error (see note)n5 Time-outn6 Ring failuren7 Ring beaconingn8 Duplicate node addressn9 Parameter request—retry count exceedednA Remove receivednB IMPL force receivednC Duplicate modifiernD No monitor detectednE Monitor contention failed for RPLSuggested Actions in Response to Open ErrorsWhen the following phase-error combination values are presented, they are theresult of certain specific occurrences. Explanation of the occurrences follows withrecommended actions listed. Table 8 on page 86 lists the recommended actions forboth the application program and the computer operator.Error Code Explanation Action11 Lobe Media, Function Failure: The testing of the lobebetween the PC Card and the access unit has beenunsuccessful because the lobe has a bit-error ratethat is too high, or the PC Card cannot receivesuccessfully.1, 3, and 5Appendix C. Running the Diagnostics Program 83
Error Code Explanation Action24 Physical Insertion, Frequency Error: The PC Card hasdetected that the ring is operating at a speed otherthan the speed at which it was inserting.226 Physical Insertion, Ring Failure: The PC Card, actingas an active monitor, was unable to complete the ringpurge function successfully. This indicates that anerror condition has occurred since the successfulcompletion of monitor contention (claim token), whenthis PC Card became the active monitor.1 and 2a27 Physical Insertion, Ring Beaconing: The PC Card hasdetected one of the following conditions:vThe PC Card tried to insert on a ring that wasoperating at a different data rate.vA monitor contention (claim token) failure occurred.vThe PC Card received a beacon MAC frame fromthe ring.1, 2, and 2b2A Physical Insertion, Remove Received: The PC Cardhas received a remove ring station MAC frame,indicating that a network management function hasdirected this PC Card to get off the ring.2a and 42D Physical Insertion, No Monitor Detected: RPL stationis the first station attempting to insert onto the ring. 1 and 2a2E Physical Insertion, Monitor Contention Failed for RPL:Physical insertion failure of RPL station. 232 Address Verification, Signal Loss: The PC Card hasdetected a 250-ms signal loss (receiver cannotrecognize signal), indicating that an error conditionhas occurred since the PC Card successfullycompleted the ring signal recognition phase of theopen operation.1 and 2a35 Address Verification, Time-out: The insertion timerexpired before this function was completed, indicatingthat the ring can be congested, experiencing a highbit-error rate, or losing an abnormally high number oftokens or frames, thus preventing successful AddressVerification MAC frame transmissions.1 and 2a36 Address Verification, Ring Failure: The PC Card,acting as an active monitor, was unable to completethe ring purge function successfully. This indicatesthat an error condition has occurred since thesuccessful completion of monitor contention (claimtoken), when this PC Card became the active monitor.1 and 2a37 Address Verification, Ring Beaconing: The PC Cardhas either detected a monitor contention (claim token)failure or received a beacon MAC frame from the ring.1 and 2b38 Address Verification, Duplicate Node Address: The PCCard has detected that another station on the ring hasa PC Card address that is the same as the PC cardaddress being tested.43A Address Verification, Remove Received: The PC Cardhas received a remove ring station MAC frame,indicating that a network management function hasdirected this specific address to get off the ring.2a and 484 Turbo 16/4 Token-Ring PC Card 2
Error Code Explanation Action42 Ring Poll, Signal Loss: The PC Card has detected a250-ms signal loss (receiver cannot recognize signal)indicating that an error condition has occurred sincethe PC Card successfully completed the ring signalrecognition phase of the open operation.1 and 2a45 Ring Poll, Time-out: The insertion timer expired beforethis function was completed, indicating that the ringcan be congested, experiencing a high bit-error rate,or losing an abnormally high number of tokens orframes. This prevents the PC Card’s successfulreception of either the ring poll request or responseMAC frame, or transmission of the required ring pollresponse MAC frame.1 and 2a46 Ring Poll, Ring Failure: The PC Card, acting as anactive monitor, was unable to complete the ring purgefunction successfully. This indicates that an errorcondition has occurred since the successfulcompletion of monitor contention (claim token), whenthis PC Card became the active monitor.1 and 2a47 Ring Poll, Ring Beaconing: The PC Card has eitherdetected a monitor contention (claim token) failure orreceived a beacon MAC frame from the ring.1 and 2b4A Ring Poll, Remove Received: The PC Card hasreceived a remove ring station MAC frame, indicatingthat a network management function has directed thisPC Card to get off the ring.2a and 455 Request Parameters, Time-out: The insertion timerexpired before this function was completed, indicatingthat the ring can be congested, experiencing a highbit-error rate, or losing an abnormally high number oftokens or frames. This prevents successfultransmission of the request parameter MAC frame orreception of either the set parameter 1 or setparameter 2 MAC frame (required response to the PCCard’s request).1 and 2a56 Request Parameters, Ring Failure: The PC Card,acting as an active monitor, was unable to completethe ring purge function successfully. This indicatesthat an error condition has occurred since thesuccessful completion of monitor contention (whenthis PC Card became the active monitor).1 and 2a57 Request Parameters, Ring Beaconing: The PC Cardhas received a beacon MAC frame from the ring. 1 and 2b59 Request Parameters, Parameter Request - RetryCount Exceeded: The PC Card has detected that thering parameter server is present on the ring but thatthe required response (set parameter 1 or setparameter 2 MAC frame) was not received in theallotted time. This indicates that the ring can becongested, experiencing a high bit-error rate, or losingan abnormally high number of tokens or frames.1 and 2a5A Request Parameters, Remove Received: The PCCard has received a remove ring station MAC frame,indicating that a network management function hasdirected this PC Card to get off the ring.2a and 4Appendix C. Running the Diagnostics Program 85
Recommended Actions TableTable 8. Recommended ActionsNumber Description1 After delaying at least 30 seconds, retry the open two times,inserting the same delay between each try.2 After delaying at least 30 seconds, check the PC Card configuration(especially the PC Card data rate) and retry the open.2a If this error persists, contact your network administrator forassistance and provide Open Error information.2b If this error persists, contact your network administrator forassistance.3 Contact your network administrator for assistance and provide OpenError information.4 Contact your network administrator for assistance and provide NodeAddress information, and try attaching to the ring after 6 minutes.5 If this error persists, problem determination of the PC Card or lobe isnecessary. Contact your network administrator for problemdetermination assistance.Transmit Error CodesIf you experience time-out errors during the on-ring test, try running the wrap test inthe diagnostics. If the wrap test is completed successfully, but the on-ring test fails,it might indicate problems on the Token-Ring network that the adapter is openingonto during the on-ring test.For any other errors, ensure that the adapter and cabling are properly connected,and retry the test. If the adapter continues to fail, record the error and contact yournetwork administrator.01 Unrecognized command code08 Unauthorized access priority22 Error on frame transmission, examine STRIPPED_FS23 Error on frame transmit or strip process24 Unauthorized MAC frame25 Maximum commands exceeded26 Correlator not acceptable27 Link not transmitting I frames, status changed from link open28 Transmit frame length not acceptable29 Link retransmission in process, buffers free40 Station ID not acceptable41 Protocol error, link not in acceptable state for command86 Turbo 16/4 Token-Ring PC Card 2
Appendix D. LANAIDC Parameter InformationLANAIDC is the command line version of LANAID. It contains all of the function ofLANAID without the graphical user interface. Its primary intended users are LANadministrators and other users who want to duplicate a certain IBM Turbo 16/4Token-Ring PC Card 2 configuration on multiple computers.The LANAIDC program is in the same directory on your hard drive where LANAIDwas installed (see “Installing LANAID” on page 33). Typing LANAIDC withoutparameters will cause LANAIDC to use a configuration file called LANAIDC.CFG toconfigure the PC Card. This file is created by the graphical LANAID program after itsuccessfully completes a PC Card configuration. See “Using LANAIDC to DuplicateConfigurations” for more information about using the configuration file.Type lanaidc /h to show the long help list for all the configuration parameters, andtype lanaidc /? to show the short help list. Also, you can choose LANAIDC from themenu that is displayed when the computer is booted from the Diagnostic andLANAIDC diskette. Using this method to configure the PC Card with LANAIDC isnot recommended, however, since correct configuration depends on the computerbeing booted in the environment under which the PC Card will run.Using LANAIDC to Duplicate ConfigurationsIn order to take a configuration performed by LANAID on one computer andduplicate it on others, follow these steps:1. Boot the computer in the same environment that the PC Card will use.2. If LANAID has not yet been installed, install it according to the instructions. SeeChapter 5. LANAID.3. Use LANAID to configure that computer for the PC Card, and exit LANAID.During configuration, LANAID creates a file called LANAIDC.CFG that containsall of the information required to recreate the same environment. TheLANAIDC.CFG file will have been placed in the same directory as LANAID.4. Copy the following files to a diskette from the directory where LANAID wasinstalled:LANAIDC.EXELANAIDC.MSGDDPRINS.MSGINSTALL.LSTLANAIDC.CFG5. Place the diskette in the computer on which the PC Card configuration is to beduplicated. At this point, you can either copy the files to a directory on the harddisk, which will allow LANAIDC to run more quickly, or you can run LANAIDCfrom the diskette.6. Type lanaidc and press Enter, either from the diskette or the directory on thehard disk where the files were copied.7. Upon completion, LANAIDC should display the PC Card configuration values.© Copyright IBM Corp. 1997, 1999 87
LANAIDC ParametersThe parameters LANAIDC uses to configure the PC Card are listed here. If nooptions are given, LANAIDC.CFG will be used for input parameters. LANAIDC.CFGis created by LANAID after a successful store has been performed./FILE=<drive:\path\filename> - specify a file with inputparameters/CFGSYS=<drive> - specify the drive of the CONFIG.SYS/MENUITEM=<keyword> - specify the menu item to install to inCONFIG.SYS/NOS - specify one of the following NetworkOperating Systems/NOS=NOVELL/NOS=W4W/NOS=LSPNDIS/NOS=VINES/NOS=LANTASTIC/NOS=OTHERNDIS/NOS=IBMLC/NOS=LSPNATIVE/NOS=MSLANMAN/NOSDIR=<drive:\dir> - specify directory where Network OperatingSystem is installed/MODE=ENHANCED - specify Enhanced Mode/MODE=AUTO16 - specify Auto 16/4 Mode/IO=<###> - specify Hex IO address- Enhanced Mode values: 300 to EFC on a 4 byte boundary- Auto16 Mode values: A20 or A24/INT=<##> or /INT=AUTOSET - specify interrupt level(3,4,5,7,9,10,11,14,15) or Autoset if Card Services is present/MMIO=<#####> or /MMIO=AUTOSET- specify Hex MMIO address- values: C0000-DE000 on an 8K boundary or Autoset if CardServices is present/SRAM=<#####> or /SRAM=AUTOSET- specify Hex SRAM address(Auto16 Mode only)- values: C0000-DC000 on a 16K boundary or Autoset if CardServices is present/RS=<##> - specify ring speed (4 or 16)/AUTO=Y or /AUTO=N - enable/disable Auto Sense/RSPROMPT=Y or /RSPROMPT=N - enable Ring Speed Prompt/SOCKET=<x> - specify socket letter (Point Enabler only)/VIEW - view the current configuration/? - display abbreviated help/H or /HELP - display extended help88 Turbo 16/4 Token-Ring PC Card 2
Appendix E. Token.lan and LAN Client Driver ParametersIn addition to the standard Novell keywords (such as slot, port, int, and frame), anumber of custom keywords are available in the driver. This list is dynamic: itchanges as support is added for new hardware as ODI specifications change. If it isknown, the driver revision level in which the keyword is available is included. Thislist describes those keywords that are available and useful to users. All of thesekeywords are optional unless otherwise noted.Note: Some parameters, if misused, can cause problems with adapter operationand must be set with a thorough understanding of adapter operations.Custom KeywordsNOFULLDUPLEXBy default, the driver will first try to open on the ring in full-duplex mode(connected to a switched Token-Ring network) on those adapters that arecapable of this function. Otherwise, it will try to open in half-duplex mode (atraditional shared-media LAN). The presence of this keyword will preventthe attempted open in full-duplex mode.NOSHALLOWMODEShallow-mode operation is fast-path transmit, fast-path receive, and no LLCprocessing (802.2) by adapter firmware. NoShallowmode is fast-pathtransmit, standard receive, and 802.2 processing. Shallowmode is thedefault on turbo-class adapters and is designed for higher performance.Including this keyword will disable fast-path receive and enable LLCprocessing on the adapter.AUTORINGSPEEDThis PCMCIA-specific keyword is used to enable autoringspeed detection ofthe adapter on the ring when the ring speed is not known or changesbecause of mobility needs (for exampke, with a laptop). The first adapterthat opens on the ring must define the ring speed, and therefore cannot usethe autoringspeed keyword. Adapters opened subsequently canautomatically adjust to the ring speed by use of the autoringspeed keyword.If the first adapter to try to open on the ring has the autoringspeed keywordspecified, the opening will fail.EXPRESSMODEValid in shallowmode operation only. During normal (shallowmode) receiveprocessing, the host is interrupted after every buffer is received. Use of thiskeyword reduces the number (and processing overhead) of interrupts perframe, but lowers overall receive performance. Use this keyword on slowermachines or on fast machines that are heavily loaded.Keywords with ParametersSAPSDefault: 1Range 0-125The numbef of adapter service access points that can be open at one time.This parameter is not used in the ODI environment and should not be usedunless an application specifically requires it.LS© Copyright IBM Corp. 1997, 1999 89
Default: 0Range: 0-255The number of adapter link staaaations that can be open at one time. Thisparameter is not used in the ODI environment and should not be usedunless an application specifically requires it.TBZDefault: (ring speed, mode, adapter dependent)Range: 96-17960The transmit buffer size, expressed in bytes. The value must be a multipleof 8 and must not exceed 4464 in a 4–Mbps environment, or 17960 in a16–Mbps environment. This value is the size of a transmit frame innon-fast-path transmit mode and the maximum frame size in fast-pathreceive mode. Generally, this value is set automatically by the driver as theminimum of the LSL, hardware, and this value. In normal operation thisparameter can be ignored.PCMCIA_INTDefault: noneRange: 2-F in hexadecimal (Version 3.32 and higher)The interrupt assigned to a PCMCIA Token-Ring adapter. Since PCMCIAadapters are handled differently from other bus types, this parameter alsoindicates to the driver that a PCMCIA adapter is being initialized. On apoint-enabled card, the only way the driver can determine the interruptvector that the card is using is to get it from the command line. Thisparameter is required on PCMCIA cards that are point-enabled.MEM0Default: CC000Range: 0-100000h in hexadecimal (Version 3.21 and higher)This parameter indicates the shared-RAM base address to the driver sincein some cases the driver cannot determine the shared-RAM base addresswithout getting it from the command line. This parameter is required onpoint-enabled PCMCIA cards, especially if more than one is in the system.The value given must be on the proper boundary depending onshared-RAM size. See the table below.Shared-RAM Size Address must be a multiple of--------------------------------------------------------------4KBor8KB 8KB16 KB 16 KB32 KB 32 KB64 KB 64 KBPORTDefault A20hRange: A20 or A24 in non-enhanced mode, 200-0FFFCH in enhanced mode.The base address of the I/O port the adapter uses. The adapter requires 4contiguous I/O ports.NIC_UAADefault: NoneRange: hexadecimal string 1-FFFFFFFFFFFFh (Version 3.21)This parameter selects the adapter to initialize by its universallyadministered address (UAA), which is in read-only storage on the card.90 Turbo 16/4 Token-Ring PC Card 2
Enhanced-mode adapters can be located at most addresses and can beselected by either their UAA or ofdinal number (1=lowest UAA, 2=highestUAA).RECEIVEBUFFERSIZEDefault: Varies with mode.Range: 192-2048 (Version 3.33)Changes the adapter shallow-mode receive buffer size. Allows tuning ofreceive buffers to more closely match the LAN traffic environment. Thisparameter is not needed for normal operations. Value must be a multiple of8 bytes. Smaller values increase performance and processor utilizationwhile larger values decrease performance and lower processor utilization.DATARATEDefault: variesRange: 4 or 16 (Version 3.36b and higher)Used to set the adapter data rate for dual-speed adapters. Somedual-speed adapters, notably MCA adapters, might not support thiskeyword. If the speed selected does not match the ring speed, the open willfail. On PCMCIA adapters, see the complementary keyword, autoringspeed.SRAMSIZEDefault: 4Range: 4, 8, 16, 32 or 64 (Version 4.01 and higher)PCMCIA only in the Windows 95 environment. Allows setting theshared-RAM size in compatibility modes in a card services environment.Appendix E. Token.lan and LAN Client Driver Parameters 91
92 Turbo 16/4 Token-Ring PC Card 2
Appendix F. Parts InformationTable 9. Part NumbersPart Number Description Diagram38H7044 PC Card Cable73G8314 STP Connector (RJ-45 for DataConnector); converts RJ-45 toToken-Ring73G2305 RJ-11 to RJ-45 Modular AdapterTo order these items, call the IBM Maintenance Parts and Warranty Center1-800-388-7080 (United States only).© Copyright IBM Corp. 1997, 1999 93
94 Turbo 16/4 Token-Ring PC Card 2
Appendix G. Notices and WarrantyReferences in this publication to IBM products, programs, or services do not implythat IBM intends to make these available in all countries in which IBM operates. Anyreference to an IBM product, program, or service is not intended to state or implythat only IBM’s product, program, or service may be used. Any functionallyequivalent product, program, or service that does not infringe any of IBM’sintellectual property rights may be used instead of the IBM product, program, orservice. Evaluation and verification of operation in conjunction with other products,programs, or services, except those expressly designated by IBM, are the user’sresponsibility.IBM may have patents or pending patent applications covering subject matter in thisdocument. The furnishing of this document does not give you any license to thesepatents. You can send license inquiries, in writing, to the IBM Director of Licensing,IBM Corporation, 500 Columbus Avenue, THORNWOOD NY 10594 USA.Notice to Users in the United KingdomThe United Kingdom Telecommunications Act 1984. This apparatus is approvedunder General Approval number NS/G/1234/J/100003 for indirect connections topublic telecommunications systems in the United Kingdom.Electronic Emission NoticesFederal Communications Commission (FCC) StatementNote:This equipment has been tested and found to comply with the limits for aClass B digital device, pursuant to Part 15 of the FCC Rules. These limits aredesigned to provide reasonable protection against harmful interference in aresidential installation. This equipment generates, uses, and can radiate radiofrequency energy and, if not installed and used in accordance with the instructions,may cause harmful interference to radio communications. However, there is noguarantee that interference will not occur in a particular installation. If thisequipment does cause harmful interference to radio or television reception, whichcan be determined by turning the equipment on and off, the suer is encouraged totry to correct the interference by one or more of the following measures:vReorient or relocate the receiving antennavIncrease the separation between the equipment and receivervConnect the equipment into an outlet on a circuit different from that to which thereceiver is connectedvConsult an IBM authorized dealer or service representative for helpProperly shielded and grounded cables and connectors must be used in order tomeet FCC emission limits. Proper cables and connectors are available from IBMauthorized dealers. IBM is not responsible for any radio or television interferencecaused by using other than recommended cables and connectors or byunauthorized changes or modifications to this equipment. Unauthorized changes ormodifications could void the user’s authority to operate the equipment.© Copyright IBM Corp. 1997, 1999 95
This device complies with Part 15 of the FCC Rules. Operation is subject to thefollowing two conditions:(1) this device may not cause harmful interference, and (2)this device must accept any interference received, including interference that maycause undesired operation.Industry Canada Class B Emission Compliance StatementThis Class B digital apparatus meets the requirements of the CanadianInterference-Causing Equipment Regulations.Avid de conformité aux normes d’Industrie CanadaCet appareil numérique de la classe B respecte toutes les exigences du Règlementsur le matériel brouilleur du Canada.European Community (EC) Mark of Conformity StatementThis product is in conformity with the protection requirements of EU CouncilDirective 89/336/EEC on the approximation of the laws of the Member Statesrelating to electromagnetic compatibility. IBM cannot accept responsibility for anyfailure to satisfy the protection requirements resulting from a non-recommendedmodification of the product, including the fitting of non-IBM option cards.This product has been tested and found to comply with the limits for Class BInformation Technology Equipment according to CISPR 22 / European Standard EN55022. The limits for Class B equipment were derived for typical residentialenvironments to provide reasonable protection against interference with licensedcommunication devices.Dieses Gerät ist berechtigt in Übereinstimmung mit dem deutschen EMVG vom9.Nov.92 das EG-Konformitätszeichen zu führen. Der Außteller derKonformitätserklärung ist die IBM Corporation, 3039 Cornwallis Road, ResearchTriangle Park, NC 27709.Dieses Gerät erfüllt die Bedingungen der EN 55022 Klasse B.Japanese Voluntary Control Council for Interference (VCCI) StatementThis equipment is in the 2nd Class category (information equipment to be used in aresidential area or an adjacent area thereto) and conforms to the standards set bythe Voluntary Control Council for Interference by Information Technology Equipmentaimed at preventing radio interference in such residential areas.When used near a radio or TV receiver, it may become the cause of radiointerference.Read the instructions for correct handling.96 Turbo 16/4 Token-Ring PC Card 2
TrademarksThe following terms are trademarks of the IBM Corporation in the United States orother countries or both:AIX Personal System/2IBM SystemViewMicro Channel ThinkPadNetView XTOS/2Windows and Windows NT are trademarks or registered trademarks of MicrosoftCorporation.Other company, product, and service names may be trademarks or service marksof others.Product WarrantyInternational Business Machines Corporation Armonk, New York, 10504Statement of Limited WarrantyThe warranties provided by IBM in this Statement of Limited Warranty apply only to Machines you originally purchasefor your use, and not for resale, from IBM or an IBM authorized reseller. The term “Machine” means an IBM machine,its features, conversions, upgrades, elements, or accessories, or any combination of them. Machines are subject tothese terms only if purchased in the United States or Puerto Rico, or Canada, and located in the country of purchase.If you have any questions, contact IBM or your reseller.Machine: IBM Turbo 16/4 Token-Ring PC Card 2Warranty Period*: Lifetime*Elements and accessories are warranted for three months. Contact your place of purchase for warranty serviceinformation.Production StatusEach Machine is manufactured from new parts, or new and serviceable used parts (which perform like new parts). Insome cases, the Machine may not be new and may have been previously installed. Regardless of the Machine’sproduction status, IBM’s warranty terms apply.Appendix G. Notices and Warranty 97
The IBM WarrantyIBM warrants that each Machine 1) is free from defects in materials and workmanship and 2) conforms to IBM’sOfficial Published Specifications. IBM calculates the expiration of the warranty period from the Machine’s Date ofInstallation. The date on your receipt is the Date of Installation, unless IBM or your reseller informs you otherwise.During the warranty period, IBM or your reseller will provide warranty service under the type of service designated forthe Machine and will manage and install engineering changes that apply to the Machine. IBM or your reseller willspecify the type of service.For a feature, conversion, or upgrade, IBM or your reseller may require that the Machine on which it is installed be 1)the designated, serial-numbered Machine and 2) at an engineering-change level compatible with the feature,conversion, or upgrade. Some of these transactions (called “Net-Priced” transactions) may include additional parts andassociated replacement parts that are provided on an exchange basis. All removed parts become the property of IBMand must be returned to IBM.Replacement parts assume the remaining warranty of the parts they replace.If a Machine does not function as warranted during the warranty period, IBM in its sole discretion will repair, replace it(with a Machine that is at least functionally equivalent), or refund the purchase price. To obtain coverage under thewarranty you may be required to present proof of purchase.This warranty is non-transferable by the end-user customer.Warranty ServiceTo obtain warranty service for the Machine, you should contact your reseller or call IBM. In the United States, call IBMat 1-800-IBM-SERV (426-7378). In Canada, call IBM at 1-800-565-3344. You may be required to present proof ofpurchase.Depending on the Machine, the service may be 1) a “Repair” service at your location (called “On-site”) or at one ofIBM’s or a reseller’s service locations (called “Carry-in”) or 2) an “Exchange” service, either On-site or Carry-in.When a type of service involves the exchange of a Machine or part, the item IBM or your reseller replaces becomesits property and the replacement becomes yours. The replacement may not be new, but will be in good working orderand at least functionally equivalent to the item replaced.It is your responsibility to:1. obtain authorization from the owner (for example, your lessor) to have IBM or your reseller service a Machine thatyou do not own;2. where applicable, before service is provided —a. follow the problem determination, problem analysis, and service request procedures that IBM or your resellerprovide,b. secure all programs, data, and funds contained in a Machine,c. inform IBM or your reseller of changes in a Machine’s location, andd. for a Machine with exchange service, remove all features, parts, options, alterations, and attachments notunder warranty service. Also, the Machine must be free of any legal obligations or restrictions that prevent itsexchange; and3. be responsible for loss of, or damage to, a Machine in transit when you are responsible for the transportationcharges.Extent of WarrantyIBM does not warrant uninterrupted or error-free operation of a Machine.Misuse, accident, modification, unsuitable physical or operating environment, improper maintenance by you, or failurecaused by a product for which IBM is not responsible may void the warranties.THESE WARRANTIES REPLACE ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.HOWEVER, SOME LAWS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES. IF THESE LAWS APPLY,THEN ALL EXPRESS AND IMPLIED WARRANTIES ARE LIMITED IN DURATION TO THE WARRANTY PERIOD. NOWARRANTIES APPLY AFTER THAT PERIOD.In Canada, warranties include both warranties and conditions.98 Turbo 16/4 Token-Ring PC Card 2
Some jurisdictions do not allow limitations on how long an implied warranty lasts, so the above limitation may notapply to you.Limitation of LiabilityCircumstances may arise where, because of a default on IBM’s part (including fundamental breach) or other liability(including negligence and misrepresentation), you are entitled to recover damages from IBM. In each such instance,regardless of the basis on which you are entitled to claim damages, IBM is liable only for:1. bodily injury (including death), and damage to real property and tangible personal property; and2. the amount of any other actual loss or damage, up to the greater of $100,000 or the charge for the Machine that isthe subject of the claim.Under no circumstances is IBM liable for any of the following:1. third-party claims against you for losses or damages (other than those under the first item listed above);2. loss of, or damage to, your records or data; or3. economic consequential damages (including lost profits or savings) or incidental damages, even if IBM is informedof their possibility.Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the abovelimitation or exclusion may not apply to you.This warranty gives you specific legal rights and you may also have other rights which vary from jurisdiction tojurisdiction.Appendix G. Notices and Warranty 99
100 Turbo 16/4 Token-Ring PC Card 2
Glossary of Terms and AbbreviationsThis glossary defines terms and abbreviationsused in this manual. If you do not find the termyou are looking for, refer to the index or to theIBM Dictionary of Computing, SC20-1699 (NewYork/ McGraw-Hill, Inc., 1994).Aaccess unit. A unit that allows multiple attachingdevices access to a Token-Ring network at a centralpoint such as a wiring closet or in an open work area.adapter address. Twelve hexadecimal digits thatidentify a LAN adapter.address. In data communication, the IEEE-assignedunique code or the unique locally administered codeassigned to each device or workstation connected to anetwork. A character, group of characters, or a valuethat identifies a register, a particular part of storage, adata source, or a data sink. The value is represented byone or more characters. To refer to a device or an itemof data by its address. The location in the storage of acomputer where data is stored. In word processing, thelocation, identified by the address code, of a specificsection of the recording medium or storage.alert. For IBM LAN management products, anotification indicating a possible security violation, apersistent error condition, or an interruption or potentialinterruption in the flow of data around the network. Seealsonetwork management vector transport.InSNA,arecord sent to a system problem management focalpoint to communicate the existence of an alertcondition. In the NetView program, a high-priority eventthat warrants immediate attention. This data baserecord is generated for certain event types that aredefined by user-constructed filters.attach. To make a device a part of a network logically.Note:Not to be confused withconnect,which impliesphysically connecting a device to a network.attaching device. Any device that is physicallyconnected to a network and can communicate over thenetwork.BBasic Input/Output System (BIOS). In IBM personalcomputers with PC I/O channel architecture, microcodethat controls basic hardware operations such asinteractions with diskette drives, fixed disk drives, andthe keyboard.Ccommand. A request for performance of an operationor execution of a program. A character string from asource external to a system that represents a requestfor system action.configuration. The arrangement of a computer systemor network as defined by the nature, number, and chiefcharacteristics of its functional units. More specifically,the term may refer to a hardware configuration or asoftware configuration. The devices and programs thatmake up a system, subsystem, or network. See alsosystem configuration.configuration parameters. Variables in aconfiguration definition, the values of which characterizethe relationship of a product, such as a bridge, to otherproducts in the same network.connect. In a LAN, to physically join a cable from astation to an access unit or network connection point.Contrast withattach.Ddefault. Pertaining to an attribute, value, or option thatis assumed when none is explicitly specified.device driver. The code needed to attach and use adevice on a computer or a network.diagnostics. Modules or tests used by computer usersand service personnel to diagnose hardware problems.diskette drive. The mechanism used to seek, read,and write data on diskettes.Ffastpath transmit. An alternate transmit interface tothe PC Card that provides higher throughput.fault. An accidental condition that causes a functionalunit to fail to perform its required function.fixed disk drive. Synonym for hard disk drive.frame. The unit of transmission in some LANs,including the IBM Token-Ring Network and the IBM PCNetwork. It includes delimiters, control characters,information, and checking characters. On a Token-Ringnetwork, a frame is created from a token when thetoken has data appended to it. On a token bus network(IBM PC Network), all frames including the token framecontain a preamble, start delimiter, control address,optional data and checking characters, end delimiter,and are followed by a minimum silence period. A© Copyright IBM Corp. 1997, 1999 101
housing for machine elements. In synchronous data linkcontrol (SDLC), the vehicle for every command, everyresponse, and all information that is transmitted usingSDLC procedures. Each frame begins and ends with aflag.Hhard disk drive. A stand-alone disk drive that readsand writes data on rigid disks and can be attached to aport on the system unit. Synonymous with fixed diskdrive, hard drive.hot plugging. The ability to remove your adapter aslong as you have shut down all the applications usingthe adapter. When you insert your adapter again, youcan restart those applications.Iinitialize. In a LAN, to prepare the adapter (andadapter support code, if used) for use by an applicationprogram.input/output (I/O). Pertaining to a device whose partscan perform an input process and an output process atthe same time. Pertaining to a functional unit or channelinvolved in an input process, output process, or both,concurrently or not, and to the data involved in such aprocess.insert. To make an attaching device an active part of aLAN.interface. A shared boundary between two functionalunits, defined by functional characteristics, commonphysical interconnection characteristics, signalcharacteristics, and other characteristics as appropriate.A shared boundary. An interface may be a hardwarecomponent to link two devices or a portion of storage orregisters accessed by two or more computer programs.Hardware, software, or both, that links systems,programs, or devices.interrupt. A suspension of a process, such asexecution of a computer program, caused by anexternal event and performed in such a way that theprocess can be resumed. To stop a process in such away that it can be resumed. In data communication, totake an action at a receiving station that causes thesending station to end a transmission. A means ofpassing processing control from one software ormicrocode module or routine to another, or of requestinga particular software, microcode, or hardware function.interrupt level. The means of identifying the source ofan interrupt, the function requested by an interrupt, orthe code or feature that provides a function or service.LLAN adapter. The circuit card within a communicatingdevice (such as a personal computer) that, together withits associated software, enables the device to beattached to a LAN.LANAID. The LAN Adapter Installation and Diagnosticprogram. This program works to simplify the installationand configuration of hardware and software in anon-Plug and Play environment.LAN Client. IBM LAN Client is a protocol stack thatoperates in protected mode in the DOS TCP/IP, NovellIPX Client, NetBIOS, and IEEE 802.2 environments.locally administered address. An adapter addressthat the user can assign to override the universallyadministered address. Contrast withuniversallyadministered address.MMAC frame. Frames used to carry information tomaintain the ring protocol and for exchange ofmanagement information.medium access control (MAC) protocol. In a localarea network, the part of the protocol that governscommunication on the transmission medium withoutconcern for the physical characteristics of the medium,but taking into account the topological aspects of thenetwork, in order to enable the exchange of databetween data stations.message. A logical partition of the user device’s datastream to and from the adapter. A group of charactersand control bits transferred as an entity.Micro Channel. The architecture used by IBMPersonal System/2 computers, Models 50 and above.This term is used to distinguish these computers frompersonal computers using a PC I/O channel, such as anIBM PC, XT, or an IBM Personal System/2 computer,Model 25 or 30.Nnetwork administrator. A person who manages theuse and maintenance of a network.node. Any device, attached to a network, thattransmits and/or receives data. An endpoint of a link, ora junction common to two or more links in a network. Ina network, a point where one or more functional unitsinterconnect transmission lines.node address. The address of an adapter on a LAN.102 Turbo 16/4 Token-Ring PC Card 2
Oopen. To make an adapter ready for use. A break inan electrical circuit. To make a file ready for use.operating system. Software that controls theexecution of programs. An operating system mayprovide services such as resource allocation,scheduling, input/output control, and data management.Examples are IBM PC DOS and IBM OS/2.option. A specification in a statement, a selection froma menu, or a setting of a switch, that may be used toinfluence the execution of a program. A hardware orsoftware function that may be selected or enabled aspart of a configuration process. A piece of hardware(such as a network adapter) that can be installed in adevice to modify or enhance device function.Ppanel. The complete set of formatted information thatappears in a single display on a visual display unit.parameter. A variable that is given a constant valuefor a specified application and that may denote theapplication. An item in a menu or for which the userspecifies a value or for which the system provides avalue when the menu is interpreted. Data passedbetween programs or procedures.PC Card. In a LAN, within a communicating device, acircuit card that, with its associated software and/ormicrocode, enables the device to communicate over thenetwork.port. An access point for data entry or exit. Aconnector on a device to which cables for other devicessuch as display stations and printers are attached.Synonymous withsocket.protocol. A set of semantic and syntactic rules thatdetermines the behavior of functional units in achievingcommunication. In SNA, the meanings of and thesequencing rules for requests and responses used formanaging the network, transferring data, andsynchronizing the states of network components. Aspecification for the format and relative timing ofinformation exchanged between communicating parties.Rrandom access memory (RAM). A computer’s oradapter’s volatile storage area into which data may beentered and retrieved in a nonsequential manner.read-only memory (ROM). A computer’s or adapter’sstorage area whose contents cannot be modified by theuser except under special circumstances.remove. To take an attaching device off a network. Tostop an adapter from participating in data passing on anetwork.ring network. A network configuration in which aseries of attaching devices is connected byunidirectional transmission links to form a closed path. Aring of an IBM Token-Ring Network is referred to as aLAN segment or as a Token-Ring Network segment.Sserver. A device, program, or code module on anetwork dedicated to providing a specific service to anetwork. On a LAN, a data station that provides facilitiesto other data stations. Examples are a file server, printserver, and mail server.shallowmode. A new mode that allows the workstationto assist the PC Card in the reception of informationfrom the Token Ring. When chosen, fastpath transmit isused as well.shared RAM. Random access memory (RAM) on anadapter that is shared by the computer in which theadapter is installed.socket. Synonym forport (2).system. In data processing, a collection of people,machines, and methods organized to accomplish a setof specific functions.system configuration. A process that specifies thedevices and programs that form a particular dataprocessing system.Ttelephone twisted pair. One or more twisted pairs ofcopper wire in the unshielded voice-grade cablecommonly used to connect a telephone to its wall jack.Also referred to as “unshielded twisted pair” (UTP).token. A sequence of bits passed from one device toanother on the Token-Ring network that signifiespermission to transmit over the network. It consists of astarting delimiter, an access control field, and an enddelimiter. The access control field contains a bit thatindicates to a receiving device that the token is ready toaccept information. If a device has data to send alongthe network, it appends the data to the token. Whendata is appended, the token then becomes a frame.Seeframe.Token Ring. A network with a ring topology thatpasses tokens from one attaching device (node) toanother. A node that is ready to send can capture atoken and insert data for transmission.Token-Ring network. A ring network that allowsunidirectional data transmission between data stationsGlossary of Terms and Abbreviations 103
by a token-passing procedure over one transmissionmedium so that the transmitted data returns to and isremoved by the transmitting station. The IBMToken-Ring Network is a baseband LAN with astar-wired ring topology that passes tokens fromnetwork adapter to network adapter. A network thatuses a ring topology, in which tokens are passed in asequence from node to node. A node that is ready tosend can capture the token and insert data fortransmission. A group of interconnected Token Rings.twisted pair. A transmission medium that consists oftwo insulated conductors twisted together to reducenoise.Uuniversally administered address. The addresspermanently encoded in an adapter at the time ofmanufacture. All universally administered addresses areunique. Contrast withlocally administered address.unshielded twisted pair (UTP). Seetelephone twistedpair.104 Turbo 16/4 Token-Ring PC Card 2
IndexAAutoSense 20autoset mode 39, 40Ccard servicesadvantages 39and hot plugging 5description 38disadvantages 39if using 4problems during reboot 49versus point enablers 39card services enabler 39CD-ROM content 45checklist 3configuring the PC Card 33Ddevice driver, NDIS 2 26, 27diagnostics error codes 81diagnostics program 81DOS 76Error Codes 76DOS Client-16 28DOS Error Codes 76EEMM386.EXE 49error codesdiagnostics 81, 83, 86DOS 76listing 50NDIS 62, 76OS/2 62expanded memory specification 42Hhardware problem 50hot-pluggability 7hot plugging 5IIBM PC hotline 50IBM Turbo 16/4 Token-Ring PC Card 2 1IBMTOKCS.DOS 49IEEE 802.2 1initialization error codes 81installationDOS environments 9inserting PC Card 5removing PC Card 6installation(continued)tips 9installing the software 33Intel 37interface softwareDOS 37OS/2 37Kkit contents 3LLANAID 33LANAID, installing with 33lanaidc parameters 87Mmemory conflicts 39memory manager 40, 49expanded memory specification 42with card and socket services 41with point enablers 40memory managers with card and socket services 41memory managers with point enablers 40Microsoft Windows for Workgroups/NDIS 2 27MPTS 26Multiple Protocol Transport Services (MPTS) 26NNDIS device driver 26NDIS device driver 26parameters 20with MPTS 26with other programs 27NDIS Error Codes 62, 76NDIS MAC parameters 20notices 95trademarks 97Novell NetWare Client32 for Windows 95 19OODI 16–bit parameters 29open error codes 83OS/2 26Error Codes 62OS/2 NDIS 2 device driver 26OS/2 NDIS device driver 27Pparameters, autoringspeed 31parameters, BUS ID PCMCIA 3 31parameters, datarate 20© Copyright IBM Corp. 1997, 1999 105
parameters, driver 20parameters, enhancedmode 31parameters, expressmode 31parameters, frame 20, 30parameters, fullduplex 21parameters, LAN Client driver 20parameters, max frame size 30parameters, mem1 21parameters, NIC UAA 30parameters, node 21parameters, node address 29parameters, nofulltuplex 30parameters, noshallowmode 30parameters, Novell NetWare Server 20parameters, PCMCIA 31parameters, port 29parameters, receivebuffersize 31parameters, slot 21part numbers 93PC Card 1connector 6inserting 5latching button 6removal 6PCMCIA 1, 4PCMCIA bus support 10Phoenix Card Services 41, 42point connectivity enablers 37advantages 38disadvantages 38versus Card and Socket Services 39point enabler 49problem determination 49RRJ-45 connector 5RT= 22RTHT= 22RTSW= 22RTTS= 22running the diagnostics program 81Sservice numbers 50shielded twisted-pair cabling 5socket servicesand hot plugging 5description 38if using 4versus point enablers 39software 37configuration 37interface 37software configuration 37software packages 45statement of limited warranty 97STP 5support 50TTCP/IP Version 1.2 for OS/2 27TCP/IP Version 2.0 for OS/2 27test options, diagnostic 81token.lan driver 10TPRn= 23trademarks 97transmit buffer 1transmit error codes 86troubleshooting 50Uunshielded twisted-pair cabling 5UPRn= 23UTP 5Wwarranty 95, 97Windows 2000 23Windows 95 23Windows 98 23Windows NT 23106 Turbo 16/4 Token-Ring PC Card 2

Navigation menu