A manual clean install, with insertions of extensions until a problem occurs, can in these cases be faster than fighting through Conflict Catcher to get the answers.ĭisconnecting SCSI devices works only if there are problems that might be SCSI related. If several problems are occurring frequently, then linear troubleshooting through Conflict Catcher may not be the answer.
#CLEAN INSTALLATION OF CLASSIC MAC OS 8 INSTALL#
(The problem being with QuickTime VR or something, but really with QuickTime, since Conflict catcher disabled QuickTime loading but left VR running.) Extension management is an excellent tool, and extensions are usually the problem.Ī clean install is another matter. I will note, however, that while Conflict Catcher is an excellent troubleshooter, it has a tendency to isolate the wrong problem. It’s something I always end up learning from. When I’m on site and have used my intuition with no avail, I run conflict test. Extension elimination can be a tricky process, and Conflict Catcher often finds “order of loading” issues or simple conflicts that I can not intuitively guess. This is certainly the correct method, which is one of the reasons I require the use of Conflict Catcher on client machines. Disconnecting SCSI devices worked 21% of the times tried.Clean installs worked 28% of the times tried.Extensions troubleshooting worked 56% of the times tried.I’ll include my comments within the document, and summarize at the end. There are addendums, or ways that I normally operate, that work a bit against this exact strategy, but in the end I’m assuming the very path this tech describes. You’ve posted quite a little gem – I’m not being sarcastic. I would also be interested to know if people agree with what this Apple tech has to say. 1998 – This is a long post, but it is relevant to many of the problems we have discussed recently.
0 kommentar(er)
