IBM Networking | IBM Turbo 16/4 Token-Ring PC Card Addendum Home | Products & services | Support & downloads | My account Select a country IBM Networking Networking hardware ·Token-Ring adapters ·How to buy ·Adapter support Support Documentation Feedback Related links: IBM Turbo 16/4 Token-Ring PC Card Addendum Table of Contents About This File New Features Token.lan Driver and PCMCIA Bus Support Card Services and Point Enablers: What Works and What Doesn't Point and Card Services Enablers ODI for Windows 95 Two Token-Ring Card Installations IntranetWare Client for DOS/Windows 3.11 NetWare Server ODI OS/2 Client ODI DOS Client NetWare Client 32 Installation under DOS Custom Keywords OS/2 Tokencs.sys Keywords Token.lan Driver Custom Keyword Documentation Custom Keywords Keywords with Parameters Driver Installation for Some OEM Machines Unattended Install for Win 95 and NT 4.0 Re-installation of Windows 95 Drivers About IBM LAN Client IBM LAN Client Features DOS Conventional Memory Usage -- Reduction Supported IBM LAN Adapters Supported Software Supported Operating Systems Related Documentation Restrictions for This Release How to Configure Route Switch Client Support Windows 95 Windows NT 4.0 and Higher Windows NT 3.51 LAN Adapter Management Agent SystemSoft Card Wizard LANAID Using LANAIDC to Duplicate Configurations Bypassing Startup Files Windows 95 Driver Installation Notes Windows 95 Driver Update Installation Using the IBM Turbo 16/4 Token-Ring PC Card with PCI-1130 Cardbus Controllers and Windows 95 OSR2 DLS Peer Services DLS Startup Note Config.sys Switches for DXMT0MOD.SYS When Using DXMCSMOD.SYS AttachMate Extra Version 3.2 for DOS with DLS 5.0 Installing NDIS Drivers for Artisoft LANtastic LAN WorkPlace NetManage Chameleon Trademarks About This File This file describes additional information on the IBM Turbo 16/4 Token-Ring PC Card. This software can also be used with older versions of this adapter, such as the IBM Auto 16/4 Token-Ring Credit Card Adapter. The information in this addendum supplements the information in the IBM Turbo 16/4 Token-Ring PC Card User's Guide. Where conflicts exist between the User's Guide and this addendum, the information in this addendum supercedes the information in the User's Guide. New Features The Device Drivers for the Turbo 16/4 PC Card are fully backward compatible with all of the previous versions of IBM Token-Ring Credit Cards. A new feature referred to as "Stealth Mode" is one of the new hardware changes made to the IBM Turbo 16/4 PC Card. This feature allows the removal of the cable from the PC Card while the card remains in the machine. The benefit of this feature is that the operating system will not be able to detect that the PC Card is still present in the machine. This is different from IBM's previous PCMCIA Credit Card Adapter, the Auto 16/4 Credit Card. For this Card not to be detected by the Operating System, you must remove the card and the cable from the machine. It is strongly recommended that when removing the cable from the PC card while the system is running and/or connected to the network that you STOP the PC Card BEFORE you remove the cable, just as you normally would when removing any PC card from the system. NOTE: If the cable is disconnect AT BOOT TIME under a Plug-N-Play Operating system, the operating system will not be aware of the card's presence and WILL NOT try to load the device driver for the PC card. However, under an operating system which is not Plug-N-Play compliant, the Operating System WILL try to load the the PC card's device driver anyway and as a result the Operating System will generate error messages referring to the adapter and/or the device drivers. Token.lan Driver and PCMCIA Bus Support Card Services and Point Enablers: What Works and What Doesn't PCMCIA cards have a tremendous potential advantage in their ability to be swapped out of the host system and to have multiple functions available without shutting down the host system. Unfortunately, the full benefits of the technology have not been realized in all software environments yet. PCMCIA cards many times come with a document like this, listing limitations of software support for the card. The IBM token.lan driver has been updated to support PCMCIA cards better in NetWare server, IBM LAN Client environments, DOS, Windows 3.1, and Windows 95. Card and Socket Services support is provided in all environments, but currently only one card is supported. Multiple Token-Ring cards must be point-enabled. There are several reasons for this, all external to the device driver. It is recommended that you use one card where possible, as two card installations currently can be difficult. We anticipate advances in the future that will remove these restrictions. Point and Card Services Enablers An enabler is a small software program that configures the PC Card socket controller to allocate resources (memory, I/O ports, interrupts, DMA channels, and power) to PCMCIA cards. Once the enabler has run successfully, the PCMCIA Token-Ring card is ready to operate and looks much like any ISA Token-Ring card. Two enablers are provided: a point enabler (pointtr.exe) and a 16-bit card service enabler (cs20tok.exe). Only one is required in a given situation to enable the PCMCIA Token-Ring card. To use cs20tok.exe, Card and Socket Services drivers must be loaded to manage the PC Card slots. Pointtr.exe works as a stand-alone. Both enablers have a common parameter interface. The POINTTR utility interface can be listed by typing in a DOS window: pointtr ? Generally, enabling a card is done by running the enabler program, either at a DOS prompt or as a config.sys device driver, with appropriate command-line parameters. For example: In autoexec.bat: pointtr sa mmio=d000 sram=d000,4 rs=16 irq=10 io=0a20 or cs20tok sa mmio=d000 sram=d000,4 rs=16 irq=10 io=0a20 In config.sys: device=c:\pointtr.exe sa mmio=d000 sram=d000,4 rs=16 irq=10 io=0a20 or device=c:\cs20tok.exe sa mmio=d000 sram=d000,4 rs=16 irq=10 io=0a20Note: If using the Auto 16/4 Credit Card the mmio and sram parameters will be as follows: In autoexec.bat: pointtr sa mmio=dc00 sram=d800,16 rs=16 irq=10 io=0a20 or cs20tok sa mmio=dc00 sram=d800,16 rs=16 irq=10 io=0a20 In config.sys: device=c:\pointtr.exe sa mmio=dc00 sram=d800,16 rs=16 irq=10 io=0a20 or device=c:\cs20tok.exe sa mmio=dc00 sram=d800,16 rs=16 irq=10 io=0a20 Both set the card in slot 1 (sa) to an 8-KB memory region based at 0xd0000, with the card operating in enhanced mode. The card is assigned port 0xa20, interrupt vector 10, and Token-Ring speed (rs) will be 16 Mbps. The program runs, then sounds two ascending beeps indicating successful operation. The card is now enabled and ready for the driver to be loaded. ODI for Windows 95 Two Windows 95 installation (INF) files are provided. The preferred file, token.inf, will support one card as a card-services-enabled card. Simply insert the card, select "have disk" at the prompt for driver, insert diskette 2 "device driver disk" and type A:\NOVELL\NETWARE. Installation is automatic. The Token-Ring media speed might have to be set using the autoringspeed or datarate keywords under advanced settings under the driver. Two Token-Ring Card Installations: Support for two cards is more complex and requires a tokenpe.inf. The INF is in the same directory on the installation diskette, but is designed to partially install two Token-Ring cards via the point enabler. Complete the installation manually via a batch file that is run at startup in Windows 95. Normally, Windows 95 will automatically use token.inf. For this reason, the token.inf must be renamed to another non-INF extension file so that tokenpe.inf will be loaded instead. We recommend that you make a backup copy of the device driver diskette before making any changes to it. The installation system will install two cards one at a time. The IBM LAN Client software is placed in \novell\client32 directory of the installaton drive. In that directory, the point enabler is copied (pointtr.exe and eno.msg). First, enable the card using the point enabler (see point enabler information above). Next, load the driver. To load token.lan, the following command line would load the driver first for Token-Ring frames, then for Token-Ring_snap frames: load token port=a20 pcmcia_int=a mem0=d0000 frame=token-ring load token port=a20 pcmcia_int=a mem0=d0000 frame=token-ring_snapThe resources chosen for the card are generally chosen by trial and error based on those available in the current environment. Consult your hardware manufacturer's information for help in this area. A sample batch file for the Turbo PC Card follows: REM ********* May be required for driver to load load cmsm load tokentsm REM ********* Enable card in slot A pointtr sa mmio=d000 sram=d000,4 rs=16 irq=10 io=0a20 REM ********* Enable card in slot B pointtr sb mmio=d200 sram=d200,4 rs=16 irq=5 io=0a24 REM ********* load driver for slot A load token port=a20 pcmcia_int=a mem0=d0000 frame=token-ring load token port=a20 pcmcia_int=a mem0=d0000 frame=token-ring_snap REM ********* load driver for Slot B load token port=a24 pcmcia_int=5 mem0=d2000 frame=token-ring load token port=a24 pcmcia_int=5 mem0=d2000 frame=token-ring_snap REM ********* OPTIONAL f: login joeOnce this process is working, add the batch file to the startup item in your task bar. This process must be done at startup rather than in autoexec.bat, since any cards enabled in either config.sys or autoexec.bat will be reset by Card and Socket Services when Windows 95 loads. Enabling during startup makes the card visible to the driver to load. IntranetWare Client for DOS/Windows 3.11 Card services: To use Card and Socket Services in DOS, load the Card and Socket Services driver according to the instructions in the Point and Card Services Enablers section. Then, run cs20tok to enable the card (only one supported). Then, load the driver as usual. PCMCIA_INT port keywords are not generally needed on card-service-enabled cards. Point enable: Run the point enabler to enable each card. Load drivers as described. Load the driver with pcmcia_int, port and mem0 keywords. NetWare Server Point or card service enablers must be installed under DOS prior to loading the server. Card services: To use Card and Socket Services in the server environment, load the DOS Card and Socket Services driver per instructions. Then run cs20tok to enable the card (only one supported). Then, load the server as usual. Point enable: Point-enable the card in config.sys or autoexec.bat prior to loading the server. Point-enabling two cards requires three parameters on the driver load command line: pcmcia_int, port and mem0 (shared-RAM base). ODI OS/2 Client If you are a user of the IBM Turbo 16/4 Token-Ring PC Card OS/2 ODI device driver TOKEN.SYS: The OS/2 ODI device driver TOKEN.SYS is not included on this diskette. If you require this device driver, please check the IBM Network Environment Support Web site at: http://www.networking.ibm.com/nes/nestoken.htm for up-to-date information on the availability of this device driver. ODI DOS Client NetWare Client 32 Installation under DOS Card and Socket Services is required to initialize the PC Card (PCMCIA) slot. On machines that do not have Card and Socket Services, it is necessary to add pointtr to the autoexec.bat file. This will allow tokencs.com to operate. Custom Keywords ENHANCEDMODE Causes the adapter to operate in fast-path receive mode and in the 4-KB paging mode of fast-path transmit operation. Note: The Auto 16/4 Credit Card can not function in Enhanced Mode. i.e. Enhanced=NO. NOSHALLOWMODE Inhibits the adapter from using its receive lookahead capability, which results in adapter performance degradation. EXPRESSMODE Valid when operating in shallow mode only (NOSHALLOWMODE custom keyword not specified). Use of this keyword reduces the number of adapter-generated receive interrupts to a maximum of two per frame. This mode of operation will lower the adapter's receive performance. RECEIVEBUFFERSIZE The default, 192 bytes, is the optimal value for high-performace class machines (486/Pentium). The maximum allowable value is 2048, with a minimum equal to the default value. This parameter will not ordinarily be required. NOFULLDUPLEX This keyword, when specified, will prevent the adapter from opening in full-duplex mode even if the adapter is connected to the ring through a full-duplex switch. 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 for configurations that use Card Services to enable the adapter. This keyword must not be used in configurations that enable the adapter via a Point Enabler. AUTORINGSPEED This keyword will cause the adapter to save the speed of the ring that it is opening into and use that ring-speed value as its speed the next time it is initialized. OS/2 Tokencs.sys keywords These are the OS/2 custom keywords defined in tokencs.sys Version 1.67 and higher. This list does not include those keywords defined by the Novell requestor (for example, slot, int, dma, mem0). Consult the Novell documentation for information on the use of these keywords. All custom keywords are placed in the net.cfg file under the driver specific section, for example: link driver tokencs slot 1 port a20 pcmcia enhancedmode... (If two cards are used, two driver sections are required.) link driver tokencs slot 1 port a24... Keywords followed by ... indicate that a value is expected following the keyword or phrase, and its range of valid input is given. PCMCIA This keyword indicates to the driver that the card being initialized is a PCMCIA adapter and changes the way the driver interacts with the card and card services drivers. It takes no parameters and is required for all PC cards. ENHANCEDMODE Enables the enhanced-mode operation of the Turbo PC card. This keyword is valid only on turbo-class PC cards. Specifically, enhanced mode uses fast-path receive, fast-path transmit, and an 8-KB memory footprint. ALTERNATE By default, the driver assumes that the installed Token-Ring adapter is at I/O port a20. Use of this keyword changes the port value to a24. Adapters in enhanced mode that are not limited to a20 or a24 port addresses should use the port keyword to specify the base I/O address if it is not one of the two legacy addresses. This also sets the default shared-RAM base address to D4000. The primary default shared-RAM base is at D8000. MAX FRAME SIZE... Default: (ring speed, mode, adapter dependent) Range: 90-17954 The transmit buffer size, expressed in bytes. The value must be a multiple of 8 and must not exceed 4458 in 4-Mbps environments, or 17954 in 16-Mbps environments. This value is the size of a transmit frame in non-fast-path transmit mode and the maximum frame size in fast-path receive mode. Generally, this value is set automatically by the driver as the minimum of the LSL, hardware, and this value. In normal operation this parameter can be ignored. NIC UAA Default: None. Range: hexadecimal string 1-FFFFFFFFFFFFh This parameter selects the adapter to initialize by its universally administered address (UAA),which is in read-only storage on the card. Enhanced-mode adapters can be located at most addresses and can be selected by either their UAA or ordinal number (1 = lowest UAA, 2=highest UAA). RECEIVEBUFFERSIZE Default: Varies with mode. Range: 192-2048 Changes the adapter shallow-mode receive buffer size. Allows tuning of receive buffers to more closely match the LAN traffic environment. This parameter is not needed for normal operations. Value must be a multiple of 8 bytes. Smaller values increase performance and processor utilization, whereas larger values decrease performance and lower processor utilization. DATA RATE Default: Varies Range: 4 or 16 Used to set the adapter data rate for dual-speed adapters. Some dual-speed adapters, notably MCA adapters, might not support this keyword. If the speed selected does not match the ring speed, the open will fail. On PCMCIA adapters, see the complementary keyword, autoringspeed. NOFULLDUPLEX By default, the driver will first attempt to open on the ring in full-duplex mode (connected to a switched Token-Ring network) on those adapters that are capable of this function. Failing that, it will attempt to open in half-duplex mode (a traditional shared-media LAN). The presence of this keyword means that the driver will not attempt to open the PC Card in full-duplex mode. NOSHALLOWMODE Shallow-mode operation is fast-path transmit, fast-path receive, and no LLC processing (802.2) by adapter firmware. NoShallowmode is fast-path transmit, standard receive, and 802.2 processing. Shallowmode is the default on turbo-class adapters and is designed for higher performance. Including this keyword will disable fast-path receive and enable LLC processing on the adapter. AUTORINGSPEED This PCMCIA-specific keyword is used to enable autoringspeed detection of the adapter on the ring when the ring speed is not known or changes because of mobility needs (for example, with a laptop). The first adapter that opens on the ring must define the ring speed, and therefore cannot use the autoringspeed keyword. Adapters opened subsequently can automatically 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 keyword specified, the opening will fail. Token.lan Driver Custom Keyword Documentation In addition to the standard Novell keywords (such as slot, port, int, and frame), a number of custom keywords are available in the driver. This list is dynamic: it changes as support is added for new hardware and as ODI specifications change. If it is known, the driver revision level in which the keyword is available is included. This list describes those keywords that are available and useful to users. All of these keywords are optional unless otherwise noted. Note: Some parameters, if misused, can cause problems with adapter operation and must be set with a thorough understanding of adapter operations. Custom Keywords NOFULLDUPLEX By 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 are capable of this function. Otherwise, it will try to open in half-duplex mode (a traditional shared-media LAN). The presence of this keyword will prevent the attempted open in full-duplex mode. NOSHALLOWMODE Shallow-mode operation is fast-path transmit, fast-path receive, and no LLC processing (802.2) by adapter firmware. NoShallowmode is fast-path transmit, standard receive, and 802.2 processing. Shallowmode is the default on turbo-class adapters and is designed for higher performance. Including this keyword will disable fast-path receive and enable LLC processing on the adapter. AUTORINGSPEED This PCMCIA-specific keyword is used to enable autoringspeed detection of the adapter on the ring when the ring speed is not known or changes because of mobility needs (for example, with a laptop). The first adapter that opens on the ring must define the ring speed, and therefore cannot use the autoringspeed keyword. Adapters opened subsequently can automatically 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 keyword specified, the opening will fail. EXPRESSMODE Valid in shallowmode operation only. During normal (shallowmode) receive processing, the host is interrupted after every buffer is received. Use of this keyword reduces the number (and processing overhead) of interrupts per frame, but lowers overall receive performance. Use this keyword on slower machines or on fast machines that are heavily loaded. Keywords with Parameters SAPS Default: 1 Range: 0-125 The number 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 used unless an application specifically requires it. LS Default: 0 Range: 0-255 The number of adapter link stations that can be open at one time. This parameter is not used in the ODI environment and should not be used unless an application specifically requires it. TBZ Default: (ring speed, mode, adapter dependent) Range: 96-17960 The transmit buffer size, expressed in bytes. The value must be a multiple of 8 and must not exceed 4464 in a 4-Mbps environment, or 17960 in a 16-Mbps environment. This value is the size of a transmit frame in non-fast-path transmit mode and the maximum frame size in fast-path receive mode. Generally, this value is set automatically by the driver as the minimum of the LSL, hardware, and this value. In normal operation this parameter can be ignored. PCMCIA_INT Default: none Range: 2-F in hexadecimal (Version 3.32 and higher) The interrupt assigned to a PCMCIA Token-Ring adapter. Since PCMCIA adapters are handled differently from other bus types, this parameter also indicates to the driver that a PCMCIA adapter is being initialized. On a point-enabled card, the only way the driver can determine the interrupt vector that the card is using is to get it from the command line. This parameter is required on PCMCIA cards that are point-enabled. MEM0 Default: CC000 Range: 0-100000h in hexadecimal (Version 3.21 and higher) This parameter indicates the shared-RAM base address to the driver since in some cases the driver cannot determine the shared-RAM base address without getting it from the command line. This parameter is required on point-enabled PCMCIA cards, especially if more than one is in the system. The value given must be on the proper boundary depending on shared-RAM size. See the table below. Shared-RAM Size Address must be a multiple of -------------------------------------------------------- 4 KB or 8 KB 8 KB 16 KB 16 KB 32 KB 32 KB 64 KB 64 KBPORT Default A20h Range: 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 4 contiguous I/O ports. NIC_UAA Default: None. Range: hexadecimal string 1-FFFFFFFFFFFFh (Version 3.21) This parameter selects the adapter to initialize by its universally administered address (UAA), which is in read-only storage on the card. Enhanced-mode adapters can be located at most addresses and can be selected by either their UAA or ordinal number (1 = lowest UAA, 2=highest UAA). RECEIVEBUFFERSIZE Default: Varies with mode. Range: 192-2048 (Version 3.33) Changes the adapter shallow-mode receive buffer size. Allows tuning of receive buffers to more closely match the LAN traffic environment. This parameter is not needed for normal operations. Value must be a multiple of 8 bytes. Smaller values increase performance and processor utilization while larger values decrease performance and lower processor utilization. DATARATE Default: varies Range: 4 or 16 (Version 3.36b and higher) Used to set the adapter data rate for dual-speed adapters. Some dual-speed adapters, notably MCA adapters, might not support this keyword. If the speed selected does not match the ring speed, the open will fail. On PCMCIA adapters, see the complementary keyword, autoringspeed. SRAMSIZE Default: 4 Range: 4,8,16,32, or 64 (Version 4.01 and higher) PCMCIA only in the Windows 95 environment. Allows setting the shared-RAM size in compatibility modes in a card services environment. Driver Installation for Some OEM machines During the installation of Turbo 16/4 Token-Ring PC Card drivers, diskette 2 of Windows 95 might be requested. If Windows 95 diskette 2 is not available, this problem can be remedied by copying the Windows 95 file precopy2.cab into the windows\options\cabs directory. Unattended Install for Win95 and NT 4.0 Procedures for using one of Microsoft's Unattended Install methods are located on IBM's Web site at http://www.networking.ibm.com/nes/nesrui.htm Re-installation of Windows 95 Drivers Notes: The following procedure applies only to systems that have been populated with previous installations of IBM Token-Ring PCMCIA cards. Under normal circumstances, some of these steps might not be needed if the files in question do not exist in the specified locations. Physically remove all IBM PCMCIA Token-Ring cards from the machine if any are installed. Go to the Control Panel folder and double-click the Network icon to bring up the Network Control Panel Applet (NCPA). Remove all instances of IBM PCMCIA Token-Ring adapters from the system configuration. Delete ibmtok.vxd from the system. Delete netibmcc.inf and netibm.inf from the system. These files are in the INF directory. Delete drvdata.bin and drvidx.bin from the system. These files are also in the INF directory. To bring up the Device Manager, go to the Control Panel folder and double-click the System icon. Click the Device Manager tab, expand the Network Token-Ring and delete all instances of IBM Token-Ring PCMCIA adapters if there are any. Shut down and power off the system. Restart the machine and wait until Windows 95 installation is complete. Insert the adapter on the system and follow the instructions on the screen. You may have to restart the system one more time. NOTE: If an IBM Token-Ring PCMCIA Adapter has not been installed previously, the procedure is much simpler: Rename/delete netibmcc.inf and netibm.inf from the system. These files are in the INF directory. Delete drvdata.bin and drvidx.bin from the system. These files are also in the INF directory. Restart the system and wait until Windows 95 installation is complete. Insert the adapter in the machine and follow the instructions on the screen. You might have to restart the system one more time. About IBM LAN Client IBM LAN Client provides program interfaces to support network application programs using selected IBM Token-Ring and Ethernet adapters. It allows a DOS client workstation to communicate with an IBM LAN Server at Version 3.0, 4.0, and Warp Server, or with a Novell NetWare Server at Version 2.15c or higher, or to use TCP/IP applications. (The IBM and Novell IntranetWare client code is included with this package, with the exception of PING and TCP/IP applications.) In addition, support is provided for programs written to the NetBIOS or IEEE 802.2 application programming interfaces. IBM LAN Client Features As little as 4 KB conventional memory required. (See below for more details.) One common environment for concurrent multiple protocols. One or more of NetBIOS, IPX, TCP/IP, and IEEE 802.2. Shim modules, such as ODINSUP and LANSUP, are not needed. Includes client software for attachment to Novell NetWare Servers and IBM LAN Servers. Supports DOS LAN Services 5.x. New Novell IntranetWare Client for DOS/Windows. Provides full access to essential NetWare services such as NetWare Directory Services (NDS). Provides improved connection reliability, including the ability to auto-reconnect open files. Provides enhanced Large Internet Packet (LIP) and Packet Burst support. Includes an installation tool with a Graphical User Interface (GUI) for easy installation of client software. Includes a command-line version of the installation tool for use by network administrators installing on a large number of workstations. Allows the same adapter device driver to be used for client workstations and for Novell NetWare servers, reducing support complexity. DOS Conventional Memory Usage -- Reduction LAN Client minimizes the use of DOS conventional memory for network communications. With IBM LAN Client, IBM LAN adapter drivers and protocol stacks no longer require large amounts of DOS memory below 1 MB. The tables in this section show how little memory is required for IBM LAN Client, compared to existing implementations. This table shows how much DOS conventional memory is used by IBM LAN Client for three popular communication protocols, compared with current usage. Table 1. Adapter Memory Reduction Protocol Before IBM LAN Client With IBM LAN Client IPX 32 KB 5 KB IEEE 802.2 9 KB 4 KB NetBIOS 32 KB 4 KB Supported Software IBM LAN Client provides support for the following protocols and client applications: For DOS 5.0 or higher: IEEE 802.2 NetBIOS DOS LAN Services 5.x (with IBM Warp Server) IntranetWare Client (IPX/SPX) (with Novell NetWare 2.15c and higher) PC3270 Version 4.x DCAF (Version 1.3 + CSDs) Artisoft LANtastic Version 6.0 Attachmate 3270 Emulation LANDP (If you are using Version 2, make sure that the service level of lan.exe is MS004 or higher.) For Windows 3.1, Windows 3.11, and Windows for Workgroups 3.11: IEEE 802.2 NetBIOS DOS LAN Services 5.x (with IBM Warp Server) IntranetWare Client (IPX/SPX) (with Novell NetWare 4.0) AS/400 for Windows (Version 4.0, V3R1M0, and V3R1M1) TCP/IP using Winsock 1.1 or 1.2 PC3270/Windows Version 4.x Artisoft LANtastic Version 6.0 APPC/Windows Note: IBM LAN Station Manager cannot be run in the same workstation as IBM LAN Client. Supported Operating Systems IBM LAN Client supports the following desktop operating systems: MS-DOS 5.x and 6.x PC-DOS 5.x, 6.x, and 7.0 Windows 3.1 and 3.11, in enhanced mode Windows for Workgroups 3.11 Related Documentation In addition to this document, you might need to consult the following publications: IBM LAN Technical Reference IEEE 802.2 and NetBIOS Application Programming Interfaces, SC30-3587 IBM LAN Server Command and Utilities, S10H-9686 IBM Guide to LAN Server Books, S10H-9688 IBM DOS LAN Services and Windows User's Guide, S10H-9684 Manuals for Novell IntranetWare Client and Novell NetWare Server 4.0 Manuals for Novell TCP/IP interface Note: IBM documentation can be obtained from your IBM marketing representative, or by calling IBM support at the following numbers: In the USA, 1-800-426-7299 In Canada, 1-800-565-3344 Note: Novell documentation can be obtained by contacting Novell, either by calling 1-800-NETWARE or over the World Wide Web at http://www.novell.com. Restrictions for This Release The following restrictions apply for this release of IBM LAN Client: IBM LAN Client will operate with only one adapter. You cannot use RPL to download IBM LAN Client from either a Novell NetWare server or an IBM LAN Server. How to Configure Route Switch Client Support Route Switch Client support has become a standard part of the device drivers for IBM Token-Ring LAN adapters, making installation of the support as easy as upgrading the device driver. Once a Route Switch Client-enabled driver has been installed, configuration consists of setting just two parameters. The first parameter, Route Switch Client Enable, is used to enable and disable Route Switch Client support. By default this parameter is set to NO in order to disable the support. Setting this parameter to YES will enable the support. The second parameter, Route Switch Client Table Entries, specifies the maximum number of logical connections that can be switched at any moment in time. Valid values for this parameter are: 16, 32, 64, 128, 512, and 1024. Workstations or client machines should set this value to one of the smaller values, and servers should set this value to one of the larger values. Windows 95 The following instructions enable the Route Switch Client function in the Windows 95 driver. These instructions assume that the IBM Token-Ring Adapter is already installed and configured. If not, refer to the Installation and Configuration Manual for the adapter being used. To set the Route Switch Client parameters in Windows 95, perform the following steps: Click Start. Click Settings/Control Panel. Double-click Network. Make sure the Configuration tab is selected. If more than one adapter is configured, select the IBM adapter to be configured by clicking the name in the top window. Click the Advanced tab to show configuration parameters. Click Enable Route Switch Client. Click the down arrow to the value of this feature and select Yes. Click Route Switch Table Size. Enter a value for the number of Route Switch table entries. Select OK to save the changed values. Windows NT 4.0 and Higher The following instructions enable the Route Switch Client function in the Windows NT 4.0 driver. These instructions assume that the IBM Token-Ring Adapter is already installed and configured. If not, refer to the Installation and Configuration Manual for the adapter being used. To set the Route Switch Client parameters in Windows NT 4.0, perform the following steps: Click Start. Click Settings/Control Panel. Double-click Network. Click the Adapters tab. If more than one adapter is configured, select the IBM adapter to be configured by clicking the name in the top window. Open the Properties window for this adapter, either by double-clicking the adapter's name as in step 5 or by clicking the properties button. Click the Route Switch Client tab. Enable Route Switch Client by clicking the check box titled Enable Route Switch Client Feature. Select the table size by dragging the slider to the appropriate value. Select OK to save the changed values. Windows NT 3.51 The following instructions enable the Route Switch Client function in the Windows NT 3.51 driver. These instructions assume that the IBM Token-Ring Adapter is already installed and configured. If not, refer to the Installation and Configuration Manual for the adapter being used. When applying a Microsoft Service Pack to an existing installation with a correctly configured IBM Turbo 16/4 Token-Ring PC Card, the Service Pack might replace the existing Token-Ring driver with an older version. When the system is rebooted, the IBM Turbo 16/4 Token-Ring PC Card might not function. It is necessary to reinstall the latest Token-Ring driver diskette in order to restore network connectivity. To reinstall the driver diskette, go to the Control Panel, select Network and then select Upgrade. To set the Route Switch Client parameters in Windows NT 3.51, perform the following steps: In the Program Manager, double-click the Control Panel icon in the Main program group. In the Control Panel window, double-click the Network icon. If more than one adapter is configured, select the IBM adapter to be configured by clicking the name in the Installed adapters panel. Open the Properties window for this adapter, either by double-clicking the adapter's name as in step 3 or by clicking the configure button. Click the Route Switch Client tab. Enable Route Switch Client by clicking the check box titled Enable Route Switch Client Feature. Select the table size by dragging the slider to the appropriate value. Select OK to save the changed values. LAN Adapter Management Agent Adapter management capability using Simple Network Management Protocol (SNMP) and Desktop Management Interface (DMI) are available by using the LAN Adapter Management Agent. As an end-to-end management solution, the Agent can be used in conjunction with the Nways Workgroup Manager Version 1.1 or higher, and Nways Manager for AIX Version 1.2 or higher. For more information about the Agent or to download the Agent, see http://www.networking.ibm.com/trl:trllma.html SystemSoft Card Wizard In the machines that ship preloaded with Windows 95 and that have the Card Wizard application (from SystemSoft), the user has to manually set some options in order to let the system do its hardware detection and configuration. After you perform the following steps, Windows will behave as expected and driver installation and configuration will work seamlessly. From the Card Wizard window, peform the following steps: Select the Properties... menu option from the View menu. Select the driver tab from the dialog box. Select the PnP option and change driver from the page. Click OK. Follow the instructions on the screen. Note: On laptops that have the CardSoft Card and Socket Services the card will work with some user intervention (for example, removing the card, booting the system, disabling Card Wizard, inserting the adapter and following normal installation methods). However, when the machine is restarted the Card Wizard takes over and the adapter is not recognized in the Device Manager. LANAID Using LANAIDC to Duplicate Configurations When using DLS, or TCP/IP without DHCP enabled, you will need to modify the TCP/IP address or DLS Machine ID and User Name to avoid duplicate addresses and/or names on each machine. The easiest way to do this is by using the /TCPIPADDR and/or /MACHID and /USERNM parameters on the LANAIDC command line. Be sure to place these parameters after the /FILE parameter so they will override the parameters in the file. Bypassing Startup Files If startup configuration files are bypassed, LANAID or LANAIDC does not have the information to determine the resources used; therefore, it will not allow you to set any parameters. Do not bypass the startup configuration if you want to configure your system. (A typical way to bypass startup files is by pressing the F5 key during the DOS boot phase.) Windows 95 Driver Installation Notes If Windows 95 does not recognize the insertion of a PC Card in the PC Card slot, it might be necessary to enable PC Card support in the Control Panel. Select Start - Settings - Control Panel and click PC Card (PCMCIA). The PC Card wizard will guide you through the process of enabling Windows 95 PC Card support. Publication Error: The printed publication incorrectly instructs the user to go to the win95 directory "A:\win95" of Diskette 2: Drivers during the Windows 95 driver installation. The correct directory for the location of the Windows 95 drivers is the root directory, "a:\". Windows 95 Driver Update Installation Windows 95 ships with support for older IBM Token-Ring PC Cards. However, these drivers are out-of-date and do not support the enhanced-mode features of the IBM Turbo Token-Ring PC Card. Because of this, it is important that you run fixwin95.bat before installing the PC Card for the first time under Windows 95. This batch file renames the INF file that ships with Windows 95 so that older PC cards will use the latest driver instead of the one built into Windows 95. Follow the procedure below to prepare your system for the new drivers: If you have never installed a Token-Ring PC Card on this installation of Windows 95, skip to step 3. Otherwise, go to the Start button and click Settings - Control Panel. Double-click the network control panel. If the IBM Token-Ring Credit Card Adapter II and Compatibles adapter is installed, remove it. Select OK, but do not restart the computer. Insert the driver diskette in drive A. Open a Command Prompt window and type A:\FIXWIN95.BAT. Remove the diskette from drive A. Restart the computer. Insert the Token-Ring PC Card. Windows 95 should detect the card and prompt you for a diskette. Insert the driver diskette and select OK. Windows will prompt you for a directory for the driver. Type in A:\ and press Enter. NOTE: The OSR2 release of Windows uses the Update Device Driver Wizard. This wizard searches the drives for an updated device driver. Due to a bug in OSR2, it does not search all subdirectories on the diskette drive. You will have to click Other Locations to specify the A:\ directory for installation. Furthermore, you might have to tell Windows to look in A:\ again after you click the Finish button in the Update Device Driver Wizard. Restart the computer. Your PC Card should now be up and running with the latest drivers. Using the IBM Turbo 16/4 Token-Ring PC Card with PCI-1130 Cardbus Controllers and Windows 95 OSR2 Some new portable PCs that have support for Cardbus PC cards use the Texas Instruments PCI-1130 Cardbus socket controller. Windows 95 OSR2 (build 4.00.950B) includes support for the PCI-1130 chipset. IBM Token-Ring PC Cards will not function correctly if: Your portable PC uses the PCI-1130 socket controller chipset AND Your installation of Windows 95 OSR2 uses the Cardbus drivers that shipped with Windows 95 OSR2 If you are having problems getting your IBM Token-Ring PC card to function and you suspect that you have the Windows 95 Cardbus socket controller drivers installed, follow the procedures below to determine if you need the Windows 95 Cardbus socket controller driver patch. Right-click the My Computer icon on the desktop and select Properties. This will bring up the system control panel. Check the version of Microsoft Windows 95. If the version is 4.00.950B, you are running OSR2 and should continue reading; otherwise, you do not need the patch. Click the Device Manager tab in the system control panel and check to see if you have the PCI-1130 Cardbus Socket Controller devices installed by expanding the PCMCIA socket section. If you do not have this device listed, then you do not need the patch. Click the start button and select Find - Files or folders... Search for the file cbss.vxd on the drive that contains your Windows installation (usually C). When it finds it, right-click the cbss.vxd file and select Properties. Click the Version tab and check the version of the file. If the version is 4.00.1111, then you are using the Cardbus socket controller drivers that shipped with Windows 95 OSR2. Contact the computer manufacturer to obtain a patch for the cardbus controller for Windows 95 OSR2. DLS Peer Services DLS Startup Note You must execute a NET START PEER to start the peer services. DLS will execute a NET START automatically for you, but to start the PEER services you have to manually perform the NET START PEER. Config.SYS Switches for DXMT0MOD.SYS When Using DXMCSMOD.SYS Switches should be added to the end of the dxmt0mod.sys file in the config.sys when using the dxmcsmod.sys driver. Use the following line when you are running PC3270 version 4.0 and DLR 3.0: DEVICE=C:\LSP\DXMT0MOD.SYS O=Y S=13 ST=13 C=13 ES=2 EST=2 AttachMate Extra Version 3.2 for DOS with DLS 5.0 When using LSP modules E0,T0/J0 with Attachmate Extra Version 3.2 for DOS, and DLS 5.0 data miscompares have been discovered during test of this software. Because of this incompatibility with Attachmate software, we recommend that you not use this configuration. Installing NDIS Drivers for Artisoft LANtastic Before installing the NDIS drivers from the diskette, you need to create the subdirectory before the installation. To create a directory for the NDIS drivers, in a DOS box type mkdir lantasti. LAN WorkPlace The LAN Workplace installation procedure places the LAN WorkPlace BIN directory before the LAN Client directory in the system path. When running PING, the system will find the LAN WorkPlace BIN directory with an older version of PING, which might report that TCP/IP is not loaded. Make sure you use the version of PING in the LAN Client directory, which is a more recent version of this program and will correctly find TCP/IP. Deleting the earlier PING version in the LAN WorkPlace directory will force the system to then find the correct one in LAN Client, or alternately replace the PING program in LAN WorkPlace with a more recent version. NetManage Chameleon During installation of Chameleon, when entering the driver information, you are requested for location of ibmtokcs.dos. When a location is given, the Chameleon software copies only the driver file. In order for the driver to work, the ltg.msg file must also be copied. Copy the ltg.msg file into the applicable directory (for example, with Chameleon 4.5, the default directory is C:\NETMANAG). Trademarks The following are trademarks of International Business Machines Corporation in the United States and/or other countries: AIX, AS/400, IBM, Nways, and OS/2. Microsoft, Windows, Windows NT, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation. Pentium is a trademark or registered trademark of Intel Corporation in the U.S. and other countries. Other company, product, and service names may be trademarks or service marks of other companies. About IBM | Privacy | Terms of use | Contact