Copyright: ©1998, Xircom, Inc. 3x REM/CEM 11 Nov 1998


Installation under Microsoft Windows 3.x

Running the Xircom Installation Program

1	With Windows running, insert the Windows 3.x Installation Disk into your disk drive.

2	From the Program Manager, choose File, then Run. In the Command Line box, type the following:

A:INSTALL

3	Press Enter or click OK.

4	Make a selection from the list displayed and follow the on-screen instructions.


Windows 3.x Modem Configuration Notes

The Xircom RealPort Ethernet 10/100+Modem 56 doubles as a LAN card and fax/modem. As a modem, the RealPort 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.

Note

Unless Card and Socket Services are being used under Windows 3.x, the Xircom RealPort Ethernet 10/100+Modem 56 requires that a LAN+modem driver (XCEMODI.COM, XCEMNDIS.EXE, or XCEMPD.COM) or a modem-only driver (CMENABLE.COM) be loaded before the modem can be used.

For modem command information, see the Help file HELPDOCS.HLP on the Windows 95/98/NT Installation Disk.

Using Network or Modem Communications under Windows 3.x

All Xircom Windows 3.x network drivers initialize both the LAN and the modem. When a network driver is loaded, the modem driver is automatically initialized.

Using Modem Communications Only under Windows 3.x

If you want to use the modem under Windows 3.x without loading a network driver, and you are NOT using Card and Socket Services, reboot the computer and run the utility CMENABLE.COM (found in the root directory of Xircom the Network Drivers Disk) from the DOS prompt before launching Windows or your communications program:

CMENABLE

Installing Communications and Fax Software

The RealPort Ethernet 10/100+Modem 56 is compatible with most popular communications and fax software packages. See the directory \SCRIPTS on the Network Drivers Disk 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.

COM Ports, IRQs, and I/O Base Addresses

Automatic COM Port Detection

RealPort Ethernet 10/100+Modem 56 drivers 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, Interrupt, and I/O Address Values

Use the COMx keyword to manually specify which COM port the RealPort 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.

Note

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

By default the LAN drivers will select the first open COM port. You can add the COMx keyword and a port number to the LAN driver configuration to activate serial port emulation. The COMx keyword can also be stated on the command line with the modem-only driver CMENABLE.COM.

Use the keywords COMIRQ and COMBASE to override the values set with COM1, COM2, COM3, or COM4 in case of a conflict between LAN and modem settings.

Sample NET.CFG File (ODI Driver) with COM Port Setting

link driver xpsodi

Int 10

port 280

mem d2000

com3

Sample PROTOCOL.INI (NDIS Driver) with COM Port Setting

[XIRCOMNET]

  DRIVERNAME=XIRCOM$

  IRQ=10

  IOADDRESS=0x320

  MEM=0xD2000

  MODE=IO

  COM4

Sample Packet Driver Command Line with COM Port Setting

XCEMPD COM3 MEM=D8000

Sample CMENABLE.COM Command Line

CMENABLE COM3 MEM=D8000

Changing Interrupt or I/O Address Settings

The COMIRQ keyword is used to override the predefined interrupt value for a specific COM port in case of a conflict between LAN and modem settings. It can also be used with COMBASE to select a user-defined COM port. Default is keyword not used. Setting is a decimal value which must be different from the value used with the INTERRUPT keyword.

The COMBASE keyword can be used to override the predefined I/O port value for a specific COM port in case of a conflict between LAN and modem settings. It can also be used with COMIRQ to select a user-defined COM port. The default condition is "keyword not used." Parameter setting is a hexadecimal value in the range 248 to 3F8 which must be different from the value used with the IOADDRESS or PORT keyword. Serial emulation mode requires 8 addresses.

The SHAREIRQ keyword is only valid when no Card Services are being used. It instructs the driver that the modem and LAN interfaces must share the IRQ line. State this keyword to configure the interface for one physical IRQ and one logical IRQ, instead of the two separate physical IRQs normally used by the PC Card controller.

Preventing Memory Conflicts

Memory allocation conflicts can cause the Xircom driver to fail to load. The RealPort Ethernet 10/100+Modem 56 requires an 8K memory block located between C000 and EFFF, with a default starting address of D2000.

Some computers require that a different address be used. To change the memory address at which the Xircom driver loads, use the MEMORY or MEM keyword in the driver configuration file or on the driver command line.

Memory Manager Exclusions

When using a memory manager such as EMM386, the memory manager will try to control the upper memory blocks where the Xircom driver normally loads. To prevent conflicts, add a statement to the EMM386 command line excluding an 8K memory block between C000 and EFFF for the Xircom driver. For example,

device=c:\path\EMM386.EXE NOEMS X=CC00-CDFF

Here are some examples of MEMORY keyword settings and the corresponding 8K exclusion:

Configuration	Keyword Setting	Exclusion

NET.CFG	MEM CC000	X=CC00-CDFF

PROTOCOL.INI	MEMORY=D4000	X=D400-D5FF

Command Line	MEMORY=C8000	X=C800-C9FF

Notes

Memory settings used to configure the RealPort Ethernet 10/100+Modem 56 always use 5 digits. Memory settings on the EMM386 command line only require 4 digits.

With Card and Socket Services, the memory exclusion is generally much larger than that required without them. This exclusion range should not be reduced.

Windows and EMM386

If you are using EMM386 and Windows, you should add an EMMEXCLUDE= line to the [386enh] section of the SYSTEM.INI file. The exclusion range should match the exclusion on the EMM386 line.

