. . IBM 10/100 EtherJet CardBus Ready Port Adapter . IBM 10/100 EtherJet CardBus Adapter . Software Release Version 3.14 . August 01, 2002 ============================================================================= This package contains a self-extracting ZIP file containing the DOS, OS/2, Windows 3.x, Netware Drivers and Installation files. This package supports the following adapters. Product Name ============ IBM 10/100 EtherJet CardBus Ready Port Adapter IBM 10/100 EtherJet CardBus Adapter Installation Instructions: 1. Download the self-extracting ZIP file EJETCB01.EXE to the drive and directory of your choice. 2. Execute EJETCB01.EXE from a command prompt to unzip the file. A path can be specified after the self-extracting zip file name in order to expand the zip file to a location other than the current directory (example: ejetcb01 x:\ - where x is a drive letter). If a path is not specified, the self-extracting zip file will be unzipped into the current directory. 3. After unzipping the file, refer to the 10/100 EtherJet CardBus Adapter Installation and Planning Guide on the CD-ROM that shipped with your adapter for complete instructions for installing the device driver. If you do not have a copy of the Installation and Planning Guide that shipped with your adapter, you can browse or print an on-line version of it. Visit the IBM web site at http://www.ibm.com/pc/support. View the Technical Documentation for the EtherJet CardBus Adapter. Thank you for purchasing your IBM 10/100 EtherJet CardBus Adapter IBM has done everything to ensure that our adapters are compatible with the widest range of portable PCs possible. As a company, we are equally committed to customer satisfaction and timely response to the needs and concerns of our customers. Documentation for using the IBM 10/100 EtherJet CardBus Adapter in DOS, Windows 3.X, OS/2 or using the 32-bit ODI driver please see the HELPDOCS.HLP file provided with this package. IBM's EtherJet CardBus Adapter is designed to work with portable PC's which include a CardBus PC Card slot. CardBus is the next generation PC Card (PCMCIA) standard. It enables portable PC's to incorporate a PCI based 32-bit bus, which dramatically improves performance. The EtherJet CardBus Adapter incorporates the latest in LAN technology, including advanced power management capabilities. For the latest information on all IBM products, visit The IBM Website at: http://www.ibm.com/pc/support CONTENTS ======== 1) IBM 10/100 EtherJet CardBus Adapter Characteristics 2) Release Notes/Known Limitations 3) CardBus Equipped Portable Computers 4) Machine Specific Notes 5) IBM Product Support 1) IBM 10/100 EtherJet CardBus Adapter Characteristics ========================================================= This release of the IBM 10/100 EtherJet CardBus Adapter has the following characteristics: -10/100Mbps connectivity - Allows portable PCs equipped with a CardBus slot to connect to 100Base-TX Ethernet networks to take advantage of higher network bandwidth. -NWay Auto-negotiation of 10 or 100Mbps Ethernet connection rate - Upon initialization, the adapter will automatically adopt the speed of the network port to which it is attached, allowing it to be used seamlessly on either 10Mbps (10Base-T) or 100Mbps (100Base-TX) network segments. -Support for Windows NT 4.0 Card and Socket Services from SystemSoft, Phoenix, Softex and Award. -Full suite of network driver support - Allows 10Mbps or 100Mbps connection across a wide range of operating systems and networks. Native 32-bit NDIS3 and NDIS4 driver support for Windows 95 and Windows NT 4.0 is included. An NDIS5 driver is included for use with Windows 98 and Windows 2000 and Windows XP. -Advanced power management capabilities including Wake on LAN, Magic Packet, and support for the ACPI and CardBus Power Management Specifications. The operating system must be capable of supporting these features. Support was not included in Windows 98 Second Edition or Windows 2000 for CardBus or PC Card adapters. Partial support is included in Windows XP for CardBus adapters. -A LAN connection diagnostic program for use under any Microsoft Windows operating system. -SNMP network management agent included - Allows a portable PC to be managed using SNMP-based network management software. 2) RELEASE NOTES/KNOWN LIMITATIONS =============================== Version 3.14 Release Notes -------------------------- -Support for Windows XP. -Additional support for newer versions of Softex Card Executive. -Corrected issue with multiple network destinations and routes under Windows 2000. -Improved OS2 support. -New keyword - LINECONFIGURATION - for OS2 and NDIS2 driver, replaces LINEMODE and LINESPEED. -New keyword - AdapterIndividualAddress - for manually entering MAC addresses with the OS2 and NDIS2 driver. -New keyword - NODEADDRESS - for manually entering MAC addresses with the OS2 and NDIS2 driver. -Corrected error seen on certain machines while using DOS imaging software. -Support for Wake-On-LAN (WOL) under Windows XP -NWay auto negotiation changes ----------------------------- NWay is an industry-standard way for hubs, switches, and network cards to automatically determine each other's speed and duplex capabilities, and set each device's communication settings to the fastest mutually supported speed. In earlier driver releases, as is normal in the industry, forcing the speed and duplex settings completely disables auto negotiation. This was done because the forced settings were meant as a backup when connecting to older non- NWay devices. When forced settings are used when connecting to other NWay devices, (perhaps to restrict bandwidth), the other device must also have its speed and duplex settings forced as it cannot reliably sense the settings without negotiation messages. In this driver release NWay negotiation is active by default whether or not the settings are forced. Other NWay devices, even in auto mode, will be able to determine your card's settings and negotiate to match them. In cases where the standard behavior is not successful, some early NWay devices and non-NWay devices do not always respond well to negotiation signals. A new keyword, Line Negotiation, can eliminate the negotiation messages when the settings are forced. The forced + no negotiation messages settings also allow immediate link if required by any special circumstances. The keywords and their settings are as follows: Keyword Settings Behavior ------- -------- --------- Line Configuration Auto (default) Full NWay negotiation, 100 Mbps/Full Duplex Line Negotiation keyword 100 Mbps/Half Duplex ignored. 10 Mbps/Full Duplex 10 Mbps/Half Duplex Line Negotiation On (default) NWay messaging sent in all modes Off NWay messaging disabled if Line Configuration is forced Automatic NDIS Driver Selection ------------------------------- This driver release now supports automatic NDIS version selection for installs under Windows 9x and Windows 2000. For installs under Windows 9X or Windows 2000, direct the install to the root of the CD (or of floppy disk 1) when the drivers are requested. The network property page tab of the EtherJet CardBus Adapter has a new entry "NdisVersion". This entry contains the following: Under Windows 95OSR2: AutoSelect, NDIS3, NDIS4 Windows 98: AutoSelect, NDIS3, NDIS4, NDIS5 Windows 98SE: AutoSelect, NDIS3, NDIS4, NDIS5 Windows 2000: "NdisVersion" does not exist and NDIS5 is the Windows XP default driver. The NDIS Switcher is not used with Windows 2000 or Windows XP. AutoSelect (the default) will choose the highest NDIS version supported by the OS. The user can also manually switch between the different supported versions of NDIS by going to NdisVersion in the network properties of the adapter and selecting the desired driver. Only drivers supported by the particular OS will be shown. NOTE: NDIS switching is not supported in Windows NT 4.0. The NDIS4 driver will be installed by default by pointing to the root of the CD or of Disk 1 if diskettes are created. The NDIS3 driver may be installed by pointing to the \NDIS3 subdirectory. Version 2.61 Release Notes -------------------------- - Added Digitally signed Windows 98 driver .CAT file NETIBMN5.CAT. This file is included in the \NDIS5 directory on the adapter CD-ROM. Version 2.60 Release Notes -------------------------- - Changed Memory Default to 0x55b84000 to correct the NT 4.0 resource conflict when certain notebooks had more than 96MB of RAM memory the adapter would not install correctly. - Added Auto Polarity correction, certain 10/100 switches (generally those using Broadcom transceivers) implement automatic correction for polarity reversed cables that is not completely compatible with the same correction provided by the EtherJet CardBus Ready Port adapter. If the network speed is forced to 10Mbps, severe throughput problems may be experienced. To resolve this problem, a new Auto Polarity keyword in the adapters advanced properties has been added. If needed, the default setting of ON (meaning that the card will compensate for reversed cables) can be set to OFF to disable polarity correction. This will restore normal throughput. - Added O2Micro bridge support for I-Series 1400/1500 ThinkPad performance problem to all drivers. - Added Ricoh bridge support to all drivers. - Updated IBMCNDIS.EXE driver for PowerQuest Ghost Imaging software. - Added SETUP.EXE to install the Diagnostics utility and Readme. A program folder called IBM Utilities is created. - TCP/IP Routing This release contains a resolution for TCP/IP problems that occur when the same network is accessed via a LAN connection and then subsequently via a remote dial-up connection in Windows 95/98. Typically, when the computer is connected to the network via the LAN, routing tables are constructed that direct packets intended for the network to the LAN interface. If the computer is then used remotely and an attempt is made to connect to the same network via dial-up networking, these packets may not be routed to the dial-up interface because the presence of the active LAN interface results in the system's continuing to route packets to it instead. In such instances, the simplest solution is to remove the LAN interface from the computer, or to use a network disabled profile. If neither of these solutions is satisfactory, a third option is now available. The drivers included with this release now support a new configuration keyword named "DynamicLinkDetect" to overcome this difficulty. The value of this keyword (ON or OFF) can be set by going to Control Panel-->Network--->EtherJet CardBus Adapter Properties--->Advanced. The default value is ON. The activity governed by this keyword operates as follows: ON - The Ethernet interface is always active once the driver initializes the adapter. An Ethernet cable doesn’t need to be connected to the port at boot time for the network side of the adapter to initialize. If the cable is plugged in later, or unplugged and then re-connected; the adapter will dynamically detect the presence of the link and connect to the LAN. This is the setting recommended unless the symptoms described above are encountered. OFF - the driver will only initialize the Ethernet interface if an active connection to the network is present at boot time. If the presence of an active link is not detected, the Ethernet portion of the card will shut down. As a result the OS will "assume" that the interface is not present, and no packets will be routed to it. As a result, the IP routing trouble discussed previously should be eliminated. -Initialization Delay Certain switches and routers are unable to immediately forward network traffic when a network adapter first establishes link to one of their ports due to initialization delays (generally while routing tables are being updated). This problem is most commonly seen when the network adapter is connected directly to ports on the switch. This may cause an initial DHCP request to fail or prevent login to a server. The adapter by default (when used under some operating systems) will have almost no delay between link and the initial network request. A new keyword, Initialization Delay, has been added to the adapter's advanced properties which will prevent forwarding of network requests for a user-selectable period of time. Delays can be added ranging from one to sixty seconds. In most cases adding a delay in the one to three second range will be sufficient to resolve the problem. Supported Environments ---------------------- The version number for the entire release of this driver set is version 3.14. The following environments are supported. Please note that each driver has its own version number. Driver Name Description ----------- ----------- IBMC.SYS NDIS3 Driver for Microsoft Windows 95 IBMCN4.SYS NDIS4 Driver for Microsoft Windows 95OSR2, Windows 98 and NT 4.0 IBMCN5.SYS NDIS5 Driver for Microsoft Windows 98 and Windows 2000, and Windows XP IBMCNT.SYS NDIS3 Driver for Use with NT 4.0 Card and Socket Services supporting PCMCIA Proposal 187, specifically Phoenix Card Executive and Softex PC Card Controller. IBMCODI.COM 16-bit ODI driver for DOS and Windows 3.X IBMC.LAN 32-bit ODI Client/Server Driver for DOS, Windows 3.X and Windows 95 IBMCNDIS.EXE NDIS2 Driver for DOS and Windows 3.X IBMCODI.OS2 ODI Driver for OS/2 IBMCNDIS.OS2 NDIS2 Driver for OS/2 IBMCPD.COM Packet Driver IBMCTEST.EXE DOS Diagnostic Test Program EJETDIAG.EXE Windows Diagnostic Test Program Known Limitations ----------------- -Wake-On-LAN (WOL) under Windows XP during a Hibernate session will not fully restore, a reboot is required. -Packet Priority is set to off under Windows XP, the user configurable keyword under Advanced Network Properties does not apply. -Windows 98SE installation may hang on 1st reboot if installed from hot insert. This issue does occur if these FOUR things are TRUE: a) The laptop did not ship with 98SE b) There is already an adapter in the network properties c) The new adapter is not recognized which causes the new hardware dialog to come up d) You are prompted to reboot when install is complete and you select yes Workarounds: Before Lockup: 1) Select NO when prompted for reboot and wait until the hour glass goes away before rebooting 2) or Insert Card before power up, and then install as normal After Lockup: 1) Reboot without card. Uninstall card, reboot, then hot insert card and install drivers. 2) or Reinstall IP protocol and reboot -Support for O2Micro chipsets under NT 4.0 requires that the laptop BIOS initialize the CardBus controller as a PCI device and set up PCI routing. -In order to connect to a 100Base-TX Ethernet network, a Category 5 unshielded twisted pair (UTP) network cable terminating in a male RJ-45 connector must be connected to a 100Mbps hub or switch. Check with your LAN Administrator if you are not certain of your network speed and infrastructure. -The IBM 10/100 EtherJet CardBus Adapter is designed to connect to a 100Base-TX network. They do not support 100VG-AnyLAN or 100BaseT4 networks. -When running the LAN Requester install, the IBMCNDIS.EXE file does not get copied to the NET directory. The file needs to be manually copied from the CD-ROM to the NET directory on the user's hard drive. -When running the Lantastic* 7.0 install, the IBMCNDIS.EXE file does not get copied to the LANTASTI directory. The file needs to be manually copied from the CD-ROM to the LANTASTI directory on the users hard drive. -The 32-bit ODI driver (IBMC.LAN) supports promiscuous mode. There is one limitation in its support. Fragment errors are captured, but they are classified, counted and reported as undersized errors. Therefore, the total count for undersized errors includes the total of undersized and fragment errors. -When using Award CardWare for NT 4.0 with IBMC.SYS or IBMCN4.SYS, the driver will co-exist with Award's software but not hot swap or hot insert unless Award version 6.0.015 or later is used. -When using the Packet Driver with the Intel(R) 10/100 Stackable hub, network connections may be lost at 10Mbps. -When attempting to use the IBM 10/100 EtherJet CardBus Adapter with a second PC Card 16-bit adapter e.g. modems, flash cards, ATA cards) in the other slot, it may be necessary to boot up with IBM 10/100 EtherJet CardBus Adapter first then hot- insert the second adapter. -If loading IBMCODI.COM in a DOS environment from the command line, you must shut down the machine to change the IRQ. -The DOS Line Configuration keyword values are as follows: IBMCNDIS.EXE/IBMCNDIS.OS2 H10 F10 H100 F100 - for 10/100Mbps and Half or Full Duplex IBMCODI.COM 10H 10F 100H 100F - for 10/100Mbps and Half or Full Duplex -The RXBUFFERSIZE values of 7, 8, 19 and 26-29 are not supported in the DOS drivers. -The online documentation for the IBMCNDIS.OS2 is incorrect for the following keywords: CACHE is actually CACHE LINE SIZE and should be used accordingly. LINKDISABLE, NOBURST and NOPREFETCH are no longer supported in this release. LINESPEED and LINEMODE have been replaced with a single keyword, LINECONFIG. Please refer to the DOS Line configuration settings listed above for the NDIS drivers. -The NODEADDRESS keyword must consist of 12 hexadecimal digits. It cannot have the Multicast bit set. So only use digits 2, 6, A, or E as the second digit of each octet. This value must be enclosed in quotation marks. [EXAMPLE: NODEADDRESS="001000000124"] 3) CardBus Equipped Portable Computers =================================== The EtherJet CardBus Adapter requires a portable computer with a CardBus PC Card Slot. Most laptops introduced after January 1997 incorporate CardBus PC Card slots. If you're not sure if your system supports CardBus, contact the manufacturer of your laptop. 4) MACHINE SPECIFIC NOTES ====================== IBM ThinkPad 760ED ------------------ -If using the 32-bit ODI client (IBMC.LAN), interrupt 9 should be used. Machines using O2Micro* CardBus chipsets --------------------------------------- O2Micro controllers cannot be used with CardBus adapters under Windows NT 4.0 unless the BIOS of the laptop initializes the controllers as PCI devices and sets up PCI routing. Several manufacturers have released or are in the process of releasing BIOS updates to provide compatibility with NT 4.0. If you desire to run NT on one of these laptops, contact the manufacturer for more information. Compaq Armada 1580 ------------------ If using the DOS 16-bit drivers, it is necessary to insert the CardBus Adapter in the bottom slot NEC Versa LX and SX ------------------- Support for CardBus cards in these laptops in either NT or DOS requires the use of the following Laptop BIOS versions or later. Note that the reported BIOS version will be 420000 after these updates are installed. Versa LX PII- 2.45.15, 1-27-99 Versa LX MMX- 2.44.15, 1-27-99 Versa SX PII- 2.47.15, 1-27-99 Versa SX MMX- 2.46.15, 1-27-99 Texas Instruments Extensa 650, 660 and 900 ------------------------------------------ If using the DOS 16-bit drivers on the TI Extensa 650, it is necessary to insert the CardBus Adapter in the top slot. If using the DOS 16-bit drivers on the TI Extensa 660 and TI Extensa 900, it is necessary to insert the CardBus Adapter in the bottom slot. Toshiba Satellite Pro 490 ------------------------- On the Satellite Pro 490, it is necessary to set the CardBus Adapter Address mode to Memory mode. To do this, run Control Panel, Network. Highlight the IBM 10/100 EtherJet CardBus Adapter and click on Properties. Go to the Advanced tab. Under Property, highlight Address Mode and change the value from IO to Memory. Click OK. The system will need to reboot for the change to take affect. 5) IBM PRODUCT SUPPORT ======================== The following IBM product support is available: * World Wide Web: - On a Web Browser: 1. Open http://www.ibm.com/pc/support 2. You now have access to all the latest drivers, technical tips, and product information. * IBM product support: - 1-800-772-2227 for IBM HelpCenter - 1-800-565-3344 for HelpPC (Canada) Trademarks ---------- * IBM and ThinkPad are registered trademarks of IBM Corporation. * EtherJet is a trademark of IBM Corporation. * Intel is a registered trademark of Intel Corporation. * Windows is a registered trademark of Microsoft Corporation. Other company, product, and service names may be registered trademarks, trademarks, or service marks of others.