Share this Page URL
Help

Fixit 18. Check for Problems with Extens... > Disable Startup Extensions to Determ... - Pg. 654

Check for Problems with Extensions and Control Panels (Startup Extensions) 654 Sometimes these conflicts are easy to diagnose. Other times, they can be very subtle. For example, an application may have some quirk that appears only when you are using a new AutoSaver startup extension while running with virtual memory turned on and the QuicKeys startup extension also installed. Regardless of the symptoms, the cause of these conflicts is typically a software bug (though de- velopers may argue among themselves whether the source of the bug is in the startup extension or in the software with which it conflicts). Three basic types of startup extension conflicts occur, as follows: Conflict with another startup extension--Conflicts with another startup extension are often the hardest to diagnose because even when you think you have found the problem startup exten- sion, another one may be at least partially responsible. This type of conflict is the one most likely to lead to system crashes during the startup sequence. Conflict with another application--The symptoms of a conflict with another application may show up as a malfunction of the startup extension or as a problem with the application (often seemingly unrelated to the startup extension functioning, such as a menu command that does not work). Conflicts with system software--The worst-case scenario is when the startup extension is in- compatible with the version of the system software you are using. In this case, problems are likely to occur in a variety of contexts across applications. The startup extension may not work at all. Startup problems are also possible. Although a startup extension conflict is not the only possible cause of many of these symptoms, it is usually an easy one to either confirm or eliminate. That's why it should be one of the first things you check. Startup Extensions That Do Not Load or Run A startup extension may simply not work at all--even without any sign of conflict with other software. Typically, this is because the startup extension never loaded into memory at startup (which it must do in order to work!). A startup extension conflict may still be the underlying cause here, but other causes are possible. For example, remember that you cannot use a newly installed startup extension without first placing it in the System Folder (typically in the Control Panels or Extensions folders) and then restarting. What to Do: Described here are the three main steps to solving startup extension conflicts: (1) Disable startup extensions to determine if you have a startup extension conflict, (2) identify the problem startup extension, (3) resolve the conflict. The final section of this Fix-It deals with what to do for a startup extension that appears not to load or run at all. Disable Startup Extensions to Determine if You Have a Startup Extension Conflict The logic is simple. Temporarily disable all of your startup extensions. If the problem goes away, then you know you have a startup extension conflict. There are three different ways to disable your startup extensions: hold down the Shift key during startup, use a startup management utility, or remove all startup extensions from your System Folder. To quickly disable all of your startup extensions, nothing is better than the Shift key method. It is simple, easy to do, and guaranteed to disable almost all system extensions and startup extension- type control panels in your System Folder.