If you are not using EMM386, but are using Windows, then you MUST add an EMMEXCLUDE= statement to the [386enh] section of the SYSTEM.INI file. The exclusion range must match the memory window the RealPort Ethernet 10/100+Modem 56 is using.


Windows 3.x Modem Driver Settings

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

Modem Driver Configuration Notes

If you want to use the modem without loading a network driver, and you are not using Card and Socket Services (or the equivalent under Microsoft Windows 95 or NT, you have to load the modem driver CMENABLE.COM, supplied on the Network Drivers Disk. (If you load a network driver such as XCEMNDIS, XCEMODI, or XCEMPD, you do not need CMENABLE.COM because the network drivers also initialize the modem.)

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

CMENABLE.COM Keywords

Keyword	Default	Valid Values

COMx 	AUTO	(x = 1, 2, 3, or 4)

COMIRQ=	Not used	(3 to 15)

COMBASE=	Not used	(0x248 to 0x3F8)

IOWAITSTATES=	Auto	(1, 2, or 3)

MEMORY=	0xD2000	(0xC0000 to 0xE0000)

MEMWAITSTATES=	Auto	(1, 2, or 3)

SLOT=	Auto	(hardware dependent)

OFF	Not used	(disables CMENABLE)

Modem Driver Example

A typical sequence for loading the modem driver CMENABLE.COM with default configuration settings is as follows:

CMENABLE.COM COMx

where COMx is a COM port value such as COM3 or COM4. If other nondefault configuration settings are used, these must also be stated on the CMENABLE.COM command line. For example,

CMENABLE COM4  COMBASE=0x320 COMIRQ=10

Windows 3.x Network Driver Parameters

The following paragraphs present configuration guidelines for each of the driver types: NDIS, ODI, and packet. These guidelines are followed by a comprehensive "keyword" reference section and a list of error messages.

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.

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 Network Drivers Disk and must be present in the same directory as the ODI driver. Files required for using XCEMODI.COM are

XCEMODI.INS	Xircom installation information file

NET.CFG	Network configuration file

XCEMODI.COM	Xircom ODI driver

Most installations will be able to use the settings detected by the 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. Keyword syntax can be found below. Keywords are not case sensitive. A Keyword Alphabetical Reference follows the discussion of keyword syntax.

NET.CFG Example

 link driver xcemodi

 	int 5

  	port 280

  	mem D2000

XCEMODI.COM Keywords

Keyword	Default	Valid Values

COMx 	AUTO	(x = 1, 2, 3, or 4)

COMIRQ=	AUTO	(3 to 15)

COMBASE=	AUTO	(0x248 to 0x3F8)

INTERRUPT	AUTO	(3 - 15)

IOADDRESS 	AUTO	(100 - FF0)

IOWAITSTATES	0	(1 - 3)

LINESPEED	auto	(10 or 100)

LINKDISABLE	(no keyword = link integrity enabled)

LINK DRIVER XCEMODI (required first item in NET.CFG)

MEMORY 	AUTO	(C0000 - EE000)

MEMWAITSTATES	0	(1 - 3)

MODE	MEM	(MEM or IO)

NOCHECK	(no keyword = adapter resource veri-	fication enabled)

NOCOM	(no keyword = MODEM enabled)

NOEARLYRX	(no keyword = early receive enabled)

NOEARLYTX	(no keyword = early transmit enabled)

NOLED	(no keyword = LEDs enabled)

S	(command line only: show resident LAN 	drivers)

SHAREIRQ

SOCKET 	Auto	(1 - 4)

U	Not used	(command line only: 	unload XCEMODI)

WORDSIZE	16	(8 or 16)

ODI Driver Example

A typical load sequence for the ODI driver XCEMODI.COM in a NetWare environment would be

LSL

XCEMODI

IPXODI

VLM

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 XCEMNDIS.EXE conforms to the Microsoft 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 Network Drivers Disk.

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

Most installations will be able to use the settings detected by the 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). A Keyword Alphabetical Reference follows the keyword listings.

PROTOCOL.INI Example

[XIRCOMNET]

 DRIVERNAME=XIRCOM

 MEM=0xD2000

 MODE=IO

NDIS 2.0.1 Keywords (XCEMNDIS.EXE)

Keyword	Default	Valid Values

COMx 	AUTO	(x = 1, 2, 3, or 4)

COMIRQ=	AUTO	(3 to 15)

COMBASE=	AUTO	(0x248 to 0x3F8)

DRIVERNAME=XIRCOM$ (required first item in PROTOCOL.INI)

INTERRUPT=	AUTO	(3 - 15)

IOADDRESS= 	AUTO	(100 - FF0)

IOWAITSTATES=	0	(1 - 3)

LINESPEED=	auto	(10 or 100)

LINKDISABLE	(no keyword = link integrity enabled)

MEMORY=	AUTO	(C0000 to EE000)

MEMWAITSTATES=	0	(1 - 3)

MODE=	MEM	(MEM or IO)

NOCHECK	(no keyword = adapter resource veri	fication enabled)

NOCOM	(no keyword = MODEM enabled)

NOEARLYRX	(no keyword = early receive enabled)

NOEARLYTX	(no keyword = early transmit enabled)

NOLED	(no keyword = LEDs enabled)

SHAREIRQ

SOCKET= 	Auto	(1 - 4)

WORDSIZE=	16	(8 or 16)

Packet Driver Settings (for driver XCEMPD.COM)

Packet driver parameters must be stated on the XCEMPD.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 Network Drivers Disk.

Refer to your network documentation for instructions on how to install the packet driver with your network.

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

Packet Driver Keywords

Keyword	Default	Valid Values

COMx 	AUTO	(x = 1, 2, 3, or 4)

