CardBus 10/100Mbps Ethernet Card
DOS ODI Client Driver Ver 1.40
1. Overview:
This Readme file explains how to install the Novell NetWare
DOS ODI Client driver.
2. Preinstallation Hardware and Software Requirements:
A. Hardware Requirements:
o An IBM-compatible personal computer with 80386 or higher
microprocessor and a PCI bus.
o A PCI board based on Digital Semiconductor 2104x/2114x
10/100 mbps based Ethernet controller.
B. Firmware Requirements:
o Fully compliant Rev. 2.0 or above PCI BIOS supplied with the PC.
o If Ethernet adapter makes use of Digital Semiconductor 21050
(PCI-PCI bridge), PCI BIOS should support PCI-PCI bridge architecture.
C. Software Revision Requirements:
o MS-DOS version 3.31 or above.
o Novell LSL.COM version 2.16 or above.
o Novell IPXODI.COM version 3.02 or above.
o Novell NETX.COM version 1.11 or above.
or
o Novell VLM.EXE version 1.20B or above.
3. Files in NWCLIENT directory
Table 1: The Novell NetWare ODI Client Directory Files
---------------------------------------------------------------------
README.TXT This File
---------------------------------------------------
DC21X4.COM DC21X4 Novell NetWare ODI Client driver.
----------------------------------------------------------
NET.CFG Novell network configuration file for this driver
---------------------------------------------------------------------
4. Installing Software:
To install the Novell NetWare ODI Client Device Driver:
1. Run INSTALL program in a:\, and select Netware Client Driver
to install.
2. Edit the NET.CFG file if necessary to select protocol and
media type options.
NOTICE:
o NO NEED TO SPECIFY SLOT NUMBER, BUS ID OR INTERRUPT NUMBER!
o If you specify Bus ID please notice that for PCI bus you write
BUS ID PCI 4
in NET.CFG
o If you specify Slot Number please notice that SLOT 1 means
in PCI : The first board found in system.
3. To connect to a server, use the following loading sequence. It can
be found in the copied STARTNET.BAT file.
LSL
DC21X4
IPXODI
NETX or VLM
LOGIN
5. Parameters
The following parameters can be used in order to control part of
the driver's operation.
These parameters are added to the driver's entry in NET.CFG
For NetWare standard parameters, please refer to NetWare user's
manual.
TP selects TP port.
TP_NO_LINK_TEST selects twisted pair connection, but disables
the LINK test for specific HUBs that do not
support LINK.
TP_FULL_DUPLEX selects twisted pair connection to work in
full duplex mode.
LINE_SPEED selects line speed between 10Mbps and 100Mbps
Format: LINE_SPEED <value>
Allowed values are: 10,100
AUTOSENSE Enables autosensing among Nic's media when driver
loads (Also called Power-Up Autosense) and at run-time
RX_BUFFERS Allows the user to select the amount of
receive buffers to work with.
More buffers means larger driver resident
in memory but with higher performance.
Format: RX_BUFFERS <Hexadecimal Value>
Allowed values: in the range 2-10hex (16 Decimal).
Default value : 10 (Hex)
TX_BUFFERS Allows the user to select the amount of
transmit buffers to work with.
Format: TX_BUFFERS <Hexadecimal Value>
Allowed values: in the range 2-3.
Default value : 3
SNOOZE Changes power-management mode to Power-Saving mode.
CFLT Configuration Latancy Timer.
Specifies, in units of PCI bus clocks, the value
of the latancy timer
Format: CFLT <Hexadecimal Value>
Allowed values: 0 to 0FF Hex
Default value : 12hex
Notice: Changing this parameter may affect the device
performance.
PBL Programmable burst length.
Indicates the Maximum number of longwords to be
transferred in one DMA transaction.
Format: PBL <Hexadecimal Value>
Allowed values: 0,2,4,8,10 or 20 Hex
(0 means Unlimited, 20Hex means 32 Longwords)
boundary alignment).
Default value : 20hex (32 Longwords)
Notice: Changing this parameter may affect the device
performance.
PBL may be limited by the driver due to
system limitations.
It is recommended to program both PBL and CAL
to the same burst value.
CAL Cache Alignment.
Programmable address boundaries for the data burst stop.
Format: CAL <Hexadecimal Value>
Allowed values: 1, 2 or 3
(8 Longwords, 16 longwords and 32 Longwords
boundary alignment).
Default value : 2
Notice: Changing this parameter may affect the device
performance.
CAL may be limited by the driver due to
system limitations.
It is recommended to program both PBL and CAL
to the same burst value.
NO_ERI Disables the Chip's Early Receive Interrupt function
which issues a receive interrupt prior to receiving
a complete packet.
Notice: Changing this parameter may affect the device
performance.
TX_THRESHOLD Transmit Threshold
Controls the minimum amount of packet's data
the Transmit fifo must contain before transmission
starts.
Format: TX_THRESHOLD <Hexadecimal Value>
Allowed values: 0-4
+----------------+------------------+--------------------+
| TX_THRESHOLD | Chip's | Chip's |
| KWD Value | threshold Value | threshold Value |
| | (10MBps) | (100MBps) |
+----------------+------------------+--------------------+
| 0 | 72 | 128 |
| 1 | 96 | 256 |
| 2 | 128 | 512 |
| 3 | 169 | 1024 |
| 4 | Full Packet | Full Packet |
+----------------+------------------+--------------------+
Default value : 0
Notice: Changing this parameter may affect the device
performance.
EXT_MRM Memory Read Multiple (MRM).
Enables the Chip's Memory Read Multiple PCI command
which is semantically identical to the Memory
Read command except that it additionally indicates
that the master may intend to fetch more than one
cacheline before disconnecting.
Format: EXT_MRM <Hexadecimal Value>
Allowed values: 0,1
(0 means Disabled, 1 means Enabled).
Default value : 1 (Enabled).
Notice: Disabling this command may affect the device
performance.
EXT_MRL Memory Read Line (MRL).
Enables the Chip's Memory Read Line PCI command
which is semantically identical to the Memory
Read command except that it additionally indicates
that the master may intend to fetch a complete
cacheline.
Format: EXT_MRL <Hexadecimal Value>
Allowed values: 0,1
(0 means Disabled, 1 means Enabled).
Default value : 1 (Enabled).
Notice: Disabling this command may affect the device
performance.
Due to incompatibility problems with certain
PCI host bridges and PCI-to-PCI bridges,
the driver currently does not enable the
Memory Write Invalidate (MWI) and Memory Read
Line (MRL) commands simultaneously.
The driver will only enable one of the two commands;
by default, MRL will be enabled.
EXT_MWI Memory Write Invalidate (MWI).
Enables the Chip's Memory Write Invalidate PCI command
which is semantically identical to the Memory
Write command except that it additionally guarantees
a minimum transfer of one complete cacheline; i.e.,
the master may intends to write all bytes within the
addressed cacheline in a singlePCI transaction unless
interrupted by the target.
Format: EXT_MWI <Hexadecimal Value>
Allowed values: 0,1
(0 means Disabled, 1 means Enabled).
Default value : 1 (Enabled).
Notice: Disabling this command may affect the device
performance.
Due to incompatibility problems with certain
PCI host bridges and PCI-to-PCI bridges,
the driver currently does not enable the
Memory Write Invalidate (MWI) and Memory Read
Line (MRL) commands simultaneously.
The driver will only enable one of the two commands;
by default, MRL will be enabled.
6. Driver selected connection
Driver selected connection is a combination of Line_Speed selection
and Media type selection.
The following table describes how does the driver detirmine the
actual media connection from these two parameters.
+--------------------+----------------------++------------------------+
|Requested Connection| Requested LineSpeed || Selected Connection |
| (From NET.CFG) | || |
+--------------------+----------------------++------------------------+
| AUTOSENSE | 10, 100 or None || AUTOSENSE |
| TP | 10 || 10BaseT |
| TP | 100 || 100BaseTX |
| TP_FULL_DUPLEX | 10 || 10BaseT FULL_DUPLEX |
| TP_FULL_DUPLEX | 100 || 100BaseTX FULL_DUPLEX |
| TP_NLT | 10 || 10BaseT NO_LINK_TEST |
| TP_NLT | 100 || 100BaseTX |
+--------------------+----------------------++------------------------+
7. Driver Error messages:
- FATAL: Failed to allocate system memory
Driver call to OS memory support routines for dynamic memory
allocation had failed.
Please reboot the system.
- FATAL: Failed to lock system memory
Driver call to OS memory support routines for locking its
internal buffers and descriptors failed.
Please reboot the system.
- FATAL: DC21X4 driver works only with 386 or above!
The driver failed to identify the CPU as a 386 or above the
driver can run on 386 (or above) machines only.
- FATAL: Slot value error!
The user has specified an illegal slot number in NET.CFG
50 - FATAL: Board not found in system
Driver could not detect a supported NIC in the system.
This may happen if no NIC is presented in the system or due to
incorrect Slot Num or BUS ID entries in NET.CFG.
200 - FATAL: Timeout when initializing DC21X4 with setup packet!
This happens mainly when the PCI slot does not support DMA.
Make sure the BIOS setup or motherboard switches are set to
enable DMA or Bus Master operation of this slot.
210 - FATAL: Failed to find a supported bus
The machine is not identified as a PCI machine or the user has
specified BUS ID which is not PCI.
212 - FATAL: Failed to locate DC21X4 on board.
Bus service functions searching for the chip returned Illegal
Chip ID Error.
Please call you Nic's vendor.
212 - FATAL: Driver Does not support this device revision or Operation Mode.
If you receive this message, please make sure you have an updated rev
of your NIC.
217 - FATAL: Failed to find PCI BIOS
The machine is not identified as a PCI machine (to support PCI
NICs). This error is generated when the driver is directed to
load a PCI NIC using the BUS ID keyword and PCI 4 is specified,
or SLOT keyword, and slot value is a PCI slot number (16 and above).
218 - FATAL: Bad PCI BIOS status
PCI BIOS returned a fail status in one of the calls. Please
check the BIOS version and BIOS correctness using an external
utility.
219 - FATAL: Bad PCI BIOS Register err
PCI BIOS returned a fail status in one of the calls. Please
check the BIOS version and BIOS correctness using an external
utility.
220 - FATAL: PCI BIOS failed to initialize DECchip CBIO reg!
PCI BIOS has initialized a DWORD register in the NIC's
configuration space (at offset 10Hex) with illegal value (in x86
machines this value is between 0 to FFFFHex). Please check the
BIOS using an external utility. Also verify that your BIOS setup
enables the slot the NIC is plugged in, allocates I/O addresses
to it and initializes correctly the device in this PCI slot.
222 - WARNING: KWD <KWD Name> No param
The user added the <KWD Name> in NET.CFG but did not
specify the parameter needed by this specific KWD.
Please add a legal number to the KWD as specified in the KWDs section
of this document.
222 - WARNING: KWD <KWD Name> Param too small
The number pareameter for <KWD Name> specified by the user is too small.
Please increase the number to a legal one as specified in the KWDs section
of this document.
222 - WARNING: KWD <KWD Name> Param too big
The number pareameter for <KWD Name> specified by the user is too big.
Please decrease the number to a legal one as specified in the KWDs section
of this document.
225 - FATAL: PCI BIOS allocated an illegal Interrupt to DECchip!
PCI BIOS has initialized a byte register in the NIC's
configuration space (at offset 3CHex) with illegal value (in x86
machines legal values are between 1 to 15). Please check the
BIOS using an external utility. Also verify that your BIOS setup
enables the slot the NIC is located in, enables interrupts to
this slot and assigns a legal interrupt number to it.
226 - WARNING: Can not handle Turbo switch
Cannot operate the 'Turbo' mechanism from one of the following reasons:
- The chipset does not support TURBO mode.
- The chipset parameters are unknown to the driver.
226 - FATAL: Failed to handle Turbo switch
Failed to operate the 'Turbo' mechanism from one of the
following reason:
- PCI BIOS returned a fail status in one of the calls involved
with operating this mechanism.
We strongly recommend to reboot the PC after such an Error occures
227 - FATAL: Internal CRC table corrupted
Driver found an error in internal CRC table either because the
driver file is corrupted or someone has changed the table's
contents.
228 - FATAL: Could not handle chipset bug workaround successfully
Failed to operate chipset bug workaround because PCI BIOS
returned a fail status in one of the calls involved with
operating this mechanism.
229 - WARNING: This machine Host to PCI bridge has a known bug.
Driver limits DC21X4 bursts as a workaround.
230 - FATAL: This machine Host to PCI bridge has a known bug when
using cache in WB mode which may cause data corruption
or system hang. Please change the cache mode to WT
(Write Through) as a workaround.
231 - WARNING: The PCI Host Bridge present in this machine requires that the
driver switch to Store and Forward Mode.
The driver detected a PCI Host Bridge with limited data transfer rates
to be present in the PC. it modifies DC21X4 chip parameters for working
in such a system. This may slightly slow the network performance.
No further action is needed.
240 - FATAL: Unable to locate Adapter ROM!
Driver failed either to locate the address ROM or read it. This
might happen due to bad data stored in the serial ROM.
240 - FATAL: Failed to read ROM!
Driver failed to read the serial flash ROM due to a hardware
failure. Make sure the IEEE flash ROM on your NIC is operational
using external utility.
240 - FATAL: Unsupported ROM Version
The version (and hence the format) of the data read from the
SROM is not supported by the driver. Please run an external
utility to upgrade the Serial ROM's data.
240 - FATAL: This DC21X4 chip does not support this ROM version
This ROM version does not contain the information needed by the
driver in order to correctly activate the DS chip located on-board.
Please run an external utility to upgrade the Serial ROM's data and
add the device specific information to it.
241 - FATAL: Unsupported media selection
The NIC or device do not support the requested media selection.
Please check the available media types on the NIC and use one of
them.
241 - FATAL: Could not find media or PHY to work with
The driver failed to find any medium in the NIC.
This may happen due to a bad Serial ROM programming or an MII PHY failure.
242 - WARNING: Could not find a connected medium.
The Power-Up autosense could not find a connected medium,
Please connect a cable to one of the ports and the Autosense routine
will automaticlly find and use it.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.