Bunsen wrote:

That's true, up to a point. Extensions Manager is adequate for most purposes. However, EM will not show every extension or CP, declaring some off-limits and invisible to the user. The third-party manager Symbionts (and, IIRC, Conflict Catcher) will show every item in those two folders, as well as other system folder items which can be "managed" (moved to non-active folders). If one wants to create the smallest possible system folder, for example for a RAM-challenged system, it does a more thorough job.

Click to expand...

True enough. The catch all description Extension can be very confusing because it includes INITs (which patch the OS at boot), OS plug-ins (eg Chooser extensions) and Libraries (like DLLs). However to resolve a startup clash, you only need to worry about Extensions and Control Panels that have INIT code. Libraries, for example, are not called during boot so they are not going to create startup problems.

However a third party extension manager is going to help manage non-INIT extensions. If you have two applications that require different versions of a Library, different startup sets are the way to work.