Intel EtherExpress(TM) PRO/100 LAN+Modem56 PC Card Software Release 2.50 March 31, 1999 ====================================================================== CONTENTS ======== 1. Intel PRO/100 LAN+Modem56 PC Card Characteristics 2. Release Notes/Known Limitations 3. V.90 Configuration and Use Information 4. Upgrading Drivers in Windows 95 5. Upgrading from Windows 95 to Windows 98 6. Installing NetWare Client 32 drivers 7. Machine Specific Notes 8. Modem Script Files 9. Obtaining cables for adapters, GSM, and cellular phones 10. New Zealand Telepermit Compliance Notes 11. Intel Customer Support CAUTION: be sure to plug the modem and LAN cables into the corresponding connector on the adapter. Look for the icons on the cables for proper identification. Forcing cables into the incorrect connector can damage the internal connectors and cause the adapter to fail. 1) INTEL PRO/100 LAN+MODEM56 PC CARD CHARACTERISTICS ================================================= This release of the Intel PRO/100 LAN+Modem56 PC Card supports the following features: -Auto-negotiation of either 10Mbps or 100Mbps Ethernet networks with simultaneous modem connections. -Full suite of network driver support - Allows 10Mbps or 100Mbps connections across a wide range of operating systems and networks. -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. -Flash ROM upgrade capability for quick and easy software upgrades. Please see the Intel Web site for the latest modem software for your PRO/100 adapter. -Windows 3.x installation program - Automatically configures both PC and NOS setup directly from Windows versions 3.1 and 3.11. -HotSwap support - Supports easy replacement of one card with another while power is on, as well as the ability to gracefully disconnect from the network. 2) RELEASE NOTES/KNOWN LIMITATIONS =============================== Supported Environments ---------------------- The following driver types are included with this release: -NDIS3 Driver for Microsoft Windows NT (Ver. 3.51, 4.0) and Windows 95/98 (M16B.SYS) -NDIS4 Driver for Microsoft Windows NT 4.0 and Windows 95 OSR2 and 98 (M16B4.SYS) -32 bit Novell Client driver and installation support files for Novell Client 32. for DOS/Windows 3.x (M16B.LAN, M16B.LDI) -DOS ODI Driver (M16BODI.COM) -DOS NDIS2 Driver (M16BNDIS.EXE) -Packet Driver (M16BPD.COM) -Diagnostic test program (M16BTEST.EXE) -Modem test program (MDMTESTW.EXE) -Modem Enabler (IMENABLE.COM) Features of this Release ------------------------ -An automated uninstall utility has been included on this release. See the file UNINSTALL.TXT in the \UNINSTAL directory on disk2 for details. -The modem .INF file (used by Windows 95/98 and Windows NT) has been updated with this release to include support for v.90 connection result codes. -Support for unattended installation to a domain server under Windows NT. For specific instructions on how to implement this please consult the READUNAT.TXT located in the NT40 subdirectory. A sample answer file (ANSWER56.TXT) has also been provided in this directory and can be consulted and used as a template if desired. -An NDIS4 Compliant Driver for use with Windows NT and Windows 95 Resolved Issues --------------- The following known issues have been resolved: -100 Mbps connections with Synoptics/Bay Networks 28115 hubs. -Hot swapping of the PRO/100 LAN+Modem56 PC Card is now supported when using SystemSoft Cardworks version 4.x for Windows NT 4.0. -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. 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 "Dynamic Link" to overcome this difficulty. The value of this keyword (ON or OFF) can be set by going to Control Panel/Network /Intel EtherExpress PRO/100 LAN/Modem PC Card (Network)/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 adapter is initialized by the driver. 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 Ethernet interface will only be initialized by the driver 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. Known Limitations ----------------- -In order to achieve 56Kbps connects, there can be only one digital to analog conversion between the connecting modems. Also, the modems at both ends of the call must be K56Flex 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. -Full-duplex Ethernet transmission is only supported on 10Mbps networks. This feature is only available when the Adapter is connected to switched full-duplex 10Mbps Ethernet hubs. -In order to connect to a 100Base-TX Ethernet network, 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. -Under OEM Service Release Version 2 of Windows 95 (OSR2), the multifunction parent device may be displayed under the Modem category in addition to the modem device. The modem device string is: "Intel EtherExpress PRO/100 LAN+Modem56 PC Card Modem". The other device listed represents the parent multifunction device. -When using QmodemPro in DOS with M16BODI.COM in SHAREIRQ mode, modem performance will be slow. Intel recommends using MODE IO to improve performance. -Using Windows NT 4.0 with Service Pack 1 may cause some portable PCs to lock up on Shutdown or Restart. Updating to Service Pack 3 resolves this issue. -If you experience intermittent times where the modem will not respond to an AT Command while running IMENABLE.COM on a portable that uses the TI1130 PCMCIA Controller, run M16BTEST and choose the test function to determine the IRQ the card is using and run IMENABLE COMIRQ=x where x is the IRQ determined by M16BTEST. See the User's Guide for additional information on using M16BTEST. -If you experience problems connecting to the network using Windows for Workgroups, add the parameter Mode=I/O in the PROTOCOL.INI file -The COM Port Monitor Utility (XCOMMON) must be launched prior to any communication applications for it to function. -In Windows 95 or Windows 98, the modem is configured to install the modem at I/O address 02E8 on COM4 by default. In some computers, other hardware or virtual ports are already installed that are using these resources in some manner, and the presence of these devices will cause the modem to install on COM5. Some applications may not be able to access the modem in such cases. In order to correct this and move the modem to a conventional COM port location (COM1 through COM4), try the following: Solution 1 If your computer contains an Infra-red serial port or a standard serial port that is not being used, disable this device in both the computer's system BIOS and in Windows via the Device Manager. Then reboot the computer. In many cases, Windows will then re- assign the modem to the resources that are now open (typically I/O address 02F8, COM2) and the situation will be corrected. Solution 2 If you are unable to disable such devices or Windows fails to re-assign the port used, try the following: 1. Go to the Device Manager. Locate the "Multifunction Parent" device entry for the modem (this may be located in either the Modems group or the Multifunction Adapters group). Double click this entry. 2. Click the Resources tab. Uncheck the box labeled "Use Automatic Settings". 3. Note the Basic Configuration number the adapter is assigned to (in most cases this will be 0000). Choose a different Basic Configuration number to assign the modem to the port desired according to the following scheme: Basic Configuration 0005 - I/O address 03E8, COM3 Basic Configuration 0006 - I/O address 02F8, COM2 Basic Configuration 0007 - I/O address 03F8, COM1 We have found the first choice (0005, 03E8, COM3) to be the best selection in most instances. 4. Once the new configuration is selected, click OK. A warning message will be displayed indicating you have made manual changes and asking if you wish to continue. Click Yes. After a few seconds the modem will be assigned to the new settings and the problem should be corrected. -On some computers running Windows NT 4.0, if NT networking functionality has not already been installed, lockup and/or "blue screen" symptoms may be encountered when installing the modem along with networking. This has been observed primarily on computers that support CardBus. The following workarounds for this situation have been found to be successful: Solution 1 Perform the installation of Windows NT networking and the modem WITHOUT the modem actually present in the computer. Assign resources that are appropriate for your computer. Once the installation process has completed, shut down the computer and insert the modem in the computer and then reboot. Solution 2 When initially installing networking, choose the "MS Loopback Adapter" from the adapter list instead of installing the modem at this time. Once networking is installed, reboot the computer, remove the "MS Loopback Adapter" from the configuration, and install the modem according to the instructions in your User's Guide. Solution 3 In some cases it is necessary to install the modem while installing networking for the purposes of joining a Domain. This is true in the case of an unattended installation to an NT domain server. In such cases, download the latest version of PCMCIA.SYS (pcmfix-i.exe). At the time of this publication this file can be obtained at the following URL: ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/nt40/ hotfixes-postSP3/pcm-fix/ Rename the existing PCMCIA.SYS located in the \I386 directory. Copy the updated version to the \I386 directory. See the online help file for additional information. In a case in which Windows NT has already been installed but networking has not and the need exists to join a domain in this manner, overwrite the PCMCIA.SYS file that currently exists in the \%systemroot%\system32\drivers directory with the new one. You should then be able to install the modem while installing networking without difficulty. -PCMCIA adapters may feel hot to the touch after prolonged periods of normal use in some environments. This is normal and is not known to affect operation of the Intel card, the host computer, or any other peripheral device. However, to avoid discomfort, use caution when removing the card from your computer after extended use (see your computer manual for removal procedures). 3) V.90 CONFIGURATION AND USE INFORMATION ====================================== S109 register ------------- Current released firmware for this modem product 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 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 Windows 95/98/NT dial up networking, go to Control Panel\Modems. Highlight the modem and click Properties. Click Connection\Advanced. Enter S109=n (where n is the value desired) in the Extra Settings box. -When using with a specific communications application, add S109=n (where n is the value desired) to the modem dial string invoked by the application. Consult the application documentation if you are uncertain about where to change the dial string values. 4) Upgrading Drivers in Windows 95 =============================== This section only applies to users who are upgrading from a previous driver version. If this is a first time installation this section does not apply. At the time of this release, in Windows 95 it is necessary to un- install the PRO/100 completely from the system and then re-install it in order for the new release to function properly. Use of the driver update feature in the Windows 95 Device Manager will NOT properly install the new driver on the system. This is due to limitations with the Windows 95 update feature itself, as well as the fact that this driver release contains added functionality that required some changes to certain installation files. Instructions to perform the uninstall can be found in the UNINSTAL.TXT file included with this release. Note that the manual uninstall is somewhat involved and should only be performed by experienced Windows 95 users. 5) UPGRADING WINDOWS 95 TO WINDOWS 98 ================================== When upgrading from Windows 95 to Windows 98, eject the adapter from the PC Card slot. Once Windows 98 is completely installed on the computer, insert the adapter into the PC Card slot. Windows 98 should detect and configure the adapter. (If the adapter is not removed prior to installation, Windows 98 may incorrectly identify it as a Standard PCMCIA modem.) 6) INSTALLING NETWARE CLIENT 32 DRIVERS ==================================== Installing in DOS ----------------- 1. Type INSTALL from the directory or diskette where the Client 32 files are located. 2. Select the products you want to install. 3. Follow the on screen instructions 4. At the Select a LAN Driver screen, select User Specified LAN Driver. 5. Insert the Intel Network Drivers Disk in drive A 6. Type A: and press enter. 7. Select 'Intel EtherExpress(TM) PRO/100 LAN/Modem PC Card Adapter'. 8. A screen will display the default settings for the driver. Most of the time, these settings do not need to be changed. 9. To complete installation, follow the on screen instructions. Installing in Windows 3.1x -------------------------- 1. Select File, Run, and type SETUP from the directory or diskette where the Client 32 files are located. 2. Follow the on screen instructions 3. When the ODI Driver Selection Dialog box appears, select User Specified Driver and click Next. 4. When prompted, insert the Intel Network Drivers Disk in drive A: 5. Select the driver 'Intel EtherExpress(TM) PRO/100 LAN/Modem PC Card Adapter'. 6. To complete installation, follow the on screen instructions. NOTE: Some computers may require a pause command after loading the driver M16BODI.LAN in order to successfully connect to the server. This driver loads in either the AUTOEXEC.BAT or STARTNET.BAT file. Installing in Windows 95/98 --------------------------- NOTE: Be sure to use version 2.2 or greater on Windows 95 OSR2. For Windows 98, Novell recommends version 2.5 of the Client 32 software. 1. Install the adapter following the instructions in the adapter manual. Ensure the adapter is working properly before installing Client 32. 2. Run the Client 32 SETUP program. Be sure to have Windows 95/98 files available, as the program will ask for updated files. Follow the onscreen instructions to complete installation. 7) MACHINE SPECIFIC NOTES ====================== ThinkPad 760ED -------------- -Intel recommends disabling the IR port and built in modem, then using interrupt 9. ThinkPad utilities that aid in configuring the 760ED are available from IBM's web site. ThinkPad 760XD ------------------- -Intel recommends disabling the IR and Serial ports, then using COM1 for the Intel modem and interrupt 9. IBM's internal MWave modem should be placed at COM2. Toshiba Portege 660CDT ---------------------- -All Intel references under CardWork in the Registry and all Tranxit references in the SYSTEM.INI must be removed for proper installation using the M16B.SYS. -Card and Socket Services (CS/S) must also be removed from the CONFIG.SYS. Panasonic CF-62 ---------------- -When using M16BODI.COM or M16BNDIS.EXE in a DOS/Win 3.x environments, C/SS needs to be loaded for the Adapter to be recognized. -When using M16B.SYS under NT 4.0, the driver fails to initialize. NEC 6050 --------- -When using M16BODI.COM or M16BNDIS.EXE in DOS/Win 3.x environments, Intel recommends adding the keyword MODE IO in the PROTOCOL.INI or NET.CFG. NEC 2400 --------- -When using M16B.SYS under Windows 95 or NT 4.0, the Plug & Play setting in the BIOS must be set to: NO. NEC 6000 and 6030 ----------------- -Intel recommends disabling the IR port. -When using the M16BNDIS.EXE or M16BODI.COM under Windows 3.x with CS/S, Intel recommends going to the CardWiz directory, execute config.exe, select Modem Card Configurations, and change the interrupt number of com4 (currently 11), to int=9. -When using the M16BNDIS.EXE or M16BODI.COM under Windows 3.x without CS/S, Intel recommends setting the Modem to load at com4 in the PROTOCOL.INI or NET.CFG. NEC 6050NT ---------- -When using M16B.SYS under NT 4.0 with Service Pack 1 using CardWizard, the driver will fail to initialize. Intel recommends removing CardWizard. Sharp 9020 ----------- -When using M16B.SYS under Windows 95, remark out the Tranxit references in the SYSTEM.INI. Sharp PC-8650 ------------- -When using M16BODI.COM in DOS/Win 3.x environments, C/SS needs to be loaded for the driver to initialize. IMENABLE.COM will not load. Toshiba Tecra 530CDT -------------------- -Unknown issues when joining a domain under NT 4.0 8) MODEM SCRIPT FILES ================== Modem script files are located on Disk 2, Network Drivers under A:\Scripts. See SCRIPTS.TXT for additional installation instructions for these modem script files. 9) OBTAINING CABLES FOR ADAPTERS, GSM, AND CELL PHONES =================================================== If you require extra Ethernet or modem cable connectors for the adapter, refer to Intel's Accessories order form on the Intel support web site at http://support.intel.com/. Go to the support site for the Mobile adapters to find the order form. Connection Kits for GSM and Cellular are also available on our accessories page for a variety of phones. 10) NEW ZEALAND TELEPERMIT COMPLIANCE NOTES ======================================= General ------- The grant of a Telepermit for any item of terminal equipment indicates only that Telecom has accepted that the item complies with minimum conditions for connection to its network. It indicates no endorsement of the product by Telecom, nor does it provide any sort of warranty. Above all, it provides no assurance that any item will work correctly in all respects with another item of Telepermitted equipment of a different make or model, nor does it imply that any product is compatible with all of Telecom's network services. This equipment is not capable, under all operating conditions, of correct operation at the higher speeds for which it is designed. Telecom will accept no responsibility should difficulties arise in such circumstances. This equipment shall not be set up to make automatic calls to the Telecom '111' Emergency Service. Important Notice ---------------- Under power failure conditions, this telephone may not operate. Please ensure that a separate telephone, not dependent on local power, is available for emergency use. Some parameters required for compliance with Telecom's Telepermit requirements are dependent on the equipment (PC) associated with this device. The associated equipment shall be set to operate within the following limits for compliance with Telecom's Specification: 1 (a) There shall be no more than 10 call attempts to the same number within any 30 minute period for any single manual call initiation, and (b) The equipment shall go on-hook for a period of not less than 30 seconds between the end of one attempt and the beginning of the next attempt. 2 Where automatic calls are made to different numbers, the equipment shall go on-line for a period of not less than 5 seconds between the end of one attempt and the beginning of the next attempt. 3 The equipment shall be set to ensure that calls are answered between 3 and 30 seconds of receipt of ringing. 11) INTEL CUSTOMER SUPPORT ====================== The following services are available 24-hours a day, 365 days a year: Internet -------- Use the World Wide Web or anonymous FTP to get the following: - Troubleshooting information - Software updates - Installation notes - Product information - Technical documents Connection information: World Wide Web: http://www.intel.com (Intel Corporate home page) http://www.intel.com/network (Intel Network Products home page) http://support.intel.com (Customer Support home page) FTP: Address: download.intel.com Directory: /support/lan_adapters/ * Third-party trademarks are the property of their respective owners.