Installation Guide for the Cogent eMASTER+ PCI DOS and OS/2
NDIS Drivers
----------------------------------------
The following is a partial list of products which use the
DOS NDIS driver:
--Microsoft LAN Manager Clients
--Microsoft Windows for Workgroups
--IBM DOS LAN Requester
--DEC PATHWORKS for DOS
--SunSelect PC-NFS
--Banyan VINES Client
--3Com 3+Open
--Various brands of TCP/IP
The following is a partial list of products which use the
OS/2 NDIS driver:
--IBM OS/2 2.0 and 2.1
--IBM OS/2 Warp
--IBM LAN Server 4.0
--MS LAN Manager
The DOS NDIS driver is compatible with DOS extended memory
managers and can be loaded into high memory. In addition,
the driver is compatible with Windows 3.0 and later.
Instructions for installing the NDIS 2.0 driver for
Microsoft LAN Manager 2.x, Microsoft Windows for Workgroups,
and IBM LAN Support Program are provided in the following
sections. If you are using another NDIS product, consult the
product's documentation for instructions about installing a
network driver.
Products known to automatically build the necessary
configuration files when the DOS NDIS driver is installed
are LAN Manager 2.x, Windows for Workgroups, and IBM LAN
Support Program. If you are using another product, you may
need to manually edit PROTOCOL.INI and CONFIG.SYS.
To Install the NDIS Driver
----------------------------------------
Follow the instructions below to install the NDIS driver for
LAN Manager, Windows for Workgroups, and IBM LAN Support
Program and others.
1. Boot your system
2. Run your network operating system's Setup program
according to the documentation provided with your
network operating system software.
3. When prompted, insert the eMASTER+ setup diskette
in drive A:.
4. Enter information as required.
5. Exit your network operating system's Setup
program.
6. Reboot your computer.
You may now use your PCI adapter.
NOTE: If you are installing multiple eMASTER+ adapters in a
single machine, you must modify CONFIG.SYS and PROTOCOL.INI.
To Configure the DOS NDIS Driver
----------------------------------------
To complete installation of your DOS NDIS driver, you may
need to edit your PROTOCOL.INI and CONFIG.SYS files using a
text editor. Some products automatically add the appropriate
lines to these files when the DOS NDIS driver is installed.
When your eMASTER+ driver is installed, several lines are
added to your configuration files.
1. In PROTOCOL.INI:
[EMPCI_NIF]
DRIVERNAME=EMPCI$
2. In the protocol section of PROTOCOL.INI:
BINDINGS=EMPCI_NIF
3. In CONFIG.SYS after the line which loads the
protocol manager:
DEVICE=C:\'path'\PROTMAN.DOS
DEVICE=C:\'path'\EMPCI.DOS
Where 'path' is an optional parameter indicating the
location of the DOS NDIS driver.
In Windows for Workgroups 3.11, the EMPCI.DOS driver loads
from the SYSTEM.INI file, rather than the CONFIG.SYS.
To Configure Multiple Adapters
----------------------------------------
If multiple eMASTER+ PCI adapters are installed in a single
computer, you must edit the PROTOCOL.INI and CONFIG.SYS
files using a text editor as follows:
1. To PROTOCOL.INI, add a unique DRIVERNAME entry for
each adapter. In addition, the BOARD parameter
must be specified for all network adapters in
the system with the exception of the first
adapter. For example, if two EM960 PCI adapters
are installed, the fragment appears as follows:
[EMPCI_NIF]
DRIVERNAME=EMPCI$
'parameter'
[EMPCI2_NIF]
DRIVERNAME=EMPCI2$
BOARD=2
'parameter'
Where 'parameter' indicates optional driver
parameters which are discussed in the following
section.
2. In the protocol section(s) of PROTOCOL.INI, bind
the protocol to multiple instances of the driver
as in the following example for two EM960 PCI
drivers:
BINDINGS=EMPCI_NIF, EMPCI2_NIF
3. In CONFIG.SYS after the line which loads the
protocol manager:
DEVICE=C:\'path'\PROTMAN.DOS
DEVICE=C:\'path'\EMPCI.DOS
Where 'path' is an optional parameter indicating
the location of the DOS NDIS driver.
PROTOCOL.INI Driver Parameters
----------------------------------------
When it loads, the DOS NDIS driver assumes a default
configuration which provides good performance with moderate
use of memory. However, to increase your adapter's
performance or decrease your adapter's memory requirements,
the driver's configuration may be modified by adding
parameters to the PROTOCOL.INI file. Keep in mind that
improving performance generally requires more memory while
decreasing memory requirements generally reduces
performance.
Special Notes:
Full Duplex Operation: Requires FULLDUPLEX parameter
be set to TRUE.
430FX PCI Chipset: If your system uses the Intel
430FX PCI chipset (which
includes Intel chips with the
following part numbers:
82437FX, 82438FX, 82371FB,
82438FX), set the FULLPACKET
parameter to TRUE.
The DOS NDIS driver supports the following parameters in the
driver section of PROTOCOL.INI. Unspecified parameters
assume their default values. Note that not all parameters
apply to all adapters.
----------------------------------------
DRIVERNAME="value"
Identifies the adapter"s driver name. Each adapter installed
must have a different driver name.
Default: EMPCI$
Range: EMPCI$, EMPCI2$, EMPCI3$, etc.
----------------------------------------
MAXRECEIVES="value"
Specifies the number of receive buffers that the network
driver will allocate. Memory use is approximately 1600 bytes
per unit.
Default: 16
Range: 1-30
----------------------------------------
MAXTRANSMITS="value"
Specifies the number of simultaneous transmit requests that
the network driver may queue. Memory use is approximately
150 bytes per unit.
Default: 8
Range: 1-30
----------------------------------------
NETADDRESS="value"
Overrides the network address of the network adapter board.
This parameter should only be used if there are duplicate
addresses on the network. If this entry is specified, its
value must be a valid individual address (i.e. not a
broadcast address). The value of this parameter is a string
of 12 hexadecimal digits enclosed in quotes, for example:
NETADDRESS="00BAD0BEEF00"
----------------------------------------
FullDuplex = "true" or "false"
This adapter forces an adapter using twisted pair cabling to
operate in full duplex mode. Full duplex can greatly
increase network throughput because both transmit and
receive pairs can be active simultaneously.
The default mode is half duplex, where only one pair is
active at a time.
Default: FALSE
Range: TRUE | FALSE
----------------------------------------
Transceiver = "AUTOSENSE" or "UTP" or "THICK" or "THIN"
This parameter selects for the cable type in use.
Default: AUTOSENSE
Range: AUTOSENSE | UTP | THICK | THIN
----------------------------------------
ACTIVESENSE = "TRUE" or "FALSE"
This parameter configures runtime autosensing. Runtime
autosensing allows the adapter to adjust to a change in
cable type or line speed without requiring a driver reload.
(When configured for ACTIVESENSE, the driver will also
display a message if a cable break occurs.) Do not use this
parameter if no cable is attached to the adapter or Quartet
port.
Default: FALSE
Range: TRUE | FALSE
----------------------------------------
SharedIRQ = "true" or "false"
This parameter is for OS/2 only and enables or disables
shared interrupts.
Default: TRUE
Range: TRUE | FALSE
----------------------------------------
IRQ = "value"
This parameter is only necessary on Quartet adapters when
used in systems which do not support the PCI bridge. This
parameter provides the interrupt that will be used by the
NDIS driver.
Default: must be specified.
Range: 3,4,5,7,9,11,12,15
----------------------------------------
DisablePosting = "true" or "false"
This parameter should be used on the first driver instance
only. The parameter will provide compatibility for certain
PCI motherboard chipsets (OPTI and SIS) which have been
found to exhibit memory contention problems between the host
CPU and the PCI bridge chip.
Default: TRUE ( for SIS,OPTI), FALSE (all others)
Range: TRUE | FALSE
Specifying Adapters in Multiple Adapter Configurations
----------------------------------------
By default, the EMPCI.SYS or EMPCI.DOS driver will find the
first uninitialized Cogent Ethernet port in the system.
Initialization of multiple ports will therefore proceed
sequentially. You can, however, use PCIBUS and PCIDEVICE
parameters to discretely specifying individual Ethernet
ports.
----------------------------------------
PCIBus="value"
This parameter determines the PCI Bus of the Ethernet port
you wish to initialize. This value can be determined by
first running the EMSETUP diagnostics program.
Default: 0
Range: 0 - 255
----------------------------------------
PCIDevice="value"
This parameter determines the PCI Device ID of the Ethernet
port (on a specific bus, determined above) you wish to
initialize. This value can be determined by first running
the EMSETUP diagnostics program and looking at the value
reported under "Configuration Status."
Range: 0 - 32
example:
[EMPCI_NIF]
DRIVERNAME=EMPCI$
PCIBUS = 1
PCIDEVICE = 4
This references the device #4 on bus #1. For a Quartet, this
would be the first port.
Performance Parameters
----------------------------------------
Certain advanced NDIS parameters for Cogent PCI adapters are
for performance tuning. You generally will not need to
change these parameters from their default value. If you
feel comfortable with performance tuning, though, these
parameters are available to you. They are CacheAlignment,
BurstLength, TxThreshold, and Fullpacket.
----------------------------------------
CacheAlignment = "value"
Sets programmable boundaries to stop burst memory transfers.
The controller bursts up to the specified cache boundary.
If a buffer is not aligned, the controller bursts up to the
address boundary, requiring an addition DMA transaction to
complete the transfer. Furthermore, if a burst crosses a
CPU cache line, then the system imposes wait-states on the
transfer while the cache controller resets the cache.
Optimum efficiency results, therefore, when the Ethernet
controller"s cache alignment matches the CPU"s cache line.
Default: 16
Range: 0 (none), 8, 16, 32
----------------------------------------
BurstLength = "value"
Specifies the maximum number of doublewords transferred in
one DMA transaction. (This setting should be less than or
equal to the CACHEALIGNMENT setting above.)
Default: 16
Range: 0,1,2,4,8,16,32
----------------------------------------
TxThreshold = "value"
Specifies the relative threshold byte boundary for the
controller to initiate transmits. A larger number
corresponds to a higher threshold. Actual values depend on
the speed of the device being controlled:
Default: 10 Mbps connector: 2 (128 bytes)
100 Mbps connector: 1 (256 bytes)
Range: 0,1,2,3,4
----------------------------------------
Fullpacket = "value"
Used for performance optimization on motherboards using
Intel's 430FX PCI chipset. Set to true only when using a
430FX PCI chipset, or when directed by Cogent Technical
Support.
Default: False
Range: True | False
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.