RE: [WinMac] Bronze PB freezing

From: Dan Schwartz (Dan[at]BrakeAndGo.com)
Date: Mon Oct 09 2000 - 12:11:47 PDT

  • Next message: kramize: "[WinMac] Update on "Bronze PB freezing""

            Awww shucks, John... Conflict Catcher is a LOT more powerful than Extension
    Manager. Besides, you can remove the " Conflict Extension" and run it as an
    application.

            Besides, MVK wrote us about this problem to begin with; so Conflict Catcher
    would be a BIG help to him in isolating the problem since it's fairly well
    automated. Using Conflict Catcher a few times will teach a user on how to
    properly use Extension Manager; but for a new user Jeffrey Robbins' program is
    a lifesaver.

            Cheers!
            Dan S.

    >-----Original Message-----
    >From: John Welch [mailto:jwelch@aer.com]
    >Sent: Monday, October 09, 2000 2:37 PM
    >To: winmac@iffy.com
    >Subject: Re: [WinMac] Bronze PB freezing
    >
    >
    >1) Run, don't walk and get Disk Warrior. Nothing else can touch it, and
    >it's *safe*. In the 2+ years since it came out, I've never had a disk killed
    >because of it, (Unlike Norton and Tech Tool), and they have excellent tech
    >support.
    >
    >2) You don't need Conflict Catcher, Extensions manager works fine, and CC
    >has been known to react oddly with certain extensions. It has some neat
    >features, but would just add to the variables.
    >
    >3) Try to shift boot. If it shift-boots, then the basic system is okay. I'd
    >delete the System Preferences file and the Finder Preferences file. These
    >can go bad, and cause odd problems.
    >
    >Also, *do* install the 9.0.4 update
    >
    >Then, in extensions manager, set it to Mac OS 9.0.4 Base, and reboot. Does
    >the problem exist here? If so, then do a clean install of the OS.
    >
    >If not, the set EM to Mac OS 9.0.4 All, and reboot. Does the problem exist
    >here? If so, in the 'View' menu, set the view to 'as packages', and then
    >disable extensions one at a time, as packages, rebooting each time, until
    >the problem goes away. Once it's gone, you've most likely found your
    >conflict.
    >
    >If the problem *doesn't* exist here, then the problem is with one of the
    >third party extensions that are left. Enable each extension, or package at a
    >time, and reboot each time until you find the problem again.
    >
    >Conflict catcher will help automate this somewhat, but again, if you don't
    >already have it, and you install it into a problematical system, you are
    >going to change the equation quite a bit, and that will make accurate
    >troubleshooting more difficult.
    >
    >john
    >
    >On 10/9/00 11:23 AM, "Dan Schwartz" <Dan@BrakeAndGo.com> wrote:
    >
    >>
    >> Make sure you run Disk First Aid to repair any file system corruption. When
    >> you get a crash, it wants to corrupt the file system. Then, when the file
    >> system starts to get corrupt the Finder wants to crash... It's a downward
    >> death
    >> spiral!
    >>
    >> Also, buy yourself a copy of Casady & Greene's Conflict Catcher: Apple's
    >> Extension Manager is a cheap knock-off; but Conflict Catcher automates the
    >> process of finding the troublemaker Extensions & Control Panels.
    >
    >--
    >"By way of deception, thou shalt do war."
    >Israel's Mossad
    >
    >
    >
    >*** Windows-MacintoshOS Cooperation List ***
    >FAQ: http://www.darryl.com/winmacfaq/
    >Archive: http://www.darryl.com/winmac/
    >
    >To unsubscribe, send mail to winmac-unsubscribe@iffy.com

    *** Windows-MacintoshOS Cooperation List ***
    FAQ: http://www.darryl.com/winmacfaq/
    Archive: http://www.darryl.com/winmac/

    To unsubscribe, send mail to winmac-unsubscribe@iffy.com



    This archive was generated by hypermail 2b29 : Mon Oct 09 2000 - 12:16:29 PDT