|
Contents:
Basic Windows* Troubleshooting
These are things to check if you're having trouble running Windows* or Windows* software. A20 Handlers
Checking Available Memory
Configuring COM Ports
Ruling Out Memory Conflicts
Swap File Corruption
Using 386 Memory Managers
Using SMARTDRV.SYS
Windows Doesn't Load
WIndows locks up when using comm application
A20 Handlers
Some computers work best with particular A20 handlers. Check with your manufacturer to find out which A20 handler works best with your computer. You can use the /m: option when starting Windows to select your A20 handler. Checking Available Memory For Windows*
The most basic thing to keep in mind is that Windows* has unusual memory requirements. When encountering a strange problem, go to a DOS prompt under Windows and type CHKDSK. Pay particular attention to the amount of AVAILABLE MEMORY.
To run Windows* in enhanced mode, you need at least 450k of available memory. The closer the amount of memory comes down to 450K the more likely you are to see problems. Ideally you should have more than 500K available memory, although you can get away with memory in the high 400k range. If you have less than 460k free memory, exit Windows and remove some of the TSRs running before loading Windows. Configuring Com Ports In Windows* 3.X
When using a faxmodem under Windows, you need to correctly configure the COM port. Here's how to configure windows COM ports for faxmodems:
- From the Windows Program Manager, select "Control Panel".
- In Control Panel, select "Ports".
- Click on the the port occupied by your faxmodem then click on the "settings" button.
- Set the baud rate to the highest speed your modem supports. Set the "Data Bits", "Parity", "Stop Bits", and "Flow Control" to meet the need of your system. Here are some common settings:
| Data Bits |
8 |
| Parity |
None |
| Stop Bits |
1 |
| Flow Control |
Hardware |
NOTE: If your faxmodem supports the V.42bis or MNP 5 data compression standards, Intel recommends that you select Hardware flow control. If your modem doesn't support V.42bis or MNP 5, select "XON/XOFF". Ask the faxmodem manufacturer which is best.
- If you set your modem to COM3 or COM4, click on the "Advanced" button and make sure the "Base I/O Port Address" and "Interrupt Request Line (IRQ)" match the settings of your faxmodem. Here are the most common settings for COM3 and COM4.
|
COM3 |
COM4 |
| Base I/O |
3E8 |
2E8 |
| IRQ |
5* |
2* |
* Don't set your modem to IRQ 5 in IBM PC/XT or compatible computers (IRQ 5 is used by the hard drive controller) and refrain from setting your faxmodem to IRQ2 (the "cascade interrupt") in IBM AT and compatible computers.
- Click on the "OK" and/or "Close" buttons to save the settings and exit the Ports configuration program, then close the Control Panel.
Ruling Out Memory Conflicts
Conflicts between devices trying to use memory between 640K and 1Mb can cause Windows to malfunction. To eliminate the possibility of a memory conflict causing Windows problems, try this command:
WIN /3 /d:x
This command starts Windows in Enhanced mode, but keeps Windows from mapping memory address between 640K and 1Mb. Swap File Corruption
If you configured Windows* 3.1 for a permanent swap file, change to a temporary swap file. Here's how:
- Open the Windows Control Panel.
- Select the 386 Enhanced icon.
- Select the Virtual Memory button.
- Select the Change>> button.
- Go to the "Type:" field and select Temporary.
- Select the OK button to save the change.
- Close the Control Panel.
Using 386 Memory Managers
In 386 systems, use an EMS emulator (such as EMM386.SYS which comes with Windows or QEMM 386) to create expanded memory for CASMGR to load into. This will save you 60K of conventional memory.
NOTE: If you use EMM386.SYS, add the number 64 after the EMM386.SYS command in the CONFIG.SYS file (eg. DEVICE=EMM386.SYS 64). Using The SMARTDRIV.SYS Disk Cache
If using SMARTDRV.SYS, conserve memory by setting BUFFERS=10 in your CONFIG.SYS file. Don't load SMARTDRV.SYS into high memory. Windows Doesn't Load
Certain problems can prevent Windows from loading correctly. These problems manifest themselves by making Windows abort loading and jump right back to a DOS prompt or lock up the system. Here are a few of the problems known to cause these symptoms:
- Selecting the wrong video driver (or and incompatible video driver) in Windows SETUP program.
- Memory conflicts in extended memory or upper memory blocks.
- Loading the program called Printer Control Panel in your AUTOEXEC.BAT file and installing FAXability in Windows.
- Using CASMODEM version 1.06i with Auto Answer enabled. Fix with CASMODEM version 1.10i or later.
Windows* Locks Up When Using Comm Application
If you run Windows in STANDARD mode (WIN /S) and use a communications application while CASMODEM is set to auto answer, Windows* will lock up. Turn off auto answer before trying to use a Windows communications application.
This applies to:
| 
