ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ PLANET ENW-9501 Plus ³
³ More Information about NDIS 2 MAC Driver ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
A. 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 2, Installing multiple boards).
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)
If the DC21X4 Driver is installed in DOS HIGH memory use
the following:
DEVICEHIGH=<drive>:[pathname]\DC21X4.DOS
B. 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, 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:
a. 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.
b. 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
C. 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.
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$]
2. Optional Keywords in the DC21X4 section:
SLOT -- Specifies where the DC21X4-based adapter is placed.
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 a PCI adapter.
Slot
units:[integer]
range:[1-26]
default:[16]
SIA_MODE -- Defines the Serial Interface connection.
o AUTOSENSE : For adapters based on the HT-200 it executes an
algorithm which detects the serial interface connection type
during the driver's initialization.
For adapters based on HT-2000 it executes an algorithm which
detects the data rate used - 10Mb or 100Mb.
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.
DATA_RATE -- Defines the data rate at which the LAN controller
will operate. (HT-2000 only)
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.
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>]
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]
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>]
SNOOZE -- Changes HT-200 and HT-2000 power-management mode
to Power-Saving mode.
o ENABLE set HT-200 and HT-2000 power-management mode
to Power-Saving mode.
o DISABLE set HT-200 and HT-2000 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.
SNOOZE
units:[text]
range:[ENABLE, DISABLE, <absent>]
default:[<absent>]
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.