ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Installation for NetWare DOS ODI Driver ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
A. 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.
o Novell VLM.EXE version 1.20B or above.
B. Installing Software:
1. Copy the driver to the NetWare Client directory. For example:
copy A:\NWCLIENT\DOS\DC21X4.COM C:\NWCLIENT
2. Edit the NET.CFG file if necessary to select protocol and
media type options.
3. To connect to a server, use the following loading sequence:
LSL
DC21X4
IPXODI
NETX or VLM
C. 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.
AUI selects AUI port.
TP selects TP port.
BNC selects BNC port.
T4 selects T4 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 10MPBs and 100MBPs.
Format: LINE_SPEED <value>
Allowed values are: 10,100
AUTOSENSE enables autosensing of media type when driver
is loading (Also called Power-Up Autosense),
and run-time autosensing of media type.
GENERAL_PURPOSE_CONTROL
the user can override the control value in the
GENERAL_PURPOSE register.
Normally, this value should not be changed.
Format: GENERAL_PURPOSE_CONTROL <Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
GENERAL_PURPOSE_DATA the user can override the data value in
the GENERAL_PURPOSE register.
Normally, this value should not be changed.
Format: GENERAL_PURPOSE_DATA <Hexadecimal Value>
Allowed values: in the range FFFF-0 hex.
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-10 hex (16 Decimal).
Default values: 10
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.
D. Driver selected connection
Driver selected connection is a combination of the Line_Speed selection
and Media type selection.
The following 2 tables describe how does the driver determines the
actual media connection from these two parameters.
First the driver determines the Line_Speed according to the following
table:
+--------------------+----------------------++------------------------+
| Line_Speed |Digital Semiconductor || Actual Line_Speed |
| (From NET.CFG) | chip Number || |
+--------------------+----------------------++------------------------+
| None | 21040 || 10 (MBps) |
| None | 21041 || 10 (MBps) |
| None | 21140 || 100 (MBps) |
| None | 21142 || 100 (MBps) |
| 10 | 21040 || 10 (MBps) |
| 10 | 21041 || 10 (MBps) |
| 10 | 21140 || 10 (MBps) |
| 10 | 21142 || 10 (MBps) |
| 100 | 21040 || 100 (MBps) |
| 100 | 21041 || 100 (MBps) |
| 100 | 21140 || 100 (MBps) |
| 100 | 21142 || 100 (MBps) |
| 100 | 21143 || 100 (MBps) |
+--------------------+----------------------++------------------------+
Then the driver determines the connection type according to the
following table:
+--------------------+----------------------++------------------------+
|Requested Connection| Requested LineSpeed || Selected Connection |
| (From NET.CFG) | || |
+--------------------+----------------------++------------------------+
| AUTOSENSE | 10, 100 or None || AUTOSENSE |
| AUI | 10, 100 or None || AUI, (10MBps) |
| BNC | 10, 100 or None || BNC, (10MBps) |
| T4 | 100 || 100BaseT4 |
| T4 | 10 || 10BaseT |
| 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 |
+--------------------+----------------------++------------------------+
E. Driver Error messages:
- FATAL: Failed to lock system memory
Driver call to OS memory support routines for locking its
internal buffers and descriptors failed.
- 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.
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: DC21X4 Does not support this bus type
The machine is not identified as a PCI machine or the user has
specified BUS ID which is not PCI.
212 - FATAL: DC21X4 Does not support this device revision
The DC21x4 drivers do not support DC21140 rev 1.0 chip. 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 (in DC21X4.COM v2.0 and
above) and PCI 4 is specified, or SLOT keyword (in DC21X4 V1.02
and below), 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 21x40 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 RXD No param
The user added the RX_BUFFERS key word in NET.CFG but did not
specify the number of buffers required.
Add the number of buffers to the KWD (such as: RX_BUFFERS 9)
222 - WARNING: KWD RXD Param too small
The number of Rx buffers specified by the user is too small
for proper driver's work.
Please increase the amount of Rx buffers in RX_BUFFERS KWD in
NET.CFG
The minimum number of rx buffers is 2.
222 - WARNING: KWD RXD Param too big
The user had specified more rx buffers than the driver can handle
Please decrease the amount of Rx buffers in RX_BUFFERS KWD in
NET.CFG
The maximum number of rx buffers is 16 but it may be less depending
on the driver's size.
225 - FATAL: PCI BIOS allocated an illegal Interrupt to DECchip 21x40!
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 on the motherboard 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. Network performance
may be affected.
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 DS 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.