IBM EtherJet PC Card readme.1st file (v2.59) 01/30/97 _____________________________________________________________________________ 1.1 About This File . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Support Information (Voice/www/ftp/bbs) . . . . . . . . . . . . . . 1 1.3 EtherJet PC Card Device Drivers Diskette Contents . . . . . . . . . 2 1.4 OS/2 NDIS 2 Installation - Error in Installation and User's Guide 3 1.5 EtherJet PC Card supports NT 3.51 and 4.0. . . . . . . . . . . . . . 3 1.6 Important information about auto-negotiation . . . . . . . . . . . . 3 1.7 IBM LAN Client Information . . . . . . . . . . . . . . . . . . . . . 3 1.8 Installation and configuration of Novell Client 32 for Windows 95 3 1.8.1 Installation of the EtherJet PC Card AFTER Novell Client 32 for Windows 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.8.2 Installation of the EtherJet PC Card BEFORE Novell Client 32 for Windows 95 has . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.8.3 Configuration of the EtherJet PC Card being used for Novell Client 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.9 Connectivity Enablers . . . . . . . . . . . . . . . . . . . . . . . 6 1.9.1 Point Enabler (POINTJET.EXE) . . . . . . . . . . . . . . . . . . 7 1.9.1.1 POINTJET.EXE syntax . . . . . . . . . . . . . . . . . . . . 7 1.9.2 Card Services Enabler (CS20JET.EXE) . . . . . . . . . . . . . . 8 1.9.2.1 CS20JET.EXE Syntax . . . . . . . . . . . . . . . . . . . . . 8 1.10 Some notes on NetWare device drivers . . . . . . . . . . . . . . . 9 1.10.1 Setting duplex mode function . . . . . . . . . . . . . . . . 10 1.10.2 NetWare 16-bit DOS client, IBMEXNWC.COM . . . . . . . . . . . 10 1.10.3 NetWare OS/2 client, IBMEXNWC.OS2 . . . . . . . . . . . . . . 10 1.10.4 NetWare Server Driver, IBMEXNWS.LAN . . . . . . . . . . . . . 11 1.11 Packet Driver Installation Procedure . . . . . . . . . . . . . . 11 1.12 Using Multiple EtherJet PC Cards in the same machine. . . . . . . 12 1.12.1 DOS NDIS2 and Novell client Environments . . . . . . . . . . 12 1.12.1.1 Using Card and Socket Services . . . . . . . . . . . . . 13 1.12.1.2 Using the point enabler. . . . . . . . . . . . . . . . . 13 1.12.1.3 Using the card services enabler . . . . . . . . . . . . . 13 1.12.2 OS/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.12.2.1 OS/2 NDIS 2 Environment . . . . . . . . . . . . . . . . . 13 1.12.2.2 OS/2 Novell Environment . . . . . . . . . . . . . . . . . 13 1.12.3 Novell Server Environments . . . . . . . . . . . . . . . . . 14 1.12.4 Windows for Workgroups - NDIS3 . . . . . . . . . . . . . . . 14 1.12.5 Packet Driver . . . . . . . . . . . . . . . . . . . . . . . . 14 1.12.6 Windows 95 . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.12.7 Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.13 System Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.13.1 Super Client Drivers . . . . . . . . . . . . . . . . . . . . 16 1.13.2 Using Phoenix Card and Socket services on IBM ThinkPads . . . 16 1.13.3 Using PC Cards in an IBM Dock II . . . . . . . . . . . . . . 16 1.13.4 Adapter not working when using the point enabler (POINTJET.EXE) 16 1.13.5 Warp MPTS may detect EtherJet PC Card as EtherJet ISA adapter. 17 1.13.6 Windows for Workgroups . . . . . . . . . . . . . . . . . . . 17 1.13.6.1 Switching between NDIS2 and NDIS3 drivers. . . . . . . . 17 1.13.6.2 Using the NDIS2 driver without the card services enabler. 18 1.13.7 Memory Conflicts and Memory Managers . . . . . . . . . . . . 18 Contents 1 1.13.8 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . 18 Contents 2 1.1 ABOUT THIS FILE ____________________ This file includes information about the IBM EtherJet PC Card that may not be included in the Installation and User's Guide. A "System Pitfalls" section is also included to help resolve problems that may occur during installation or operation of the EtherJet PC Card. NOTE: Drivers described in this document as "card-services aware" are drivers that can find and initialize an EtherJet PC Card via installed card and socket services. DOS drivers that are card-services aware can also find cards configured via one of the supplied enablers (CS20JET.EXE or POINTJET.EXE). 1.2 SUPPORT INFORMATION (VOICE/WWW/FTP/BBS) ____________________________________________ If you are having a problem with your EtherJet PC Card be sure to follow the instructions in the "Help and Service Information" section of your Installa- tion and User's Guide. Here are the phone numbers for voice product support: 1-800-426-7299 Options by IBM HelpCenter 1-800-237-5511 IBM Support Services 1-800-772-2227 IBM PC Help Center 1-800 565-3344 HelpPC (Canada) Online file access is available via the world wide web at the following sites: Latest disk images : http://www.raleigh.ibm.com/nes/neshome.html IBM Networking Home Page: http://www.raleigh.ibm.com/ IBM PC Company Home Page: http://www.pcco.ibm.com/ FTP access is available via anonymous FTP to: lansupport.raleigh.ibm.com For BBS support: United States (919) 517-0001 (directory 32) Vancouver (604) 664-6464 Toronto (416) 956-7877 Montreal (514) 938-3022 Winnipeg (204) 934-2735 Markham (905) 316-4255 Halifax (902) 420-0300 1 1.3 ETHERJET PC CARD DEVICE DRIVERS DISKETTE CONTENTS ______________________________________________________ Here is a brief description of files contained on the EtherJet PC Card diskette 1 (the files in the DMI subdirectory are not included here). readme.1st - This file. ibmexndi.dos - The DOS NDIS2 card-services aware device driver. ibmexndi.nif - NDIS2 install file. There are several different files with this name - the OS/2 NDIS2 NIF is in the diskette root directory. Most of the other copies are various flavors of DOS NIF files used by DOS protocol stack install programs. ibmexnwc.com - The DOS Novell card-services aware client device driver. ibmexnwc.ins - Install file for the DOS Novell client driver (ibmexnwc.com). protocol.smp - Sample NDIS2 PROTOCOL.INI - shows examples of how to use NDIS2 driver parameters. protocol.ini - There are several of these at various spots on the diskette. They are used by various NDIS2 install programs. ibmexnws.lan - Novell Server driver. This driver requires the use of an enabler, either POINTJET.EXE or CS20JET.EXE. ibmexnws.ldi - Novell server install file. ibmexnws.inf - Windows 95 install file for Novell Client 32. ibmexndi.os2 - The OS/2 NDIS2 card-services aware device driver. ibmexnwc.os2 - The OS/2 Novell client card-services aware client device driver. net.smp - Contains information on net.cfg parameters for the IBMEXNWC.COM and IBMEXNWC.OS2 drivers. ibmexpkt.com - The packet driver. This is a driver for DOS/Windows environments. This driver requires the use of an enabler, either POINTJET.EXE or CS20JET.EXE. ibmexpkt.zip - The packet driver source code. readme.txt - Packet driver description. ibmexwfw.386 - Windows for Workgroups NDIS3 device driver. This driver requires the use of an enabler, either POINTJET.EXE or CS20JET.EXE. ibmexw95.inf - The Windows 95 install file. ibmexw95.vxd - The Windows 95 NDIS3 device driver. cs20jet.exe - The DOS mode card services enabler. disk1 - File to identify the disk for Windows NT install. ibmexwnt.sys - The Windows NT NDIS3 device driver. jet.msg - The message file used by POINTJET.EXE oemsetnt.inf - Windows NT install file. oemsetup.inf - Install file for NDIS2 and WFW NDIS3 drivers. pointjet.exe - DOS mode point enabler supporting Intel 82365SL and compatible socket controllers, or host bus adapters. 2 1.4 OS/2 NDIS 2 INSTALLATION - ERROR IN INSTALLATION AND USER'S GUIDE ______________________________________________________________________ If you install your card in an OS/2 NDIS 2 environment it is not necessary to install or run LANAID. If your 'Installation and User's Guide' has an installation step titled "Configure the PC Card" for either the "OS/2 NDIS 2 Device Driver Using LAPS" or "OS/2 NDIS 2 Device Driver Using MPTS" installa- tion sections, it may be skipped. 1.5 ETHERJET PC CARD SUPPORTS NT 3.51 AND 4.0. _______________________________________________ Your version of the "Installation and User's Guide" may list "Microsoft Windows NT, Versions up through 3.51" in the "Software Requirements for the EtherJet PC Card". The EtherJet PC Card was tested on both Windows NT 3.51 and NT 4.0. 1.6 IMPORTANT INFORMATION ABOUT AUTO-NEGOTIATION _________________________________________________ The EtherJet PC Card supports auto-negotiation, meaning it can communicate with an appropriate hub to enable full duplex operation over twisted pair (10Base T) medium. Use auto-negotiation only if you are sure the switch or hub you plan to attach to supports it (not many support auto-negotiation at this time). All EtherJet PC Card device drivers default to half duplex operation and accept optional parameters to specify half or full duplex operation, or auto- negotiation for full/half duplex operation. If you configure the adapter to auto-negotiate for full/half duplex operation and attach to a full duplex switch that does not support auto-negotiation the adapter may select half duplex operation, causing incorrect operation on the full duplex network. NOTE: The EtherJet PC Card conforms to IEEE Draft specification "IEEE Auto- Negotiate Link Signaling Configuration Algorithm, Version 1.0, March 15, 1994". 1.7 IBM LAN CLIENT INFORMATION _______________________________ See the file LCREAD.ME on EtherJet PC Card disk 2 for information about IBM LAN Client. 1.8 INSTALLATION AND CONFIGURATION OF NOVELL CLIENT 32 FOR WINDOWS 95 ______________________________________________________________________ Novell Client 32 is now supported by the 32-bit ODI driver, IBMEXNWS.LAN in the Windows 95 environment. This support was not available when the EtherJet PC Card User's Guide was published so configuration and installation of Novell Client 32 on Windows 95 is included here. Please refer to the appropriate section to install or con- figure the EtherJet PC Card: 3 o Installation of the EtherJet PC Card AFTER Novell Client 32 for Windows 95 o Installation of the EtherJet PC Card BEFORE Novell Client 32 for Windows 95 has been installed o Configuration of the EtherJet PC Card being used for Novell Client 32 for Windows 95 logon 1.8.1 INSTALLATION OF THE ETHERJET PC CARD AFTER NOVELL CLIENT 32 FOR WINDOWS 95 This procedure should be followed when installing the EtherJet PC Card after Client 32 for Windows 95 has been installed. 1. When the EtherJet PC Card is inserted, Windows 95 will recognize that a new adapter has been installed. Select "Driver from disk provided by manufacturer" and click "OK". 2. When the "Install from disk" panel is displayed insert the EtherJet PC Card disk 1 and type "a:\netware" in the space provided. Click "OK". 3. Follow any instructions until the Novell Client 32 for Windows 95 has finished installing the adapter. 4. Reboot the computer for the changes to take effect. 1.8.2 INSTALLATION OF THE ETHERJET PC CARD BEFORE NOVELL CLIENT 32 FOR WINDOWS 95 HAS BEEN INSTALLED 1. When the EtherJet PC Card is inserted, Windows 95 will recognize that a new adapter has been installed. Select "Driver from disk provided by manufacturer" and click "OK". 2. When the "Install from disk" panel is displayed insert the EtherJet PC Card disk 1 and type "a:\netware" in the space provided. Click "OK". 3. After the files are copied, double-click on the "My Computer" icon on the desktop. In "My Computer", double-click on the "Control Panel" icon. On the "Control Panel", double-click on the "System" icon. In "System", click on the "Device Manager" tab. 4. Click on the EtherJet PC Card in the "Network adapters" section. There will be a red X over the adapter icon. Click "Remove". Click "OK" to confirm the device removal. When asked whether or not to reboot the com- puter, click "No". Click "Close" 5. Click the Windows 95 "Start" icon and select "Run" from the menu. 6. Enter the location of the Client 32 for Windows 95 setup program in box provided. If installing from diskette, insert the Client 32 for Windows 95 Disk 1--Setup diskette in drive a: and enter a:\setup.exe in the box. 4 If installing from a network driver, consult your LAN administrator for further assistance. Click "OK". 7. Insert diskettes, CD's, and specify the correct path as prompted by the Client 32 install. 8. When Client 32 is finished installing, click on "Customize" to allow the EtherJet PC Card to work with Client 32. You'll be taken to the "Network" panel. 9. On the "Network" panel, click "Add". On "Select Network Component Type", click on "Adapter" and then click on "Add". 10. On "Select Network Adapters, click on "Have Disk". 11. On "Install from disk.." , insert the EtherJet PC Card disk 1 in driver a: and enter "A:\NETWARE" in the box provided. Click "OK" 12. On "Select Network Adapter", click on EtherJet PC Card if it is not already highlighted, and click on "OK". 13. On the "Network" panel, click "OK". 14. Provide additional diskettes as prompted by the setup program. If you get a pop-up indicating that a file cannot be found, ensure that the correct path to the file is specified. 15. When installation is complete you will be given the opportunity to restart the computer. Click on "Yes". 16. When the computer reboots Windows 95 will find the adapter. Click on "Have Disk" and "OK". Insert the EtherJet PC Card disk 1 into drive a: and specify "A:\NETWARE" as the path. Click "OK". 17. Click on "START" and select "SHUTDOWN". Select to reboot the computer. 18. The installation is complete. 1.8.3 CONFIGURATION OF THE ETHERJET PC CARD BEING USED FOR NOVELL CLIENT 32 Configuration can be done any time after Client 32 for Windows 95 and the EtherJet PC Card have been installed. If multiple EtherJet PC Card are installed, you must specify the "Slot" parameter to identify which EtherJet PC Card to use. If multiple EtherJet PC Cards are installed and the slot parameter is not specified a red box will appear as the driver loads asking you to indicate which adapter you would like to use. 1. To configure, double-click on the "My Computer" icon on the desktop. In "My Computer", double-click on the "Control Panel" icon. On the "Control Panel", double-click on the "Network" icon. In "Network", click on the "EtherJet PC Card" and then click on "Properties". Click on the "Advanced" tab and you will be able to set the properties of the adapter. 5 When all properties have been set, click on "OK" to exit the "EtherJet PC Card Properties" panel. Click on "OK" to exit the "Network" panel. 2. You will need to reboot for the new properties to take effect. 1.9 CONNECTIVITY ENABLERS __________________________ Connectivity enablers allow the EtherJet PC Card to be used in a DOS environ- ment without card and socket services or allow use of device drivers that are not card-services aware in a card services environment. If card services is installed, a connectivity enabler is not required for card-services aware device drivers, but CS20JET.EXE must be used for drivers that are not card-services aware. If card services is not installed in the DOS environment, POINTJET.EXE is required to enable the PC Card. Card services or PCMCIA support must be installed in the OS/2 environment to use the PC Card. Here are the supplied card-services aware drivers: Drivers that are card-services aware (no enabler required): ------------------------------------------------------------- ibmexndi.dos - The DOS NDIS2 device driver ibmexnwc.com - The DOS Novell client device driver ibmexndi.os2 - The OS/2 NDIS2 device driver ibmexnwc.os2 - The OS/2 Novell client device driver Here are the supplied drivers that are not card-services aware: Drivers that are not card-services aware (enabler required): ------------------------------------------------------------- ibmexwfw.386 - The DOS NDIS3 Windows for Workgroups driver ibmexnws.lan - The DOS Novell server driver. ibmexpkt.com - The packet driver. NOTE: The Windows 95 driver supports plug and play, and does not need to directly use card and socket services. The Windows NT driver has its card enabled by Windows NT at initialization time. Each enabler has parameters allowing it to be customized to the communication software. The parameters allow the selection of which socket, memory, IO, and interrupt level to use for the card. The default parameters should be sufficient for most users. Connectivity Enabler software is used to configure the PCMCIA socket hardware and the EtherJet PC Card for operation. The enabler must execute before the device driver so the PC card is enabled when the driver loads and looks for 6 the card. For a driver that loads from config.sys, like the NDIS2 driver (ibmexndi.dos) the enabler must be loaded earlier in config.sys than ibmexndi.dos. If the driver loads after config.sys time, like the DOS Novell Client driver IBMEXWNWC.COM, you can execute the enabler at any time before you start the driver. NOTE: After POINTJET.EXE has run, it removes itself from system memory. CS20JET.EXE remains resident in memory once it is loaded. For the adapter to function properly in systems without card services, it is essential that values for IRQ and IO base specified in PROTOCOL.INI and NET.CFG files be the same as values set up by POINTJET.EXE or CS20JET.EXE. Compare the parameters on the POINTJET.EXE line in the config.sys with those in the IBMEXNDI_NIF section of your protocol.ini or the IBMEXNWC section of your net.cfg. 1.9.1 POINT ENABLER (POINTJET.EXE) POINTJET.EXE is an enabler that communicates directly to Intel 82365SL (or equivalent) hardware, a PCMCIA socket controller common in many systems. The enabler should only be used if your system does not have card and socket ser- vices, or if the drivers do not work on the level of card and socket services you have. Since the point enabler supports a variety of Intel socket controller imple- mentations on a wide variety of machines, it uses the most conservative set- tings for the socket (e.g. wait states). Your performance may be slightly better if you are able to use the Card and Socket services designed for your machine in conjunction with either the card services enabler (CS20JET.EXE) or a card-services aware device driver. A 4K window of RAM is used during execution of POINTJET.EXE to examine the CIS of the card in the specified slot to verify that it is a EtherJet PC Card. This memory is returned to the system after POINTJET.EXE execution, but it is imperative that the memory window used by the enabler not be in conflict with anything else in the system. The enabler is unable to detect memory or IRQ (interrupt) conflicts. 1.9.1.1 POINTJET.EXE syntax NOTE: Resources specified on the POINTJET command line must not be in use by other system components or improper operation may occur. POINTJET Syntax: 7 DEVICE=\path\POINTJET.EXE SA/SB/SC/SD/RA/RB/RC/RD IRQ=X SRAM=xxxx IOBASE=xxx SA/SB/SC/SD/RA/RB/RC/RD - Socket number. SA, SB, SC, SD support four sockets on the first controller, and RA, RB RC, and RD support four sockets on the second controller. IRQ - Interrupt Level (PCMCIA controller interrupt) SRAM - Shared Ram address XXXX IOBASE - I/O port base address ? - Display parameter help note: x is a hexadecimal number example: DEVICE=C:\POINTJET.EXE SB SRAM=D400 This would configure a EtherJet PC Card for socket B, attribute window at D400 segment. Since IOBASE was not specified the default of 300 is used, and IRQ is set to the default of 3. The default parameters are: SA (Socket A) IRQ=3 (PCMCIA controller interrupt at IRQ 3) SRAM=D000 (Shared RAM at D000 segment) IOBASE=300 (I/O port base address is 300) 1.9.2 CARD SERVICES ENABLER (CS20JET.EXE) CS20JET.EXE is the card services enabler for the EtherJet PC Card. It is used with drivers that are not card-services aware. It is run as a device driver from config.sys or as a DOS executable. Card and socket services for your system must be loaded in order to use the card services enabler. If you do not have card and socket services installed on your computer you should use the point enabler, POINTJET.EXE. 1.9.2.1 CS20JET.EXE Syntax CS20JET Syntax: 8 DEVICE=\path\CS20jet.EXE IO=xxx IR=x SL=x IO - Defines the IO base address of the card. IO is specified as three hexadecimal digits. The enabler allows any value for IO, but the drivers require the value to be on a sixteen-byte boundary in the range of 200 to 360 (inclusive). IR - Interrupt Level specified as a single hex digit. SL - Socket containing the PC Card. SL is specified as a number between 1 and 8. The first physical socket on the computer is 1. note: x is a hexadecimal number example: DEVICE=C:\CS20JET.EXE IO=300 IR=5 SL=1 Each instance of CS20JET.EXE enables one EtherJet PC Card. If you want to enable more than one PC Card you must load or execute a copy of CS20JET.EXE for each PC Card and specify a unique SL and IO parameter for each card. If no parameters are specified, the PC Card can be enabled in any socket and the I/O base address and interrupt are determined by Card Services. It is recommended that you do not specify the IO or IR parameters unless you want to use a specific resource. If the Card Services enabler encounters problems such as not being able to acquire a resource, four alternating tones will sound. If the PC Card is in the slot when the card services enabler is loaded, error messages will also be displayed in the case of errors. If the card services enabler successfully enables the PC Card, two tones will sound. If the PC Card is in the socket when the enabler is loaded and the PC Card is enabled successfully, you will also see a message indicating the card was enabled successfully. If card services is installed in your computer, you should use the built in card services function of IBMEXNWC.COM, but if you decide to use the card services enabler with IBMEXNWC.COM you must specify "enable nopcmcia" in your NET.CFG. 1.10 SOME NOTES ON NETWARE DEVICE DRIVERS __________________________________________ 9 1.10.1 SETTING DUPLEX MODE FUNCTION All Novell device drivers default to half-duplex operation. Please refer to the "Important Information about auto-negotiation" section of this file for more information on auto-negotiation. To change the duplex mode of the DOS and OS/2 client drivers place a DUPLEXMODE line in the net.cfg: For example, LINK DRIVER IBMEXNWC NODE ADDRESS 020000000001 DUPLEXMODE FDX ;Use DUPLEXMODE HDX for half-duplex (default if no DUPLEXMODE is ;specified) or DUPLEXMODE AUTO if you want to auto-negotiate and you ;are attached to an auto-negotiating switch. To change the duplex operation of the Netware server driver, place a DUPLEXMODE=FDX, DUPLEXMODE=HDX (default if no DUPLEXMODE parameter is speci- fied), or DUPLEXMODE=AUTO on the LOAD device driver input line. DUPLEXMODE and its value MUST be capitalized. For example, LOAD IBMEXNWS DUPLEXMODE=FDX NAME=IBMEXNWS_1_E82 FRAME=Ethernet_802.2 1.10.2 NETWARE 16-BIT DOS CLIENT, IBMEXNWC.COM This driver is Novell certified for half and full duplex operation. See the file NET.SMP in the \DOS directory of the device driver diskette for information on net.cfg parameters. As noted in NET.SMP, if you use the point enabler or card services enabler to enable the PC Card you MUST place ENABLE NOPCMCIA in the LINK DRIVER IBMEXNWC section of the net.cfg. If card services is installed on your computer, you should not use the card services enabler with IBMEXNWC.COM since IBMEXNWC.COM has built-in card services function. 1.10.3 NETWARE OS/2 CLIENT, IBMEXNWC.OS2 This driver is Novell certified for half duplex operation. See the file NET.SMP in the \OS2 directory of the device driver diskette for information on net.cfg parameters. As noted in net.smp, a NODE ADDRESS is REQUIRED in the LINK DRIVER IBMEXNWC section of the net.cfg. The IBMEXNWC.OS2 driver supports only one EtherJet PC Card. 10 1.10.4 NETWARE SERVER DRIVER, IBMEXNWS.LAN The NetWare server driver is not card-services aware so you must use the point enabler, POINTJET.EXE, or the card services enabler, CS20JET.EXE, to enable the PC Card before loading IBMEXNWS.LAN. The NetWare installation tool (INSTALL.NLM) may include extraneous parameters on the LOAD command for the IBMEXNWS.LAN driver. You might see messages such as "Unneeded parameter XXXXX ignored" when the driver is loaded. These mes- sages do not indicate a problem. To stop getting the error messages, edit the AUTOEXEC.NCF and remove the parameters from the LOAD command that are indicated in the message. For example, INSTALL.NLM will generate a line in AUTOEXEC.NCF which looks like: LOAD IBMEXNWS PORT=300 INT=3 NAME=IBMEXNWS_1_E82 FRAME=Ethernet_802.2 This should become LOAD IBMEXNWS NAME=IBMEXNWS_1_E82 FRAME=Ethernet_802.2 NOTE: If you are using an IBM ThinkPad 365xx you may need to use an I/O address of 300. The I/O address parameter must be specified as IOBASE=300 if using POINTJET.EXE or IO=300 if using CS20JET.EXE. 1.11 PACKET DRIVER INSTALLATION PROCEDURE __________________________________________ The packet driver is not card-services aware, so it must be used with an enabler, either POINTJET.EXE or CS20JET.EXE. Tailor the following example to fit your needs: o Make a subdirectory on your hard drive, such as "packet" to store your files: md c:\packet o Copy the appropriate enabler from the EtherJet PC Card disk 1 to your newly created subdirectory: - If you have card and socket services loaded and want to use the card services enabler: copy a:\CS20JET.EXE c:\packet - If you plan to use the point enabler, copy these files: copy a:\pointjet.exe c:\packet copy a:\jet.msg c:\packet o Now copy the packet driver to your hard drive: copy a:\packet\ibmexpkt.com c:\packet 11 o Now create a c:\packet\startnet.bat to start your packet driver. If you plan to point enable your card, include the following lines in your file: pointjet sa iobase=300 irq=3 sram=d000 ibmexpkt 0x60 Note: You must ensure the parameters on the pointjet command line do not conflict with anything else in your system. o If you plan to use the card services enabler, make your c:\packet\startnet.bat look like this: cs20jet ibmexpkt 0x60 If you need to specify parameters on the CS20JET command line add them to the example. If you load more than one card and packet driver you need to specify the IO address on each copy of ibmexpkt you load (there is a later section on loading multiple drivers). o You should now be ready to start. If your EtherJet PC Card is not inserted, power off your machine, insert the card (if you are point enabled, be sure it is the slot specified on the pointjet command line) and turn on your system. After it has initialized switch to the packet subdirectory and invoke your startnet bat file. o An example STOPNET.BAT file that would work with both enabled environ- ments would look like this: ibmexpkt -u 0x60 If you have questions see the file README.TXT in the PACKET subdirectory on the EtherJet PC Card disk 1. 1.12 USING MULTIPLE ETHERJET PC CARDS IN THE SAME MACHINE. ___________________________________________________________ Instructions for supporting multiple cards vary for each driver type and environment. 1.12.1 DOS NDIS2 AND NOVELL CLIENT ENVIRONMENTS If you want to use multiple adapters with an enabler you must follow the instructions in this section. If you are using your card in a card services environment you may be able to use multiple cards without extra setup but you could get unpredictable results if your cards are connected to different physical networks, i.e. specific network software may connect to a different card (and possibly physical network) each time it initializes. 12 1.12.1.1 Using Card and Socket Services If you use your network driver with card and socket services (without POINTJET.EXE or CS20JET.EXE) then the best way to use multiple cards is to specify the "SLOT=x" parameter for each driver instance in your PROTOCOL.INI or NET.CFG file. Most network operating systems have a way to set configura- tion values for adapters - otherwise you have to manually edit your network configuration file manually. 1.12.1.2 Using the point enabler. If you point enable your PC cards then each card has an assigned IO address. Specify the assigned IO address in the appropriate network configuration file (PROTOCOL.INI or NET.CFG) for each driver instance. 1.12.1.3 Using the card services enabler If you want to use the card services enabler with multiple cards then you must specify the IO=xxx and SL=x parameter for each card, then specify the IO address in your PROTOCOL.INI or NET.CFG file. 1.12.2 OS/2 1.12.2.1 OS/2 NDIS 2 Environment To use multiple cards with the OS/2 NDIS 2 driver, configure each adapter with a unique PCMCIA slot or IO address via MPTS or LAPS. This can be done via the LAPS configuration screen by selecting "Edit" for each EtherJet PC Card in the current configuration and filling in either the "I/O Port Base Address" field with a unique address for each card, or updating the "PCMCIA Slot number" field with a unique slot for each card. The "PCMCIA Slot number" is the recommended method - this ties a specific protocol to a specific card, and therefore to a specific network connection. If I/O addresses are specified, they could be unavailable, or assigned to different cards each time you initialize. You may need to experiment with one card at a time to find out how your spe- cific computer assigns slots - that is a function of the computer implementa- tion and the supporting card and socket services. Slot numbering should remain constant from initialization to initialization. If you use multiple cards without specifying slot or IO address you may receive message XND0030, indicating no cards were found. 1.12.2.2 OS/2 Novell Environment The OS/2 Novell driver (IBMEXNWC.OS2) only supports one card at this time. 13 1.12.3 NOVELL SERVER ENVIRONMENTS You must use an enabler with the Novell server driver. Enable each card, specifying the IO address on the POINTJET or SL (slot) on the CS20JET command line. When you start each copy of the server driver identify the correct PC Card as follows: o Using CS20JET, specify the SL, slot number, on the CS20JET command line and use the specified SL with the SLOT parameter on the driver LOAD command. o Using POINTJET, specify the IO address on the POINTJET command line and use the specified IO address with the PORT parameter on the driver LOAD command. 1.12.4 WINDOWS FOR WORKGROUPS - NDIS3 To use multiple cards in Windows for Workgroups running with NDIS3 drivers, you must specify the IO address in the configuration for each network adapter. If you use the point enabler (POINTJET.EXE) then use the IO value specified in the command line. If you use the card services enabler (CS20JET.EXE) you must specify the IO=xxx parameter on the CS20JET command line, and include that value in the configuration for the adapter. You should also specify the SL=x on the CS20JET.EXE command line to complete the link between network software, to specific card to specific physical network. 1.12.5 PACKET DRIVER To use multiple adapters with the packet driver you must use an enabler (POINTJET.EXE or CS20JET.EXE) to enable each card at a unique interrupt and IO base address. After the cards are enabled, invoke the packet driver for each card, passing the IO base address used on the enabler command line to the packet driver (IBMEXPKT.COM). Since the enabler can be run as a DOS exe- cutable, this can all be done from a DOS bat file. Here is an example of a 'startnet.bat' you could use to start two cards with packet drivers using the point enabler: STARTNET.BAT example: . . pointjet sa iobase=300 irq=5 pointjet sb iobase=320 irq=3 ibmexpkt 0x60 0x300 ibmexpkt 0x61 0x320 . . Since the STARNET.BAT in the example runs POINTJET.EXE as a DOS executable, be sure the default memory area used by the enabler (D000) does not conflict with anything else. If it does, add the "SRAM=xxxx" parameter to each pointjet line, and specify a value for "xxxx" that does not conflict. 14 You can also use the card services enabler instead of the point enabler by just replacing the pointjet lines in the above example with the corresponding CS20JET command line. You need to specify the IO=300 and IO=320 on the CS20JET command lines so the packet drivers know which adapter to use. You also must be sure the IRQ values you choose are not used by anything else in your system. Here is an example of a STOPNET.BAT you could use with the above STARTNET.BAT: STOPNET.BAT example: . . ibmexpkt -u 0x60 ibmexpkt -u 0x61 . . 1.12.6 WINDOWS 95 To use multiple PC Cards with Windows 95, just follow the installation instructions for the first card and then plug in the extra cards. 1.12.7 WINDOWS NT At the time of this writing, Windows NT does not support multiple PC Cards of the same type in one machine. 1.13 SYSTEM PITFALLS _____________________ Some of the new systems that support PCMCIA 2.0 I/O cards have features that the user must be aware of when using the EtherJet PC Card. For the PCMCIA socket to receive power, many computers must have the power to the PCMCIA socket enabled. This is typically done with a setup utility that comes with the computer. If you are using Card and Socket Services, make sure your PCMCIA socket is enabled. If your socket is not enabled, Socket Services will not load and will not display an error message; Card Services will not load, but will display an error message that Socket Services is not present. 15 1.13.1 SUPER CLIENT DRIVERS Many vendors are providing customers with Super Client drivers. This is a driver that will enable many different PCMCIA cards. PC-DOS 6.1 includes one called PCMSCD.EXE, for example. They are best used for modems and other cards that do not have a Card Services client driver of their own. The EtherJet PC Card client drivers have been written to take advantage of Card Services and a super client driver could possibly interfere with operation of the card. The adapter DOS drivers use a feature called "Request Exclusive". This allows the DOS drivers to coexist with a super client driver. Bas- ically, the drivers take control away from the super client driver when the driver configures the card. 1.13.2 USING PHOENIX CARD AND SOCKET SERVICES ON IBM THINKPADS Some versions of the IBM DOS Operating system are shipped with Phoenix card and socket services, or your IBM Thinkpad may have Phoenix card and socket services installed. The EtherJet PC Card may not operate correctly in some models of the IBM Thinkpad if you use Phoenix Card and Socket services. If you are using your EtherJet PC Card in an IBM Thinkpad it is best to use the IBM card and socket services supplied with your machine. You can get the latest Thinkpad files via FTP at ftp.pc.ibm.com or from http://www.pc.ibm.com/listfiles.html . 1.13.3 USING PC CARDS IN AN IBM DOCK II You might experience problems if you operate your EtherJet PC Card in either of the extra two slots of an IBM Dock II. There is a timing fix available from IBM for the Dock II that you can obtain. Contact your service represen- tative, or if you have ftp or web access you can search for the files your- self on the IBM PC Company web page or ftp site: Web site: http://www.pc.ibm.com ftp site: ftp://ftp.pc.ibm.com/pub/pccbbs/mobiles At the time this file was written, the files to retrieve were: yptf012.exe - for DOS / Windows 95 yptf022.exe - for OS/2 yptf032.exe - for Windows NT. 1.13.4 ADAPTER NOT WORKING WHEN USING THE POINT ENABLER (POINTJET.EXE) Usually when drivers do not work with a point enabler it is due to one of the following reasons: 1. There is a memory conflict. The point enabler uses a 4k memory window (only during its execution) that can conflict with memory managers, or DOS's use of upper memory. Use the SRAM=xxxx parameter to move this value around (to any area from A000-FFFF, try values from C000, C100 16 through E800 for example). Some values may hang your system. This is one reason it is better to use card and socket services. Also experiment with other config.sys settings that affect loading programs or data in the 640k to 1meg memory range (dos=high, or DEVICEHIGH type of state- ments). 2. There is an IRQ or interrupt conflict. If the IRQ you specify is in use by something else on your computer, the network will not work. If this happens, usually the adapter appears to initialize correctly but the network application does not work (cannot connect to the server). When there is an IRQ conflict the adapter can probably transmit, but not receive data. 3. Parameter values from POINTJET.EXE, either the ones you specify or default values for parameters you do not specify, may not exactly match values in your network configuration file (net.cfg or protocol.ini). If a single card is being used, the DOS drivers can find enabled cards without IO, or IRQ parameters in NET.CFG or protocol.ini. 4. The card must be inserted, the cable attached to the card, and the cable attached to active media before starting the enabler or network driver. 1.13.5 WARP MPTS MAY DETECT ETHERJET PC CARD AS ETHERJET ISA ADAPTER. Newer versions of IBM OS/2 Warp MPTS have network adapter detection and driver installation. It is possible that some versions of MPTS could mistakenly detect your EtherJet PC Card adapter as an IBM EtherJet ISA adapter. If this happens, do not select the listed device driver for the EtherJet ISA card. Instead, complete the installation of the EtherJet PC Card OS/2 card and choose it as the adapter you want to run. At the time of this writing, the latest fix level of MPTS had this problem fixed. 1.13.6 WINDOWS FOR WORKGROUPS 1.13.6.1 Switching between NDIS2 and NDIS3 drivers. Normally you can enter and exit Windows for Workgroups without rebooting your system, but if you re-configure your network and switch between the EtherJet PC Card NDIS2 and NDIS3 driver you must re-boot your system before the network will work again. 17 1.13.6.2 Using the NDIS2 driver without the card services enabler. If you have card services installed when you invoke the EtherJet PC Card LANAID installation program, and you install an NDIS2 or NDIS3 driver, the installation program will install the card services enabler (CS20JET.EXE) in your config.sys file. Since the NDIS2 driver is card-services aware, you can remove the CS20JET.EXE from your config.sys (unless it has parameters on the command line that you need to keep, like slot, IO address or interrupt level). 1.13.7 MEMORY CONFLICTS AND MEMORY MANAGERS The EtherJet PC Card does not use shared RAM for normal operation, but the point enabler requires a 4k memory window when it executes. Generally, card services also requires some memory for PC cards so if you use the DOS drivers with card services, or use the card services enabler (CS20JET.EXE) some memory is normally required for card initialization. The DOS utility EMM386.EXE, if used, may need memory excluded for card and socket services. If the point enabler (POINTJET.EXE) is used, the memory it uses (default segment D000, can be altered via SRAM parameter of POINTJET) must also not be in conflict with anything else in your system. Here is an example invocation of EMM386.EXE in your CONFIG.SYS: DEVICE=C:\DOS\EMM386.EXE X=D000-D3FF This would exclude the memory areas necessary for standard default operation. When using utilities like QEMM or 386MAX, it is important to exclude the memory used by these utilities from the memory used by the PC Card. The operation of the PC Card will be affected. If you are unsure of the memory manager syntax, refer to the documentation for the memory manager or DOS manuals. 1.13.8 MISCELLANEOUS o For successful initialization of EtherJet PC Card hardware and drivers, you must have the card completely inserted in your machine, the cable plugged into your card, and the cable attached to an active network. o The EtherJet PC Card card is designed so that detaching the cable from the PC card has the same effect as unplugging the card. Without the cable attached to the PC card it will look like there is no card inserted in the slot (the installation programs, enablers and drivers will be unable to detect the card's presence). o If you are using the point enabler it is not advisable to insert or remove the card until turning off the power on your system. 18 o Using card and socket services generally allows you to insert and remove cards while your system is powered on. Although card-services aware drivers can re-initialize a card that has been removed and re-inserted, some network operating systems may not support this. If you used the card services enabler, CS20JET.EXE, to enable the PC Card you are not using card services function in the device driver so you should not remove the PC Card until the network device driver is unloaded or the operating system is shutdown. o Notebook computers typically use Card and Socket Services. If you do not want to use Card and Socket Services, POINTJET.EXE can be used. Unpre- dictable results may occur if you use POINTJET.EXE while card services is loaded. o If you plan to use DOS LAN Requester and your machine has MS-DOS on it, you may run into a problem where the DOS LAN Requester installation indi- cates you have an incorrect DOS version. If you have this problem, use the SETVER command and driver to alter the version of DOS reported to CIP_MAIN.EXE. Change the version of DOS to 5.00 for this program and you should be able to finish the installation. See your MS-DOS manual for implementation details. This is not a problem with PC-DOS. o The EtherJet PC Card driver does not currently support OS/2 SMP or Warp SMP (multiple processor) machines. Single processor OS/2 and OS/2 Warp are supported. o On the IBM 750P Thinkpad there may be a conflict between the Pen inter- rupt and the interrupt for the EtherJet PC Card. There are several ways to solve this problem. If you are using Card Services, please get the latest PCMCIA Features Diskette. This should be Version 1.20 or above. You can determine or change the pen interrupt by running PS2. o If you have an IBM PS/2 E and you are installing the EtherJet PC Card under a Card Services environment, you will likely need to upgrade your Card and Socket Services. You will need the latest PCMCIA features diskette, level 1.20 or above. The features diskette for the IBM Thinkpad 350 or 75X can be used on the PS/2 E. Older versions of Card and Socket Services may hang your computer when you start your network. o The IBM Port Replicator and Dock II have two PCMCIA sockets. If you are using a point enabler, they have the following assignments. You must use the RA/RB parameter with the POINTJET.EXE enabler. POINTJET Typical Parameter SLOT number Computer Top Socket SA 1 Computer Bottom Socket SB 2 Additional Top Socket RA 3 Additional Bottom Socket RB 4 o Some additional machines and their pointjet assignments: 19 Top Bottom Slot Slot +-------------------------+ Compaq Contura 410CX SC SA o If card and socket services is installed, you should be able to view the status of the EtherJet PC Card with a utility such as EZPLAY or Card Ser- vices director. If the EtherJet PC Card is not detected by these utili- ties there is most likely a problem with your card and socket services installation. o If you are using OS/2 on the ThinkPad 365xx and card services is identi- fying the EtherJet PC Card as a memory card, ensure that if the BIOS is dated on or after 2/2/96 that the RESERVE.SYS line in your config.sys is as follows: BASEDEV=RESERVE.SYS /MEM:C600,2000 If your BIOS is dated earlier than 2/2/96 the line should read BASEDEV=RESERVE.SYS /MEM:CA00,6000 o You may not be able to mix EtherJet PC Card and IBM EtherJet ISA adapters in the same computer. 20