Installation Guide for the DOS ODI Driver ---------------------------------------- The DOS ODI driver supports eMASTER+ PCI single port adapters. This DOS ODI driver does NOT support Quartet adapters. The following is a partial list of products which the DOS ODI driver supports: --Novell NetWare 286 Client --Novell NetWare 3.1x Client --NetWare 4.x DOS Requester (VLM) --Novell Personal NetWare --Novell LAN WorkPlace for DOS --Farallon Timbuktu for Windows (PhoneNet) The DOS ODI 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. DOS ODI Driver Versions supplied on diskette --------------------------------------- \DOSODI\EMPCI.COM - Standard Version \DOSODI\EMPCIP.COM - Predictive Pipelining Version Predictive Pipelining Requirements ---------------------------------------- Predictive Pipelining is a Cogent technology that provides a performance boost between any two Cogent adapters on a NetWare network. You need Cogent adapters in your NetWare server to take advantage of Predictive Pipelining EMPCI.COM and EMPCIP.COM are installed and configured identically. All information provided below applies to both drivers. To Install and Configure the DOS ODI Driver ---------------------------------------- If you are using the VLM DOS Requester, you can run the automated NetWare Client Install that comes with NetWare: 1. Run INSTALL from your Novell install diskette labeled WSDOS_1 2. At STEP 4 during the install process, remove the WSDOS_1 diskette and insert your eMASTER+ diskette, specifying \DOSODI as the directory location for your adapter driver. Otherwise, to install the DOS ODI driver manually, follow the instructions below. 1. Boot your system under MS-DOS version 3.1 or later. 2. Insert the eMASTER+ setup diskette into drive A:. 3. Copy the \DOSODI directory on the eMASTER+ setup diskette into your workstation's NetWare directory (usually called \NWCLIENT) 4. Edit your NET.CFG file using a text editor. Add the following lines: LINK DRIVER EMPCI "parameters" (see optional parameters below) The driver will autoconfigure and perform well with no additional configuration. Optional parameters (see below) must be on indented lines below the LINK DRIVER line. The length of the indentation does not matter. For further reference, a sample NET.CFG file is provided in the \DOSODI directory with your driver. 5. Save and exit the NET.CFG file. 6. Using a text editor, edit your AUTOEXEC.BAT file so that the driver is loaded between NetWare's Link Support Layer and the network protocol, as in this example: LSL.COM EMPCI.COM IPXODI.COM VLM.EXE 7. Save and exit the AUTOEXEC.BAT file. 8. Reboot your computer. You may now use your PCI adapter. Example NET.CFG Sections ---------------------------------------- NetWare 3.11 Example: Link Driver EMPCI Frame Ethernet_802.2 Protocol IPX E0 Ethernet_802.2 Protocol IPX Bind #1; binds IPX to first frame type listed in "Link Driver EMPCI" section NetWare 3.12, NetWare 4.x Example: Link Driver EMPCI Frame Ethernet_802.2 Protocol IPX 0 Ethernet_802.3 TCP/IP Example: Link Driver EMPCI Frame Ethernet_II Protocol IP 800 Ethernet_II Protocol ARP 806 Ethernet_II Multiple Protocol Example (TCP/IP and IPX): Link Driver EMPCI Frame Ethernet_II Frame Ethernet_802.2 Protocol IP 800 Ethernet_II Protocol IPX E0 Ethernet_802.2 Protocol IPXODI Bind #2; binds IPX to second frame type Multiple Adapter Example (Two adapters, IP and IPX) NOTE: The IPX protocol can only run on one adapter per machine in DOS environments. Link Driver EMPCI SLOT 16 Frame Ethernet_II Protocol IP 800 Ethernet_II Link Driver EMPCI SLOT 17 Frame Ethernet_802.2 Protocol IPX E0 Ethernet_802.2 NET.CFG Driver Parameters ---------------------------------------- All of the following custom parameters are OPTIONAL. Parameters will AUTOSENSE or DEFAULT to the proper value in most cases. Parameter Special Notes: Full Duplex Operation: The DOS environment does not really support Full Duplex operation, but if you need to connect your adapter to a Full Duplex switch port, use the UTP_FDE parameter. Parameters listed without an associated "value" should simply be placed alone on an indented line in the LINK DRIVER section of NET.CFG. ------------------ SLOT "value" PCI slot number. Required for multiple adapters. DEFAULT: 16 for first adapter, 17 for second, etc., up to the number of Cogent adapters and Quartet ports ------------------ SBASE "value" Determines PCI slot number used for first adapter. When used, SLOT value for remaining adapters = SLOT + 1 DEFAULT: 16 RANGE: 16 - 255 ------------------ NODE ADDRESS "value" Specifies (in hex) the Ethernet node ID DEFAULT: as supplied on adapter Example: Link Driver EMPCI Node Address 000092123456 ------------------ FP_OFF Improves driver performance on some machines. Do not use with Intel's 430FX PCI chipset (which includes Intel chips with the following part numbers: 82437FX, 82438FX, 82371FB, 82438FX). RANGE: Place the FP_OFF keyword in NET.CFG ------------------ RXBUFS "value" Number of receive buffers network driver will allocate. Default provides good performance for most systems. DEFAULT: 4 RANGE: 2-4 ------------------ TXBUFS "value" Number of transmit buffers network driver will allocate. Default provides good performance for most systems. DEFAULT: 4 RANGE: 2-4 ------------------ MAXSIZE "value" (EMPCIP.COM ONLY) Enables or disables Predictive Pipelining. DEFAULT: 4202 RANGE: 1514, 4202 ------------------ PBL "value" Determines Packet Burst Length (the maximum number of DWORDs to be transferred in one DMA transaction). Zero value means that the burst is only limited by the amount of data stored in the RX FIFO buffer, or the amount of free space in the TX FIFO before issuing a bus request. DEFAULT: 16 RANGE: 0, 1, 2, 4, 8, 16 ------------------ CAL "value" Determines Cache Alignment Length, in increments of DWORDs. A value of "1" indicates an alignment length of 8 DWORDs. A value of "2" indicates a length of 16 DWORDs. A value of "3" indicates a value of 24 DWORDs. DEFAULT: 1 RANGE: 1, 2, 3 ------------------ CFLT "value" Determines PCI Configuration Latency Timer. The default is to use the latency timer as specified by the system BIOS. DEFAULT: As set in BIOS RANGE: 1-FF ------------------ Frametype "value" Specifies frame type(s) to be supported by driver. DEFAULT: ETHERNET_802.2 RANGE: ETHERNET_802.2 ETHERNET_802.3 ETHERNET_II ETHERNET_SNAP ------------------ PROTOCOL "value" Used to specify the protocol type(s) to be run on the eMASTER+ adapter. Used in multiprotocol configurations to clarify the frame type to be used by each of the loaded protocols. DEFAULT: NONE RANGE: IPX E0 ETHERNET_802.2 IPX 0 ETHERNET_802.3 IPX 8137 ETHERNET_II IP 800 ETHERNET_II ARP 806 ETHERNET_II ------------------ CABLE TYPE PARAMETERS The following parameters can be used in the NET.CFG to override cable type and line speed autosensing. THICK (EM960 C only)Sets cable type to AUI Thicknet. THIN (Combo models only)Sets cable type to BNC Thinnet. UTP Sets cable type to RJ-45 twisted pair UTP_LINK_OFF Deactivates link integrity on RJ-45 port. UTP_FDE (10BASE-T and 100BASE-Enables Full Duplex mode on RJ-45 X only)port. SPEED "value" (10/100 models only)Sets cable speed to be used by the adapter. Example: Speed 10 ACTIVESENSE Configures the driver for autosensing at regular intervals during runtime. The driver will automatically 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. Use the ACTIVESENSE keyword only when a cable is connected to the adapter. DEFAULT: Driver will perform an autosense cycle at initialization time to determine cable type and line speed.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.