Com 226 comp trouble shooting II theory book
Dealing With Software Conflicts
Download 1.89 Mb. View original pdf
|
| Dealing With Software Conflicts Two types of software can cause conflicts in atypical PC TSRs and device drivers. TSRs sometimes called popup utilities) load into memory, usually during initialization, and wait until a system event (e.g., a modem ring or a keyboard hotkey combination. There are no DOS or system rules that define how such utilities should be written. As a result, many tend to conflict with application programs (and even with DOS itself. If you suspect that such a popup utility is causing the problem, find its reference in the AUTOEXEC. BAT file and disable it by placing the command REM in front of its command line (e.g., REM C:\UTILS\NEWMENU.EXE AD. The REM command turns the line into a “REMark,” which can easily be removed later if you choose to restore the line. Remember to reboot the computer so that your changes will take effect. Device drivers present another potential problem. Most hardware upgrades require the addition of one or more device drivers. Such drivers are called from the CONFIG.SYS file during system initialization (or loaded with Windows, and use a series of command-line parameters to specify the system resources that are being used. This is often necessary to ensure that the driver operates its associated hardware properly. if the command line options used for the device driver do not match the hardware settings (or overlap the settings of another device driver, system problems can result. If you suspect that a device driver is causing the problem, find its reference in the CONFIG.SYS file and disable it by placing the command REM in front of its command line (e.g., REM DEVICE = C:\DRIVERS NEWDRIVE.SYS /A360 /I:5). The REM command turns the line into a “REMark,” which can easily be removed later if you choose to restore the line. Remember that disabling the device driver in this fashion will prevent the associated hardware from working, |