+--------------------------------------------------------------+
| NDIS 2 MAC DRIVER for DC21040/DC21041/DC21140 V2.00 |
+--------------------------------------------------------------+
Note that this installation kit includes both the DOS
and OS/2 NDIS2 driver and this document describes
installation under both environments. This revision
supersedes the DOS and OS/2 NDIS2 driver version 1.03 .
RELEASE.TXT in the top level directory describes changes
from the previous driver versions.
NOTE: The generic term "DC21X4" relates to the DECchip
21040, DECchip 21041 and DECchip 21140 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 DC21X4 PCI boards .
5.2 Installing the DC21040 EISA 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 Microsoft Lan Manager .
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 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 (Beta Version) .
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:
First Edition, June 1994
Present Revision March 1995
Digital Equipment Corporation makes no representations that
the use of its products in the manner described in this
publication will not infringe on existing or future patent
rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use, or
sell equipment or software in accordance with the
description.
Copyright Digital Equipment Corporation 1994, 1995.
All rights reserved.
Do not redistribute the driver files.
Windows, 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.
Alpha, DEC, DECchip, DECnet, Digital, PATHWORKS, ThinWire,
and the DIGITAL logo, are trademarks of Digital Equipment
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, OS/2 and Win95 .
This driver is currently supported for the DECchip 21040,
DECchip 21041, DECchip 21140 based 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 EISA or PCI bus.
o a DECchip DC21X4-based Ethernet adapter for that bus.
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 or V3.0 (WARP) with one of
0 Lan Manager Versions 1.3 or 2.x .
0 Lan Server Versions 3.0 or 4.0 .
OR
o Windows95 (Beta build 426 and onwards).
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:
5.1 Installing the DECchip 21040/21041/21140 PCI Evaluation Boards
For the EB40, see the DECchip 21040 PCI Evaluation Board User's guide.
For the EB140, see the DECchip 21140 PCI Evaluation Board User's guide.
For the EB41, see the DECchip 21041 PCI Evaluation Board User's guide.
5.2 Installing the DECchip 21040 EISA LAN Controller(DE425):
The following conditions for the DE425 may be selected in
the !DEC4250.CFG file:
1. Interrupt options:
o Edge-Triggered Interrupt (default)
o Level-Triggered Interrupt (no sharing)
o Level-Triggered Interrupt (sharing)
2. Supported interrupt numbers are:
o 5 (default)
o 9
o 10
o 11
3. For cable types:
o AutoDetect (default)
o Twisted Pair (actual default)
o Twisted Pair - Full Duplex
o Twisted Pair - No Link Test
o AUI Thick-wire
o BNC (ThinWire)
Note: Two cable types are not supported by this driver
with the DE425 adapter:
Autodetect and Twisted Pair - No Link Test.
If either of these 2 choices is made in the EISA
configuration utility, Twisted Pair will be used
instead.
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).
6.1 Basic driver installation (for DOS-based and OS2/2 NOS)
o Add the following line to CONFIG.SYS:
DEVICE=<drive>:[pathname]\DC21X4.DOS (or DC21X4.OS2)
If the DECchip 21X40 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:
DC21X4 NDIS 2 MAC Driver Version <version>
(C) Copyright Digital Equipment Corporation. All rights reserved.
DC21040 Adapter
PCI Slot: <nn> IRQ:<nn>
Operation Mode:<xxx>
(For the DC21041 or DC21140 the adapter name is different)
(Foe EISA adapters, the EISA slot is specified)
Where:
Slot is the slot of the adapter
IRQ is the interrupt request level
Operation Mode is the serial interface mode and data rate - 10Mb
or 100Mb (DC21140 only) .
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
If 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 .
6.2.2.2 Manual Installation for Windows for Workgroups 3.1
If 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.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:
If 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
If 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.OS\DRIVERS\ETHERNET\DC21X4\DC21X4.OS
and
\MSLANMAN.OS\DRIVERS\ETHERNET\DC21X4\PROTOCOL.INI
to the new directory.
3. Copy the file
\MSLANMAN.OS\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 or 4.0 for OS/2
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 3.0 - Click on the LAPS icon.
LanServer 4.0 - Click on the MPTS icon.
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 .
The driver version 2.00 was tested only on a beta version of Win95
(build 426). This beta version's installation procedure still
isn't entirely stable.
There are two paths of installation:
1. 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.
2. The driver can be installed during the machine's boot when new
Plug-and-Play devices are identified. In this case follow the
instructions on the screen, using the <Have Disk> option, and
loading the driver from A:\WIN95.
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.
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
DECchip 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 A number from 1 to 15 specifies a slot number on the EISA bus
o 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" .
If the slot value is not specified or is specified
as 0, the driver scans for an EISA adapter; if no EISA
adapter is found, it then scans for a PCI adapter.
Slot
units:[integer]
range:[1-26]
default:[16]
SIA_MODE -- Defines the Serial Interface connection.
o AUTODETECT : For adapters based on the DECchips 2104X
it executes an algorithm which detects the serial interface
connection type during the driver's initialization. For adapters
based on DECchip 21140 it executes an algorithm which detects
the data rate used - 10Mb or 100Mb.
o AUTOSENSE is similar to AUTODETECT, however the detection
algorithm is executed also during run time.
o 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 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 TP selects the RJ45 connector for the Twisted Pair (10BaseT)
on-board transceiver, for connection to a Twisted Pair hub.
o TP_FULL_DUPLEX 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.
o TP_LINK_DISABLE selects the Twisted Pair transceiver with
Link-Fail test ignored.
AUTODETECT and AUTOSENSE are valid keywords in all adapters.
However, dynamic sensing is relevant at present only for adapters
based on DECchip 21041.
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
SIA_MODE value.
DATA_RATE -- Defines the data rate at which the LAN controller
will operate.
o MB10 specifies a data rate of 10Mb (Suitable for standard
ethernet)
o MB100 specifies a data rate of 100Mb (suitable for fast
ethernet). The keyword is valid only if the physical 100Mb
port is connected to the net.
NICs based on the DC2104x will ignore this keyword and always
work on a 10Mb rate.
For NICs based on DC21140 the default is MB100.
SOFTWARE_CRC -- Controls whether packet CRCs are calculated by
software or appended by the DC21X4
o ENABLED means that the CRC will always be calculated by
software, for packets greater than 144 bytes.
o DISABLED means that the CRC will never be calculated by
software (always appended by DC21X4).
o <absent> If this keyword does not appear in PROTOCOL.INI,
packet CRCs will be calculated by software for DC21040 chip
revisions A-H (for packets longer than 144 bytes), and
will be appended by the DC21X4 for all other chips.
SOFTWARE_CRC
units:[text]
range:[ENABLED, DISABLED, <absent>]
default:[<absent>]
NUM_TX_BUFFERS -- 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 If the combined number of transmit and receive buffers is
large, problems may arise. Specifically, in OS/2 environments
the driver may be unable to load.
NUM_TX_BUFFERS
units:[integer]
range:[4-16]
default:[8]
NUM_RX_BUFFERS -- 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 12.
o If the combined number of transmit and receive buffers is
large, problems may arise. Specifically, in OS/2 environments
the driver may be unable to load.
NUM_RX_BUFFERS
units:[integer]
range:[4-16]
default:[12]
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 DC21X4 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>]
8. Driver error messages and their explanation:
* 'Could not locate adapter.'
No DC21X4-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 DC21X4 chip in the system isn't supported.
* 'Problems in PCI Bus.'
A problematic PCI device was found, and driver execution must halt.
The usual solution is changing the cache-mode in the machine setup
performed during boot time.
* '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 DC21X4 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 DC21X4 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 DC21X4 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 DC21X4 interrupt pin is hooked to an illegal interrupt line in the
host machine. Thus, the DC21X4 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.
9. Hotline and Support Information:
Call the Digital Semiconductor Information Line for information
and technical support:
United States and Canada 1-800-332-2717
TTY (United States only) 1-800-332-2515
Outside North America +1-508-568-6868
Ordering Digital Semiconductor Products
To order Digital's Alpha semiconductor products, contact your
local Digital sales office. When working with your sales
representative, you may be able to take advantage of discounts
and volume pricing.
To order Digital Semiconductor samples or Sample Kits call
1-800-DIGITAL.
You can order the following from Digital:
21040-AA DECchip 21040 PCI Ethernet LAN Controller
21140-AA DECchip 21140 PCI Fast Ethernet LAN Controller
21050-AA DECchip 21050 PCI-to-PCI Bridge
21A40-01 DECchip 21040 PCI Evaluation Board Kit
21A40-02 Quad DECchip 21040 PCI Evaluation Board Kit
21A40-03 DECchip 21140 PCI Fast Ethernet Evaluation Board Kit
21A50-01 DECchip 21050 Evaluation Board Kit
Ordering Associated Literature
Digital Semiconductor documentation and literature is
available with the products. For a complete list and
for information about ordering, contact the Digital
Semiconductor Information Line.
Associated Ethernet Controller Literature:
EC-N0280-72 DECchip 21040 PCI-Ethernet LAN Controller
Data Sheet
EC-QC0BA-TE DECchip 21140 PCI Fast Ethernet LAN Controller
Data Sheet
Ordering Third-Party Literature
You can order the following third-party literature
directly from the vendor:
Title Vendor
----------------------------------------------------------
PCI System Design Guide PCI Special Interest Group
N/S HH3-15A
5200 N.E. Elam Young Pkwy
Hillsboro, Oregon 97124-6497
1-503-696-2000
----------------------------------------------------------
Electronic Orders
To place an order through your account at the Electronic Store,
dial 1-800-234-1998, using a modem set to 2400- or 9600-
baud. You must use a VT terminal or terminal emulator set
at 8 bits, no parity. If you need assistance using the
Electronic Store, call 1-800-DIGITAL (1-800-344-4825) and
ask for an Electronic Store specialist.
Telephone and Direct Mail Orders
From Call Write
__________________________________________________________
U.S.A. DECdirect Digital Equipment Corporation
Phone: P.O. Box CS2008
1-800-DIGITAL Nashua, NH 03061
(1-800-344-4825)
FAX: 603-884-5597
Puerto Phone: Digital Equipment Corporation
Rico 809-781-0505 3 Digital Plaza, 1st Street
FAX: 809-749-8377 Suite 200
Metro Office Park
San Juan, Puerto Rico 00920
Canada Phone: Digital Equipment of Canada Ltd.
1-800-267-6215 100 Herzberg Road
FAX: 613-592-1946 Kanata, Ontario, Canada K2K 2A6
Attn: DECdirect Sales
International - Local Digital subsidiary or
approved distributor
Internal DTN 264-3030 U.S. Software Supply Business
orders 603-884-3030 Digital Equipment Corporation
FAX: 603-884-9690 10 Cotton Road
Nashua, NH 03063-1260
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.