COMIRQ=	AUTO	(3 to 15)

COMBASE=	AUTO	(0x248 to 0x3F8)

INTERRUPT=	AUTO	(3 - 15)

IOADDRESS=	AUTO	(100 - FF0)

IOWAITSTATES=	0	(1 - 3)

LINESPEED=	auto	(10 or 100)

LINKDISABLE	(no keyword = link integrity enabled)

MEMORY=	AUTO	(C0000 - E8000)

MEMWAITSTATES=	0	(1 - 3)

MODE=	MEM	(MEM or IO)

NOCHECK	(no keyword = adapter resource veri	fication enabled)

NOCOM	(no keyword = MODEM enabled)

NOEARLYRX	(no keyword = earlyrx enabled)

NOEARLYTX	(no keyword = earlytx enabled)

NOLED	(no keyword = LEDs enabled)

SHAREIRQ

SINT	60	(60 - 80)

SOCKET=	Auto	(1 - 4)

WORDSIZE=	16	(8 or 16)

Packet Driver Example

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

XCEMPD

ETHDRV

If nondefault configuration settings are used, these must be stated on the XCEMPD.COM command line. For example,

XCEMPD IOADDRESS=320 INT=7

ETHDRV


Driver Keyword Alphabetical Reference

?	displays a summary of command line options.

COMx 	specifies which COM port the RealPort 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 values instructs the driver to use pre-defined values for I/O address and interrupt level, and to enable the specified I/O address in the COM port BIOS table. The modem driver CMENABLE.COM defaults to COM3. Use the keywords COMIRQ and COMBASE to override the values set with COM1, COM2, COM3, or COM4 in case of a conflict between LAN and modem settings.

COMBASE	can be used to override the pre-defined I/O port value for a specific COM port in case of a conflict between LAN and modem settings. It can also be used with COMIRQ to select a user-defined COM port. Default is no keyword. Parameter setting is a hexadecimal value in the range 248 to 3F8 which must be different from the value used with the IOADDRESS or PORT keyword. Serial emulation mode requires 8 addresses.

COMIRQ	is used to override the pre-defined interrupt value for a specific COM port in case of a conflict between LAN and modem settings. It can also be used with COMBASE to select a user-defined COM port. Default is no keyword. Parameter setting is a decimal value which must be different from the value used with the INTERRUPT keyword.

FRAME	(ODI) designates support for multiple Ethernet frame types. One or more types can be used. Refer to your NetWare documentation for more information. The Xircom ODI driver's default frame type is 802.2, but the NET.CFG file supplied with the ODI driver on the Network Drivers Disk sets both 802.2 and 802.3. Therefore if your network's frame type is 802.3, you must use Xircom's NET.CFG with the ODI driver.

INTERRUPT	specifies a LAN interrupt to use. It requires a decimal value designating the PC Card port hardware interrupt (for example, INT 5 or INT 7). Default (if parameter not specified) is 5. Any value supported by the PC Card hardware can be used.

INTERRUPTNUMBER	See INTERRUPT.

IOADDRESS	specifies the LAN I/O address to use, in hexadecimal notation. Valid range is 100 - FF0.

IOBASEADDRESS	see IOADDRESS.

IOWAITSTATES	specifies the number of wait states that should be added to I/O accesses to the card. Values are a decimal number from 1 to 3. On some machines it may be necessary for the driver to run with I/O waitstates. By default, the driver will attempt to automatically configure this parameter. The keyword is provided as a troubleshooting aid.

LINKINTEGRITY 	ON or  OFF. See LINKDISABLE.

LINKDISABLE	disables the link integrity check on the network twisted pair cabling (for operation with non-IEEE 10BASE-T networks such as StarLAN 10). Without the LINKDISABLE keyword in the driver command line, the driver defaults to link integrity ENABLED.

MEMORY	specifies the memory location to use. It is specified in hexadecimal notation and is not a segment value. Specify the full address for all drivers. For example, D2000, not D200. The RealPort Ethernet 10/100+Modem 56 uses 4 Kbytes of memory (1000 hexadecimal) for the LAN. Use the MODE IO setting to disable MEMORY MODE. Default is D2000. Possible values are C0000 through E0000.

MEMORYBASEADDRESS	see MEMORY.

MEMWAITSTATES	specifies the number of wait states that should be added to memory accesses to the card. Values are decimal 1 to 3. On extremely fast machines it may be necessary for the driver to run with waitstates. By default, the driver will attempt to automatically configure this parameter. The keyword is provided as a troubleshooting aid.

MODE	specifies whether to run the network in memory-mapped or I/O mode. Values are the ASCII strings MEMORY or IO. The default setting is MEM. Set this keyword to IO to disable requests for memory-mapped mode on systems that only support an I/O driven card.

NOCHECK	disables verification of adapter resources. This keyword is intended to be used as a troubleshooting tool.

NOCOM	the RealPort Ethernet 10/100+Modem 56 driver will configure a COM port by default. The NOCOM keyword can be used to defeat this feature. If the keyword is not used, the modem is enabled. LAN operations are not affected.

NOEARLYRX	disables Advanced Look-ahead Pipelining features of the Xircom RealPort Ethernet 10/100+Modem 56. You may need this keyword for NDIS version 2.01 drivers which do not fully support the "early RX" feature.

NOEARLYTX	disables early transmit features of the Xircom RealPort Ethernet 10/100+Modem 56. Try using this keyword if you are experiencing a large number of transmit overruns.

NOLEDS	turns off network LED indicators on LAN adapter cables to conserve battery power.

PORT	(ODI) specifies the LAN I/O address to use, in hexadecimal notation. Default address is 320.

SHAREIRQ	is optional when no Card Services are being used. It instructs the driver that the modem and LAN interfaces must share the IRQ line. State this keyword to configure the interface for one physical IRQ and one logical IRQ, instead of the two separate physical IRQs normally used by the PC Card controller.

SINT	(Packet Driver) is number from hexadecimal 60 to 80 designating a software interrupt. Default is 60.

SLOT	Same as SOCKET but used with CMENABLE.COM.

SOCKET	forces the driver to look in the selected socket specifically for a Xircom RealPort Ethernet 10/100+Modem 56. If no keyword is stated, the driver will scan all PC Card slots looking for the right card. Valid values are from 1 to the number of PC Card slots supported by the computer being used. This keyword may be useful if you have a memory card or other PC Card device in socket 1 and a RealPort Ethernet 10/100+Modem 56 in socket 2. Then set the keyword to SOCKET=2 in your configuration file or on the command line.

WORDSIZE	this parameter specifies the size of the data path for the LAN controller. Values are 8 or 16 decimal. Default is 16. Since the modem always uses an 8-bit data path, this keyword does not affect the modem.


Error Messages for Windows 3.x Drivers

Except as noted, these messages are specific to the Xircom RealPort Ethernet 10/100+Modem 56. For an explanation of other messages that may appear on the screen, see your computer and network operating system documentation.

A PCMCIA card was not detected

If the SOCKET keyword was stated, then no PC Card was detected in the slot specified. If the SOCKET keyword was not used, then no PC Card was detected in any slot.

An invalid I/O address was specified

The Xircom RealPort Ethernet 10/100+Modem 56 requires 32 consecutive I/O locations. This message indicates that the I/O address specified does not start on a 32-byte boundary. Examples of valid I/O addresses, in hexadecimal notation, are 300, 320, 240. Examples of invalid I/O addresses are 301, 325, 247.

XCEMODI only supports the BUS ID PC Card, not the selected BUS ID. Either delete the BUS ID keyword from the NET.CFG file or change its value to 3.

This message applies only to the ODI driver. Do not use the keyword BUS ID in the ODI NET.CFG file. If you do use it, you must set the value to 3.

Network Controller running in 8-bit mode

The Network Interface Controller (NIC) has been forced to run in 8-bit mode with the keyword WORDSIZE set at 8 (default is 16-bit mode). This option is used when the PC Card hardware does not support 16-bit mode.

Network Controller running in I/O mode

The Network Interface Controller (NIC) has been forced to run in I/O-only mode with the keyword MODE set at IO (default is MEM). This option is used when the PC Card hardware does not support performance-enhancing memory-mapped I/O mode.

The card is unreadable, possible memory conflict

The Card Information Structure (CIS) of the PC Card was unreadable. This could be a result of failure to exclude the selected memory range from the memory managers loaded on the machine. Either exclude a 8K memory range, select a memory range that has already been excluded, or include the NOCHECK keyword in the configuration file.

Please specify a different interrupt for the modem

The LAN adapter and modem cannot be configured for the same interrupt. Either select a different modem interrupt (using the COMIRQ keyword or a different COM port value), or select a different LAN interrupt (using the INTERRUPT keyword).

The COMBASE keyword is required in this configuration

If the COMIRQ keyword has been specified, but COM1, COM2, COM3, or COM4 has NOT been specified, the COMBASE keyword must be specified with an appropriate value.

The COMIRQ keyword is required in this configuration

If the COMBASE keyword has been specified, but COM1, COM2, COM3, or COM4 has NOT been specified, the COMIRQ keyword must be specified with an appropriate value.

The Network Controller is not responding

A Xircom RealPort Ethernet 10/100+Modem 56 adapter was detected, but subsequent attempts to initialize the network controller failed. Try setting the WORDSIZE parameter to 8.

Please specify a decimal number for the INTERRUPT keyword

is displayed after the Performance Series Adapter error message.

Please specify a decimal number for the INTERRUPT keyword

This message applies only to the NDIS 2.0 Driver. The value specified under the INTERRUPT keyword in the PROTOCOL.INI file must be a decimal not a hexadecimal number.

Please specify a hexadecimal number for the IOADDRESS keyword

This message applies only to the NDIS 2.0 Driver. The value specified under the IOADDRESS keyword in the PROTOCOL.INI file must be a hexadecimal number.

Please specify a hexadecimal number for the MEMORY keyword

This message applies only to the NDIS 2.0 Driver. The value specified under the MEMORY keyword in the PROTOCOL.INI file must be a hexadecimal number.

Please specify either 8 or 16 for the WORDSIZE keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the WORDSIZE keyword in the NET.CFG or PROTOCOL.INI file must be either 8 or 16.

Please specify a nonzero decimal number for the SOCKET keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the SOCKET keyword in the NET.CFG or PROTOCOL.INI file must be a decimal number other than zero.

Please specify 0, 1, 2, or 3 for the MEMWAITSTATES keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the MEMWAITSTATES keyword in the NET.CFG or PROTOCOL.INI file must be either 0, 1, 2, or 3.

Please specify 0, 1, 2, or 3 for the IOWAITSTATES keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the IOWAITSTATES keyword in the NET.CFG or PROTOCOL.INI file must be either 0, 1, 2, or 3.

The memory test failed - Please select a different memory address

The memory test will write data into the memory, read them back, and verify if they are the same. In this case, the memory written and read back were found to be different.

The I/O test failed - Please select a different I/O address

The driver failed the I/O test. Try a different I/O address.

The IRQ test failed - Please select a different IRQ

The driver failed the IRQ test. Try a different IRQ address.

Please specify either IO or MEM for the MODE keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the MODE keyword in the NET.CFG or PROTOCOL.INI file must be either IO or MEM.

Please specify a decimal number for the COMIRQ keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the COMIRQ keyword in the NET.CFG or PROTOCOL.INI file must be a decimal number.

Please specify a hexadecimal number ending in 8 for the COMBASE keyword

This message applies to both the ODI and NDIS 2.0 drivers. The value specified under the COMBASE keyword in the NET.CFG or PROTOCOL.INI file must be a hexadecimal number in the range 248 to 3F8.

No standard COM ports available. Please use custom COM port (COMIRQ, COMBASE)

This message applies to both the ODI and NDIS 2.0 drivers. All COM ports (COM1 - COM4) are being used. Create a custom COM port by adding the COMIRQ and COMBASE keywords, with assigned values, to the NET.CFG or PROTOCOL.INI file.

The selected COM IRQ is in use by another device

The IRQ value set for the COM port is already in use by another device. Assign a different IRQ value for the COM port.

The selected COM port already exists

The COM port is already in use by another device. Assign a different I/O port for the COM port.


Utilities

This topic describes Windows 3.x (16-bit) software utilities and modem script files provided with the RealPort Ethernet 10/100+Modem 56.

Utilities

Xircom provides several utilities with the RealPort Ethernet 10/100+Modem 56 that run under Microsoft Windows or MS-DOS. The utilities are:

•	CountrySelect Utility

•	Dial-Up Product Registration

•	Modem Test

•	Diagnostic Test (MS-DOS prompt required)

•	Modem COM Port Monitor

•	Modem Script Files

The Windows utilities described in this topic are automatically copied to your hard drive and launched during installation of the RealPort Ethernet 10/100+Modem 56 when you run the Xircom Installation Program under Windows 3.1 or 3.11. Icons for these utilities are also installed in the Xircom program group set up at the time of installation.

CountrySelect Utility

The CountrySelectTM software is a Windows-based utility that enables the RealPort Ethernet 10/100+Modem 56 user to select a "country of installation" setting for modem communications. This setting enables the modem to function in accordance with the configuration requirements of a specific country.

How to Use CountrySelect

The CountrySelect software is automatically copied to your hard drive and launched during installation of the RealPort Ethernet 10/100+Modem when you run the Xircom Installation Program under Windows 3.1 or 3.11. An icon for CountrySelect is also installed in the Windows program group so that the software can be rerun if the country settings needs to be changed.

Follow the steps below to run CountrySelect from the Xircom program group if you need to modify the country setting chosen during the installation process.

1	Launch CountrySelect through Windows. Either double-click the CountrySelect icon in the Xircom program group containing the Windows 3.x 16-bit utilities, or use the Windows File/Run command sequence and type [path]TELSEL.EXE in the Command Line box, where [path] indicates the location of the CountrySelect software on your hard drive.

2	The current country setting is listed at the top of the screen, and the other countries supported are listed below. To change to a different country, locate the country on the list and double click. The application will verify that the country setting has been changed.

3	Click on Exit to close the program.

Product Registration (XREG)

Register your Xircom product and become eligible to receive notification of updates and new products. Registration also makes you eligible to receive future software updates free of charge.

In addition to registering electronically via modem, you can also print out and fax or mail the online registration form once it has been filled out. To register without using the electronic registration program at all, complete and mail the postpaid registration card provided with the product.

The Xircom Automated Product Registration software will load when you restart Windows or reboot the computer after running the Installation Program. Complete the information requested and follow the onscreen instructions to complete the registration using your RealPort Ethernet 10/100+Modem 56.

Modem Test Utility

The Xircom Modem Test utility indicates the status of the COM ports on your computer, including which COM port the Xircom modem is configured to use. The icon for this program will be installed in the Xircom program group containing the Windows 3.x 16-bit utilities at installation. Double-click the icon to run the Modem Test utility.

If a Xircom modem is enabled, the Modem Test utility can also be used as a terminal program to input AT commands to the modem without the use of other communications software. Click the Terminal button on the Modem Test screen to open a window for input of modem commands. See the Help file HELPDOCS.HLP on the Windows 95/98/NT Installation Disk for a complete list of modem commands supported by the RealPort Ethernet 10/100+Modem 56.

Diagnostic Test Utility (XCEMTEST.EXE)

Xircom provides a DOS-based self test diagnostics program. This program, located on the RealPort Ethernet 10/100+Modem 56 disk containing Windows 3.x network drivers, tests several adapter functions. It also reports test results, the serial number of the unit, and the node (or Ethernet) address.

XCEMTEST can only be run from an MS-DOS command line. Under Windows 95 and Windows NT, power down the computer perform a clean boot to the MS-DOS prompt (under Windows 95 press Shift+F5 at the message Starting Windows 95 . . . ).

The XCEMTEST utility is intended to be a diagnostic tool for troubleshooting configuration errors. Cards can be inserted and removed at any time. Multiple cards and different configurations can be tested.

Executing the Self Test

Use the following steps to execute the self test.

1	Install the RealPort Ethernet 10/100+Modem 56 according to the instructions for your operating system.

2	Power down and restart the computer from MS-DOS (use Shift+F5 in Windows 95). DO NOT load a network driver.

Note

Do not run XCEMTEST with a network driver loaded. Loading a network driver before running XCEMTEST may cause unpredictable results when exiting the test utility.

3	Run the diagnostic test by typing [path]XCEMTEST at the MS-DOS prompt, then press Enter. [path] can be either C:\XIRCOM\CEM56\XCEMTEST or A:\XCEMTEST.

Note

If an error message displays when you execute the self test, see Error Messages for Windows 3.x and MS-DOS .

Main Screen

The program consists of several function "buttons" and a view pane. Pressing or invoking a function will bring up the corresponding screen in the view pane. This view remains until another is selected. To exit XCEMTEST type 'x' or push the 'Exit' button.

When a function is active, the button appears to remain down or pushed. Once the button pops up, the function is completed and the screen is a passive results display.

There are nine functions which can be invoked by pushing the associated button on the main screen. A button can be pushed by pressing the highlighted letter indicated on the button, or by using the left mouse button. Each function is explained below.

TEST

This function uses the current configuration to initialize the adapter and verify it is powered on and properly seated in its slot. It displays the current setting and test result for each parameter. Parameters are configured through the CONFIGURE function described below. If a card is detected and initialized successfully, the CIS information is displayed.

A failure may indicate that service is required for the RealPort Ethernet 10/100+Modem 56. Contact Xircom Customer Support.

The CIS section displays the serial number of the unit, its manufacturing date and time, and its network node address. This data has been preprogrammed at the factory and cannot be altered.

Important

Write down the RealPort Ethernet 10/100+Modem 56 model and serial numbers and network node (Ethernet) address for reference.

Customer Support will ask you to supply the model and serial numbers when requesting assistance or warranty service from Xircom.

CONFIGURE

This function allows the user to set the parameters used for testing. The address mode can be set to Auto, Memory, or I/O. For Memory and I/O a hexadecimal address can be specified. The IRQ can be set to Auto, or IRQ. The IRQ selection can be used to force a particular interrupt. The network line speed and line mode can also be set from this function.

SOFTWARE

This function attempts to determine what software is currently loaded that could affect the operation of the card. It displays the current version of MS-DOS and Windows, and any Card and Socket Services available (under Windows 3.x or MS-DOS).

HARDWARE

This function attempts to determine if a RealPort Integrated PC Card Controller exists on the machine. It first checks for PCI BIOS extensions, and then it searches for any RealPort Integrated PC Card Controllers. If found it displays controller type, base I/O address, offset, number of the socket in which the RealPort Integrated PC Card is installed, and the PCI interrupt (if enabled by the BIOS)

NETWORK

This function enables the card on the Ethernet network and performs some diagnostics. It reports the operating mode and speed detected and monitors the network for traffic. Network traffic is shown on a graph. This graph provides a visual representation of the volume of traffic on the local area network (LAN). The Receive Statistics window displays the cumulative totals for received Packets, KBytes, and Errors.

RESOURCES

This function attempts to determine free resources that are available for use by the driver. It searches for memory, I/O, and IRQ.

ADVANCED

This function allows the user to set up advanced diagnostics.

ABOUT

This function displays the current version of the diagnostic program.

HELP

This function displays the help screen.

EXIT

This function exits the application.

COM Port Monitor (Windows 3.x only)

The Xircom COM Port Monitor XCOMMON is an onscreen LED program that runs under Microsoft Windows 3.1 and 3.11, and Windows for Workgroups 3.11. XCOMMON provides a simulated onscreen display of modem status LEDs such as those found on external modems. XCOMMON is copied to your hard drive when you install under Windows 95 or NT or when you run the Xircom Installation program.

How to Use XCOMMON

To launch XCOMMON, double-click on the XCOMMON icon in the Xircom program group containing the Windows 3.x 16-bit utilities or use the File/Run command in Program Manager. The XCOMMON window will be present on the desktop and within applications, and can be moved by dragging it with the mouse.

XCOMMON is configurable with COM ports 1-4. To configure with a specific COM port, click once on the XCOMMON window, and a dialog box will appear. Select a COM port and click OK.

The XCOMMON window contains the following LEDs:

Tx	Transmit

Rx	Receive

CTS	Clear to Send

CD	Carrier Detect

RI	Ring Indication

To exit the XCOMMON program, Shift+Click on the XCOMMON window, or click on the window to open the dialog box, then click on the EXIT button.

Modem Script Files

Note

The modem script files described below are intended to be used if (1) your software package does not already include a Xircom modem file and (2) you have tried a generic Hayes or Microcom configuration without success.

The file SCRIPTS.TXT, which can be found in the \SCRIPTS directory on the RealPort Ethernet 10/100+Modem 56 Xircom disk containing Windows 3.x drivers, includes instructions for setting up your RealPort Ethernet 10/100+Modem 56 with popular communications programs, using the modem scripts provided in the same directory.


IBM OS/2 Installation

Installing under IBM OS/2 (Warp 3.0 and 4.0) Using the NDIS or ODI Driver

This chapter contains information on how to install and configure the Xircom RealPort Ethernet 10/100+Modem 56 for systems running IBM OS/2 Warp versions 3.0 and 4.0.

Topics covered in this chapter are as follows:

•	Installation Steps for Warp 3.0 and 4.0 (NDIS Driver)

•	Installation Steps for Warp 3.0 and 4.0 (ODI Driver)

•	OS/2 NDIS 2.0.1 Driver Configuration Notes (XCEMNDIS.OS2)

•	OS/2 ODI Driver Configuration Notes (XCEMODI.OS2)

•	OS/2 Modem Configuration Notes

Xircom's RealPort Ethernet 10/100+Modem 56 includes NDIS2 and ODI drivers for OS/2. Currently, the RealPort Integrated PC Card is not supported using OS/2 Card and Socket Services. Therefore, in order to install the , RealPort Integrated PC Card driver in OS/2, OS/2's Card and Socket Services must be disabled. Follow IBM's instructions for disabling Card and Socket Services.

