• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Fixit 18. Check for Problems with Extens... > Do a Conflict Test to Isolate the Pr...

Do a Conflict Test to Isolate the Problem Extension(s)

If none of the preceding methods succeed, it's time to systematically disable and reenable all your startup extensions. This is a potentially long and tedious process, especially if you have many extensions. Not only does it take a long time, but it requires your active involvement throughout the process. This means you can't just walk away for an hour and come back after the procedure is over. You must constantly be present to watch what happens and respond accordingly.

In previous editions of Sad Macs, I described a procedure for "manually" doing this sort of isolation. It basically involves systematically shuttling extensions in and out of your System Folder, restarting each time, until you figure out which extension is causing the problem. However, using Conflict Catcher is a so much better alternative that I am no longer going to waste the space to discuss any other way to do it. If you are serious about tracking down extension conflicts, get Conflict Catcher. Conflict Catcher can also include fonts and Control Strip modules and other related files in a conflict test.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint