Table of Contents | Previous Page | Next Page

Xircom Ethernet PC Card
Troubleshooting

• Configuration Reference
• General Troubleshooting Checklist
• Keyword Alphabetical Reference

Configuration Reference

Configuration notes are available for the following operating systems:

• Windows 2000
• Windows 98 and 95 
• Windows NT 4.0
• Windows 3x
• IBM OS/2

Windows 2000 Troubleshooting

Upgrading your Windows 2000 drivers

Windows 2000 RC2 contains built-in drivers for the Xircom RealPort Ethernet 10/100, CreditCard Ethernet 10/100, and CreditCard Ethernet 10, as well as many other Xircom PC Cards. The built-in drivers are functional but may lack some features of later releases To update the Windows 2000 driver do the following:

1. With your Xircom PC Card already installed and inserted, go to Start, Settings, Control Panel, double-click on Network and Dial-up Connections, and double-click on Local Area Connection. Select Properties.
2. Click the Configure button on the top of the Local Area Connection Properties screen, just under the "Connect using" listing for the Xircom CreditCard Ethernet Adapter 10/100. Next select the Driver tab, and click the Update Driver button. This starts the Upgrade Device Driver Wizard. Click Next. On the next screen select "Search for a suitable driver for my device (recommended)". Click Next. On the Locate Driver Files screen, select "Specify a location", and click Next. Enter the path to the Xircom compact disc (for example, if your CD-ROM drive is E, type "E:\").
3. The Wizard will announce that it has a suitable driver already installed, and that it has also found other drivers suitable for this device. Select the "Install one of the other drivers" check box and click Next. You will then see a screen showing both the Microsoft-supplied driver, and the new Xircom driver (identified as Xircom Ethernet Adapter 10/100, and with a path listed to the Xircom compact disc). Pick the Xircom driver, and 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. Reboot the machine to utilize the new driver. Repeat step 1 above, click the Configure button, and select the Advanced tab to+ access the new driver settings. 

Windows 98 and 95 Troubleshooting

Network Installation

Review this section if any of the following problems occur:

• The Xircom Ethernet PC Card is not detected during installation.

• The Xircom Ethernet PC Card appears to have installed correctly but you cannot access network resources.

Use the following steps to verify that the PCMCIA Card Socket controllers are enabled.

1. In the Control Panel, double-click the System icon.

2. Click the Device Manager tab.

3. Under PCMCIA Socket, make sure that the PCMCIA Card Socket device is installed and that it is enabled. Disabled devices are indicated with a red “X.” To enable the PCMCIA Socket controller, go to Control Panel and double-click the PC Card (PCMCIA) icon. Follow the PC Card Socket Wizard instructions. When prompted to do so, shut down the computer (using the Windows Start/Shut Down procedure), turn it OFF, then turn it back ON after a few seconds. DO NOT use Ctrl+Alt+Del or the reset button to restart the computer

An exclamation mark (!) on a device usually indicates a resource conflict.

4. In Control Panel, double-click the System icon.

5. Click the Device Manager tab.

6. Highlight and double-click the Xircom Ethernet PC Card entry.

7. Select Properties, Resources. Remove the check mark from the Use Automatic Settings box. Highlight and double-click on the first memory range listed. Use the up or down arrow to adjust the memory range to 000D2000-000D3FFF. Click OK.

8. Double-click the second memory range listed. Use the up or down arrow to adjust the memory range to 000D4000-000D4FFF. Click OK.

9. Click OK again. Close the Resource Properties windows. When prompted to confirm that resources have been adjusted manually, select Yes. After the hour glass disappears (it may take a few seconds) verify that the exclamation mark is gone.

Any device attempting to use the same memory segments as another device will cause the card to fail initialization. Ideally there should be 12K of contiguous memory starting with the first 4K block following the video drivers, which typically load in the C0000-C7FFF range. This varies from computer to computer. The memory range identified for the Xircom card is any block in the C0000-E7FFF range. On many computers, use of the range D0000-DFFFF is optimal. Be aware that not all blocks of memory are available. 

Failure to access to network resources may be due to Windows network configuration issues.

1. In Control Panel, double-click the Network icon.

2. In the configuration window verify that the correct Network Clients are installed.
   

   • To install a Microsoft Network Client, click Add. Double-click Client. Under the Manufacturers list, select Microsoft. Double-click Client for Microsoft Networks.
   • To install a Novell Network Client, click Add. Double-click Client. Under the Manufacturer list, select Microsoft. Double-click Client for NetWare Networks.

3. In the configuration window verify that the correct Network Protocols are installed.
   

   • To install the native Microsoft Network Protocol, double-click Protocols. Click Add. Under the Manufacturers list, select Microsoft. Double-click NetBEUI.
   • To install the IPX/SPX compatible Protocol, double-click Protocols. Click Add. Under the Manufacturers list, select Microsoft. Double-click IPX/SPX compatible Protocol.

   If necessary, consult your network administrator for additional information regarding client and protocol configuration details.  

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

Default Settings and Configurable Parameters 

By default the Xircom Ethernet 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: CE3.SYS (NDIS3), CE3N4.SYS (NDIS4), and CE3N5.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:

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

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.

Windows NT 4.0 Troubleshooting

Network Installation

Windows NT 4.0 does not support plug and play resource assignment for the Xircom adapter. Default settings are specified by the installation files. If these settings do not work on your system, use the following general guidelines to assist you. Contact Xircom Customer Support if you are unable to resolve the issues.

Resource Conflict Symptoms

• After network installation the computer locks up on reboot.
• A Service Control message reports that a service or driver did not start.

• The Xircom card initializes properly, but another hardware device functions sporadically, the computer locks up randomly or exhibits very slow network performance.

The most likely cause of these symptoms is a resource conflict between the Xircom card and another hardware device. Interrupt conflicts are the most common. Open the Event Viewer to review errors encountered during the boot process (Start, Programs, Administrative Tools, Event Viewer). Double-click the bottom error message to start reviewing. Identification of the device or service that failed to start may help in pinpointing where the conflict lies.  

Error messages reporting that the driver failed to start because a device attached to the system is not functioning may not involve the Xircom card. For example, an error is sometimes displayed if a device not currently connected to the computer is still listed as an installed component.

Two items frequently in conflict with the Xircom card are:

Possible Solutions

Remove the card and reboot NT 4.0 normally. Click OK at message stating that a Service or Services failed to start. Use the following steps to evaluate assigned resources and settings:

1. Under the Device applet in the Control Panel verify that PCMCIA status is Started and the Startup setting is Boot. If it is not change it to start on Boot and then restart the computer.
2. Start Windows NT Diagnostics (Start, Programs, Administrative Tools).
3. Under the Version tab note the Service Pack level. The NT 4.0 version is displayed as follows:  
   Microsoft (R) Windows NT (TM) Workstation
   Version 4.0 (Build 1381: Service Pack x)
   If no service packs have been applied on Version 4.0, “(Build 1381: service pack X)” is displayed. Or service pack level 1, 2, 3, or 4 will display. Service Packs integrate software upgrades to your current system and are available from Microsoft.
4. Select the Resources tab. By default the IRQ levels in use are displayed. Verify that the IRQ assigned to the Xircom card is not in use by any other device. This list is not inclusive and may not be completely indicative of resources in use.

5. Click the I/O Port button. Verify that the I/O Port Address assigned to the Xircom card is not shared by any other device. I/O Port 0x280 is usually available. This is displayed as:
   0280 - 028E     CEM56     Bus 0     Type ISA
   For an I/O Port Address to be usable the entire I/O range must be available. For example, the above listed I/O range would be unusable if another device was using any I/O port within that range.

CE3N4.SYS (NDIS4) Settings for Microsoft Windows NT

CE3N4.SYS is an NDIS4 NIC driver. It conforms to the Microsoft Network Driver Interface Specification (NDIS). The CE3.SYS driver supports the networking environment in Microsoft Windows NT versions 3.5 and greater.

Windows NT Parameters

Under most circumstances it will not be necessary to make modifications directly to the registry. Incorrect settings can result in undesirable changes to the configuration of Windows NT. Consult Xircom Customer Support for assistance if you find it necessary to modify the registry.

The files necessary for using CE3N4.SYS include:

There are user-configurable parameters to the CE3N4.SYS driver which can be modified using the Network Control Panel built into Windows NT. This applet uses the OEMSETNT.INF file to set the corresponding parameters in the registry. The user-configurable parameters are as follows:  

Note: The network node address can be modified by manually editing the registry and adding the parameter ‘NetworkAddress’ with a hexadecimal string value, such as ‘0080C7112233’. If the user does NOT specify a ‘NetworkAddress’ then the CE3.SYS driver uses the network node address contained in the Xircom Ethernet PC Card Information Structure.

Windows 3.x Troubleshooting

This troubleshooting information is intended for users or network administrators who are already familiar with the Xircom Ethernet PC Card and its user documentation, and who have run into difficulties after having completed the appropriate installation and troubleshooting procedures for their operating environment.

Diagnostic Self Test (MS-DOS)

Xircom provides a DOS-based self test diagnostics program. This program, located on the Xircom CD-ROM, tests several Xircom Ethernet PC Card functions. It also reports test results, the serial number of the unit, and the node address. CE3TEST can only be run from an MS-DOS command line.

Executing the Self Test

Use the following steps to execute the self test.

1. Install the Xircom Ethernet PC Card according to the instructions contained in the Installation Guide and under the heading Windows 3.x Installation.

2. Start your computer from DOS. DO NOT load a network driver.
   Do not run CE3TEST with a network driver loaded. Loading a network driver before running CE3TEST may cause unpredictable results when exiting the test utility.

3. Run the diagnostic test by typing CE3TEST at the MS-DOS prompt, then pressing Enter.

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

Nine functions can be invoked by pushing the associated button on the main screen, using the highlighted letter indicated on the button, or the left mouse button. Online help is provided.  

Write down the Xircom Ethernet PC Card model and serial numbers for reference. Customer Support will ask you to supply the model and serial numbers when requesting technical assistance or warranty service from Xircom.

Windows 3.x Driver Parameters

The following paragraphs present configuration guidelines for each of the driver types: NDIS, ODI, and packet. 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 is only supported at 10Mbps and must be explicitly configured with the FULLDUPLEX keyword. Full-duplex operation is not supported at 100Mbps.

ODI Settings (for drivers CE3ODI.COM and CE3ODI.OS2)

Custom parameters for networks using the ODI driver can be set up manually, using an ASCII editor, in the NET.CFG file. DOS Card and Socket Services are no longer supported by Xircom DOS drivers and should be uninstalled prior to loading these drivers.

DOS ODI Driver Configuration Notes (CE3ODI.COM)

The ODI driver CE3ODI.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 CE3ODI.COM are

DOS Card and Socket Services are no longer supported by Xircom DOS drivers and should be uninstalled prior to loading these drivers.

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 CE3ODI

Parameters can also be implemented on the command line. Keyword syntax can be found below. Keywords are not case sensitive. A Keyword Alphabetical Index explains keyword syntax.

NET.CFG Example

 link driver ce3odi

      int 5

      port 280

      mem D2000

CE3ODI.COM Keywords

ODI Driver Example

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

LSL

CE3ODI

IPXODI

VLM

OS/2 ODI Driver Configuration Notes (CE3ODI.OS2)

The OS/2 ODI driver CE3ODI.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 CE3ODI.OS2 supports Novell's NetWare Requestor for OS/2 networking client environment.

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

NET.CFG	Network configuration file
CE3ODI.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 CE3ODI

Parameters can also be implemented on the command line. Keyword syntax can be found below. Keywords are not case sensitive. A Keyword Alphabetical Reference explains the keyword syntax.

NET.CFG Example

link driver ce3odi

   int 5

   port 280

   mem D2000

CE3ODI.OS2 Keywords

NDIS 2.81 Settings (for drivers CE3NDIS.EXE and CE3NDIS.OS2)  

Custom parameters for the NDIS driver can be set up manually, using an ASCII editor, in the PROTOCOL.INI file. DOS Card and Socket Services are no longer supported by Xircom DOS drivers and should be uninstalled prior to loading these drivers.

NDIS 2.81 DOS Driver Configuration Notes

The DOS NDIS driver CE3NDIS.EXE conforms to the 3Com/Microsoft LAN Manager Network Driver Interface Specification (NDIS) version 2.81. 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 CE3NDIS.EXE are:

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 explains the keyword listings.

NDIS 2.81 OS/2 Driver Configuration Notes

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

The files required for using CE3NDIS.OS2 are:

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 explains the keyword listings.

PROTOCOL.INI Example

[XIRCOMNET]

 DRIVERNAME=XIRCOM

 MEM=0xD2000

 MODE=IO

NDIS 2.0.1 Keywords (CE3NDIS.EXE and CE3NDIS.OS2)

Novell Server Driver Settings (for driver CE3ODI.LAN)

The driver CE3ODI.LAN conforms to the Novell “ODI NetWare Server Driver Development Tool Kit Driver Specification” version 3.2. It is a 32-bit driver. The NetWare Server ODI stack including CE3ODI.LAN supports NetWare versions 3.11, 3.12, and 4.01.

Novell Server Driver Keywords

Parameters for configuring the Novell server driver must be specified on the command line.

Packet Driver Settings (for driver CE3PD.COM)  

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

Packet Driver Configuration Notes

The Xircom packet driver CE3PD.COM conforms to FTP Software’s public domain packet-driver specification. It is a DOS-based terminate-and- stay-resident (TSR) program.

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. DOS Card and Socket Services are no longer supported by Xircom DOS drivers and should be uninstalled prior to loading these drivers.

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

Packet Driver Keywords  

Packet Driver Example

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

CE3PD

ETHDRV

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

CE3PD IOADDRESS=320 INT=7

ETHDRV

IBM OS/2 Configuration Guidelines

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 CE3NDIS.OS2conforms to the Microsoft LAN Manager Network Driver Interface Specification (NDIS) version 2.81. It is an IBM OS/2-based device driver for use with OS/2 versions 2.0 and later.

The files required for using CE3NDIS.OS2 are:

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.81 Keywords (CE3NDIS.OS2)

OS/2 ODI Driver Configuration Notes

The OS/2 ODI driver CE3ODI.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 CE3ODI.OS2 supports Novell's NetWare Requestor for OS/2 networking client environment.

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

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 CE3ODI

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 (CE3ODI.OS2) Keywords

General Troubleshooting Checklist

Please review the following troubleshooting measures before calling Xircom Customer Support:

• Review the README file by running SETUP from the compact disc and selecting "View Readme File" from the menu. It contains important information (including known incompatibilities and machine specific issues) that may solve your problem. The README file can also be accessed after installation by clicking Start, Programs, Xircom Utilities, README.
• Obtain current versions of drivers for your adapter from the Xircom website at http://www.xircom.com.
• Boot the computer in a clean environment (press F8 or hold down the Shift key to bypass loading of CONFIG.SYS and AUTOEXEC.BAT), then use the Xircom test utility to see if the adapter is functioning and detecting network traffic.
• When loading drivers or running the test utility, have the dongle cable attached to the CardBus adapter.
• Under Novell, ensure that the FRAME TYPE you are using is the same as that of the file server. The server frame type should be specified as the first frame type in the NET.CFG.
• In a twisted pair environment, try plugging directly into the hub or concentrator.
• Try using a network connection that works for another computer.
• Try using the Xircom adapter on a different computer.
• Try another Xircom adapter if available.
• If your computer has multiple PC Card sockets, move the adapter to another socket.
• If you have more than one PC Card device in your computer, remove the non-Xircom PC Card devices during your configuration/testing.
• Make sure you are using the most recent version of Card and Socket Services. Call the computer manufacturer or the company that makes the Card and Socket Services. Upgrading to new drivers from Xircom may also be required, as new Card and Socket Services software is released.
• Test the Xircom adapter without loading Card and Socket Services to see if there is a conflict between the Xircom adapter configuration and that of Card and Socket Services. The interrupt, memory address location, and I/O address specified to the Card and Socket service drivers must match the Xircom configurations in NET.CFG or PROTOCOL.INI (if used).
• If you own several models of Xircom CardBus adapters, ensure you are using the appropriate driver for the currently inserted adapter.
• Make sure that the Xircom adapter is not conflicting (interrupt, memory address, I/O address) with any other adapters or hardware that is installed in the computer (including sounds cards, CD-ROM drives and PEN devices).
• Try loading the CardBus 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).

Keyword Alphabetical Reference

?

displays command summary for driver

CABLETYPE   

(NDIS 3) sets the driver to autodetect the cable type or set unshielded twisted pair.  

DRIVERNAME   

DRIVERNAME=XIRCOM$ required as first item in the XIRCOM section of the PROTOCOL.INI file for the CE3NDIS driver.  

DYNAMICLINKDETECT   

allows the Ethernet interface to be configured so that it is only initialized if an active connection to the network is detected at boot time. Set this parameter to OFF to prevent conflicts between LAN and remote dial-up connections on the same network under Windows 98 and 95.  

EARLYTRANSMIT   

(NDIS 3) when set to OFF functions like the keyword NOEARLYTX.  

FULLDUPLEX   

(10MBPS only) enables the Xircom Ethernet PC Card to send and receive data simultaneously when connected to a full-duplex hub. Default is keyword not used, and therefore full-duplex “disabled.” This parameter is ignored in 100Mbps mode.  

INT   

see INTERRUPT  

INTERRUPT   

specifies a PC Card port hardware interrupt. Use 5 or 7 on most PCs. Default (if parameter not specified) is 5. Use 0 (zero) to force the adapter into a polled mode.

IOADDRESS   

specifies the base I/O address of the Xircom adapter I/O ports, in hexadecimal notation. Default address is 320.

I/O PORT   

see IOADDRESS.  

IOWAITSTATES   

specifies the number of wait states to use for accesses to the Xircom adapter.  

LINESPEED   

forces operation at 10 or 100Mbps. If the keyword is not stated, the line speed will be automatically detected.  

LINKDISABLE   

disables link integrity for non-IEEE 10BASE-T networks such as StarLAN 10. Without this keyword in the driver command line, the driver defaults to link integrity ENABLED.  

LINKINTEGRITY   

(NDIS 3) when set to OFF, operates like the LINKDISABLE parameter.  

LINK DRIVER   

LINK DRIVER CE3ODI required as first item in the NET.CFG file listing configuration parameters for the CE3ODI driver. This must be the first keyword in the section of the NET.CFG file for the Xircom adapter.  

MEM   

see MEMORY.  

MEMORY   

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). The memory block occupies 4Kbytes of host memory.  

MEMWAITSTATES   

specifies the number of waitstates to use for memory accesses to the Xircom adapter. Values are decimal 1 to 3. The keyword is provided as a troubleshooting aid.  

MODE   

set this keyword to IO to disable 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   

allows user to override adapter’s unique network node address by specifying a different node address. Network node address can be displayed with the CE3TEST utility (MS-DOS).  

NODEADDRESS   

see NETWORKADDRESS.  

NOCHECK   

disables verification of adapter resources, for troubleshooting purposes.  

NOEARLYRX   

disables Advanced Look-ahead Pipelining features of the Xircom Ethernet PC Card. This parameter should be used in the NET.CFG file when the ODI driver is used with Microsoft Windows for Workgroups 3.11.  

NOEARLYTX   

disables early transmit features of the Xircom Ethernet PC Card. Try using this keyword if you are experiencing a large number of transmit underruns (in which hardware reports not finding expected data in the transmit buffer).  

NOLED   

turns off LED indicators on LAN adapter module to conserve power.  

PORT   

(ODI) see IOADDRESS.  

S   

(ODI)(MS-DOS command line only) displays LAN drivers resident in memory.  

SILENT   

(CE3TEST) disables display of information on the screen and returns DOS error code when tests are complete.  

SINT   

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

SOCKET   

the number of the host computer’s PC Card slot or socket into which the Xircom Integrated PC Card is inserted. If a socket number is specified, the only the specified socket is checked for the Xircom adapter. If no socket is specified, the all sockets are searched until the Xircom adapter is found.  

U   

(ODI)(MS-DOS command line only) unloads driver from memory  

WORDSIZE   

this parameter specifies the network data path size. Values are 8 or 16 for 8- or 16-bit transfers. Default is 16.

Table of Contents | Previous Page | Next Page