Intel EtherExpress PRO/100 User Manual page 101

PC Card driver configuration file should match the resources
assigned by the LAN1xxxxxx keywords in the CARDID.INI
file. The LAN1MEMORYBASE2 entry can be ignored.
A driver failed to load, and I'm NOT using Card and Socket Services
A Verify that a block of memory for use by the PRO/100 PC Card
has been excluded from any memory manager being loaded.
Memory managers are generally loaded in the CONFIG.SYS.
The following example is given for EMM386.EXE and a PRO/
100 PC Card loading at its default memory address of D2000:
DEVICE=C:\PATH\EMM386.EXE NOEMS X=D200-D2FF
B Since your are not using Card and Socket Services, verify that
power management has been disabled and the PC Card socket is
powered/enabled in the computer system's CMOS setup. These
settings may not be present in all machines. Consult your
computer documentation for information on how to access and
modify the system setup.
C Reboot the machine by turning off the power and turning it back
on again (cold boot). If the driver still fails to load, the cause is
generally a resource conflict. Common causes of resource
conflicts include sound systems, other PC Card adapters, and
built in ROMs. The resources required for a PRO/100 PC Card
include a memory window (MEM keyword), an interrupt (INT
keyword, and an I/O address (IOADDRESS keyword). The
default settings are indicated below.
Review your computer documentation to determine what
resources are available, or use a trial and error approach. The
table on the next page shows a suggested trial and error se-
quence. If you use this method, be sure to add a memory
exclusion from C000-DFFF to the EMM386 line until a suitable
memory location has been found. Then the memory exclusion
can be reduced to a 4K window. Perform a cold boot between
each trial to ensure that the PRO/100 PC Card and PC Card
sockets are completely reset.
When the PRO/100 PC Card driver is loaded it either reads a
configuration file or uses command line parameters to determine
which resources it should use. See the list of driver types, driver
file names, and configuration methods earlier in this chapter.
Troubleshooting
101