Installation Steps for Warp 3.0 and 4.0 (NDIS driver)

1	Remove OS/2's Card and Socket Services according to IBM's instructions.

By default, the RealPort Integrated PC Card  NDIS driver will be installed. If you wish to install the ODI client, the Novell Client installation program should be used. See the OS/2 ODI Client install section for instructions.

2	Run MPTS (Multi-Protocol Transport Services). For Warp 3.0, MPTS is on the desktop. For Warp 4.0, MPTS is in System Setup.

3	In the MPTS window, click Configure

4	In the Configure window, select the LAN adapter and protocols radio button, then click Configure.

5	In the LAPS Configuration window, in the Network Adapter section, click Other Adapter.

6	Set the path as A:\NDIS and click OK.

7	Back at the LAPS Configuration window, in the Network Adapter section, select Xircom 16-bit 10/100+Modem 56 by clicking on it and then clicking Add.

8	In the Protocols section, select the protocols you wish to use by clicking on the protocols and then clicking Add.

9	In the Current Configuration section, click Xircom 16-bit Ethernet 10/100+Modem 56 and click edit to edit the driver settings.  The default settings for the product will be displayed. Generally, the default settings should be used. The most important to check are INT and SOCKET. If there is a conflict, these should be adjusted using trial and error.

10	To specify the COM port used for the modem, enter YES in the appropriate "Emulate COM port X" field where X represents the COM port you wish to use. The port chosen must be available, i.e., not already assigned to a different serial device.

11	After reviewing the settings, click OK.

12	Click OK again

13	Click close

14	Follow the onscreen instructions to complete installation.

In Warp 4.0, a free interrupt can be found by running Hardware Manager (under System Setup). Under IRQ, look for a free one (the program shows which interrupts are being used).

Installation Steps for Warp 3.0 and 4.0 (ODI driver)

1	Remove OS/2's Card and Socket Services according to IBM's instructions.

2	In order to install Xircom's OS/2 ODI driver, the Novell NetWare Client for OS/2 installation disks are needed. Insert disk 1 of the OS/2 client installation disks (the  WSOS2_1 disk) in the floppy drive and run INSTALL.

3	In the NetWare Workstation for OS/2 Installation Utility window, click the Installation menu item and select the Requester on Workstation option.

4	In the 'Set Target Directory' Windows, set the destination directory (default is c:\netware) and click OK.

5	In the 'Requester Installation' window, select the the option 'Edit config.sys and copy all files' and click OK.

6	In the 'Step 1- choose the ODI LAN Driver' window, click the list box to display the list of LAN drivers. An Installation Message window will appear. Put the Xircom Network Drivers Disk in the floppy drive and click OK.

7	In the list box, enter XCEMODI.OS2 as the LAN driver to install, and click Continue.

8	The Installation Message window will reappear. Re-insert the NetWare Client disk in the floppy drive (disk WSOS2_1) and click OK.

9	Follow the onscreen instructions to complete the installation of the NetWare Client for OS/2 software.

OS/2 Modem Configuration Notes

If difficulties in accessing the modem are encountered, proceed as follows:

1	Edit the OS/2 CONFIG.SYS file.

2	Move the following driver references to the very end of the file.

DEVICE=C:\OS2\BOOT\COM.SYS

DEVICE=C:\OS2\MDOS\VCOM.SYS

3	Verify that the COM port chosen in the MTPS configuration window for the RealPort Ethernet 10/100+Modem 56 is not assigned to another serial device.


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 XCEMNDIS.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

XCEMOS2.NIF	Xircom installation file for Microsoft LAN Manager

XCEMNDIS.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	Default	Valid Values
COMBASE	AUTO	3F8,2F8,3E8,2E8
COMIRQ	AUTO	3-15
DRIVERNAME=	XIRCOM$	(REQUIRED FIRST ITEM IN PROTOCOL.INI)
IOADDRESS	AUTO	240 - 360
IRQ	AUTO	3 - 15
LINEMODE	AUTO	HALF, FULL
LINESPEED	AUTO	10 or 100
LINKDISABLE	AUTO
MEMORY	AUTO	C000 - EC00
MODE	MEM	IO or MEM
NOCHECK	AUTO	Yes, No
NOEARLYRX	AUTO	Yes, No
NOEARLYTX	AUTO	Yes, No
NOLED	ACTIVE	Yes, No
SHAREIRQ	AUTO	Yes, No
SOCKET	AUTO	1 - 2
TXBUFFERSIZE	2	1 - 20
VERBOSE	AUTO	Yes, No
WORDSIZE	16	0, 4, 8, 16, 32
OS/2 ODI Driver Configuration Notes

The OS/2 ODI driver XCEMODI.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 Requester for OS/2 networking client environment.

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

NET.CFG	Network configuration file

XCEMODI.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	Default	Valid Values
COMBASE	AUTO	3F8,2F8,3E8,2E8
COMIRQ	AUTO	3-15
IOADDRESS	AUTO	240 - 360
IRQ	AUTO	3 - 15
LINEMODE	AUTO	HALF, FULL
LINESPEED	AUTO	10 or 100
LINKDISABLE	AUTO	Yes, No
MEMORY	AUTO	C000 - EC00
MODE	MEM	IO or MEM
NOCHECK	AUTO	Yes, No
NOEARLYRX	AUTO	Yes, No
NOEARLYTX	AUTO	Yes, No
NOLED	ACTIVE	Yes, No
SHAREIRQ	AUTO	Yes, No
SOCKET	AUTO	1 - 2
TXBUFFERSIZE	2	1 - 10
VERBOSE	AUTO	Yes, No


