+---------------------------------------------+
| NDIS 2 MAC DRIVER for DC21X4 V3.00 |
+---------------------------------------------+
Note that this installation kit includes both the DOS
, Windows for Workgroups, Windows95 and OS/2 NDIS2 driver
and this document describes installation under all
environments. This revision supersedes the DOS and OS/2
NDIS2 driver version 2.41 .
RELEASE.TXT in the top level directory describes changes
from the previous driver versions.
NOTE: The generic term "21X4" relates to the Intel
21040, 21041, 21140, 21142, 21143
Ethernet and Fast Ethernet LAN controllers.
Table of Contents:
------------------
1. Copyright Notice .
2. Overview and Product Description .
3. Preinstallation Hardware and Software Requirements .
3.1 Hardware Requirements .
3.2 Software Requirements .
4. Files and Directories (in the installation diskette) .
5. Installing the Hardware Boards .
5.1 Installing the 21X4 PCI boards .
6. Installing Software.
6.1 Basic driver installation (for DOS and OS/2 based NOS) .
6.2 Installing the NDIS2 DOS driver :
6.2.1 Installation with Micrososft Lan Manager 2.x.
6.2.2 Installation with Windows for Workgroups Version 3.1 .
6.2.3 Installation with Windows for Workgroups Version 3.11 .
6.2.4 Installation with PATHWORKS for DOS Version 4.0 .
6.3 Installing the NDIS2 OS/2 driver :
6.3.1 Installation with Microsoft LAN Manager 2.x for OS/2 .
6.3.2 Installation with IBM Lan Server 3.0 or 4.0 for OS/2 .
6.4 Installing the NDIS2 driver under Win95 .
6.5 Installing multiple boards .
7. PROTOCOL.INI parameters .
7.1 Required Keywords .
7.2 Optional Keywords .
8. Driver error messages and their explanation .
9. Hotline and Support Information .
-----------------------------------------------------------------------------
1. Copyright Notice:
This readme.txt as well as the software described in it is
furnished under license and may only be used or copied in accordance with
the terms of the license. The information in this manual is furnished for
informational use only, is subject to change without notice, and should
not be construed as a commitment by Intel Corporation. Intel Corporation
assumes no responsibility or liability for any errors or inaccuracies that
may appear in this document or any software that may be provided in
association with this document.
Except as permitted by such license, no part of this document may be
reproduced, stored in a retrieval system, or transmitted in any form
or by any means without the express written consent of Intel Corporation.
Windows, Windows 95, Windows NT, and NT are trademarks, and
Microsoft, MS, MS-DOS are registered trademarks of Microsoft
Corporation.
OS/2 and LAN server are trademarks of International Business
Machines Corporation.
Intel are trademarks of Intel Corporation.
All other trademarks and registered trademarks are the property
of their respective holders.
2. Overview and Product Description:
This Readme file explains how to install the NDIS2 driver
under DOS, Windows for Workgroups, OS/2 and Win95 .
This driver is currently supported for the 21X4 Ethernet and
FastEthernet adapters.
3. Preinstallation Hardware and Software Requirements:
3.1 Hardware Requirements:
o An IBM-compatible personal computer with 80386 or higher
microprocessor and PCI bus and/or CardBus.
o A PCI/CardBus board based on Intel 21x4
10/100 mbps based Ethernet controller.
3.2 Software Requirements:
o MS-DOS 5.0 or later with one of
o Microsoft LAN Manager Versions 1.3 or 2.x .
o Microsoft Windows for Workgroups Versions 3.1 or 3.11 .
o PATHWORKS for DOS Version 4.1 .
OR
o OS/2 V1.3, V2.x, V3.0 (WARP) or V4.0 (WARP) with one of
0 Lan Manager Versions 1.3 or 2.x .
0 Lan Server Versions 3.0 or 4.0 .
0 IBM TCP/IP V2.0 and higher.
OR
o Windows95 .
4. Files and Directories:
Directory Structure:
The accompanying figure shows the directory tree of the NDIS2 driver
kit. Files with preceding underscores are directories.
Top-level
============
README.TXT
RELEASE.TXT
|
----------------------------------------------------------
| | | | | |
WFW31 WFW311 LANSRVR WIN95 MSLANMAN.DOS MSLANMAN.OS2
General files in root directory
--------------------------------------------------------------------
RELEASE.TXT Release notes for this version of the driver.
README.TXT The readme file that you are currently reading.
Installation in different operating systems
-------------------------------------------
WFW31 Directory with Windows for Workgroups 3.1 installation files.
WFW311 Directory with Windows for Workgroups 3.11 installation files.
LANSRVR Directory with LanServer installation files.
WIN95 Directory with Win95 installation files.
MSLANMAN.DOS Directory structure used for installation under LanManager (DOS)
MSLANMAN.OS2 Directory structure used for installation under LanManager (OS2)
5. Installing the Hardware Boards:
Installing the DC 21040/21041/21140/21142/21143
PCI Evaluation Boards
For the EB40, see the DC 21040 PCI Evaluation Board User's guide.
For the EB140, see the DC 21140 PCI Evaluation Board User's guide.
For the EB41, see the DC 21041 PCI Evaluation Board User's guide.
For the EB142, see the DC 21142 PCI Evaluation Board User's guide.
For the EB143, see the DC 21143 PCI Evaluation Board User's guide.
6. Installing Software:
Various network operating systems (NOS) provide utility programs for
installing drivers.
For some of the NOS the installation diskette provides support
FOR THE FIRST BOARD INSTALLED ONLY. If multiple boards are installed,
the second and subsequent boards must be installed manually. (See
section 6.5, Installing multiple boards).
In CardBus, Card and Socket Services must be loaded before loading
the driver.
6.1 Basic driver installation (for DOS-based, Window For Workgroups
and OS/2 NOS).
o Add the following line to CONFIG.SYS:
DEVICE=<drive>:[pathname]\DC21X4.DOS (or DC21X4.OS2)
When the DC21X4 Driver is installed in DOS HIGH memory use
the following:
DEVICEHIGH=<drive>:[pathname]\DC21X4.DOS
o The following information is displayed when the system is rebooted:
Intel 2104x/2114x 10/100 mbps Ethernet Controller <version>
(C) Copyright 1994-1997 Intel Corporation.
Working with Intel 21040 based Ethernet Controller
PCI Slot: <nn> IRQ:<nn>
(For the DS21041, DS21140 or DS21142 the 3rd line is similar)
Where:
Slot is the slot of the adapter
IRQ is the interrupt request level
In OS/2 the following line is displayed:
Selected madia: xxx
(In DOS this line is displayed later)
6.2 Installing the NDIS2 DOS driver.
6.2.1 Installation with Microsoft LAN Manager 2.x
6.2.1.1 Automatic installation using the LAN Manager Setup Program:
1. Start the LMSETUP program.
2. Select <Configuration> from the Main Menu.
3. Select <Network Driver> from the Configuration Menu.
4. Remove the old adapter using <Remove Configuration>.
5. Select <Add Configuration>.
6. Select <Other Drivers> and follow the directions.
6.2.1.2 Manual Installation for DOS LAN Manager
When LAN Manager is already installed and configured and you do
not wish to use the installation program, you have to perform
the following steps manually:
1. Create DC21X4 Driver directory
<DRIVE>:\LANMAN.DOS\DRIVERS\ETHERNET\DC21X4
2. Copy the files
\MSLANMAN.DOS\DRIVERS\ETHERNET\DC21X4\DC21X4.DOS
and
\MSLANMAN.DOS\DRIVERS\ETHERNET\DC21X4\PROTOCOL.INI
to the new directory.
3. Copy the file
\MSLANMAN.DOS\DRIVERS\ETHERNET\DC21X4\DC21X4.NIF
to the directory
<DRIVE>:\LANMAN.DOS\DRIVERS\NIF
4. Add the following line to your CONFIG.SYS to load the
driver:
DEVICE=<DRIVE>:\LANMAN.DOS\DRIVERS\ETHERNET\DC21X4\DC21X4.DOS
5. Modify your PROTOCOL.INI file using any DOS Editor by
appending the PROTOCOL.INI stub (included with this kit) to
the end of your old PROTOCOL.INI file. The stub contains
the following information:
[DC21X4_NIF]
DRIVERNAME=DC21X4$
6. Modify TCPIP_XIF and NETBEUI_XIF modules in the PROTOCOL.INI
file by changing the value of the BINDINGS keyword
from BINDINGS = driverlabel
to BINDINGS = DC21X4_NIF
6.2.2 Installation with Microsoft Windows for Workgroups Version 3.1
6.2.2.1 Automatic installation using the Network Setup Program
1. Select the Control Panel icon.
2. Select the Network Program.
3. Select <Adapter> option.
4. Select <Remove> to remove the old adapter.
5. Select <Add> to add the DC21X4-based adapter
6. Select <Unlisted or Updated Network Adapter> and follow
the Windows for Workgroups instructions, installing the driver
from A:\WFW31 .
7. If there was a problem in 6, try to delete the old instalation
files of the driver:
c:\>del c:\windows\system\oem*.inf
and repeate 1. - 6.
6.2.2.2 Manual Installation for Windows for Workgroups 3.1
When you do not wish to use network installation program 'Network'
from the Control Panel icon, you have to perform the following
steps manually:
1. Copy the DC21X4.DOS file from this kit to the Windows
directory:
<DRIVE>:\WINDOWS
2. Add the following line to CONFIG.SYS
DEVICE=<DRIVE>:\WINDOWS\DC21X4.DOS
3. Modify your PROTOCOL.INI file using any DOS Editor by
appending the PROTOCOL.INI stub (included with this kit) to
the end of your old PROTOCOL.INI file. The stub contains
the following information:
[DC21X4]
DRIVERNAME=DC21X4$
4. Modify the NETWORK.SETUP and MS$NETBEUI sections of your
PROTOCOL.INI file as follows:
[network.setup]
version=0x3100
netcard=DC21X4,1,DC21X4
transport=ms$netbeui,MS$NETBEUI
lana0=DC21X4,1,ms$netbeui
[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=6
NCBS=12
BINDINGS=DC21X4
LANABASE=0
6.2.3 Installation with Microsoft Windows for Workgroups Version 3.11
1. Select the Networking icon group.
2. Select the Network Setup icon.
3. Select <Drivers> option.
4. Select <Add Adapter> to add the DC21X4-based adapter
5. Select <Unlisted or Updated Network Adapter> and follow
the Windows for Workgroups instructions, installing the driver
from A:\WFW311 .
6. If there was a problem in 5, try to delete the old instalation
files of the driver:
c:\>del c:\windows\system\oem*.inf
and repeate 1. - 5.
6.2.4 Installation with PATHWORKS for DOS Version 4.1
NOTE: The Pathworks scheduler (SCHK) must be started with the
switch /N. If /N is not used, initialization may fail with the
following message:
"No NIS Interrupt Activity. Maybe NI_IRQ set wrong or cable not
attached or hardware/DLL broken"
6.2.4.1 Automatic Installation for DOS Pathworks Using the
Netsetup Utility:
When you install PATHWORKS for the first time or update it using
installation program NETSETUP respond to the following prompts as
shown
1. Select your desired choices for
Type of configuration
Destination Drive (boot device)
LK250 Keyboard setup information.
2. Select <Ethernet> network adapter type.
3. Select <Other NDIS> Ethernet adapter.
4. For full DRIVE:\PATH\FILENAME for NDIS driver, enter
A:\DC21X4.DOS
5. For full DRIVE:\PATH\ for the PROTOCOL.INI stub, enter
A:\
The files are copied from this installation kit to its
directory.
NOTE:If PATHWORKS is updated using the NETSETUP installation
program, it is suggested to copy your old copy of the CONFIG.SYS
and PROTOCOL.INI files before starting NETSETUP
6.2.4.2 Manual installation for DOS Pathworks
1. Copy the DC21X4.DOS file from this installation kit
to the PATHWORKS directory. For example:
C:\DECNET> copy A:\DC21X4.DOS
2. Add the following line to your CONFIG.SYS to load the driver:
DEVICE=<drive>:\DECNET\DC21X4.DOS
3. Modify your PROTOCOL.INI file using any DOS Editor by
appending the PROTOCOL.INI stub (included with this kit) to
the end of your old PROTOCOL.INI file. The stub contains
the following information:
[DC21X4.DOS]
DRIVERNAME=DC21X4$
4. Modify the DATALINK and IPX4MAC sections of your
PROTOCOL.INI file.
Change the value of the BINDINGS keyword
from BINDINGS = driverlabel
to BINDINGS = DC21X4.DOS
6.3 Installing the NDIS2 OS/2 driver.
6.3.1 Installation with Microsoft LAN Manager 2.x for OS/2
6.3.1.1 Automatic installation using the LAN Manager Setup Program:
1. In the \LANMAN directory, start the SETUP program
2. Select <Configuration> from the Main Menu.
3. Select <Network Driver> from the Configuration Menu.
4. Remove the old adapter using <Remove Configuration>.
5. Select <Add Configuration>.
6. Select <Other Drivers> and follow the directions.
6.3.1.2 Manual Installation for OS/2 LAN Manager
When LAN Manager is already installed and configured and you do not
wish to use the setup program, perform the following manual steps:
1. Create DC21X4 Driver directory
<DRIVE>:\LANMAN\DRIVERS\ETHERNET\DC21X4.
2. Copy the files
\MSLANMAN.OS2\DRIVERS\ETHERNET\DC21X4\DC21X4.OS2
and
\MSLANMAN.OS2\DRIVERS\ETHERNET\DC21X4\PROTOCOL.INI
to the new directory.
3. Copy the file
\MSLANMAN.OS2\DRIVERS\NIF\DC21X4.NIF
to the directory
<DRIVE>:\LANMAN\DRIVERS\NIF.
4. Add the following line to your CONFIG.SYS to load the
driver:
DEVICE=<DRIVE>:\LANMAN\DRIVERS\ETHERNET\DC21X4\DC21X4.OS2.
5. Modify your PROTOCOL.INI file using any OS/2 Editor by
appending the PROTOCOL.INI stub (included with this kit) to
the end of your old PROTOCOL.INI file. The stub contains
the following information:
[DC21X4_NIF]
DRIVERNAME=DC21X4$
6. Modify TCPIP_XIF and NETBEUI_XIF modules in the PROTOCOL.INI
file by changing the value of the BINDINGS keyword
from BINDINGS = driverlabel
to BINDINGS = DC21X4_NIF
6.3.2 Installation with IBM Lan Server 3.0, 4.0 or TCP/IP for OS/2
NOTE: IBM TCP/IP installation is similar to that of Lan Server 3.0
1. In LanServer V3.0 start by copying the files in A:\LANSRVR to
C:\IBMCOM\MACS . ( C: being the hard disk where the LanServer
files are stored ).
2. Start the Adapter/Protocol setup program:
LanServer 4.0 - Click on the MPTS icon.
LanServer 3.0 - Click on the LAPS icon, or manually run LAPS.EXE
from the IBMCOM directory.
3. Select <Configure> option .
4. Choose "Lan Adapters and Protocols" and select <Configure> option.
5. (Lanserver 4.0 only)
Select <Other Adapters>, and load files from A:\LANSRVR .
6. Select the "DC21X4-Based adapters" from the adapters' list, and
click on the <Add> option.
7. Choose a protocol in a similar way.
8. Exit the program, saving the changes done.
6.4 Installing the NDIS2 driver under Win95 .
There is only manual way for installation:
Similar to that of Windows for Workgroups 3.1 - installing
through the control panel. Since Win95 supports additional
driver formats, choose the driver to operate in 16-bit mode.
1. In the control panel window:
- Select the <Network>
- Select the <Adapter> (INTEL DC21x4x PCI Ethernet Controller)
- Select the <Properties>
- Select the <Driver Type> Page
- Select the Driver type - Real Mode (16-bit) NDIS driver
- Select <OK>
2. Reboot
3. Copy the file DC21X4.DOS from A:\WIN95 to the Win95 directory
<DRIVE>:\WIN95
4. Reboot
6.5 Installing multiple boards
Installation of more than one board is different in the various network
operating systems. For n adapters one must load n instances of the driver,
and have n entries in the PROTOCOL.INI file, each one corresponding to
one driver instant.
Automatic installation of multiple boards is possible in Windows for
Workgroups, Win95 and Lan Server. In Lan Manager, manual installation
must be used. In some of the networking operating systems configuring
the adapters isn't enough, and the system as a whole must be
reconfigured ( Lan Server, for example. Follow the manual ) .
One must ensure that two PROTOCOL.INI parameters are set correctly:
1. DriverName parameter must be unique for every driver instance.
The first has "DriverName=DC21X4$", the second "DriverName=DC21X42$",
and so on.
In other words, the drivers' device names are DC21X4$, DC21X42$,
DC21X43$, DC21X44$, etc.
2. SLOT must be specified for multiple boards. The first PCI device has
"SLOT=16", the second - "SLOT=17" and so on.
In CardBus the first device has "SLOT=1", currently the driver supports
only one CardBus adapter.
Here is an example of the PROTOCOL.INI for two DC21X4 boards installed
under Windows for Workgroups, using Twisted Pair:
[network.setup]
version=0x3100
netcard=DC21X4,1,DC21X4
netcard=DC21X42,1,DC21X42
transport=ms$netbeui,MS$NETBEUI
lana0=DC21X4,1,ms$netbeui
lana1=DC21X42,1,ms$netbeui
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI
[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=DC21X4,DC21X42
LANABASE=0
[DC21X4]
DriverName=DC21X4$
SLOT=16
SIA_Mode=TP
[DC21X42]
DriverName=DC21X42$
SLOT=17
SIA_Mode=TP
7. PROTOCOL.INI Parameters
Changing settings of the adapter is done by editing and changing the
PROTOCOL.INI file. This file is located in different directories,
depending on the networking operating system used.
The PROTOCOL.INI file stores configuration and binding information. It
consists of a series of named sections, where the section name is in
fact the module name from a module characteristics table. A set of
configuration settings for the module in format is as follows.
Keyword = value
where value - appropriate value for corresponding Keyword.
The following sections describe the PROTOCOL.INI settings used for the
DC21X4 Driver, their default values, the range of values that
can be given and value units.
7.1 Required Keyword
DRIVERNAME -- Specifies the network device driver.
DRIVERNAME=DC21X4n$ , where n is empty for the first board,
2 for the second, etc.
units:[text]
range:[DC21X4$ - DC21X48$]
default:[DC21X4$]
7.2 Optional Keywords in the DC21X4 section:
SLOT -- Specifies where the DC21X4-based adapter is placed.
o In PCI a number from 16 to 26 specifies the relative position
of an adapter on the PCI bus. 16 specifies the first
DC21X4-based adapter on the PCI bus, 17 the second such
adapter, and so on. When one PCI adapter is used in the system,
use "SLOT=16" .
o In CardBus a number from 1 to 16 specifies the relative socket
of an adapter on the CardBus. 1 specifies the first
DC21X4-based adapter on the CardBus. When one CardBus adapter
is used in the system, use "SLOT=1" .
o <absent> If the slot value is not specified or is specified
as 0, the driver scans for a PCI adapter if there is none
and a Card and Socket Services was loaded before the driver,
the driver will search in the CardBus sockets for an adapter.
Slot
units:[integer]
range:[0-26]
default:[16]
ConnectionType -- Defines the Serial Interface connection.
o Autosense : For adapters based on the DC 2104X
it executes an algorithm which detects the serial interface
connection type during the driver's initialization. If the chip
support dynamic autosense the detection algorithm is execute
also during run time. For adapters based on DC 21140 it
executes an algorithm which detects the data rate used -
10Mb or 100Mb. The detection algorithm is executed
also during run time if the chip support this mode.
o _10Base5_(AUI) selects the AUI connector for external
transceiver Some boards may also require a jumper on
the board to be set to distinguish between AUI and BNC.
o _10Base2_(BNC) selects the BNC (thin wire) connector for
internal transceiver. Some boards may also require a jumper
on the board to be set to distinguish between AUI and BNC.
o _10BaseT selects the RJ45 connector for the Twisted Pair
on-board transceiver, for connection to a Twisted Pair 100 Mb
hub.
o _10BaseT_FD specifies Full Duplex operation via the Twisted
Pair transceiver. The adapter should be connected to another
Ethernet station with a cable suitable for Full Duplex mode.
The line speed is 10 Mbs.
o _10BaseT_No_Link_Test selects the Twisted Pair transceiver
with Link-Fail test ignored.
o _100BaseTx selects the RJ45 connector for the Twisted Pair
on-board transceiver, for connection to a Twisted Pair 100 Mbs hub.
o _100BaseTx_FD specifies Full Duplex operation via the Twisted
Pair transceiver. The adapter should be connected to another
Ethernet station with a cable suitable for Full Duplex mode.
The line speed is 100 Mbs.
o _100BaseT4 selects port on EB140-T4 or compateble.
AUTOSENSE is a valid keywords in all adapters.
However, dynamic sensing is relevant only for adapters
based on DC 21x4.
Some DC21X4-based adapters include a jumper to switch between
AUI and BNC. To select one of these modes on such an adapter,
you should both set the jumper and specify the correct
ConnectionType value.
The driver will display an error message, and not oparate, if
the chosen media is not supported by the specific NIC.
SoftwareCRC -- controls whether packet CRCs are calculated by software
or appended by the 21X4.
o 1 means that the CRC will always be calculated by software, for
packets greater than 144 bytes. This applies only for the chips
DS21040 revisions A-H.
o 0 means that the CRC will never be calculated by
software (always appended by 21X4).
o <absent> If this keyword does not appear in PROTOCOL.INI,
packet CRCs will be calculated by software for DS21040 chip
revisions A-H (for packets longer than 144 bytes), and
will be appended by the 21X4 for all other chips.
SoftwareCRC
units:[integer]
range:[1, 0, <absent>]
default:[<absent>]
NETADDRESS -- Specifies the IEEE ethernet address to be used by the
NIC. Overrides the value specified on the ROM.
o The address is a 12-byte hexadecimal number. The user should
make sure the address is a legal IEEE address.
o The address should be surrounded by quotes.
o Example: NETADDRESS = "08002B3C45FC"
NETADDRESS
units:[hexadecimal]
range:[12 digits]
default:[ROM on NIC]
TransmitBuffers -- Specifies the number of transmit buffers the
driver should use.
o The number of transmit buffers may vary between 4 and 16.
o If this value is not specified, or the keyword is absent,
the default number of transmit buffers is 8.
o The combined number of transmit and receive buffers must
not exceed 22. If it does, the driver retreats to the
default values of 8 and 8.
TransmitBuffers
units:[integer]
range:[4-16]
default:[8]
ReceiveBuffers -- Specifies the number of receive buffers the driver
should use.
o The number of receive buffers may vary between 4 and 16.
o If this value is not specified, or the keyword is absent,
the default number of receive buffers is 8
o The combined number of transmit and receive buffers must
not exceed 22. If it does, the driver retreats to the
default values of 8 and 8.
ReceiveBuffers
units:[integer]
range:[4-16]
default:[8]
TX_THRESHOLD - Controls the transmit threshold of the device. A small
threshold may improve performance, however in some machines
it could cause many packets to be lost, and perhaps the
connection may fail.
o FP means the threshold is "Full Packet" which is maximal. The
packet will be transmitted only after it is all in the FIFO.
o LW1024 is a threshold of almost one packet.
LW512 smaller threshold,
LW256 even smaller,
LW128 the smallest threshold.
The threshold is relevant only for devices operating in 100Mb rate.
For devices working in 10Mb rate the changes are minor.
TURBO -- Controls whether host-to-PCI posting (HPPE) will be
enabled or disabled. This is relevant only if the
system's host-to-PCI bridge is INTEL's 82424 (CDC) or
82434 (PCMC) bridge.
o ENABLED means that HPPE will be disabled. This may improve
the performance of the 21X4 device.
o DISABLED means that the system configuration will remain
as it is with no intervention by the driver.
o <absent> If this keyword does not appear in PROTOCOL.INI,
the driver will do nothing and leave system settings as
they are.
TURBO
units:[text]
range:[ENABLED, DISABLED, <absent>]
default:[<absent>]
SnoozeMode -- Changes DS21041 and DS21140 power-management
mode to Power-Saving mode.
o 1 set DS21041 , DS21140 power-management mode
to Power-Saving mode.
o 0 set DS21041 and DS21140 power-management mode
to Normal operation mode.
o <absent> If this keyword does not appear in PROTOCOL.INI,
the driver will not operate the Chip Power-Saving mode.
SnoozeMode
units:[integer]
range:[1, 0, <absent>]
default:[<absent>]
PCILatencyTimer -- Configuration Latancy Timer. Specifies,
in units of PCI bus clocks, the value
of the latency timer. Changing this
parameter may affect the device performance.
PCILatencyTimer
units:[integer]
range:[1 - 255]
default:[18]
BurstLength -- Programmable burst length.
Indicates the Maximum number of longwords to be
transferred in one DMA transaction. Changing this
parameter may affect the device performance.
BurstLength
units:[integer]
range:[0,1,2,4,8,16,32] (0 means Unlimited)
default:[16 / 32] in DS2104x / DS2114x family respectively
CacheLineSize -- Cache Alignment. Programmable address boundaries
for the data burst stop. 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.
CacheLineSize
units:[integer]
range:[32,64,128,<absent>]
default:[64]
EXT_MRM -- Disable the extended PCI command MRM (Memory
Read Multiple)
o 0 Disables the MRM command.
o 1 Enables the MRM command, for the adapters
21140A rev >= 21 , 21143 rev >= 20.
o <absent> If this keyword does not apear in the PROTOCOL.INI
file, the MRM command is enabled (for the above chips).
MRM_OFF
units:[integer]
range:[0,1,<absent>]
default:[1]
EXT_MRL -- Disable the extended PCI command MRL (Memory
Read Line)
o 0 Disables the MRL command.
o 1 Enables the MRL command, for the adapters
21140A rev >= 21 , 21143 rev >= 20.
o <absent> If this keyword does not apear in the PROTOCOL.INI
file, the MRL command is enabled (for the above chips).
MRL_OFF
units:[integer]
range:[0,1,<absent>]
default:[1]
EXT_MWI -- Disable the extended PCI command MWI (Memory
Write Invalidate)
o 0 Disables the MWI command.
o 1 Enables the MWI command, for the adapters
21140A rev >= 21 , 21143 rev >= 20.
o <absent> If this keyword does not apear in the PROTOCOL.INI
file, the MRM command is enabled (for the above chips).
MWI_OFF
units:[integer]
range:[0,1,<absent>]
default:[1]
8. Driver error messages and their explanation:
* 'Could not locate adapter.'
No 21X4-based adapter is present in the system.
* 'Could not locate adapter at specified SLOT.'
The adapter wasn't found in the slot specified in the PROTOCOL.INI file.
* 'This revision of the chip is not supported by the driver.'
The revision of the 21X4 chip in the system isn't supported.
* 'FATAL: Unsupported BUS or missing BIOS support.'
For a PCI adapter :
Check that your machine has a PCI BUS and BIOS.
For CardBus adapter :
If you are using a static enabler, make sure that the enabler is loaded
prior to the loading of the driver.
If you are using a Card and Socket Services, make sure that the Card and
Socket Services were loaded prior to the loading of the driver.
Note: Card and Socket Services support is with DC21X4 v3.00 and above.
* 'Problems in devices ROM.'
A problem was detected in the device's ROM. For example, an incorrect
version number, an incorrect checksum, etc.
* 'Driver Instance Limit Exceeded.'
Too many NICs (either 4 or 8) with the DS21X4 chip are in the system.
* 'Could not open Protocol Manager.'
The protocol manager, which coordinates between different networking
software, could not be opened and therefore the driver cannot be
initialized.
* 'Could not register driver with Protocol Manager.'
The driver could not be registered with the protocol manager. This is
probably due to an initialization problem.
* 'Could not close Protocol Manager.'
The protocol manager couldn't be closed.
* 'Invalid keyword in PROTOCOL.INI.'
One of the entries in the PROTOCOL.INI file in the DC21X4 section is
invalid (an unrecognized keyword). This may sometimes be solved by
using uppercase letters when specifying values of keywords.
* 'PROTOCOL.INI keyword has too many parameters.'
One of the entries in the PROTOCOL.INI file in the DC21X4 section has
too many parameters.
* 'PROTOCOL.INI parameter too low, ignored.'
One of the entries in the PROTOCOL.INI file in the DC21X4 section has
a value too low.
* 'PROTOCOL.INI parameter too high, ignored.'
One of the entries in the PROTOCOL.INI file in the DC21X4 section has
a value too high.
* 'PROTOCOL.INI string parameter too long, ignored.'
One of the entries in the PROTOCOL.INI file in the DC21X4 section has
a string value with too many characters.
* 'Invalid PROTOCOL.INI string parameter, ignored.'
One of the entries in the PROTOCOL.INI file in the DC21X4 section has
a string value which is invalid.
* 'PCI BIOS failed to enable I/O operation.'
The DS21X4 cannot access the machine's I/O space and it is therefore
not operational.
* 'PCI BIOS configured I/O base illegal for Intel platform.'
The DS21X4 cannot access the machine's I/O space due to wrong
address mapping, and it is therefore not operational.
* 'PCI BIOS configured IRQ illegal for Intel platform.'
The DS21X4 interrupt pin is hooked to an illegal interrupt line in the
host machine. Thus, the DS21X4 isn't operational.
* 'Could not allocate GDTs.'
The driver was unable to allocate descriptor tables and it is therefore
not operational.
Relevant for the OS/2 driver only.
* 'Number of Tx/Rx buffers too large - using defaults'
The number of buffers specified by the user demands too much memory - so
the driver initializes with the default Tx/Rx buffer number.
* 'Unsupported Media - Check The PROTOCOL.INI file setting'
The Nic or driver do not support the requested media selection.
Please check the available media types on the Nic and use one of
them.
* 'No Media to work with - Cant initialize NIC '
The driver didn't find any media in the Nic to operate communication.
Please check the available media types on the NIC and the requested media
type in the PROTOCOL.INI file seting.
* ' Failed to set Connection with Mii Phy '
The driver failed to set network connection using the Mii Phy.
Please check the available media types on the NIC and the requested media
type in the PROTOCOL.INI file seting.
* ' Failed to set Connection '
The driver failed to set network connection.
Please check the available media types on the NIC and the requested media
type in the PROTOCOL.INI file seting.
* FATAL: Failed to register with Card Services.
The driver cannot register itself with this version of Card Services.
Please check that the driver supports this version of Card Services.
Important Notice
As of May 17, 1998, Digital Equipment Corporation's StrongARM,
PCI Bridge, and Networking component businesses, along with the chip
fabrication facility in Hudson, Massachusetts, were acquired by
Intel Corporation and transferred to Intel Massachusetts, Inc.
As a result of this transaction, certain references to web sites,
telephone numbers, and fax numbers have changed in the documentation.
This information will be updated in the next version of this manual.
Copies of documents that have an ordering number and are referenced
in this document, or other Intel literature may be obtained by calling
1-800-332-2717 or by visiting Intel's website for developers at:
http://developer.intel.com
The Intel Massachusetts Customer Technology Center continues to
service Network Product technical inquiries. Please use the
following information lines for support:
For documentation and general information:
Intel Massachusetts Information Line
United States: 1-800-332-2717
Outside United States: +1-303-675-2148
Electronic mail address: techdoc@intel.com
For technical support:
Intel Massachusetts Customer Technology Center
Phone (U.S. and international): 1-978-568-7474
Fax: 1-978-568-6698
Electronic mail address: techsup@intel.com
Upgrading Drivers
See the components page available on the Intel World Wide Web
Internet site at:
http://developer.intel.com/design/network/new21/download/dsc-software-nc.htm
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.