Extensions Conflicts - System 7.5
Diagnosing Extensions Conflicts: Plan A
Remember if you need to sleuth out an Extensions conflict take a strong dose of patience and go directly to your handy-dandy Extensions Manager via the Control Panels menu in the Apple Menu.
If the Extensions conflict is so severe that your computer cannot start up ("will not boot"), then you need to restart the computer while holding down the Shift key. This will force the computer to start up with "Extensions off", thereby temporarily sidestepping the conflict while you hunt it down. Then go to the Extensions Manager Control Panel.
At the top of the Extensions Manager window, there is a pull-down menu that is labeled Sets:. Your current set of Extensions is most likely called Custom. Let's rename this normal set of Extensions so we can save it for later reference. Choose the Save Set command from the Sets pull-down menu and name this set of Extensions something meaningful to you like "Normal".
Extensions are turned on in the Extensions Manager window by clicking on each Extension name so that a small check mark appears to the left of the name. Extensions are turned off in the same manner clicking on them in the Extensions Manager so that the check mark disappears.
Now you will begin a systematic game of "Whodunit?". Most Extensions conflicts occur after you have installed a new piece of software, because one of the Extensions (or Control Panels) already on your system is not coexisting peacefully with the new arrival. To first test this theory turn off the newest Extension (or Control Panel), restart your computer (note, at the bottom of the Extensions Manager, it says "changes take effect at restart") and see if the Extensions conflict goes away. If it doesn't, then try Plan B. If it does, continue on with the following process to ferret out which of your older Extensions is conflicting with the new one.
Return to the Extensions Manager. Turn the newest Extension back on. Then you are going to begin a systematic process of turning off each of the older Extensions one by one then testing to see if the symptom of the conflict reoccurs.
Go down the list in the Extensions Manager. Turn off one Extension. Restart your computer. Test for the Extensions conflict. If the conflict still occurs, return to the Extensions Manager. Turn the first Extension back on, turn the next one off. Restart your computer. Again, test for the Extensions conflict. And then keep going turning each Extension off and then on again until you have isolated the culprit. Don't forget to test the Control Panels listed in the Extensions Manager window, too.
After each Extension is turned off, it is advisable to rename this new Extension set for this testing procedure. So, each time you remove an Extension, choose the Save Set command from the pull-down menu and name your set "test". You will be asked if you want to replace the previous "test" set, and yes, you do.
Diagnosing Extensions Conflicts: Plan B
So you're unable to figure out what's causing the Extensions conflict? How about a different approach...
From the Sets pull-down menu at the top of the Extensions Manager window, select the set of Extensions called System 7.5.5 (or whatever is your current operating system) this set includes only those Extensions that were installed with your operating system. Now restart your computer. If the symptoms of the Extensions Conflict do not disappear at this point, then something else is likely wrong with your computer...try Plan C Clean Install
Once your machine is running with the default System set of Extensions, open the Extensions Manager Control Panel again. You will now use the Extensions Manager to turn on additional Extensions one at a time adding them back to this System set.
Restart your computer after each additional Extension is added back into the set and test whether your computer exhibits the same Extensions conflict symptom.
Again, it is advisable to rename each new Extension set for this testing procedure. So, each time you add an Extension, choose the Save Set command from the pull-down menu and name your set "Test". You will be asked if you want to replace the previous "Test" set, and yes, you do.
Once you have identified an Extension that when turned on causes the Extensions conflict to reoccur, you should find its partner in the conflict. To do this, you will keep this problem Extension on and systematically turn off others one by one as described above in Plan A.
Fixing Extensions conflicts
Once you have found the troublemakers, what do you do? Contact the companies that produce both Extensions to discuss the problem with them. Often there is an updated version for one of the Extensions or another remedy for the conflict. If you are in the unfortunate position, of being one of the first users to discover this particular conflict then you at least have alerted the company to the problem.
If there is no known fix for the Extensions conflict and you still want to use the software or hardware on your machine, you do have recourse through the Extensions Manager. Create two (or more) different Extension sets so that you can turn on and off conflicting Extensions when you need to. For example, we have a CD-ROM Extensions set to avert problems when our children play their games...for a while we had a Scanner Extensions set while we were working the bugs out of Kim's new scanner set up. Just go into the Extensions Manager choose the Extensions you need for that function and rename that new set CD-ROM or Scanner or whatever. Then you only need to select that set and restart a minor inconvenience compared to not being able to use that software or hardware at all.
By the way, there is a very popular program called Conflict Catcher (Casady and Greene, Inc.) that automates this process of testing Extensions and in some cases prevents conflicts before they occur.
Copyright © 1997 WriteDesign. All Rights Reserved.