Troubleshooting

Connecting the hardware

Make sure you are not trying to use the adapter in a 16-bit PCMCIA slot. The CardBus Adapter is designed not to fit into a 16-bit PCMCIA slot. Do not try to force the adapter into a slot if it does not seem to fit properly.
If you are sure that the slot you are using is a CardBus slot, check that the adapter is correctly fitted into that slot. Still, however, do not force the adapter.
Check that the cable to the network is correctly and securely attached to the adapter, and that it is properly connected through to a network hub. If there is anything wrong with the network connection, the loopback test in the diagnostics program will fail. Finally, make sure you have not attached the CardBus Adapter to a Local Ringhub.

I/O ranges

If an I/O conflict involving the Madge 16/4 CardBus Adapter occurs, run DIAG to find out which I/O range the adapter is trying to use. To run DIAG, put the MADGE CSS Release Disk into the floppy drive and type: A:\UTILS\DIAG.

When you have discovered the I/O range that the adapter is trying to use, perform one of the following:

From the list of available I/O ranges that your Card Services software keeps, delete the range that the Madge 16/4 CardBus Adapter is trying to use. To do this you must refer to the Card Services documentation supplied with your PC.
Install the Madge Card Services software. Only do this, however, if you intend to use no CardBus adapters from manufacturers other than Madge. When you have installed MADGECS, create a MADGECS.CFG file (or edit the one you are already using) and use the EXCLUDE_IO= option to delete from MADGECS's list of available I/O ranges the range that your adapter is trying to use.

Sample MADGECS.CFG file

Possible conflicts with sound cards

Interrupts

The CardBus slots in most computers are permanently fixed to a single interrupt. However, on some computers each CardBus slot can use one of several interrupts. On these computers it is possible for interrupt conflicts to occur between the Madge 16/4 CardBus Adapter and devices that Card Services has not been able to find. If you are running DOS, and you receive a Madge software error message indicating an interrupt conflict, then run DIAG to find out the interrupt that the adapter is using. Then delete that interrupt from the list of available interrupts kept by Card Services. (To specify the interrupts that Card Services keeps in its list, follow the advice in your Card Services documentation.)

Memory managers

If you are running Card Services over DPMS, then there will be no memory conflict between your Card Services software and any other applications or devices in your PC. However, if you are not running over DPMS, you might need to prevent the area of upper memory that Card Services uses from being mapped by your memory manager. (If Card Services was already installed on your PC when you purchased it, you probably will not need to do this.) The following sample EMM386 device-line in CONFIG.SYS prevents 64kbytes of DOS memory from being mapped:

DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-CFFF

Make sure that Card Services allocates to itself an area of upper memory that is within the range of addresses you have excluded from your memory manager. (To specify the area of upper memory that Card Services allocates to itself, follow the advice in your Card Services documentation.)

Software error messages (use the browser's back button to return to this page).

Madge Technical Support (use the browser's back button to return to this page).