#

Table of Contents | Previous Page | Next Page

# Ethernet 10/100+Modem 56
Troubleshooting

The technical information in these online documents is valid for the following Xircom products: RealPortTM Ethernet 10/100+Modem 56 and CreditCard Ethernet 10/100+Modem 56.TM

This section provides the following troubleshooting information:

- Troubleshooting Guidelines
- Diagnostic Software
- Windows 2000 Troubleshooting
- Windows Me (Millennium Edition) Troubleshooting
- Windows 98 and 95 Troubleshooting
- Driver Parameters for Use with Windows 2000, Me, 98 and 95
- Windows NT 4.0 Troubleshooting
- IBM OS/2 Configuration Reference
- Windows 3.x Driver Parameters
- General Troubleshooting Checklist
- Driver Keywords Alphabetical Reference

### Troubleshooting Guidelines

This troubleshooting information is intended for users or network administrators who have run into difficulties after having completed the appropriate setup and installation procedures for their product and operating environment.

### Diagnostic Software

Xircom provides LAN and modem diagnostic utilities to test several functions of the RealPort Ethernet 10/100+Modem 56 and CreditCard Ethernet 10/100+Modem 56. The LAN utility reports the serial number and network node address of the unit. Write down the model and serial numbers for reference.

#### Running the Diagnostic Utilities

1. Verify that the Ethernet 10/100+Modem 56 has been installed and configured to work with your version of Windows.
2. Be sure that you have run SETUP.EXE at the end of the installation procedure and restarted the system to install the Xircom utilities.
3. Click Start, Programs, Xircom Utilities, and select LAN Test or Modem Test.
4. Follow the onscreen instructions provided.

### Windows 2000 Troubleshooting

##### Upgrading your Windows 2000 Drivers

Windows 2000 contains built-in drivers for the RealPort Ethernet 10/100+Modem 56 and CreditCard Ethernet 10/100+Modem 56. The built-in drivers are functional but may lack the newest features of the release included on your Xircom compact disc. Xircom recommends that you upgrade to the latest Xircom drivers to take advantage of the full functionality of your Xircom card. To update the Windows 2000 driver after completing an automatic installation of the Windows 2000 built-in driver, proceed as follows:

