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

Windows 3.x/MS-DOS Installation 4-59
3 Turn computer power off and then on again (cold boot).
4 Start the Windows Terminal program in the Accessories group.
Select a COM port under the setting/communications options, click
OK to get back to the terminal screen. Change to modem command
mode and type AT, then press enter. If the modem responds with
OK, the trial configuration was correct.
5 In some cases an interrupt conflict will not be apparent until a
Windows mouse driver is loaded. It will then be necessary to cold
boot the machine, load the PRO/100 PC Card driver and re-start at
step 1. above.
C. Try disabling Card and Socket Services if they are enabled (see Item 2
of these Symptoms and Solutions).
D. If you are NOT using Card and Socket Services, try the following:
1 Verify the following entries in the Windows SYSTEM.INI file:
BOOT.
COMM.DRV=COMM.DRV
386ENH.
DEVICE=*VCD
You may need to remark out any *VCD.386 added by other
programs (IBMVCD.386, PCMVCD.386, SSVCD.386).
2 In Windows, go into the Control Panel, then Ports, and under the
Advanced options, set the selected COM port IOADDRESS and
INTERRUPT to default settings.
3 Exit Windows and turn computer off and on again (cold boot).
4 Start the Windows Terminal program in the Accessories group.
Select a COM port under the setting/communications options, click
OK to get back to the terminal screen. Change to modem command
mode and type AT, then press enter. If the modem responds with
OK, the trial configuration was correct.
5 In some cases an interrupt conflict will not be apparent until a
Windows mouse driver is loaded. It will then be necessary to cold
boot the machine, load the PRO/100 PC Card driver and re-start at
step 1. above.