English: Customer Support
Customer Support

Xircom offers an extensive family of service and support programs, including world-class phone support, software updates, plus 24-hour access to our BBS and World Wide Web site.

Warranty Service Procedures

For details on warranty coverage and service, see the printed User's Guide.

If you think there is a problem or defect with your Xircom product, your point of contact will be

In the U.S.A.

Xircom's Technical Support department at (805) 376-9200.

Outside the U.S.A.

Contact your local Xircom supplier or regional office.

Software and Driver Updates

World Wide Web

To download drivers (subject to the terms of the Xircom Software License Agreement) from the Xircom website, go to:

www.xircom.com

Bulletin Board System (BBS)

Set your modem to its maximum speed, no parity, 8 data bits, 1 stop bit to connect at up to 56,000 bps in U.S. and Europe, 33,600 bps elsewhere.

Americas Support

Xircom, Inc.

2300 Corporate Center Drive

Thousand Oaks, California 91320-1420

Direct Line to Customer Support

(805) 376-9200	Customer Support

(6 a.m. to 5 p.m. Monday through Friday U.S. Pacific time)

(805) 376-9100	Fax to Customer Support

Online or Automated Access (24 hours, 7 days)

(805) 376-9130	BBS (up to 33.6Kbps)

(805) 375-5280	BBS (up to 56Kbps)

cs@xircom.com	E-mail

www.xircom.com	World Wide Web

Europe, Middle East, Africa Support

Xircom Europe N.V.

King Square, Veldkant 39

2550 Kontich, Belgium

Direct Line to Customer Support

+32/(0)70 233 307	Telephone English language

+32/(0)70 233 852	Telephone Dutch language

+32/(0)70 233 851	Telephone French language

+32/(0)70 233 850	Telephone German language

(9:00 to 18:00 Monday through Friday)

+32/(0)70 233 306	Fax to Technical Support

Online or Automated Access (24 hours, 7 days)

+32/(0)70 233 163	BBS (up to 56Kbps)

eurots@xircom.com	E-mail

Asia Pacific Support

Xircom Asia Pacific (Pte) Ltd.

76 Shenton Way

Unit #06-01

Singapore 079119

+65 323 3404	Customer Support

+65 224 3313	Fax

+65 323 0455	BBS (up to 33.6Kbps)

asiats@xircom.com	E-mail

Xircom Australia

Level 15, 99 Walker Street

North Sydney, NSW

Australia  2060

+61 (02) 9911 7794	Customer Support

+61 (02) 9911 7796	Fax

+61 (02) 9911 7758	BBS (up to 33.6Kbps)

aunzts@xircom.com	E-mail

Japan Support

Xircom Japan KK

TOHTAM Building 2F

3-10-5 Shibuya, Shibuya-ku

Tokyo 150-0002 Japan

+81-3-3407-1900	Customer Support

+81-3-3407-0180	Fax

Additional International Access

Contact your local reseller or distributor

www.xircom.com	World Wide Web

Please fill out and return the Product Registration Card supplied with the product. Your information will be entered into our support database.


English: Software License Agreement
Software License Agreement

Xircom grants you a non-exclusive license to use the copies of software programs supplied with this product on the following terms:

You may:

a	Use the software program on any computer or network but only in conjunction with any Xircom hardware product;

b	Permit any other individuals to use the software program either directly or on a computer network, but only if there is no more than one user for each Xircom hardware product in use in conjunction with such use;

c	Make only those number of backup and archival copies of the software program in machine readable form as are essential to backup use of the software program, provided that you reproduce all proprietary notices on each copy.

You may not:

a	Modify, translate, reverse engineer, decompile, disassemble, create derivative works based on, or copy (except for archival purposes) the program or the accompanying documentation;

b	Rent, transfer, sublicense or grant any rights in the program or accompanying documentation (including any time-sharing arrangement) in any form to any other person without the prior written consent of Xircom;

c	Remove any proprietary notices, labels, or marks on the program and accompanying documentation.

Failure to comply with any of the above restrictions will terminate this license. This is not a sale. Title and copyrights to the program and accompanying documentation and any copies remain with Xircom, except that title to software programs shipped by Xircom through an agreement with another manufacturer is owned and retained by the original manufacturer, and no title to the intellectual property contained in such programs is transferred hereunder. The human readable code of the software program (source code), including the source code of programs shipped by Xircom through an agreement with another manufacturer, is not sublicensed hereunder.

U.S. Government Restricted Rights

The SOFTWARE and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (c)(1) and (c)(2) of the Commercial Computer Software-Restricted Rights at 48 CFR52.227-19, as applicable. Contractor/manufacturer is Xircom, Inc., 2300 Corporate Center Drive, Thousand Oaks, CA 91320-1420.

This Agreement is governed by the laws of the State of California.


Windows 3.x Help Documents

The information and instructions in this HELP file are valid for the following Xircom products: RealPort Ethernet 10/100+Modem 56, RealPort Ethernet+Modem 56, CreditCard Ethernet 10/100+Modem 56. For modem reference information, see the file HELPDOCS.HLP on the Windows 95/98/NT Installation Disk.

Windows 3.x Installation and Troubleshooting

Windows 3.x Installation

Windows 3.x Driver Settings

Windows 3.x Modem Configuration Notes

Keyword Alphabetical Reference

Windows 3.x Error Messages

IBM OS/2 Installation and Configuration

IBM OS/2 Installation

IBM OS/2 Configuration Reference

Utilities

Utilities

Appendixes

Customer Support

Software License Agreement