Troubleshooting For Soft Essays - Booting, Task Manager,

Troubleshooting For Soft Programs running in the Background Sometimes you will run into the problem where two programs that are installed on your PC conflict with each other and refuse to run at the same time. It can be tricky to find the culprit, because you think that no other programs were running, so what could possibly conflict? You'd be surprised at how many programs are running on your PC right now. Take a look right now and be amazed. Push Control (Ctrl), Alternate (Alt) and Delete (Del) on your keyboard right now. You should now see a dialog box labeled Close Programs. In there is a list of some pretty funny looking names. Each one of those is a program running right now in the background. Didn't expect to see that many, did you? Two of the items listed here are always there, that is Explorer and Systray. Those are Windows components and they are supposed to be there. But everything else is a program running right now that could be a possible culprit for your software conflict. They get loaded automatically every time you start Windows. How do they get loaded? There are several places where you can find out. Let's first look at your startup files. Go to Start/Run, and type Sysedit. In the resulting window you'll see many cascading Windows. In the Autoexec.bat window you might find a few lines to start a program. Or in the Win.ini file, look at the load= and run= lines. Anything in those lines after the = sign is a program to be loaded. Windows also has a startup folder where it checks every time Windows starts. If there are any programs listed, it will start them automatically. You can find the contents of the startup folder by going to Start/Programs/Startup. Didn't realize you had those items in there, did you? Then there is another not so obvious place: the Windows Registry. The registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run holds a list of programs to be loaded on Windows startup as well. You probably think how did they get in there since you didn't put them there. Some of them need to be running in the background to function properly, such as a virus scanner. They put themselves into a startup menu automatically when you install them. Others might not need to be there, but they load anyway to be available when you need them. Now that you know how to find out what programs you have running in the background and how they got there, let's talk about how to do some troubleshooting to find the culprit. Be systematic To find out which application is the conflicting one, you need to take a systematic approach. There are two ways to do this: You can shut down all other programs, make sure the conflict does not happen anymore, then turn them back on one by one, until the conflict happens again. Most likely the last program you turned on before the conflict reappeared is the culprit. The other option is to shut down one program at a time, until the conflict disappears. Most likely, the one program you just shut down is the culprit. Prevent them from loading The best approach is to make sure a possible suspect doesn't even load on startup. Windows 98 comes with a built-in utility that lets you control what loads when Windows starts. Start this utility by going to Start/Run, typing msconfig and clicking OK. You'll see a dialog with several tabs across the top. The last tab is labeled Startup. In here is a complete list of items that Windows loads automatically. Note the checkbox next to each item. Uncheck the first item, reboot, see if the conflict persists. If so, go back to msconfig, re-check that item, uncheck the next item and reboot. Repeat this procedure until you found the culprit. Shut them down There is also a way to shut down a program that runs in the background of your current Windows session which does not require a reboot. You can push Ctrl-Alt-Del to bring up the Close Program window. Now highlight the program you want to disable for now and click End Task. The Close Program window should disappear. Sometimes it can take a few seconds for the program to unload, so be patient. Other times, you might get another window informing you that the program is not responding. That window will have its own End Task button that you should push to close it for good. Repeat this