Fast Ethernet PCI Ethernet Adapter
+-------------------------------------------------------------+
| DC21X4 driver for Novell ODI Server |
| V3.11 |
+-------------------------------------------------------------+
1. Preinstallation Hardware and Software Requirements:
A. Hardware Requirements:
o An IBM-compatible personal computer with 80386 or higher
microprocessor and PCI bus.
o A DECchip 21142/3-based Ethernet adapter for that bus.
B. Firmware Requirements:
o Fully compliant Rev. 2.0 or above PCI BIOS supplied with the PC.
o If Ethernet adapter makes use of DECchip 21050 (PCI-PCI bridge),
PCI BIOS should support PCI-PCI bridge architecture.
C. Software Revision Requirements:
o NetWare version 3.11 or above.
o Novell support modules as supplied in kit directories.
2. Supplied Files:
Table 1: The Novell NetWare ODI Server Directory Files
---------------------------------------------------------------------
DC21X4.LAN DC21X4 Novell NetWare ODI server driver. This file
supports the EB40, the EB41, the EB140 and the EB142/3
PCI boards.
---------------------------------------------------
DC21X4.LDI Novell network installation file for this driver
---------------------------------------------------
DC21X4.INF Novell network Windows 95 installation file for
this driver
---------------------------------------------------
ETHERTSM.NLM Novell TSM needed to run the ODI server driver
---------------------------------------------------
MSM.NLM Novell MSM needed to run the ODI server driver
---------------------------------------------------
NBI.NLM Novell NBI needed to run the ODI server driver
---------------------------------------------------
MSM31X.NLM Novell MSM needed to run the ODI server driver with
NetWare v3.12, and 3.11 in respective directories.
---------------------------------------------------
NBI31X.NLM Novell NBI needed to run the ODI server driver with
NetWare v3.12 ONLY.
---------------------------------------------------
PATCHMAN.NLM Novell module needed in NetWare v3.1x in addition
to MSM31X.NLM
---------------------------------------------------
A3112.NLM Novell module needed in NetWare v3.11 in addition
to MSM31X.NLM
---------------------------------------------------
LSLENH.NLM Novell module needed in NetWare v3.1x in addition
to MSM31X.NLM
---------------------------------------------------
MONITOR.NLM NetWare server MONITOR module for NetWare v3.11
---------------------------------------------------
LSWAP.EXE For Netware 3.12 you must copy the LOADER.EXE and
LOADER.EXE LSWAP.EXE to the NWSERVER directory and run the
LSWAP.EXE to update the loader segment in the
server.exe file. This is required by Novell in order
for the NBI31X/MSM31X to function correctly.
---------------------------------------------------------------------
3. Installing Software:
To install the Novell NetWare ODI Server Device Driver:
DC21X4.LAN is the Novell NetWare ODI server driver for
both the EB142/3 and the EB40, the EB41 and EB140 PCI
evaluation boards.
1. NetWare v3.1x installation (use respective directory i.e.
3.11 or 3.12):
1.1 Copy The DC21X4.LAN to the SYS:\SYSTEM directory on
the NetWare server.
1.2 Add to your AUTOEXEC.NCF the line required to load
the DC21X4.LAN and bind it. Refer to the sample
AUTOEXEC.NCF for more information (according to the
type of NetWare you are using, i.e. v3.11, 3.12 or 4.x).
1.3 For Netware 3.12 ONLY you must copy the LOADER.EXE and
LSWAP.EXE to the NWSERVER directory and run the
LSWAP.EXE to update the loader segment in the
server.exe file. This is required by Novell in order
for the NBI31X/MSM31X to function correctly.
2. NetWare v4.x installation:
2.1 Have ready a diskette with DC21X4.LAN and DC21X4.LDI
both from the driver's kit.
2.2 On the server's prompt type: LOAD INSTALL
2.3 When the install program comes up, choose the menu
item that refers to NETWORK DRIVERS.
Note that this menu item is on different place on
different NetWare versions (i.e. v4.0x vs. 4.1x).
2.4 Install the network driver DC21X4.LAN according to
the NetWare manual, or use the on-line instructions
and help.
NOTE: The slot numbers in Netware 3.11 are different from the
ones in Netware 3.12 and 4.x. This is due to the fact that
the 3.12 and 4.x driver (one and the same) use the NBI layer
from Novell, and the 3.11 driver does not. Novell DO NOT and
will NOT supply an NBI layer for 3.11.
4. Parameters
The following parameters belong on the server's command line, or in
the load line inside the AUTOEXEC.NCF. The general way of using these
parameters is:
LOAD <driver name> <PARAMETER NAME>... <PARAMETER NAME[=VALUE]>
Example:
LOAD <driver name> TURBO SLOT=16 FRAME=Ethernet_802.2
------------------------------------------------------------------
NOTE that wrong values (such as 'line_speed=128') are IGNORED, and
a default value is taken instead.
------------------------------------------------------------------
Driver specific parameters list (as for NetWare standard parameters,
please see the NetWare user's manual):
AUI selects AUI port on EB41, DE425 or compatible (see DE425
installation instructions to select correct jumper
settings).
TP selects TP port on EB40, EB41 and DE425 or compatible
BNC selects BNC port on EB41, DE425 or compatible (see DE425
installation instructions to select correct jumper
settings).
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.
TURBO Fixes the problem of multiple transmit
underflows and receive overflows (i.e. lose of
packets) in systems that use certain PCI
chipsets.
(**) LINE_SPEED selects line speed between 10MPBs and 100MBPs
on network cards based on DC21140.
Format: LINE_SPEED=<value>
Allowed values are: 10,100
(**) GENERAL_PURPOSE_CONTROL user override of the control value in
the GENERAL_PURPOSE register in DC21140
based network cards.
Normally, this value should not be
changed.
Format: GENERAL_PURPOSE_CONTROL=<Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
(**) GENERAL_PURPOSE_DATA user override of the data value in the
GENERAL_PURPOSE register. in DC21140
based network cards.
Normally, this value should not be
changed.
Format: GENERAL_PURPOSE_DATA=<Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
T4 run in T4 100Mbps mode
NT run under NT requester
OS2 run in NetWare for OS/2
Unixware run in UnixWare (ONLY valid for transmognified drivers on
Unixware v2.01).
Client32Win run in Client32 environment for windows
Client32Win95 run in Client32 environment for Windows95
Client32DOS run in Client32 environment for DOS
Notes:
------
(**) Those keywords affect ONLY DC21140/142/143 based network interface cards.
5. Serial ROM version support
Driver version | Serial ROM version | Serial ROM Burn program version
------------------|--------------------------|-----------------------------------
1.02 and below | Legacy format | No such program
1.03 and 1.04 | Extended Legacy format | SROM v1.00
1.05 to 1.10 | ROM format version 1.00 | SROM v1.01, v1.02, v1.03
2.00 | ROM format version 3.00 | SROM v3.00
2.13 | ROM format version 4.00 | not yet available
Note: The Legacy format is DEC's classical ethernet address format.
The extended legacy format is a middle version between the Legacy
and format version 1.00. It should NOT be used anymore.
The v1.00 format is the current serial ROM format.
Note that the added functionallity in SROM version from v1.01 and up
till SROM v1.03 can be found at the SROM release notes and README file.
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.