At 12:14 -0400 10/5/2001, Tobey Wheelock opined:
>Ron Risley 10/5/01 12:01 PM [EMAIL PROTECTED]
>
>>It can, but it is *far* more likely that a poorly written application
>>or extension has written to an area of memory that it isn't supposed
>>to.
>
>How do you know which it is?

The usual technique is to disable all non-Apple extensions and avoid 
running all but your most vital applications for a time and see if 
your crashes go away. If so, then add your desired extensions back 
one at a time until the crashes start occurring again.

If the crashes are frequent enough, you can use Conflict Catcher to 
narrow down the problem fairly quickly.

--Ron
-- 
Ron Risley      ||       Fresh Baby Pictures Added Daily!
[EMAIL PROTECTED]  ||         http://risley.net/matthew/
www.risley.net  ||

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to