Xircom(R) CARDBUS ETHERNET 10/100+MODEM 56 Adapters Software Release Version 3.14 May 2, 2002 ___________________________________________________________________ Thank you for purchasing your Xircom(R) CardBus Ethernet 10/100+Modem 56 Adapter. Xircom has done everything to ensure 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. The drivers in this software release are compatible with the following Xircom(R) CardBus Ethernet 10/100+Modem 56 Adapters: Product Name Model Number ------------ ------------ CardBus Ethernet 10/100+Modem 56 CBEM56G-100 RealPort CardBus Ethernet 10/100+Modem 56 RBEM56G-100 RealPort2 Cardbus Ethernet 10/100+Modem 56 R2BEM56G-100 For the latest information on all Xircom products, please visit the Intel Website at: www.intel.com Documentation for using the CardBus Ethernet 10/100+Modem 56 in DOS, Microsoft* Windows* 3.X, OS/2*, or using the 32-bit ODI driver can be found in the HELPDOCS.HLP file on the Xircom CD-ROM. DISCLAIMER THE INFORMATION IN THIS DOCUMENT APPLIES TO THE CBEM, RBEM and R2BEM, UNLESS OTHERWISE NOTED. CBEM, RBEM AND R2BEM USE THE EXACT SAME DRIVER SOFTWARE. ALL REFERENCES TO Microsoft Windows* 95 ARE SPECIFIC TO Microsoft Windows* 95OSR2 (VERSION 950B OR LATER), UNLESS OTHERWISE NOTED. CONTENTS -------- 1) Xircom(R) CardBus Ethernet 10/100+Modem 56 Characteristics 2) What's New in the 3.14 Software Release 3) Using CBEM in Microsoft Windows* 95 4) Notes on Card Services 5) Release Notes/Known Limitations 6) Using the CBEM/RBEM/R2BEM in Microsoft Windows* 2000 7) Machine Specific Notes 8) Creating a Disk Install 9) SNMP Agent 10) SCO UNIX Support 11) Linux Support 12) Xircom Technical/Sales Support 1) Xircom(R) CARDBUS ETHERNET 10/100+MODEM 56 CHARACTERISTICS ============================================================== This release of the Xircom(R) CardBus Ethernet 10/100+Modem 56 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. See model descriptions below for additional information. The CardBus Ethernet 10/100+Modem 56 takes advantage of the PCI- based 32-bit bus provided by the CardBus slot. This eliminates the bottleneck of a 16-bit bus, thus providing high-performance 100Mb networking. CBEM includes Xircom's second generation CardBus technology for improved performance and power management. 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. Utilizes 56K modem technology, which allows access to information and e-mail on corporate networks, the Internet, and other online services at speeds up to 56Kbps over standard phone lines. K56 technology enables speeds up to 56Kbps when data is downloaded. Upstream data sent from the user travels at the standard V.34 rate. The modems at both ends of the connection must support 56K protocols (v.90/K56Flex) in order to achieve 56Kbps speeds. Support for using a second PC Card at the same time as the Xircom CardBus adapter in any version of Microsoft Windows* 95 OSR2 or later (CBEM and R2BEM only). See machine specific notes for limitations. Support for using a second PC Card at the same time as the Xircom CardBus adapter in Microsoft Windows* NT4.0 (CBEM and R2BEM only). 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 Microsoft Windows* 95 and Windows* NT4.0 is included. An NDIS5 driver is included for use with Microsoft Windows* 98, Windows* 2000 and Windows* XP. Includes Xircom's Battery save (TM) technology. When the LAN cable is disconnected from the adapter, the CBEM56G-100 automatically puts the LAN circuitry into a low power state. When the LAN cable is reattached, it automatically powers itself back up. 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 Microsoft* Windows* 98 Second Edition or Microsoft Windows* 2000 for CardBus or PC Card adapters. Partial support is included in Microsoft Windows* XP for CardBUs adpaters. Xircom software is included that enhances the ability of Microsoft Windows* 95 OSR2 (950B) and later to support CardBus multifunction devices. Other Xircom(R) software utilities provided in this release include: A Windows LAN diagnostic program. A Windows Modem diagnostic program. A Windows Modem informational and management program. SNMP network management agent included - Allows a portable PC to be managed using SNMP-based network management software. Models available: CBEM56G-100BTX: Supports both 10Base-T and 100Base-TX with a single cable connector. RBEM56G-100BTX: Supports both 10Base-T and 100Base-TX with an integrated RJ45 connector. R2BEM56-100BTX: Supports both 10Base-T and 110Base-TX with an integrated RJ45 connector. 2) WHAT'S NEW IN THE 3.14 SOFTWARE RELEASE ========================================== -Support for Windows* XP -Corrected issue with multiple network destinations and routes under Microsoft Windows* 2000. -Improved OS2 support. -New keyword - LINECONFIGURATION - for OS2 and NDIS2 driver, replaces LINEMODE and LINESPEED. -New keyword - Adapter Individual Address - 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 Microsoft Windows* XP 3) USING CBEM IN Microsoft Windows* 95 ======================================= Using CBEM in Microsoft Windows* 95 versions 950 and 950A --------------------------------------------------------- The software in this release DOES NOT include support for Microsoft Windows* 95 versions 950 and 950A. A separate set of drivers specifically designed for use with Microsoft Windows* 950 and 950A is contained in the download file "XBEM_1B.EXE, which is available from the "Hot Fixes" section on the Intel web site downloads page. Xircom Enhancements for Microsoft Windows* 95 OSR2 (950B) --------------------------------------------------------- Microsoft Windows* 95 version OSR2 (950B) and later support Plug and Play of CardBus devices. However, OSR2 may have problems properly allocating resources to some CardBus multifunction (Ethernet + Modem) devices. CBEM includes software which enhances the ability of Microsoft Windows* 95 OSR2 and later to support CardBus multifunction devices. This support is implemented in the NDIS3/NDIS4 drivers (CBE.SYS/CBEN4.SYS) and CBMFFIX.EXE. CBMFFIX.EXE is a Xircom program that helps Microsoft Windows* 95 OSR2 configure and use CBEM. It is launched automatically at the end of the adapter's installation. The only indication that it has run will be a dialog box telling the user to reboot to complete the installation. On some machines, the program may detect that particular VXD files from Microsoft are out of date. Also, on some computers, it is possible that the files may not be reported as out-of-date, but the adapter may not fully function after installation (for example, the network side may function but the modem will not). If the warning appears or such symptoms are encountered, it may be necessary to obtain more recent versions of these files. The specific files are: CBSS.VXD PCI.VXD PCCARD.VXD Microsoft has made available a program to automatically update these files. Before using this program, it is IMPORTANT TO BACK UP YOUR CURRENT COPIES of these files (normally located in C:\windows\system) to another directory or to a floppy disk. Microsoft's update program does not back up these files and cannot be reversed without manually locating and recopying these files to your machine. This update is available on the Microsoft* Web site. In order to function with Microsoft Windows* 95 OSR2, CBMFFIX places a "forced configuration" onto the slot the card is inserted into. Once this forced configuration is applied, no other card can be inserted into that slot. However, the CBEM adapter can still be removed and reinserted into the same slot while the laptop is running. The adapter should not be installed into the other slot. The forced configuration on the slot can be removed at a later time by running CBMFFIX manually. See the section below titled, "Removing the Forced Configuration." A log of the forced configuration data can be found in the Windows\System directory in a file called CBMF.LOG. This log also contains the VXD file versions currently installed in the system. Removing the Forced Configuration --------------------------------- The forced configuration on the slot can be removed by running CBMFFIX.exe manually. It can be found in the Windows\System directory. When double-clicked, the CBMFFIX displays a dialog box describing the forced configuration information. Each CardBus socket is displayed along with its Status (either Plug&Play or Locked), and whether a Xircom card is currently inserted. Forced configurations may be removed either from each socket individually (by selecting the individual locked socket and clicking on the Remove Lock button) or all at once with the Remove All button. This should be done before performing an upgrade from 95OSR2 to Microsoft Windows* 98, Microsoft Windows* 2000, or Microsoft Windows* XP. Known Limitations in Microsoft Windows* 95 OSR2 ----------------------------------------------- Under Microsoft Windows* 95 OSR2, once CBEM is installed, no other card can be inserted into the slot into which CBEM was installed. However, CBEM can be removed and reinserted into the same slot while the laptop is running. The adapter should not be installed into the other slot, or a forced configuration will be applied to both slots, and other PC Cards may not be usable. If this happens, see the section above titled "Removing the Forced Configuration" for instructions on how to remove it. Microsoft Windows* 95 may fail to load CBEM when Microsoft Windows* 95 comes out of Suspend/Resume. To make CBEM load in this situation, click on the PC Card (PCMCIA icon) in Control Panel, highlight the adapter and click on Stop. Next, eject CBEM and then re-insert it. CBEM will now load. There may be machine specific issues with certain computers. See Section 9, "Machine Specific Notes", for further information. Upgrading from Microsoft Windows* 95 OSR2 to Microsoft Windows* 98 ------------------------------------------------------------------ If CBEM is installed in Microsoft Windows* 95 OSR2 and you are upgrading to Microsoft Windows* 98, the CBMFFIX is not needed and the "forced configurations" it creates must be removed. See the section above titled "Removing the Forced Configuration" for instructions on how to remove it. 4) NOTES ON CARD SERVICES ========================= Note: With this release Xircom has implemented automatic driver selection and installation for all supported Windows versions, including Microsoft Windows* NT4.0 with supported versions of third- party card services. No special installation procedures are now required, nor do special purpose drivers need to be selected for NT card services. For all installations under Microsoft Windows* 95 OSR2 (or better), Microsoft Windows* 98, Microsoft Windows* NT4.0, Microsoft Windows* Millennium, and Microsoft Windows* 2000, the drivers may be found by pointing to the root of the CD-ROM, or of floppy diskette 2. Microsoft Windows* 95 OSR2 and Third Party Card Services -------------------------------------------------------- Phoenix* Card Manager for Microsoft Windows* 95 OSR2: The Phoenix* software must be de-installed prior to running CBEM. See the Phoenix* README file for instructions on de-installing the software. Xircom has tested with Phoenix* version 4.00.48. SystemSoft* CardWorks for Microsoft Windows* 95 OSR2: This software is compatible with CBEM. No special instructions are necessary. Xircom has tested with versions 5.32.11, 5.32.12 and 5.32.20. Microsoft Windows* NT4.0 and Third Party Card Services ------------------------------------------------------ The Xircom(R) Ethernet CardBus + Modem 10/100 Adapter supports manual installation under Microsoft Microsoft Windows* NT4.0. Plug and Play installation and hot swapping of CardBus adapters are not directly supported by NT4.0, but may be supported through third- party Card and Socket services software. Some Microsoft Windows* NT4.0 installations include third party Card and Socket Services software designed to improve PC Card installation and to support hot swapping. In addition to its standard NDIS3 and NDIS4 drivers, Xircom has also developed CBENT.SYS and CBMODEMN.SYS to provide additional support for Phoenix* and Softex* Card and Socket Services software. With this release, the RealPort CardBus Ethernet + Modem Adapter supports the following Microsoft Windows* NT4.0 Card and Socket Services software: Card Executive for NT 4.0 from Softex* (Phoenix* Technologies) -------------------------------------------------------------- NOTE: The minimum version of Softex* Card Executive to support Softex* PCI Routing is v2.86, this driver set does not support PCI Routing. Leaving the IRQ and other settings on "AutoDetect" is recommended NOTE: Concurrency is not supported with this version of Softex drivers. If network and modem connectivity is required at the same time, please visit our support website to download the Softex_Concurrent.exe file. Support for Softex* Card Services are provided by the special Card and Socket Services drivers CBENT.SYS and CBMODEMN.SYS. These will be automatically selected and installed if your computer uses Card Executive. 1. Boot your machine. Insert the CardBus Ethernet 10/100+Modem 56 Adapter into the CardBus PC Card slot. 2. Once the Card Services software has detected the adapter, follow the onscreen installation instructions for your Card and Socket Services software. Insert the Xircom driver CD-ROM or floppy diskette 2, and select "Install the driver that was provided with the PC Card." Phoenix Card services will automatically search the floppy drive for drivers, but if you are installing from CD-ROM you may need to direct the install to the root of the CD. 3. Working resources will be automatically determined by the install. Accept them, and after a short delay card services will announce that the card is configured and available for use. After the network drivers are installed, you will need to install the modem. Restart your computer, and proceed as follows: MODEM SETUP ----------- NOTE: Newer Fujitsu-Seimens* machines may require you to place the modem on COM2, I/O 02F8. 1. After the computer has restarted, double-click the Modems icon in Control Panel. 2. At the Install New Modem screen, verify that the "Don't detect my modem; I will select it from a list" option is NOT checked and then click Next. 3. Windows NT queries the COM ports to determine if a modem is present. 4. Once NT detects the modem, the Install New Modem window appears displaying the type of modem found. In most cases, a Standard Modem is displayed. NOTE: If the modem is not detected, try changing the COM port and/or IRQ. 5. Click Change. This action brings up the dialog box containing a list of Manufacturers and modem models. Click the Have Disk button. 6. Enter the path to the Xircom files in the "Copy manufacturer's files from:" box. Click OK. 7. Verify that the Xircom CardBus Modem 56 is selected (DO NOT select the Xircom(R) CardBus Modem 56 - Manual Load), then click OK. 8. Verify that the Xircom(R) CardBus Modem 56 is indicated in the next dialog box and then click Next. 9. At the Install New Modem screen click Finish. 10. At the Modem Properties window, click Dialing Properties... Set the appropriate dialing properties and click Close. 11. To install the Xircom Program Group click Start, select Run, browse the Xircom CD-ROM, and select SETUP.EXE. 12. Click OK, then click OK again to install the Xircom utilities and on-line documentation. 13. Restart the computer so that the Xircom CountrySelect utility Runs. Select the appropriate country, save the settings and then click Exit. 14. The Xircom Registration utility runs automatically after the Xircom CountrySelect software closes. Complete the registration form and send it to Xircom. PC Card Controller for NT from Softex* Incorporated --------------------------------------------------- Softex(R) PC Card Controller for NT provides functionality similar to Phoenix(R) CardExecutive. The correct drivers will be automatically selected and installed just as with CardExecutive. CardWare for Microsoft* Windows* NT 4.0 from Award* Software ------------------------------------------------------------ With versions of Award* CardWare prior to 6.0.015 the Xircom driver will co-exist with Award's software but full functionality including hot swapping and hot insertion are not supported. Full support including hot insertion and hot swapping are available with Award version 6.0.015 or later. SystemSoft* CardWizard ---------------------- SystemSoft* CardWizard v. 4.1 and above will provide basic support for CardBus Ethernet + Modem devices. This version is required to support CBEM. Full featured functionality (i.e., hot insertion, hotswap) has been implemented in CardWizard v. 5.0 and above. These versions are recommended for use with CBEM/RBEM/R2BEM. Installation under NT 4.0 Using SystemSoft* Card and Socket Services: 1. Insert the Xircom(R) CardBus Ethernet 10/100+Modem 56 Adapter into the CardBus PC Card slot. 2. Once the Card Services software has detected the adapter, follow the onscreen installation instructions for your Card and Socket Services software. Use of default resource settings is recommended. 3. If the Card Services software includes a driver for the Xircom CardBus Ethernet Adapter, install that driver. Otherwise, follow the guidelines below: SystemSoft* CardWizard Card Services software will display a CardWizard icon on the task bar when you insert the Xircom(R) CardBus Ethernet 10/100+Modem 56 adapter. Use the drivers located in the root of the Xircom CD-ROM or of floppy diskette 2. COMM Port Assignment -------------------- See the RELEASE NOTES section below for information on the COMM Port assignment in Microsoft Windows* 95 OSR2 and Microsoft Windows* 98. 5) RELEASE NOTES/KNOWN LIMITATIONS ================================== Please note that the 'Xircom Program Group' and related utilities are no longer created during installation. To install the 'Xircom Program Group' and related services, insert the Xircom CD-ROM; go to 'START','RUN' and type "D:\SETUP.EXE". The utilities may also be installed from floppy diskette 3 if you have made a floppy diskette set. Supported Environments ---------------------- The version number for the entire release of this driver set is version 3.11. The following environments are supported. Driver Name Description ----------- ------------------------------------------------- CBE.SYS NDIS3 Driver for Microsoft Windows* 95 (OSR2), Windows* 98 and Windows* NT4.0 CBEN4.SYS NDIS4 Driver for Microsoft Windows* 95 (OSR2), Windows* 98 and Windows* NT4.0 CBEN5.SYS NDIS5 Driver for Microsoft Windows* 98/98SE Windows* 2000, and Windows* XP. CBMODEM.SYS Modem enabler for Microsoft Windows* NT4.0 CBMFFIX.EXE CBEM configuration program for Microsoft Windows* 95 OSR2 CBEODI.COM 16-bit ODI driver for DOS and Microsoft Windows* 3.X CBMODEM.COM Modem enabler for DOS/Win 3.X CBE.LAN 32-bit ODI Client/Server Driver for DOS, Microsoft Windows* 3.X and Windows* 95 CBENDIS.EXE NDIS2 Driver for Microsoft Windows* 3.X supporting LAN MANAGER*, LAN REQUESTER* and Lantastic* 7.0 CBEODI.OS2 ODI Driver for OS/2* CBENDIS.OS2 NDIS2 Driver for OS/2* CBMODEM.OS2 Modem enabler for OS/2* CBEPD.COM Packet Driver CBETEST.EXE DOS Diagnostic Test Program CBEDIAG.EXE Windows Diagnostic Test Program (Microsoft Windows* 95 OSR2,Windows* 98, Windows* NT4.0 SP6 and Windows* 2000 only) COMSEL.EXE Xircom(R) COM Select Utility (Microsoft Windows* 95 OSR2 and Windows* 98 only) MDMTEST.EXE Windows based modem test utility (Microsoft Windows* 3.X,95 and 98) REALVIEW.EXE Xircom(R) Modem Informational and Management Utility TELSEL.EXE Xircom(R) Country Select Modem Utility APUNINST.EXE Xircom(R) Utilities Uninstaller New Features ============ Automatic Windows Driver Selection and Installation --------------------------------------------------- With this release Xircom has implemented automatic driver selection and installation for all supported Windows versions, including Microsoft Windows* NT4.0 with supported versions of third-party card services. No special installation procedures are now required, nor do special purpose drivers need to be selected for NT card services. For all installations under Microsoft Windows* 95 OSR2 (or better), Microsoft Windows* 98 and 98SE, Microsoft Windows* NT4.0, Microsoft Windows* Millennium, and Microsoft Windows* 2000, the drivers may be found by pointing to the root of the CD-ROM, or of floppy diskette 2. NDIS Driver Selection --------------------- This driver release now supports NDIS version selection for installs under Microsoft Windows* 9x, Microsoft Windows* NT4.0, and Microsoft Windows* 2000. For installs under Microsoft Windows* 9X, Microsoft Windows* NT 4.0, or Microsoft Windows* 2000, direct the install to the root of the CD (or of floppy disk 2) when the drivers are requested. The network property page tab of the CBEM/RBEM/R2BEM has a new entry "NdisVersion". This entry contains the following: Under Microsoft Windows* 95OSR2: AutoSelect, NDIS3, NDIS4 Microsoft Windows* 98: AutoSelect, NDIS3, NDIS4, NDIS5 Microsoft Windows* 98SE: AutoSelect, NDIS3, NDIS4, NDIS5 Microsoft Windows* NT 4.0: NDIS4 (default), NDIS3 Microsoft Windows* 2000: "NdisVersion" does not exist and NDIS5 is the default driver. The NDIS Switcher is not used with Microsoft Windows* 2000, and 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. Improved Windows NT Installation -------------------------------- This release contains additional improvements for Microsoft Windows* NT4.0 that allow faster and easier manual (without card services) installations. NT 4.0 alone provides no Plug&Play functionality, and gives little guidance in choosing acceptable resources. The drivers in this release incorporate a resource scan that checks for resources already in use, and excludes those resources from the range shown in the adapter's configuration settings. The initial default resources are no longer fixed, but are automatically set to resources determined to be available. This greatly increases the chances that the adapter will function without further configuration changes. 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 it's 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, the negotiation messages can be disabled. 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 forced RealView Utility ---------------- This release includes Xircom's(R) RealView modem and network informational and diagnostic utility, provided in the RealView directory of the Driver CD-ROM. There is a separate Setup program in the RealView directory that may be used to install RealView if desired. RealView contains extensive context-sensitive help that is available from within the program. NOTE: The version of RealView in this release does not have support for the card uninstaller feature when used with the CBEM/RBEM/R2BEM cards, and this feature has been turned off by default. Later versions of RealView will provide this functionality. Additional Information ====================== TCP/IP Routing- Dynamic Link Detect Keyword ------------------------------------------- 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 Microsoft 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. However, in the case of a multi- function adapter, this solution cannot be used. 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/Network of Xircom.../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 need not 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. 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 CBEM/RBEM/R2BEM. 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 adapter's 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. 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. Com Port Assignment in Microsoft Windows* 95 OSR2 and 98 -------------------------------------------------------- Microsoft Windows* 95/98 will assign the modem in CBEM/RBEM/R2BEM to COM5. Windows applications supporting TAPI support the use of COM5. If you have an application which does not support the use of COM5, the Xircom Com Select Utility can be used to change the com port assignment in Microsoft Windows* 95/98. It will allow you to select an unassigned com port and assign it to CBEM/RBEM/R2BEM. The Com Select Utility is installed to the Xircom program group when the setup program is run. See Machine Specific Notes in Section 9 for additional information on using the Com Select Utility with specific machines. The Com Select Utility operates only under Microsoft Windows* 95 and Microsoft Windows* 98. It does not operate under Microsoft Windows* NT4.0. However, it does get copied to the program group in Microsoft Windows* NT4.0. If launched, the program will report that it does not work under Microsoft Windows* NT4.0. V.90 configuration and use information - S109 register ------------------------------------------------------ Current released firmware for Xircom 56K modem products now includes support for the v.90 56K modem standard. This firmware is designed to initially attempt to make a v.90 connection, and then fall back to K56flex if the host being dialed does not support v.90. However, the host being dialed must support v.90 autodetect in order for a v.90 connection to be initiated by default. At this point in time many v.90 hosts do not yet support autodetect. In such cases it will be necessary to issue an ATS109=2 command to the modem in order to force a v.90 connection. Please note that if this command is used and a v.90 connection is not achieved, the modem will fall back directly to v.34. When S109=2, fall back from v.90 to K56Flex is disabled. To set this value back to the default, issue an ATS109=1 command. In summary, the values of this register and the resultant behavior are: S109=1 (default) - Negotiates initially at v.90 if host supports v.90 autodetect. If host does not support v.90 autodetect or does not support v.90 at all will negotiate back to K56flex. S109=2 - Forces v.90 for PCM connects. If host does not support v.90, falls directly back to v.34. Changing the value of the S109 register can be implemented via the following means: When using a terminal emulator program, enter ATS109=n (where n is the value desired). To implement with Microsoft Windows* 95/98/NT4.0 dial up networking, go to Control Panel\Modems. Highlight the Xircom modem and click Properties. Click Connection\Advanced. Enter S109=n (where n is the value desired) in the Extra Settings box. Modem Script Files ------------------ Modem script files for popular applications can be found in the \SCRIPTS directory on the CD-ROM. Known Limitations ----------------- -Wake-On-LAN (WOL) under Microsoft Windows* XP during a Hibernate session will not fully restore, a reboot is required. -Packet Priority is set to off under Microsoft Windows* XP, the user configurable keyword under Advanced Network Properties does not apply. -Microsoft 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 NT4.0 requires that the laptop BIOS initialize the CardBus controller as a PCI device and set up PCI routing. -Under Microsoft Windows* 95 OSR2, once CBEM is installed, no other card can be inserted into the slot into which CBEM was installed. However, CBEM can be removed and reinserted into the same slot while the laptop is running. The adapter should not be installed into the other slot. -Microsoft Windows* 95 may fail to reinitialize the CBEM when Microsoft Windows* 95 comes out of Suspend/Resume. To make the CBEM restart in this situation, click on the PC Card icon in the System Tray (or in Control Panel), click Stop, eject CBEM and then re-insert it. CBEM will now load. -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 Xircom(R) CardBus Ethernet 10/100+Modem 56 Adapter is designed to connect to a 100Base-TX network. It does not support 100VG-AnyLAN or 100BaseT4 networks. -When running the LAN Requester install, the CBENDIS.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 CBENDIS.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 (CBE.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 fragments errors. -When using the Packet Driver with the Intel 10/100 stackable hub, network connections may be lost at 10Mbps. -When attempting to use CBEM with a second 16-bit adapter (e.g. modems, flash cards, ATA cards) in the other slot, it may be necessary to boot up with the CBEM first then hot-insert the second adapter. -In order to achieve 56Kbps connects (v.90 or K56flex), there can be only one digital to analog conversion between the connecting modems. Also, the modems at both ends of the call must be 56K compatible to achieve 56K speeds; otherwise a standard V.34 connection (maximum 33.6Kpbs) will be negotiated. Current FCC regulations limit download speeds of the modem to 53Kbps. -If loading CBEODI.COM in a DOS environment from the command line, you must shut down the machine to use a different IRQ. -The DOS Line Configuration keyword values are as follows: CBENDIS.EXE H10 F10 H100 F100 - for 10/100Mbps and Half or Full Duplex CBEODI.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 CBENDIS.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"] 6) Using the CBEM/RBEM/R2BEM in Microsoft Windows* 2000 ======================================================= Microsoft Windows* 2000 contains built-in drivers for the Xircom CBEM, RBEM and R2BEM, as well as many other Xircom Cards. The built-in drivers are functional but lack the new features of this release. To update the Microsoft Windows* 2000 driver do the following: 1. You will need to have the Xircom CBEM/RBEM/R2BEM installed and inserted in the laptop to proceed. Go to Start/Settings/Control Panel, double click on Network and Dial- up Connections, and double click on Local Area Connection. Select Properties. 2. Click the Configure button on the top of the Local Area Connection Properties screen, just under the "Connect using:" listing for the Xircom(R) CardBus Ethernet Adapter 100 + Modem 56. Next select the Driver tab, and click the Update Driver button. This starts the Upgrade Device Driver Wizard. Click Next. On the next screen select "Search for a suitable driver for my device (recommended)". Click Next. On the Locate Driver Files screen, select "Specify a location", and click Next. Enter the path to the Xircom driver CD, diskette, or directory where you extracted the files. For example, if you were installing from the CD and your CD -ROM drive was drive D, you would enter "D:\". 3. The Wizard will announce that it has a suitable driver already installed, and that it has also found other drivers suitable for this device. Select the "Install one of the other drivers" check box and click Next. You will then see a screen showing both the Microsoft-provided driver, and the new Xircom driver (identified as Xircom(R) Ethernet Adapter 100 + Modem 56, and with a path listed to your driver CD or diskette). Select the Xircom driver, and click Next. 4. You will then may be notified that Microsoft has not digitally signed the software, and asked if you want to continue the installation. Click Yes. The updated drivers will then be copied to your computer. Click Finish, and then click Close. Click OK to close the Local Area Connection Properties box. Reboot the machine to utilize the new driver. By following step 1 above, clicking the Configure button, and selecting the Advanced tab you may now access the new driver settings. 7) MACHINE SPECIFIC NOTES ========================= Visit the Intel web site for the latest machine specific information. The Xircom(R) CardBus Ethernet 10/100+Modem 56 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 Machines using O2Micro CardBus chipsets --------------------------------------- O2Micro* controllers cannot be used with CardBus adapters under Microsoft Windows* NT4.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 CBEM in the bottom slot. Dell* Inspiron 3200 ------------------- The Com Select Utility does not change the com port assignment on this machine. Hitachi* VisionBook Plus 5000 ----------------------------- The Com Select Utility reports Com3 as being available even though it is used by the internal modem. After reboot, the internal modem will be moved to Com5 and CBEM will be assigned to Com3. HP 4150 ------- In some environments the 4150 can experience video corruption and network problems when used with CardBus adapters. A BIOS update which resolves these issues is available to affected customers by calling HP Customer Support. IBM* ThinkPad 760ED ------------------- If using the 32-bit ODI client (CBE.LAN), interrupt 9 should be used. NEC* Versa LX and SX -------------------- These machines require BIOS version 42 or better (available for download from the NEC web site) when used with Xircom(R) CardBus adapters. Texas Instruments(T) Extensa 650, 660 and 900 --------------------------------------------- If using the DOS 16-bit drivers, on the TI Extensa 650 it is necessary to insert the CBEM 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 CBEM in the bottom slot. 8) CREATING A DISK INSTALL ========================== If you need a diskette version of the CBEM software for installation on a system without a CD-ROM, the CD-ROM includes four directories, DISK1, DISK2, DISK3, and DISK 4, which contain files that can be copied to diskettes. This can be done manually or by running MAKEDISK.BAT. DISK1 includes the files necessary for DOS, Microsoft Windows* 3.X and OS/2*. DISK2 includes the files necessary for Microsoft Windows* 95, Windows* 98,Windows* NT4.0, Windows* 2000, and Windows* XP. DISK3 contains Xircom utilities and their install program. DISK4 contains the Realview modem and network utility install. 9) SNMP AGENT ============= Xircom provides SNMP support for the CBEM. To use the agent under DOS, follow these instructions: ------------------------------------------------------ 1. Copy all of the SNMP directory on the CD-ROM to your hard disk drive, typically to the \NWCLIENT directory. 2. Edit the SNMP.CFG file and add the correct IP address and other configuration information. Contact your system administrator if necessary. 3. Edit the NET.CFG file (typically in \NWCLIENT) to include: Frame Ethernet_II 4. After the LAN driver is loaded, load the SNMP driver, XAGENT_O.EXE, by changing to the directory where it exists, typing XAGENT_O and pressing ENTER. Alternatively, add the following lines to AUTOEXEC.BAT: CD\NWCLIENT XAGENT_O Note: You must change to the directory (NWCLIENT) before loading the driver, otherwise it won't load properly. To use the agent under Microsoft Windows* 95, follow these instructions: --------------------------------------------- 1. First install the Microsoft* SNMP agent: For Win95: Control panel -> Network -> Add -> Service -> either: Microsoft -> SNMP Agent or: Have disk -> WIN95 CD-ROM\\admin\nettools\snmp 2. Then install the Xircom Extension agent: Control panel -> Network -> Add -> Service -> Have disk -> 3. Insert the Xircom CD-ROM Then select D:\ Select: Xircom SNMP extension agent -> OK To use the agent under Microsoft Windows* NT, follow these instructions: --------------------------------------------- 1. First ensure that the NT network has been installed and configured with: -NWLINK IPX/SPX; -TCP/IP (with SNMP Service); 2. For Microsoft Windows* NT: Main -> Control panel -> Network -> Add Software -> 3. Select "Other" from the Add Network Software menu, click on "continue" 4. Insert the Xircom CD-ROM and click OK 5. The "Xircom SNMP Mobile Extension Agent" appears in the Select OEM Option window 6. Click OK and complete the installation 7. Reboot 10) SCO UNIX Support ==================== Xircom(R) CardBus PC cards are certified for use with SCO UNIX OpenServer 5.X. Drivers may be downloaded from the Xircom driver download area at http://support.intel.com. 11) LINUX SUPPORT ================= Drivers for Xircom products under Linux are currently developed and supported by the Linux On Line Community. 12) Xircom Technical Support ============================ ============================================== XIRCOM TECHNICAL SUPPORT ============================================== A complete listing of Xircom Support numbers, addresses, hours and languages is available at http://www.intel.com/support/9089.htm *Other names and brands may be claimed as the property of others. ============================end==================================