CardBus 10/100Mbps Ethernet Card NDIS2 DOS Driver Ver 1.40 Table of Contents: ------------------ 1. Overview . 2. Preinstallation Hardware and Software Requirements . 2.1 Hardware Requirements . 2.2 Software Requirements . 3. Files and Directories . 4. Installing Software. 4.1 Basic driver installation . 4.2 Installing the NDIS2 DOS driver : 4.2.1 Installation with Micrososft Lan Manager 2.x. 4.2.2 Installation with Windows for Workgroups Version 3.11 . 5. PROTOCOL.INI parameters . 5.1 Required Keywords . 5.2 Optional Keywords . 6. Driver error messages and their explanation . ----------------------------------------------------------------------------- 1. Overview: This Readme file explains how to install the NDIS2 driver under DOS, Windows for Workgroups. 2. Preinstallation Hardware and Software Requirements: 2.1 Hardware Requirements: o An IBM-compatible personal computer with 80386 or higher microprocessor and PCI bus. 2.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.11 . 3. Files and Directories: Directory Structure: General files in root directory -------------------------------------------------------------------- README.TXT The readme file that you are currently reading. Installation in different operating systems ------------------------------------------- \WFW311 Directory with Windows for Workgroups 3.11 installation files. \MSLANMAN.DOS Directory structure used for installation under LanManager (DOS) 4. 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 4.5, Installing multiple boards). 4.1 Basic driver installation (for DOS-based, Window For Workgroups) o Add the following line to CONFIG.SYS: DEVICE=<drive>:[pathname]\CBNDIS2.DOS When the CBNDIS2 Driver is installed in DOS HIGH memory use the following: DEVICEHIGH=<drive>:[pathname]\CBNDIS2.DOS o The following information is displayed when the system is rebooted: CardBus 10/100Mbps Ethernet Card Ver 1.40 (C) Copyright 1994-1998. All rights reserved Working with Digital Semiconductor 21143 based Ethernet Controller PCI Slot: <nn> IRQ:<nn> Where: Slot is the slot of the adapter IRQ is the interrupt request level Selected madia: xxx (In this line is displayed later) 4.2 Installing the NDIS2 DOS driver. 4.2.1 Installation with Microsoft LAN Manager 2.x 4.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. 4.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 CBNDIS2 Driver directory <DRIVE>:\LANMAN.DOS\DRIVERS\ETHERNET\CB100 2. Copy the files \MSLANMAN.DOS\DRIVERS\ETHERNET\CB100\CBNDIS2.DOS and \MSLANMAN.DOS\DRIVERS\ETHERNET\CB100\PROTOCOL.INI to the new directory. 3. Copy the file \MSLANMAN.DOS\DRIVERS\NIF\NETCB.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\CB100\CBNDIS2.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: [NETCB_NIF] DRIVERNAME=CBNDIS2$ 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 = NETCB_NIF 4.2.2 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 CardBus 10/100Mbps Ethernet Card 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. 5. 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 CBNDIS2 Driver, their default values, the range of values that can be given and value units. 5.1 Required Keyword DRIVERNAME -- Specifies the network device driver. DRIVERNAME=CBNDIS2n$ , where n is empty for the first board, 2 for the second, etc. units:[text] range:[CBNDIS2$ - CBNDIS28$] default:[CBNDIS2$] 5.2 Optional Keywords in the CBNDIS2 section: SLOT -- Specifies where the card is placed. o A number from 16 to 26 specifies the relative position of an adapter on the PCI bus. 16 specifies the first card 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 <absent> If the slot value is not specified or is specified as 0, the driver scans for a PCI adapter. Slot units:[integer] range:[0-26] default:[16] ConnectionType -- Defines the Serial Interface connection. o Autosense : it executes an algorithm which detects the serial interface connection type and data rate during the driver's initialization. The detection algorithm is executed also during run time. 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. 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 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>] SnoozeMode -- Changes power-management mode to Power-Saving mode. o 1 set power-management mode to Power-Saving mode. o 0 set 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:[32] 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. o <absent> If this keyword does not apear in the PROTOCOL.INI file, the MRM command is enabled. 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. o <absent> If this keyword does not apear in the PROTOCOL.INI file, the MRL command is enabled. 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. o <absent> If this keyword does not apear in the PROTOCOL.INI file, the MRM command is enabled. MWI_OFF units:[integer] range:[0,1,<absent>] default:[1] 6. Driver error messages and their explanation: * 'Could not locate adapter.' No 10/100Mbps Ethernet Card is present in the system. * 'Could not locate adapter at specified SLOT.' The card 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 chip in the system isn't supported. * 'Problems in PCI Bus.' A problematic PCI device was found, and driver execution must halt. The ususal solution is changing the chache-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 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 NETCB_NIF 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 NETCB_NIF section has too many parameters. * 'PROTOCOL.INI parameter too low, ignored.' One of the entries in the PROTOCOL.INI file in the NETCB_NIF section has a value too low. * 'PROTOCOL.INI parameter too high, ignored.' One of the entries in the PROTOCOL.INI file in the NETCB_NIF section has a value too high. * 'PROTOCOL.INI string parameter too long, ignored.' One of the entries in the PROTOCOL.INI file in the NETCB_NIF 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 NETCB_NIF section has a string value which is invalid. * 'PCI BIOS failed to enable I/O operation.' The CBNDIS2 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 CBNDIS2 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 CB100 interrupt pin is hooked to an illegal interrupt line in the host machine. Thus, the CBNDIS2 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.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.