1. Update the Xircom Ethernet driver: With your Xircom PC Card already installed and inserted, go to Start, Settings, Control Panel, double-click Network and Dial-up Connections, and double-click Local Area Connection. Select Properties.
2. On the Local Area Connection Properties screen, click the Configure button on the top of the screen, just under the "Connect using" listing for your Xircom Ethernet 10/100+Modem 56 PC Card model. 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 "NDIS5" folder on the Xircom compact disc (for example, if your CD-ROM drive is E, type "E:\NDIS5"). Then click OK.
3. The Wizard will report that it has found a driver that is a closer match for this device than your current driver. Click Next.
4. You will 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, then Close. Click OK to close the Local Area Connection Properties box.
5. Update the Xircom modem driver: With your Xircom PC Card already installed and inserted, go to Start, Settings, Control Panel, double-click System, click the Hardware tab, click Device Manager.
6. Select Modems and then the Xircom Ethernet 10/100+Modem 56 [modem interface]. Right click on the entry and select Properties.
7. 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 compact disc (for example, if your CD-ROM drive is E, type "E:\").
8. The Wizard will report that it has found a driver that is a closer match for this device than your current driver. Click Next.
9. You will 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, then Close.

Note: To view driver settings, go to Start, Settings, Control Panel, double-click Network and Dial-up Connections, and double-click Local Area Connection. Select Properties, then Advanced. Driver parameters and settings are discussed later in this section.

### Windows Me (Millennium Edition) Troubleshooting

##### Upgrading your Windows Me Drivers

Windows Me includes built-in drivers for the RealPort Ethernet 10/100+Modem 56 and CreditCard Ethernet 10/100+Modem 56. These built-in drivers are functional but may lack the newest features of the release included on your Xircom compact disc. Xircom recommends that you upgrade to the latest Xircom drivers to take advantage of the full functionality of your Xircom card. To update the Windows Millennium driver after completing plug and play installation of the Windows Me built-in driver, proceed as follows:

1. After Windows Me has installed the built-in driver, the New Hardware Found Wizard will disappear. Insert the Xircom CD-ROM.
2. Go to Start, Settings, Control Panel, System, Device Manager. Note: If you don't see the System icon in the Control Panel window, click the link "view all Control Panel options," then double-click the System icon and select the Device Manager tab.
3. Find and select the Multifunction adapter "Xircom Ethernet 10/100 + Modem 56 Parent."
4. Click "Properties" then click the "Driver" tab and "Update Driver."
5. On the Update Device Driver Wizard, click "Automatic search for a better driver (recommended)" and click Next. Windows will find and search the CD-ROM drive for the driver. This may take several seconds.
6. The Update Device Driver Wizard will indicate it is ready to install the new driver. Click Next.
7. The Wizard will indicate that the updated driver has been installed. Click Finish and then close any open Device Manager windows.
   Note: If you did not do so after completing the initial plug and play installation, run SETUP now to install Xircom utilities and online documentation onto your hard drive. Proceed as follows:
8. Click Start, and then Run. Type the path to the SETUP.EXE program on the Xircom compact disc (for example, if your CD-ROM drive is E, type E:\SETUP.EXE), then click OK.
9. On the menu that appears, click "Install Software and Tools" and follow the onscreen instructions. Xircom online documentation and utilities will be copied to your hard drive and installed under Start, Programs, Xircom Utilities. You must have Microsoft Internet Explorer or Netscape Navigator installed to view the online documentation.
10. To change the country configuration of your modem, run CountrySelect under Start, Programs, Xircom Utilities. Choose the country from which you will make modem calls, then click Save and Exit.

### Windows 98 and 95 Troubleshooting

#### Modem Installation Troubleshooting

- Modem initialization errors occur when you are attempting to dial out using a communications application.
- Connection fails.

#### Possible Solutions

- It may be necessary to define a modem type within your communications application. If the Xircom modem is not listed, choose a "Generic Hayes compatible" device.
- If your computer is equipped with an infrared communications port, you may need to disable this port. These ports often use COM port resources required for other communications devices. Disable the infrared port both in the computer's CMOS or BIOS setup program and the Windows 95 Device Manager, as follows:

1. Some computers use a hardware setup utility to configure the infrared port in the BIOS. See your computer documentation for instructions on how to disable it.
2. To disable the infrared communications port in Windows 95, go to the Device Manager tab under System in the Control Panel.
3. Double-click the Ports (COM & LPT) entry and the IR Serial Port entry. Remove the check mark under "Device Usage."
4. Check the "Disable in this Hardware Profile" option to disable the device.

#### How to Use the Windows 98 or 95 Modem Diagnostics Tool

1. In the Modems option in Control Panel, click Diagnostics.
2. In Diagnostics properties, highlight the COM port associated with the Xircom modem and click the More Info button. This causes Windows to send commands to the modem, read responses from the modem, and display information about the modem and its COM port. The Port Information box should display the following information:

- The IRQ and I/O addresses of the modem's COM port. These should match the physical configuration of the port or modem adapter.
- Modem responses to various AT commands. The Xircom modem may return ERROR for some AT commands that are not supported. This does not indicate a failure.

3. A log file can be useful to help identify modem problems by recording modem commands and responses. Windows 95 and 98 have slightly different procedures for creating and maintaining a log file:

- Windows 98 creates a log file by default in the Windows directory, using a filename based on the modem device identifier, with a .LOG extension, such as "Xircom_Network_modem.log" (or a shortened version in MS-DOS). To continue adding information to the log file, place a check mark in the Append to Log option box in the Advanced Connection Settings window (use the path Control Panel, Modems, Properties, Connection, Advanced).
- In Windows 95, go to Control Panel, Modems, Properties, Connection, Advanced. In the Advanced Connection Settings window, place a check mark in the Record a log file option box. A MODEMLOG.TXT file will be created in the C:\WINDOWS directory the next time the modem is used.

### Driver Parameters for Use with Windows 2000, 98, Me, and 95

##### Default Settings and Configurable Parameters

By default the Xircom Ethernet+Modem PC Card software automatically selects the NDIS driver required by your system. The NdisVersion keyword can also be manually set to a particular version of the NDIS driver. Files required for each version of the NDIS driver are: CEM56.SYS (NDIS3), CEM56N4.SYS (NDIS4), and CEM56N5.SYS (NDIS5). See Note 1 following the Driver Parameters table.

The user-configurable parameters listed below can be modified using the Network Control Panel built into Windows. The Control Panel applet queries the user for parameter selections and then sets the corresponding parameters in the registry. The following user-configurable parameters may be set by selecting the Advanced tab of the driver Properties:

Parameter | Default | Valid Values
CableType | Autodetect | 10B2 (coax)
|  | 10BT/100BTX (TP)
Dynamiclinkdetect | ON | ON
|  | OFF
Early Transmit | ON | ON
|  | OFF
Line Mode | Autodetect | Full Duplex
|  | Half Duplex
Line Speed | Autodetect | 10Mbps
|  | 100Mbps
Link Integrity | ON | ON
|  | OFF
Mode | I/O | I/O
|  | Memory Mapped
Ndisversion | Autoselect | See note 1 below
NetworkAddress |  | See note 2 below
PacketPriority* | OFF | ON
|  | OFF
TransmitBufferSize | 11,264 | 1024-29696

*Available under Windows 98 Second Edition and Windows 2000 only, and with the NDIS5 driver only. See the Driver Keywords Alphabetical Reference.

Note 1: Valid NDIS versions displayed and selectable vary with the operating system:

Windows 95OSR2: | AutoSelect, NDIS3, NDIS4
Windows 98: | AutoSelect, NDIS3, NDIS4, NDIS5
Windows 98SE: | AutoSelect, NDIS3, NDIS4, NDIS5
Windows 2000 and Windows Me: | "NdisVersion" does not exist and NDIS5 is the default driver. The Ndis Switcher is not used with Windows 2000 or Windows Me.
Windows NT 4.0: | "NdisVersion" is not supported. Use Network Card properties to change NDIS option (NDIS4 is the default).

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 2: The network node address can be modified by specifying a value for ‘NetworkAddress’ such as ‘0080C7112233’. If the user does NOT specify a ‘NetworkAddress’ then the CEM56.SYS driver uses the network node address contained in the Xircom Ethernet PC Card Information Structure.

## Windows NT 4.0 Troubleshooting

##### Windows NT Driver Parameters

CEM56.SYS driver parameters can be modified using the Windows NT Network Control Panel. This applet uses the OEMSETNT.INF file to configure the corresponding parameters in the registry.

For definitions of the parameter keywords, see Driver Keywords Alphabetical Reference.

Parameter | Valid Values | Registry Value
AutoPolarity | OFF ON | 0 1
CableDetect | OFF ON | 0 1
DynamicLinkDetect | OFF ON | 0 1
EarlyReceive | OFF ON | 0 1
EarlyTransmit | OFF ON | 0 1
InterruptNumber | 3-15 | same
InterruptStyle | AutoDetect PCI-IRQ ISA-IRQ | 0 1 2
IOBaseAddress | 0x1000-0xF800 | same
LineMode | AutoDetect Half-Duplex Full-Duplex | 0 1 2
LineSpeed | AutoDetect 10Mbps 100Mbps | 0 1 2
LinkIntegrity | OFF ON | 0 1
MemoryBaseAddress | 0xC0000-B000C000 | same
MemoryMode | OFF ON | 0 1
RXBUFFERSIZE | 0-100 | same
Socket | AutoDetect 1, 2, 3 | 0, 1, 2, 3
TXBUFFERSIZE | 0-100 | same

For Network Administrators Only. To modify the network node address manually, select Run, type regedit and press Return. Select HKEY_LOCAL_MACHINE, System, CurrentControlSet, Services, CEM56.SYS. Click the Edit menu, select New, String Value. Rename the new value NetworkAddress (no spaces, case sensitive), press Enter. Double-click NetworkAddress and enter the 12 digit address (no spaces) in the "Value Data" box, click OK.

## IBM OS/2 Configuration Reference

The following paragraphs present configuration guidelines for the OS/2 NDIS2 and ODI drivers. An explanation of each keyword can be found in the Keyword Alphabetical Reference.

All of the drivers described here automatically detect the speed of the network to which the adapter is attached (10Mbps or 100Mbps), unless otherwise noted. Speed can also be specified with the LINESPEED keyword.

Full-duplex operation must be explicitly configured with the LINEMODE keyword, unless the adapter is being connected to a hub which supports n-way auto-negotiation. In this case the adapter will auto-detect full-duplex operation.

OS/2 NDIS Driver Configuration Notes

The OS/2 NDIS driver XCEM NDIS.OS2 conforms to the Microsoft LAN Manager Network Driver Interface Specification (NDIS) version 2.0.1. It is an IBM OS/2-based device driver for use with OS/2 versions 2.0 and later.

The files required for using XCEMNDIS.OS2 are:

PROTOCOL.INI | Configuration and binding information file
XCEM OS2.NIF | Xircom installation file for Microsoft LAN Manager
XCEM NDIS.OS2 | Xircom OS/2 NDIS 2.0.1 driver

If any parameters need to be changed, use an ASCII text editor to modify the PROTOCOL.INI file with the appropriate keywords and values.

Keyword syntax for PROTOCOL.INI can be found below. Keywords are not case sensitive, and can be abbreviated to a unique sequence of initial characters (for example, IN for INTERRUPT, IO for IOADDRESS). An explanation of each keyword can be found in the Keyword Alphabetical Reference.

NDIS 2.0.1 Keywords (XCEMNDIS.OS2)

Keyword | Valid Values
CACHE | 0, 4, 8, 16, or 32 |
ERT | NOT PRESENT |
IOADDRESS | 100 - FF80 |
IRQ | 3 - 15 |
ISAIRQ | YES or NO |
LATENCY | 0 - 255 |
LINEMODE | AUTO, HALF or FULL |
LINESPEED | AUTO, 10 or 100 |
LINKDISABLE | YES or NO |
MEMORY | C0000 - 7FFFF000 |
MODE | IO or MEM |
NOBURST | YES or NO |
NOCHECK | YES or NO |
NOEARLYRX | NOT PRESENT |
NOEARLYTX | NOT PRESENT |
NOLED | YES or NO |
NOPOLL | YES or NO |
NOPREFETCH | YES or NO |
NOWRITEPOST | YES or NO |
PCIIRQ | YES or NO |
RXBUFFERSIZE | 1 - 30 |
SOCKET | 1 - 4 |
TXBUFFERSIZE | 1 - 10 |
VERBOSE | YES or NO |

OS/2 ODI Driver Configuration Notes

The OS/2 ODI driver XCEM ODI.OS2 conforms to the Novell ODI Developer's Guide for OS/2 Client Driver Hardware Specific Modules version 2.1. It is an IBM OS/2-based device driver for use with OS/2 versions 2.0 and later. The Novell OS/2 workstation ODI stack including XCEMODI.OS2 supports Novell's NetWare Requestor for OS/2 networking client environment.

Files required for using XCEMODI.OS2 include Novell OS/2 Requestor files and the following files:

NET.CFG | Network configuration file
XCEM ODI.OS2 | Xircom ODI driver for OS/2

If any parameters need to be changed, use an ASCII text editor to open and modify the NET.CFG file and insert the appropriate keywords and values after the line

> LINK DRIVER XCEMODI

Keyword syntax for NET.CFG can be found below. Keywords are not case sensitive, and can be abbreviated to a unique sequence of initial characters (for example, IN for INTERRUPT, IO for IOADDRESS). An explanation of each keyword can be found in the Keyword Alphabetical Reference.

ODI (XCEMODI.OS2) Keywords

Keyword | Valid Values
CACHE | 0, 4, 8, 16, or 32
ERT | NOT PRESENT
IOADDRESS | 100 - FF80
IRQ | 3 - 15
ISAIRQ | YES or NO
LATENCY | 0 - 255
LINEMODE | AUTO, HALF or FULL
LINESPEED | AUTO, 10 or 100
LINKDISABLE | YES or NO
MEMORY | C0000 - 7FFFF000
MODE | IO or MEM
NOBURST | YES or NO
NOCHECK | YES or NO
NOEARLYRX | NOT PRESENT
NOEARLYTX | NOT PRESENT
NOLED | YES or NO
NOPOLL | YES or NO
NOPREFETCH | YES or NO
NOWRITEPOST | YES or NO
PCIIRQ | YES or NO
RXBUFFERSIZE | 1 - 30
SOCKET | 1 - 4
TXBUFFERSIZE | 1 - 10
VERBOSE | YES or NO

OS/2 Modem Enabler Configuration Notes

CMENABLE.OS2 will automatically search for the next available COM port. If there is a conflict, it will be necessary to manually assign the com port. This is done by using the COMx keyword with CMENABLE.OS2. For example, to force the com port to COM4, the following line would be put in CONFIG.SYS:

C:\IBMCOM\MACS\CMENABLE.OS2 COM4

Prior to assigning a COM port, it is necessary to find an available COM port. To find one, run OS/2's Hardware Manager. Hardware Manager will display a list of COM parts that are being used. In Hardware Manager, COM ports are listed as Serial_(Port -1) Serial Controller. The following table is an example of how the ports are listed:

Serial_0 Serial Controller | COM1
Serial_1 Serial Controller | COM2
Serial_2 Serial Controller | COM3
Serial_3 Serial Controller | COM4

Example

Hardware Manager displays the following serial ports in use:

> Serial_0 Serial Controller
> Serial_3 Serial Controller

This means that COM1 and COM4 are being used. Therefore, CMENABLE.OS2 should use the next available COM port, COM2. CMENABLE.OS2 would be loaded with the following line in CONFIG.SYS

DEVICE=C:\IBMCOM\MACS\CMENABLE.OS2 COM2

CMENABLE.OS2 must be loaded before COM.SYS and XCEMNDIS.OS2 or XCEMODI.OS2

OS/2 Modem Enabler Keywords (CMENABLE.OS2)

Keyword | Valid Values
CACHE | 0, 8, 16, or 32
COMx | Auto, 1-4
IOADDRESS | Hardware dependent
IRQ | 3 - 15
ISAIRQ | No value required
LATENCY | 0 - 255
MEMORY | Hardware dependent
NOCHECK | No value required
PCIIRQ | No value required
VERBOSE | No value required

## Windows 3.x Driver Parameters

The following paragraphs present configuration guidelines for each of the driver types: NDIS2, ODI, and packet. For details on individual driver parameters see the Keyword Alphabetical Reference.

All of the drivers described here automatically detect the speed of the network to which the adapter is attached (10Mbps or 100Mbps), unless otherwise noted. Speed can also be specified with the LINESPEED keyword.

Full-duplex operation must be explicitly configured with the LINEMODE keyword, unless the adapter is being connected to a hub which supports n-way auto-negotiation. In this case the adapter will autodetect full-duplex operation.

All of the DOS drivers have enhanced resource detection capability built in. The drivers will detect free system memory, IRQ, and I/O resources for use by the drivers. To use this feature, do not force a particular resource by placing a keyword in the network configuration file. This will override the automatic resource detection for that parameter.

#### ODI Settings (for driver XCEMODI.COM)

Custom parameters for networks using the ODI driver can be entered manually, using an ASCII editor, in the NET.CFG file.

### DOS ODI Driver Configuration Notes (XCEMODI.COM)

The ODI driver XCEMODI.COM conforms to the Novell ODI Specification: 16-bit DOS Client HSMs. It is a DOS-based terminate-and-stay-resident (TSR) program. The driver will configure itself according to the options specified in the NET.CFG file. This file is supplied on the Xircom CD-ROM and must be present in the same directory as the ODI driver. Files required for using XCEMODI.COM are

XCEM ODI.INS | Xircom installation information file
NET.CFG | Network configuration file
XCEM ODI.COM | Xircom ODI driver

If any parameters need to be changed, use an ASCII text editor to open and modify the NET.CFG file and insert the appropriate keywords and values after the line

>     LINK DRIVER XCEMODI

Parameters can also be implemented on the command line. Command line parameters override parameters placed in the NET.CFG file.

### XCEM ODI.COM and XCEMODI.OS2 Keywords

Keyword | Default | Valid Values
AUTOPOLARITY | ON | ON or OFF
CABLEDETECT | ON | ON or OFF
ISAIRQ | AUTO | no value required
PCIIRQ | AUTO | no value required
MEMORY | AUTO | hardware dependent
IOADDRESS | AUTO | hardware dependent
IRQ | AUTO | 3 - 15
SOCKET | AUTO | hardware dependent
MODE | MEM | IO or MEM
NOCHECK | ACTIVE |
NOLED | ACTIVE |
TXBUFFERSIZE | 2 | 1 - 10
RXBUFFERSIZE | 15 | 1 - 30
ERT | HIGH | LOW, MEDIUM, or HIGH
NOEARLYRX | NOT PRESENT |
NOEARLYTX | NOT PRESENT |
LINESPEED | AUTO | 10 or 100
LINEMODE | AUTO | HALF or FULL
LINKDISABLE | NOT PRESENT |
NOBURST | NOT PRESENT |
LATENCY | 32 | 0 - 255
CACHE | 8 | 0, 4, 8, 16, or 32
NOWRITEPOST | NOT PRESENT |
NOPREFETCH | NOT PRESENT |
VERBOSE | NOT PRESENT |
S |  | COMMAND LINE ONLY: SHOW RESIDENT LAN DRIVERS
U |  | COMMAND LINE ONLY: UNLOAD Drivers

NDIS 2.0.1 Settings (for driver XCEMNDIS.EXE)

Custom parameters for the NDIS driver can be entered manually, using an ASCII editor, in the PROTOCOL.INI file.

NDIS 2.0.1 DOS Driver Configuration Notes

The DOS NDIS driver XCEM NDIS.EXE conforms to the Microsoft LAN Manager Network Driver Interface Specification (NDIS) version 2.0.1. It is a DOS-based executable terminate-and-stay-resident (TSR) program that will configure itself according to the options specified in the PROTOCOL.INI file, which is supplied on the Xircom CD-ROM.

The files required for using XCEMNDIS.EXE are:

> PROTOCOL.INI Configuration and binding information file
> XCEMDOS.NIF Xircom installation file for Microsoft LAN Manager
> XCEMNDIS.EXE Xircom DOS NDIS 2.0.1 driver

NDIS 2.0.1 Keywords (XCEMNDIS.EXE)

Keyword | Default | Valid Values
DRIVERNAME=XIRCOM$ (REQUIRED FIRST ITEM IN PROTOCOL.INI) |  |
AUTOPOLARITY | ON | ON or OFF
CABLEDETECT | ON | ON or OFF
ISAIRQ | AUTO |
PCIIRQ | AUTO |
NOPOLL | ACTIVE |
MEMORY | AUTO | hardware dependent
IOADDRESS | AUTO | hardware dependent
IRQ | AUTO | 3 - 15
SOCKET | AUTO | hardware dependent
MODE | MEM | IO or MEM
NOCHECK | ACTIVE |
NOLED | ACTIVE |
TXBUFFERSIZE | 2 | 1 - 10
RXBUFFERSIZE | 15 | 1 - 30
ERT | HIGH | LOW, MEDIUM, or HIGH
NOEARLYRX | ACTIVE |
NOEARLYTX | ACTIVE |
LINESPEED | AUTO | 10 or 100
LINEMODE | AUTO | HALF or FULL
LINKDISABLE | ACTIVE |
NOBURST | ACTIVE |
LATENCY | 32 | 0 - 256
CACHE | 8 | 0, 4, 8, 16, or 32
NOWRITEPOST | ACTIVE |
NOPREFETCH | ACTIVE |
VERBOSE | OFF |

Packet Driver Settings (for driver XCEMPD.COM)

Packet driver parameters must be stated on the XCEM PD.COM command line when running the packet driver.

Packet Driver Configuration Notes

The Xircom packet driver XCEMPD.COM conforms to FTP Software's public domain packet-driver specification. It is a DOS-based terminate-and-stay-resident (TSR) program. The driver file XCEMPD.COM is located in the \PKTDRV directory on the Xircom CD-ROM.

Refer to your network documentation for instructions on how to install the packet driver with your network. Most installations should be able to use the default settings listed below.

Keywords are not case sensitive, and can be abbreviated to a unique sequence of initial characters (for example, IN for INTERRUPT).

Packet Driver Keywords (XCEMPD.COM)

Keyword | Default | Valid Values
AUTOPOLARITY | ON | ON or OFF
CABLEDETECT | ON | ON or OFF
ISAIRQ | AUTO |
PCIIRQ | AUTO |
NOPOLL | ACTIVE |
MEMORY | AUTO | hardware dependent
IOADDRESS | AUTO | hardware dependent
IRQ | AUTO | 3 - 15
SOCKET | AUTO | hardware dependent
MODE | MEM | IO or MEM
NOCHECK | ACTIVE |
NOLED | ACTIVE |
TXBUFFERSIZE | 2 | 1 - 10
RXBUFFERSIZE | 15 | 1 - 30
ERT | HIGH | LOW, MEDIUM, or HIGH
NOEARLYRX | ACTIVE |
NOEARLYTX | ACTIVE |
LINESPEED | AUTO | 10 or 100
LINEMODE | AUTO | HALF or FULL
LINKDISABLE | ACTIVE |
NOBURST | ACTIVE |
LATENCY | 32 | 0 - 256
CACHE | 8 | 0, 4, 8, 16, or 32
NOWRITEPOST | ACTIVE |
NOPREFETCH | ACTIVE |
SINT | 60 | (60 - 80)
VERBOSE | NOT PRESENT |

Packet Driver Example

A typical sequence for loading the packet driver XCEMPD.COM and default configuration settings is as follows:

>     XCEMPD
>     ETHDRV

If configuration settings other than the defaults are required, these must be stated on the XCEMPD.COM command line. For example,

>     XCEMPD IOADDRESS=320 INT=7
>     ETHDRV

#### Windows 3.x Modem Configuration Notes

The Xircom Ethernet 10/100+Modem 56 doubles as a LAN card and fax/modem. As a modem, the Ethernet 10/100+Modem 56 features Hayes and Microcom compatibility and the latest in data transmission, data compression, and error control techniques. It can be used with most standard communications and fax software packages.

The Xircom Ethernet 10/100+Modem 56 requires that a modem driver (CMENABLE.COM) be loaded before the modem can be used. By default, the Xircom Installation Program installs both the modem driver CMENABLE.COM and a LAN driver (XCEMODI or XCEMNDIS). To use either the modem alone, reboot and load only the modem driver CMENABLE.COM.

For detailed modem command information, see AT Commands.

Using Modem Communications Only under Windows 3.x

If you want to use the modem under Windows 3.x without loading a network driver, reboot the computer and run the modem driver CMENABLE.COM (found in the root directory of the Xircom CD-ROM) from the DOS prompt before launching Windows or your communications program:

> CMENABLE

Installing Communications and Fax Software

The Ethernet 10/100+Modem 56 is compatible with most popular communications and fax software packages. See the directory \SCRIPTS on the Xircom CD-ROM for configuration assistance.

Running Windows Communications and Fax Software

Windows 3.x-based fax and communications programs can be started immediately once the modem has been initialized.

Running DOS Communications and Fax Software

DOS-based communications software should be run from a DOS prompt without Windows loaded. DOS software can also be run in a DOS box with Windows loaded.

Automatic COM Port Detection

The Ethernet 10/100+Modem 56 modem driver will automatically configure a COM port on the system. The driver scans the BIOS table for the first unused COM port, then checks to see if the corresponding IRQ is in use. If it is, it moves to the next available COM port.

This process takes precedence over the network resources. If you specify a network IRQ that is the same as the first available COM IRQ (3 or 4), the driver will respond with an error.

To force a COM port, use the COMx keyword described in the following heading. If you do not want a COM port, add the NOCOM keyword to your configuration file or command line.

Manually Setting COM Port

Use the COMx keyword to manually specify which COM port the Ethernet 10/100+Modem 56 should use when providing serial port emulation for modem operations. Values for x can be 1, 2, 3, or 4. Each of these settings also activates a specific set of predefined values for I/O address and interrupt level, as follows:

PORT | IRQ | IOADDRESS
COM1 | 4 | 03F8
COM2 | 3 | 02F8
COM3 | 4 | 03E8
COM4 | 3 | 02E8

Do not select a COM port that is currently used by any other system device, such as the PC Card interface itself, or a mouse or trackball.

Configure your communications software to the COM port you selected with the COMx keyword.

Windows 3.x Modem Driver Settings

The modem driver CMENABLE.COM searches for an available COM port or one specified by the user and configures the Xircom hardware accordingly.

Modem Driver Configuration Notes

If you want to use the modem alone, load the modem driver CMENABLE.COM, supplied on the Xircom CD-ROM, without loading a network driver such as XCEMNDIS or XCEMODI (the Xircom Installation Program loads both modem and LAN drivers by default).

Reboot the computer and run CMENABLE.COM from the DOS prompt before launching Windows or a communications program.

CMENABLE.COM Keywords

Keyword | Valid Values
CACHE | 0, 8, 16, or 32
COMx | Auto, 1-4
IOADDRESS | Hardware dependent
IRQ | 3 - 15
LATENCY | 0 - 255
MEMORY | Hardware dependent
NOCHECK | No value required
VERBOSE | No value required

### General Troubleshooting Checklist

If you encounter problems with the Xircom RealPort Ethernet 10/100+Modem 56 after installation, try the following general troubleshooting measures before contacting Customer Support.

- When loading drivers or running the test utility, keep the LAN adapter cable attached to the Xircom adapter.
- In a network environment, try connecting the Xircom 10/100 Network + 56K Modem PC Card directly to the hub or concentrator.
- Plug in to a known working network connection.
- Try using the Xircom adapter on a different computer.
- Try another Xircom adapter if available.
- Make sure that the interrupt, memory address, and I/O address for the Xircom device do not conflict with other installed hardware (such as sound cards and CD-ROM drives).
- Try loading the drivers at different memory locations (i.e.: C800, CC00, D400, D800).
- Try using different interrupt locations (i.e.: 5, 10, 11).
- Try using different port addresses (i.e.: 280, 290, 310, 320).

## Driver Keywords Alphabetical Reference

AUTOPOLARITY allows autonegotiation of cable polarity to be turned off. Default is ON.

CABLEDETECT turns the automatic cable detect feature on or off. When on, cable detect senses when there is no LAN cable attached to the card, and puts the adapter into a low-power mode. Normal power is restored when the cable is reattached.

DYNAMICLINKDETECT determines whether the network cable must be attached for the driver to load, and whether the driver detects cable removal and insertion. When set to OFF, the driver will fail to load if the network cable is not attached (and a link is not detected) at startup. When ON (default), the driver will load at startup and network cable removal and insertion will be detected at any time. Turn this parameter OFF if you are experiencing TCP/IP problems when using Dial-Up Networking.

EARLYRECEIVE turns the Xircom Advanced Look-ahead Pipelining feature on or off. Can be used to troubleshoot network problems. Use of this keyword may negatively impact performance.

EARLYTRANSMIT turns the early transmit feature on or off. Can be used to troubleshoot network problems. Use of this keyword may negatively impact performance.

INTERRUPTNUMBER specifies a hardware interrupt for use by the adapter.

INTERRUPTSTYLE forces the driver to use ISA IRQ routing or PCI IRQ routing. Some bridges have the capability of supporting both PCI and ISA style IRQ routing. Valid parameters are AutoDetect, PCI-IRQ, and ISA-IRQ.

IOBASEADDRESS specifies the base I/O address of the Xircom adapter I/O ports, in hexadecimal notation. The Xircom adapter requires 128 contiguous I/O addresses if run in I/O mode. If using memory-mapped I/O mode, no I/O ports are necessary. If not used, driver will detect an I/O port automatically.

LINEMODE selects either half-duplex or full-duplex mode for the network. Valid parameters are AutoDetect, Half-Duplex, and Full-Duplex. Selecting full-duplex enables the Ethernet 10/100+Modem 56 to send and receive data simultaneously when connected to a full-duplex hub.

LINESPEED forces operation to 10 or 100Mbps. Valid parameters are AutoDetect, 10Mbps, and 100Mbps.

LINKINTEGRITY can be used to turn link integrity off for non-IEEE 10Base-T networks. Default is ON.

MEMORYBASEADDRESS specifies the host PC memory location for the Xircom adapter in hexadecimal notation, when MODE MEMORY (memory-mapped I/O) is being used (see MODE).

MODE when set to IO disables requests for memory-mapped mode on systems that only support an I/O-driven card. The MEMORY setting provides increased performance on computers that allow simultaneous availability of memory and I/O resources.

NDISVERSION allows automatic NDIS version selection for installs under Windows 2000, 98, and 95. AutoSelect (the default) will choose the highest NDIS version supported by the operating system. 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 required driver. Only drivers supported by the operating system will be shown. NDIS driver selection is not supported by Windows NT 4.0. The NDIS4 driver can be installed by default from the root of the Xircom compact disc.

NETWORKADDRESS can be used to override the adapter's unique network node address by specifying a different node address.

> Caution: The NETWORK ADDRESS setting should be modified only by a network administrator.

PACKETPRIORITY enables support of priority-tagged frames, which are frames that carry an IEEE 802.1p user priority value in their MAC header. It is supported only under Windows 98 Second Edition and Windows 2000, and only with the NDIS5 driver. If set to ON under NDIS3 or NDIS4, it will be automatically reset to OFF and the computer will restart.

RXBUFFERSIZE sets size of the adapter receive packet buffer. This is a decimal number in the range 1 - 100. Each packet adds approximately 1520 bytes to the resident size of the driver.

SOCKET identifies the number of the host computer's PC slot or socket into which the Xircom adapter is inserted. Valid parameters are AutoDetect, 1, 2, and 3. If a socket number is specified, only the specified socket is checked for the Xircom adapter. Under AutoDetect, the driver will automatically check all slots for the Xircom adapter.

TXBUFFERSIZE sets the size of the adapter transmit packet buffer. This is a decimal number of transmit packets in the range 1 - 100. Each packet adds approximately 1520 bytes to the resident size of the driver.

Table of Contents | Previous Page | Next Page