International Business Machines Corporation 35H3636 Manuel D’Utilisation
Appendix B. Problem Determination
Check this list of possible error conditions if problems occur.
1. Make sure that the PC Card is in the socket and that the cable is connected to
the PC Card.
2. You are using EMM386.EXE or another memory manager.
EMM386 is the source of many problems with PC Cards. The problem occurs
when EMM386.EXE and the LAN device driver are using the same memory.
This is called
when EMM386.EXE and the LAN device driver are using the same memory.
This is called
memory contention. The PC Card will not function correctly if this
contention occurs. If you are using Card Services, check to be sure that the
memory that Card Services controls is excluded by the memory manager. If you
are using a point enabler, be sure that the memory that you use is excluded by
the memory manager. As a quick test, you may want to comment out
EMM386.EXE in your CONFIG.SYS, reboot, and try the PC Card again.
memory that Card Services controls is excluded by the memory manager. If you
are using a point enabler, be sure that the memory that you use is excluded by
the memory manager. As a quick test, you may want to comment out
EMM386.EXE in your CONFIG.SYS, reboot, and try the PC Card again.
If the PC Card functions, you will have to edit the EMM386.EXE command to
exclude some memory. The PC Card uses 8 KB of memory in two separate
areas. These memory areas may be consecutive. See Using a Memory
Manager in DOS Environments for more information.
exclude some memory. The PC Card uses 8 KB of memory in two separate
areas. These memory areas may be consecutive. See Using a Memory
Manager in DOS Environments for more information.
3. You are using Card Services.
During reboot, you hear four alternating tones. This indicates that Card Services
was unable to give you one or more resources that your program requested.
Resources are I/O ports, interrupt level, and memory locations.
was unable to give you one or more resources that your program requested.
Resources are I/O ports, interrupt level, and memory locations.
Note: The items in the following paragraph are performed by the installation
program.
If you are using the NDIS driver (IBMTOKCS.DOS), edit the PROTOCOL.INI file
and see whether you have specified a particular value for the interrupt level or
memory locations. This would be indicated by the keywords INTERRUPT=X,
MMIO=0xXXXX, or RAM=0xXXXX. If you are using the ODI driver
(TOKENCS.COM), edit the NET.CFG file and see whether you have specified a
particular value for the interrupt level or memory locations. This would be
indicated by the keywords INT X, MEM #1 XXXXX, or MEM #2 XXXXX.
and see whether you have specified a particular value for the interrupt level or
memory locations. This would be indicated by the keywords INTERRUPT=X,
MMIO=0xXXXX, or RAM=0xXXXX. If you are using the ODI driver
(TOKENCS.COM), edit the NET.CFG file and see whether you have specified a
particular value for the interrupt level or memory locations. This would be
indicated by the keywords INT X, MEM #1 XXXXX, or MEM #2 XXXXX.
These keywords specify a particular value for these parameters. If you find one
or more of these keywords, comment them out by placing a semicolon in front
of the keyword. Save the file and reboot your computer. If all three are
commented out or are not in PROTOCOL.INI or NET.CFG, the driver is in
Autoset mode and lets Card Services determine what values are used by the
driver. If you reboot and still receive the alternating beep alarm, there is a
problem with Card Services. Check your level of Card Services and ensure that
it is the latest available.
or more of these keywords, comment them out by placing a semicolon in front
of the keyword. Save the file and reboot your computer. If all three are
commented out or are not in PROTOCOL.INI or NET.CFG, the driver is in
Autoset mode and lets Card Services determine what values are used by the
driver. If you reboot and still receive the alternating beep alarm, there is a
problem with Card Services. Check your level of Card Services and ensure that
it is the latest available.
4. You are using a point enabler.
When you use a point enabler, it is essential that the I/O ports, interrupt,
memory areas, and slot number that are chosen by the enabler agree with what
the LAN device driver is expecting. Problems occur when the enabler has set
up certain resources and the LAN device driver is expecting others. Typically,
the LAN driver will not initialize. Look at the default values for the interrupt,
whether the PC Card is a primary or secondary PC Card (this affects the I/O
ports), and where the MMIO memory and the SRAM memory are located. Be
sure that the enabler settings and the settings of the LAN driver coincide. By the
use of parameters on the command line of the enabler and the parameters for
memory areas, and slot number that are chosen by the enabler agree with what
the LAN device driver is expecting. Problems occur when the enabler has set
up certain resources and the LAN device driver is expecting others. Typically,
the LAN driver will not initialize. Look at the default values for the interrupt,
whether the PC Card is a primary or secondary PC Card (this affects the I/O
ports), and where the MMIO memory and the SRAM memory are located. Be
sure that the enabler settings and the settings of the LAN driver coincide. By the
use of parameters on the command line of the enabler and the parameters for
© Copyright IBM Corp. 1997, 1999
49