Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!ncar!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!tuegate.tue.nl!rc6.urc.tue.nl!rw6.urc.tue.nl!rcbaem From: rcbaem@rw6.urc.tue.nl (pooh 'Ernst' Mulder) Newsgroups: comp.sys.mac.system Subject: Re: Problems with the Control Panel cache (solved!) Message-ID: Date: 17 Apr 91 10:17:03 GMT Sender: news@rc6.urc.tue.nl Reply-To: rcbaem@urc.tue.nl Lines: 38 Summary: There's nothing wrong with the Control Panel cache. Hello world, First I would like to thank everyone who repied. I have found the source of the problems. I've got a third party SCSI port (You know? The ones you plug in the ROM sockets of a Mac 512 to have a SCSI port. My Mac once was a Mac 512, and now it's a Mac 512 with 4Mb and SCSI :) to which I traced back the problem. I wrote a small RAM test program and my RAM is OK. So is my Hard Disk. After some research the SCSI port was the only thing left that could be wrong. I called the manufacurer and explained my problem. They immediately recognized it and said I probably had an older model SCSI port which had a bug in one of its PALs. They replaced the PAL with a new one and all problems were gone! (so far :) The bug in the PAL would only have effect after certain sequences on the address bus. Apparently these occur in the Control Panel cache code and when copying files in MultiFinder. Well, I'm rather glad this problem is solved. I'm just a bit ashamed to have posted a long article claiming the Control Panel cache didn't work (which is probably not true :) but a erratic PAL wasn't one of the first things I could think of. Well, all's well that ends well. Thanks! pooh -- /********************************************************************* * Everything stated above is absolutely true. * Only the facts have been changed to protect the people involved. ***/