User's Manual
Table Of Contents
- Contents
- Hardware Installation
- Software Supplied
- Hardware Installation
- Unpacking and Inspection
- Other Required Equipment
- Installing Card and Cables
- PRO/100 Modem and Ethernet Connections
- Windows* 95 Installation
- Which Version of Windows 95?
- How Can I Tell Which Version I Have?
- Additional Information in this Chapter
- Windows 95 Installation (Retail Version)
- Windows 95 OSR2 Installation (OEM Version)
- How to Install for Windows 95 and NetWare*
- Utilities
- Power-Saving Modes
- Windows 95 Troubleshooting
- Troubleshooting Checklist
- Windows 95 Driver Parameters Reference
- Windows NT Installation
- Which Version of Windows NT?
- How Can I Tell Which Version and Service Pack I Have?
- Additional Information in this Chapter
- Windows NT 4.0 Installation
- Windows NT 3.51 Installation
- Power-Saving Modes
- Utilities
- Windows NT Driver Parameters Reference
- Windows 3.x/DOS Installation
- Installation under MS-DOS
- Windows 3.x Network Driver Parameters
- ODI Settings (for M16BODI.COM)
- Error Messages for Windows 3.x and MS-DOS Drivers
- Windows 3.x Troubleshooting
- Computer-Specific Application Notes (Windows 3.x)
- Utilities and Applications
- Utilities
- Country Identifier Utility
- Modem Test Utility
- Diagnostic Test Utility (M16BTEST.EXE)
- COM port monitor (Windows 3.x only)
- Communications Application Notes and Modem
- Modem Reference
- Result Codes
- AT Command Reference
- S-Register Reference
- Automated Customer Support
- Specifications
- Agency Notices
- Software License Agreement
- Index

4-56 PRO/100 LAN+Modem PC Card User’s Guide
If none of the above settings allows the driver to load, it may be necessary
to add an IOWAITSTATES=2 and MEMWAITSTATES=2 parameter to
the appropriate PRO/100 PC Card driver configuration file or command
line.
D. If the driver still fails to load after youve tried the combinations above,
your machine may require the use of Card and Socket Services. See the
preceding section.
E. Machine-specific notes:
IBM 755, 360, 355 - Set the keyword WORDSIZE=8 in your configura-
tion file or on the command line (WORDSIZE 8 for the ODI driver).
The driver loaded successfully, but I can’t
get on the network
A. Check all connections and verify that the cable drop is good (try a cable
that is known to work on another workstation).
B. Reboot by powering down the machine (cold boot). On some ma-
chines the PC Card controller chipset is not properly reset on a warm
boot, and this can cause network errors.
C. In a NetWare environment, verify that the frame type running on your
network server is the same as the FRAME type listed first in the
NET.CFG. If you are not sure what the correct Ethernet frame type is,
check with your system administrator. On a multi-server network, add a
preferred server statement to the NET.CFG.
D. There could be an interrupt conflict. Try loading the driver with a
different interrupt specified in the PRO/100 PC Card configuration file.
(This may also require some re-configuration of Card and Socket Services,
if theyre being used.)
E. If the problem persists, and youre on a 10BASE-T network, try
patching directly into the hub. If the adapter works when plugged directly
into the hub, but not when attached via a longer cable run, verify that the
cable run length is within the IEEE 10BASE-T specification (100 meters).
If the cable length is correct, the adapter may be defective. Contact Intel
Customer Support.