Driver Diskette (Ver 4.20) Overview
For 10/100 Mbps Fast Ethernet CardBus Adapter
TOPIC
======================================
1. DISKETTE CONTENTS
2. NETWORK DRIVERS FOR WINDOWS 95
3. NETWORK DRIVERS FOR WINDOWS 98
4. NETWORK DRIVERS FOR WINDOWS NT4.0
5. NETWARE DOS ODI DRIVER
[1] DISKETTE CONTENTS
Files and
Subdirectories Contents
--------------------------------------------------------------------
\README.TXT This file
\LNDL100C.INF An INF file for Windows 95 and Windows 98
\OEMSETNT.INF An INF file for WinNT4.0
\LNDL100.SYS Windows 95,98,NT4.0 Driver
\ODI Novell Netware DOS ODI Driver
\ENABLER Contains enabler programs to enable CardBus
\Manual\MAN100N.HTM Manual file, HTML format
[2] Network Drivers for Windows 95 OSR2
INSTALLATION PROCEDURE:
1) Plug the 10/100 Ethernet CardBus Adapter into the CardBus slot,
and insert "Driver Diskette" into Drive A:.
The system displays the "Update Device Driver Wizard" dialog box,
press "Next" button.
2) If no driver is found, select "Other Locations". Then input
"A:\" to specify the driver's location where the device information
file (.INF file) and the driver (.SYS file) can be found.
3) Press "OK", the driver then installs itself. If have "Insert Disk"
dialog box for asking other file, type in your Windows path or
Windows\system or your Winsows 95 CD-ROM to find the file.
4) Click "Finish" to complete the installation process.
5) Reboot the machine to start the network.
[3] Network Drivers for Windows 98
INSTALLATION PROCEDURE:
1) Plug the 10/100 Ethernet CardBus Adapter into the CardBus slot,
and insert "Driver Diskette" into Drive A:.
The system displays the "Add New Hardware Wizard" dialog box,
press "Next" button.
2) Select "Search for the best driver for your device", click "Next".
3) Select "Floppy disk drives", press "Next" button.
4) If the driver is found, press "Next" button, then it installs itself.
3) If have "Insert Disk" dialog box for asking other file, type in your
Windows path or Windows\system or your Winsows 98 CD-ROM.
4) Click "Finish" to complete the installation process.
5) Reboot the machine to start the network.
[4] NDIS 4.0 DRIVER FOR WINDOWS NT4.0
The NT4.0 driver supports 15 types of CardBus Controllers, include
TI1130, TI1131, TI1250, TI1220, TI1221, TI1225, TI1251, Cirrus Logic 6832,
O2 Micro OZ6832/6833, 6836/6860, 6812, Toshiba ToPIC95,Ricoh RL5C475,
476, and 478.
INSTALLATION PROCEDURE:
1) Open the Control Panel, and choose Network Settings.
2) Select the "Adapter".
3) Click "Add" button.
4) Press "Have Disk" button.
5) You can see "Cnet 10/100 Mbps CardBus Adapter" in the dialog box, Press "OK".
6) Select free IRQ and I/O address.
7) Then go back "Network", select "Bindings"
8) Press "Close" button.
9) If you use TCP/IP Protocol ,set IP Address, asking your Windows NT 4.0 Server Administrator.
10) Click on "OK" and restart the computer.
11) Please go to "Devices" of "Control Panel" for check the driver status,
if it display "Cnet 10/100 Mbps CardBus Driver Started Automatic",
the driver is wroking.
12) If still can't link to network, user can try another IRQ number,
maybe 5, 9, 10, or 11.
[5] Netware DOS ODI Driver
1. For those who installed EMM386.EXE in your config.sys, please exclude
memory address D400-D7FF from your system. PCMCIA Ethernet card enabler
program will use this space to read Ethernet ID and CIS from on-board
flash memory.
[Example]
DEVICE=EMM386.EXE NOEMS X=D400-D7FF
or
DEVICE=EMM386.EXE NOEMS X=D000-DFFF
2. User need to add "LASTDRIVE=[Device Name]" in the Config.sys file,
then reboot Notebook. Example, if you want to login to Device "N",
the string is "LASTDRIVE=M".
3. Enable the FastEthernet PC Card
The "\ODI" directory contains Ethernet DOS ODI driver DC21X4.COM
that supports NetWare 3.x and 4.x, NetWare Lite and other ODI interface
application.
DC21X4.COM : DOS/ODI Driver for NetWare 3.x and 4.0.
You can follow the instruction below to install DOS ODI Drivers of
Novell's NetWare Operating System.
How To Install
--------------
You need following some files to install DOS ODI DRIVER.
a. PBX.COM ---- Intercept PCI BIOS function call
b. ENABLER.EXE ---- Enabler Program for CardBus Controllers
c. LSL.COM ---- supported by Novell
d. DC21X4.COM ---- Novell DOS ODI Driver ,supported
by manufacturer
e. IPXODI.COM ---- supported by Novell
f. NETx.EXE ---- supported by Novell
or
EMSNETx.EXE
or
XMSNETx.EXE
g. NET.CFG ---- optional,configuration file
There is a sample BATCH file named "STARTNET.BAT".
You can type "STARTNET" command to log in to the Netware's File
Server. If want to know more information, Please read the "readme.txt"
file in the \ODI directory.
Normally, you will need a NET.CFG file to configure your Ethernet
PC Card.
You can see Netware 386 Installation appendix E for more
information about NET.CFG.
Below is a sample NET.CFG file:
LINK DRIVER CARDODI
Frame Ethernet_II
Frame Ethernet_802.3
Protocol IPX 0 Ethernet_802.3
:
:
Error messages
==============
- FATAL: Failed to lock system memory
Driver call to OS memory support routines for locking its
internal buffers and descriptors failed.
- FATAL: DC21X4 driver works only with 386 or above!
The driver failed to identify the CPU as a 386 or above the
driver can run on 386 (or above) machines only.
- FATAL: Slot value error!
The user has specified an illegal slot number in NET.CFG
50 - FATAL: Board not found in system
Driver could not detect a supported NIC in the system.
200 - FATAL: Timeout when initializing DC21X4 with setup packet!
This happens mainly when the PCI slot does not support DMA.
Make sure the BIOS setup or motherboard switches are set to
enable DMA or Bus Master operation of this slot.
210 - FATAL: DC21X4 Does not support this bus type
The machine is not identified as a PCI machine or the user has
specified BUS ID which is not PCI.
212 - FATAL: DC21X4 Does not support this device revision
The DC21x4 drivers do not support DC21140 rev 1.0 chip. If you
receive this message, please make sure you have an updated rev
of your NIC.
217 - FATAL: Failed to find PCI BIOS
The machine is not identified as a PCI machine (to support PCI
NICs). This error is generated when the driver is directed to
load a PCI NIC using the BUS ID keyword (in DC21X4.COM v2.0 and
above) and PCI 4 is specified, or SLOT keyword (in DC21X4 V1.02
and below), and slot value is a PCI slot number (16 and above).
218 - FATAL: Bad PCI BIOS status
PCI BIOS returned a fail status in one of the calls. Please
check the BIOS version and BIOS correctness using an external
utility.
219 - FATAL: Bad PCI BIOS Register err
PCI BIOS returned a fail status in one of the calls. Please
check the BIOS version and BIOS correctness using an external
utility.
220 - FATAL: PCI BIOS failed to initialize DECchip 21x40 CBIO reg!
PCI BIOS has initialized a DWORD register in the NIC's
configuration space (at offset 10Hex) with illegal value (in x86
machines this value is between 0 to FFFFHex). Please check the
BIOS using an external utility. Also verify that your BIOS setup
enables the slot the NIC is plugged in, allocates I/O addresses
to it and initializes correctly the device in this PCI slot.
222 - WARNING: KWD RXD No param
The user added the RX_BUFFERS key word in NET.CFG but did not
specify the number of buffers required.
Add the number of buffers to the KWD (such as: RX_BUFFERS 9)
222 - WARNING: KWD RXD Param too small
The number of Rx buffers specified by the user is too small
for proper driver's work.
Please increase the amount of Rx buffers in RX_BUFFERS KWD in
NET.CFG
The minimum number of rx buffers is 2.
222 - WARNING: KWD RXD Param too big
The user had specified more rx buffers than the driver can handle
Please decrease the amount of Rx buffers in RX_BUFFERS KWD in
NET.CFG
The maximum number of rx buffers is 16 but it may be less depending
on the driver's size.
225 - FATAL: PCI BIOS allocated an illegal Interrupt to DECchip 21x40!
PCI BIOS has initialized a byte register in the NIC's
configuration space (at offset 3CHex) with illegal value (in x86
machines legal values are between 1 to 15). Please check the
BIOS using an external utility. Also verify that your BIOS setup
enables the slot the NIC is located in, enables interrupts to
this slot and assigns a legal interrupt number to it.
226 - WARNING: Can not handle Turbo switch
Cannot operate the 'Turbo' mechanism from one of the following reasons:
- The chipset on the motherboard does not support TURBO mode.
- The chipset parameters are unknown to the driver.
226 - FATAL: Failed to handle Turbo switch
Failed to operate the 'Turbo' mechanism from one of the
following reason:
- PCI BIOS returned a fail status in one of the calls involved
with operating this mechanism.
We strongly recommend to reboot the PC after such an Error occures
227 - FATAL: Internal CRC table corrupted
Driver found an error in internal CRC table either because the
driver file is corrupted or someone has changed the table's
contents.
228 - FATAL: Could not handle chipset bug workaround successfully
Failed to operate chipset bug workaround because PCI BIOS
returned a fail status in one of the calls involved with
operating this mechanism.
229 - WARNING: This machine Host to PCI bridge has a known bug.
Driver limits DC21X4 bursts as a workaround.
230 - FATAL: This machine Host to PCI bridge has a known bug when
using cache in WB mode which may cause data corruption
or system hang. Please change the cache mode to WT
(Write Through) as a workaround.
231 - WARNING: The PCI Host Bridge present in this machine requires that the
driver switch to Store and Forward Mode. Network performance
may be affected.
The driver detected a PCI Host Bridge with limited data transfer rates
to be present in the PC. it modifies DC21X4 chip parameters for working
in such a system. This may slightly slow the network performance.
No further action is needed.
240 - FATAL: Unable to locate Adapter ROM!
Driver failed either to locate the address ROM or read it. This
might happen due to bad data stored in the serial ROM.
240 - FATAL: Failed to read ROM!
Driver failed to read the serial flash ROM due to a hardware
failure. Make sure the IEEE flash ROM on your NIC is operational
using external utility.
240 - FATAL: Unsupported ROM Version
The version (and hence the format) of the data read from the
SROM is not supported by the driver. Please run an external
utility to upgrade the Serial ROM's data.
240 - FATAL: This DS chip does not support this ROM version
This ROM version does not contain the information needed by the
driver in order to correctly activate the DS chip located on-board.
Please run an external utility to upgrade the Serial ROM's data and
add the device specific information to it.
241 - FATAL: Unsupported media selection
The NIC or device do not support the requested media selection.
Please check the available media types on the NIC and use one of
them.
241 - FATAL: Could not find media or PHY to work with
The driver failed to find any medium in the NIC.
This may happen due to a bad Serial ROM programming or an MII PHY failure.
242 - WARNING: Could not find a connected medium.
The Power-Up autosense could not find a connected medium,
Please connect a cable to one of the ports and the Autosense routine
will automaticlly find and use it.
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.