CONTENTS Table of Contents =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- About This File 1.0 DMI 2.0 Diskette 2 file compression 2.1 DMI with Windows NT 2.2 Updating PATH in config.sys 2.3 LANAID 3.0 Using LANAIDC to duplicate configurations 3.1 Bypassing startup files 3.2 SystemSoft Card Wizard 4.0 Windows 95 Driver Installation notes 5.0 Windows installation with older Token-Ring credit card adapters 5.1 Windows95 driver update Installation 5.2 Using the IBM Turbo 16/4 Token-Ring PC Card with PCI-1130 Cardbus Controllers and Windows 95 OSR2 5.3 DLS Peer Services. 6.0 DLS startup note 6.1 DLS PEER services with Windows and 4M of memory or less. 6.2 Config.SYS switches for DXMT0MOD.SYS when using DXMCSMOD.SYS 7.0 AttachMate Extra version 3.2 for DOS with DLS 5.0. 8.0 ODI OS/2 Client 9.0 ODI DOS Client 10.0 Custom Keywords 10.1 OS/2 Tokencs.sys keywords 11.0 Token.LAN driver custom keyword documentation 12.0 Custom Keywords 12.1 Keywords with parameters 12.2 Token.LAN driver and PCMCIA Bus Support 13.0 Card Services and Point Enablers: What Works and What Doesn't 13.1 Point and Card Services enablers 13.2 ODI for Windows 95 13.3 Two token-ring card installations: 13.4 DOS (ODI) 13.5 Netware Server 13.6 Driver Installation for some OEM machines 14.0 Installing NDIS drivers for Artisoft Lantastic 15.0 Unattended Install for Win95 and NT 4.0 16.0 Re-installation of Windows 95 Drivers 17.0 LAN WorkPlace 18.0 NetManage Chameleon 19.0 IBM TCP/IP DOS (TCPDOS) 20.0 1.0 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. 2.0 DMI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 2.1 Diskette 2 file compression =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- All the files on disk 2 concerning DMI have been compressed. Before using the files, execute the self extracting file DMI.EXE that you will find in the DMI directory on disk 2. 2.2 DMI with Windows NT =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Do not attempt to use DMI support in Windows NT when the adapter's bindings are disabled in the Network Control Panel for NT, the system will hang. 2.3 Updating PATH in config.sys =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Some text editors may truncate the long path statement in the config.sys, effectively destroying the config.sys. Use an editor which is able to handle long lines and locate line beginning with SET PATH= ; go to the end of this line and add ;[drive]\IBMCOM\PROTOCOL. 3.0 LANAID =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 3.1 Using LANAIDC to duplicate configurations =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Note: Installation manual addition for step 6 in Appendix H When using TCP/IP or DLS, you will need to modify the TCP/IP address and/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. 3.2 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 the user to set any parameters. Do not bypass the startup configuration if you want to configure your system. (A typical way that the startup files are bypassed is with the F5 key during the DOS boot phase.) 4.0 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 performing the following steps Windows will behave as expected and driver installation and configuration will work seamlessly. From the Card Wizard window, do the following: 1. Select the "Properties..." menu option from the View menu. 2. Select the driver tab from the dialog box 3. Select the PnP option and change driver from the page 4. Click OK 5. Follow the instructions on the screen. NOTE On laptops that have the Card Soft card & socket services the card will work with some user tweaking (i.e., 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. 5.0 Windows 95 Driver Installation notes =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 5.1 Windows installation with older Token-Ring credit card adapters =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Users of the IBM Turbo 16/4 Token-Ring PC Card may skip this section. Older IBM Token Ring PC Cards (e.g. IBM Auto 16/4 Token-Ring Credit Card Adapter) do not install properly under Windows 95. This occurs because the Windows 95 resource manager does not allocate appropriate resources to the PC card. If you are having problems using this new driver with an older IBM Token Ring PC Card, follow the below procedure to manually correct the resources for the PC card. 1. Click on the Start button, and then click on Settings -> Control Panel. 2. Double-click on the System control panel icon. 3. Inside the System control panel, click on the Device Manager tab. This displays all the devices in your system, grouped by device class (e.g. Network, Display, etc.). 4. Click on the "+" beside Network to show the installed network devices. (NOTE: This section may already be expanded. If so, the affected device's icon will be shown with a small "!" over it to indicate that there is a problem.) 5. Double-click the affected PC card. This should bring up the Device properties window. 6. Select the "Resources" tab at the very top. This will display the resources that the driver is attempting to use. At this point, note the current resources being used and check to make sure that they "make sense". The table below shows some typical values for PC card resources: Base I/O Port A20-A23 Interrupt 9 Memory Window 000D2000-000D5FFF Memory Window 000D6000-000D7FFF For older Token Ring PC cards, the first adapter should always use I/O port A20. If there is another older Token-Ring PC card installed, it should use I/O port A24. Two memory windows are required for older PC Cards. Typically, they are located in the memory space between 000C0000 and 000DFFFF. Using anything else could conflict with other system devices. Any non-conflicting interrupt can be used for the PC Card. If your PC card is assigned bad resources, continue: 7. Uncheck "Use automatic settings". This allows you to change the device's resources manually. 8. Change the memory windows to a typical configuration (see above). 9. Make sure that the I/O port is A20-A23. 10. Make sure that the interrupt does not conflict with other installed devices. 11. After this is done, select OK. Windows 95 will prompt you to reboot the system. Your PC Card should now be operable on the network. 5.2 Windows95 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: 1. 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 on Settings -> Control Panel. 2. Double-click on 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! 3. Insert the driver disk into your A: drive. Open a Command Prompt window and type "A:\WIN95\FIXWIN95.BAT". 4. Remove the diskette from the A: drive. Restart the computer. 5. Insert the Token Ring PC Card. Windows 95 should detect the card and prompt you for a diskette. Insert the driver disk and select OK. Windows will prompt you for a directory for the driver. Type in A:\WIN95 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 doesn't search all subdirectories on the floppy drive. You will have to click on "Other Locations" to specify the A:\WIN95 directory for installation. Furthermore, you may have to tell Windows to look in A:\WIN95 again after you click the "Finish" button in the Update Device Driver Wizard. 6. Restart the computer. Your PC Card should now be up and running with the latest drivers. 5.3 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 properly if: * Your portable 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. 1. Right-click on the My Computer icon on the desktop and select Properties. This will bring up the system control panel. 2. Check the version of Microsoft Windows 95. If the version is 4.00.950B, you are running OSR2 and should continue reading; otherwise, you can stop here. 3. Click on 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 may stop reading here. 4. Click on the start button and select Find -> Files or folders... 5. Search for the file CBSS.VXD on the drive that contains your Windows installation (usually C:). When it finds it, right-click on the CBSS.VXD file and select properties. 6. Click on 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. 6.0 DLS Peer Services. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 6.1 DLS startup note =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The user must execute a NET START PEER to start the peer services and if using windows, you need to execute a NET START PEER before entering windows. DLS will execute a NET START automatically for the user but to start the PEER services the user has to manually perform the net start peer. 6.2 DLS PEER services with Windows and 4M of memory or less. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- With Card and Socket services installed on machines with less than 4 M of memory, there is only 485K of memory left once Card/Socket Services, Lanclient and DLS Peer are loaded. This limitation prevents Windows 3.1x from starting because there is not enough free memory to load Windows. 7.0 Config.SYS switches for DXMT0MOD.SYS when using DXMCSMOD.SYS =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Switches should to be added to the end of the DXMT0MOD.SYS file in the CONFIG.SYS when using the DXMCSMOD.SYS driver. The following line will work for running PC3270 ver 4.0 and DLR 3.0: DEVICE=C:\LSP\DXMT0MOD.SYS O=Y S=13 ST=13 C=13 ES=2 EST=2 8.0 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. 9.0 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: A last-minute technical problem has prevented IBM from providing the OS/2 ODI device driver TOKEN.SYS 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/nespcmci.htm for up-to-date information on the availability of this device driver. 10.0 ODI DOS Client =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 10.1 Custom Keywords =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ENHANCEDMODE Causes the adapter to operate in 4k paging mode. NOSHALLOWMODE Disables adapter shallow mode operation. Shallow mode utilizes the receive look ahead capability EXPRESSMODE Enables adapter fast path receive express mode operation. RECEIVEBUFFERSIZE (Default value is 192. Engineering has done some performance testing and found that optimal performance is dependant on the host systems processor linked to this value. I.E.: 486/pentium optimum is with a 192 byte buffer.) NOFULLDUPLEX Disables full duplex ring insertion. BUS ID PCMCIA 3 Must be present in NET.CFG otherwise driver assumes adapter is ISA bus type. PCMCIA Must be present in NET.CFG for configurations that use Card Services to enable the adapter. Must not be present in NET.CFG for configurations that use the Point Enabler to enable the adapter. AUTORINGSPEED Causes the ring speed at which the adapter is opened to be saved and to be used as the ring speed the next time the driver is initialized. 11.0 OS/2 Tokencs.sys keywords =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- These are the OS/2 custom keywords defined in tokencs.sys version 1.67 and higher. This list doesn't include those keywords defined by the Novell requestor (slot, int, dma, mem0, etc). Consult the Novell documentation for info on the use of these keywords. All custom keywords are placed in the net.cfg file under the driver specific section, i.e. link driver tokencs slot 1 port a20 pcmcia enhancedmode ; if two cards are used, two driver section are required. link driver tokencs slot 1 port a24 Keywords followed by a indicate that a value is expected following the keyword or phrase and its range of valid input are 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 credit card adapters. ENHANCEDMODE Enables the enhanced mode operation of the Turbo credit card adapter. This keyword is valid only on turbo class credit card adapters. Specifically, enhanced mode uses fast path receive, fast path transmit, and a 8k memory foot print. 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. Enhanced adapters that aren't limited to a20 or a24 port addresses should use the port keyword to specify the base I/O address if it isn't one of the two legacy addresses. 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 4mbs environments or 17954 in 16mbs 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: hex string 1-FFFFFFFFFFFFh This parameter selects the adapter to initialize by its UAA (universally administered address) that is in read only storage on the card. Enhanced mode adapters can be located at most any address and can be selected either by 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 while 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 may not support this keyword. If the speed selected doesn't 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 will forgo 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. Inclusion of 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 (i.e. a laptop). If the driver attempts to open at the wrong ring speed the speed will be changed to match the ring. Use of this keyword pre-supposes that another adapter is already open on the LAN as an adapter set to sense the ring speed and adjust may open at the wrong speed if it is the first adapter to open. See the datarate keyword which complements this functionality. 12.0 Token.LAN driver custom keyword documentation =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Token.LAN Driver Revision: 4.02 ODI Specification level 3.3 (Green River) In addition to the standard Novell keywords (slot, port, int, frame, etc) a number of custom keywords are available in the driver. This list is dynamic: it changes as support is added for new hardware and ODI specifications change. In the case it is known, the driver revision level that the keyword is available in is included. This list describes those keywords that are available and useful to users. All of these keywords are optional unless otherwise noted. CAUTION: Some parameters, if misused, can cause problems with adapter operation and MUST be set with a thorough understanding of adapter operations. 12.1 Custom Keywords =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 will forgo 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. Inclusion of 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 (i.e. a laptop). If the driver attempts to open at the wrong ring speed the speed will be changed to match the ring. Use of this keyword pre-supposes that another adapter is already open on the LAN as an adapter set to sense the ring speed and adjust may open at the wrong speed if it is the first adapter to open. See the datarate keyword which complements this functionality. EXPRESSMODE Only valid in shallowmode operation. 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. 12.2 Keywords with parameters =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- SAPS Default: 1 Range: 0-125 The number of adapter service access points that may 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 may 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 4mbs environment or 17960 in a 16mbs 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 Ver. 3.32 and above. The interrupt that a PCMCIA token-ring adapter is assigned. 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 hex. Ver. 3.21 and above This parameter indicates the shared ram base address to the driver since in some cases the driver can't 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 that 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 -------------------------------------------------------- 4k or 8k 8K 16K 16k 32k 32k 64k 64k PORT Default A20h Range: A20 or A24 in non-enhanced mode, 100-0FFCH in enhanced mode. The base of the I/O port the adapter uses. The adapter uses 4 contiguous I/O ports at this location. May be required in some cases. NIC_UAA Default: None. Range: hex string 1-FFFFFFFFFFFFh Ver. 3.21 This parameter selects the adapter to initialize by its UAA (universally administered address) that is in read only storage on the card. Enhanced mode adapters can be located at most any address and can be selected either by their UAA or ordinal number (1 = lowest UAA, 2=highest UAA). RECEIVEBUFFERSIZE Default: Varies with mode. Range: 192-2048 Ver. 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 Ver. 3.36b and above. Default: varies Range: 4 or 16 Used to set the adapter data rate for dual speed adapters. Some dual speed adapters, notably MCA adapters may not support this keyword. If the speed selected doesn't match the ring speed the open will fail. On PCMCIA adapters, see the complementary keyword, autoringspeed. SRAMSIZE Ver. 4.01 and above. Default: 4 Range: 4,8,16,32, or 64 PCMCIA only in the windows 95 environment. Allows setting the shared RAM size in compatibility modes in card services environment. Not needed in normal usage. 13.0 Token.LAN driver and PCMCIA Bus Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 13.1 Card Services and Point Enablers: What Works and What Doesn't =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- PCMCIA cards have a tremendous potential advantage in the ability to be swapped out of the host system and to have multiple functionalities available without shutting down the host system. Unfortunately, the full benefits of the technology haven't 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 LanClient environments, DOS, Windows 3.1, and Windows95 operating systems. Card and socket service support is provided in all environments but, for now, all only supports 1 card. Multiple token-ring cards must be point enabled. There are several reasons for this, all external to the device driver. We urge you to use 1 card where possible as two card installs currently can be difficult. We anticipate advances in the future that will remove these restrictions. 13.2 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 card. 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 an 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 standalone. There are advantages and disadvantages to both but that discussion is beyond the scope of this document. 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 at a DOS prompt or as a config.sys device driver with appropriate command line parameters. For example: ; 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 ; 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=0a20 both set the card in slot 1 (sa) to an 8k 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 16mbs. The program runs, then sounds two ascending beeps indicating successful operation. The card is now enabled and ready for the driver to be loaded. 13.3 ODI for Windows 95 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Two Windows 95 installation (INF) files are provided. The preferred file, TOKENCS.INF will support 1 card as a card services enabled card. Simply insert the card, select "have disk" at the prompt for driver, insert disk 2 "Device driver disk" and enter the path "A:\NOVELL\NETWARE". The card will install automatically. The token-ring media speed may have to be set via autoringspeed or datarate keywords under advanced settings under the driver. 13.4 Two token-ring card installations: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Support for 2 cards is more complex and requires a TOKENPE.INF. The INF is in the same directory on the installation disk but is designed to PARTIALLY install 2 token-ring cards via the point enabler. The remaining installation is manually done via a batch file that is run at startup time in Windows 95. Normally, Windows 95 will automatically use TOKENCS.INF. For this reason, the TOKENCS.INF must be renamed to another non-INF extension file so that TOKENPE.INF will be loaded instead. We recommend you make a backup copy of the device driver disk before making any changes to it. The installation system will install two cards one at a time. The IBM LanClient software is placed in \novell\client32 directory of the installation drive. In that directory, the point enabler is copied (POINTTR.EXE and EN0.MSG). First, enable the card using the point enabler (see point enabler info above). Next, load the driver. To load TOKEN.LAN, the following command line would load the driver for 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_snap Unfortunately, the resources chosen for the card are generally chosen by trial and error based on those available in the current environment. Consult your hardware manufacture's information for help in this area. A sample batch file 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 joe Once this process is working, add the batch file to the startup item in your task bar. This process must be done at startup time rather than autoexec.bat since any cards enabled in either CONFIG.SYS or AUTOEXEC.BAT will be reset by card and socket services loading as Windows 95 loads. By enabling during startup time, the card is then visible to the driver to load. We look forward to advances that allow us to automate this process. 13.5 DOS (ODI) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Card services: To use card and socket services in the DOS, load the card and socket services driver per manufactures instructions. Then run cs20tok to enable the card (only 1 supported!). Then load the driver as usual. PCMCIA_INT, port keywords aren't generally needed on card service enabled cards. Point enable: Run point enabler to enable each card load driver(s) as described. Load the driver with pcmcia_int, port and mem0 keywords. 13.6 Netware Server =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Card services: To use card and socket services in the server environment, load the DOS card and socket services driver per manufactures instructions. Then run cs20tok to enable the card (only 1 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 3 parameters on the driver load command line: pcmcia_int, port and mem0 (shared ram base). 14.0 Driver Installation for some OEM machines =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- During the installation of Turbo 16/4 Token-Ring PC Card drivers, diskette #2 of Windows95 may be requested. If Windows95 diskette 2 is not available, this problem may be remedied by copying the Windows95 file PRECOPY2.CAB into the Windows\options\cabs directory. 15.0 Installing NDIS drivers for Artisoft Lantastic =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Before installing the NDIS drivers from the diskette, you need to create the sub directory before the installation. To create a directory for the NDIS drivers, in a DOS box use the command "MakeDir Lantasti". 16.0 Unattended Install for Win95 and NT 4.0 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Procedures for using one of Microsoft's Unattended Installation methods can be located on IBM's Web site: HTTP: //www.networking.ibm.com/nes/nespcmci.htm or by downloading files NTPCCRD.EXE for NT 4.0 or W95PCCRD.EXE for Windows95 17.0 Re-installation of Windows 95 Drivers =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- NOTE 1: The following procedure applies only to systems that have been populated with previous installations of IBM Token-Ring PCMCIA cards. NOTE 2: Under normal circumstances some of these steps may not be needed if the files in question do not exist in the specified locations. 1. Physically remove all IBM PCMCIA Token-Ring cards from the machine if there are any. 2. Go to the Control Panel folder and double click on the Network icon to bring up the NCPA (Network Control Panel Applet). 3. Remove all instances of IBM PCMCIA Token-Ring adapters from the system configuration. 4. Delete ibmtok.vxd from the system. Search for this filename on all available drives and make sure to delete ALL instances of it. 5. Rename/delete netibmcc.inf and netibm.inf from the system. These files will be found in the INF directory. 6. Delete DRVDATA.BIN and DRVIDX.BIN from the system. These files will be found under the INF directory. 7. Bring up the registry editor (REGEDIT.EXE). Expand the HKEY_LOCAL_MACHINE\Enum\PCMCIA and remove all instances of IBM-TOKEN_RING under the PCMCIA tree if there are any. Expand HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control and remove the following files from the Installed Files folder: ibmtok.vxd, netibm.inf, netibmcc.inf, netibm2.inf and ibmtok.dos. Expand HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net and delete all instances of Token Ring adapters that use the ibmtok.vxd driver if there are any. 8. Bring up the Device Manager. Go to the Control Panel folder and double click on the System icon. Click on the Device Manager tab, expand the Network Token-Ring and delete all instances of IBM Token-Ring PCMCIA adapters if there are any. 9. Shut down and power off the system. 10. Restart the machine and let Windows 95 come up completely. 11. 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 the machine has not had a previous installation of an IBM Token Ring PCMCIA Adapter the procedure becomes much simpler: 1. Rename/delete netibmcc.inf and netibm.inf from the system. These files will be found under the INF directory. 2. Delete DRVDATA.BIN and DRVIDX.BIN from the system. These files will be found in the INF directory. 3. Restart the system and let Win95 come up completely. 4. Insert the adapter on the machine and follow the instructions on the screen. You may have to restart the system one more time. 18.0 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 may 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 which 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. 19.0 NetManage Chameleon =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- During installation of Chameleon, when entering the driver information, you are requested for location of the IBMTOKCS.DOS. When a location is input, the Chameleon software only copies the driver file. In order for the driver to work, the LTG.MSG file is also required to be copied. Copy the LTG.MSG file into the applicable directory (for example, with Chameleon 4.5, the default directory is C:\NETMANAG). 20.0 IBM TCP/IP DOS (TCPDOS) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- When installing drivers for IBM TCPDOS, the installation program will prompt for the driver diskette. The drivers are on diskette 1 in the subdirectory \ibm\trcc\ndis