Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!cbmvax!amix!vanth!jms From: jms@vanth.UUCP (Jim Shaffer) Newsgroups: comp.sys.amiga.hardware Subject: system lockup problem continues Message-ID: Date: 22 Jan 91 13:46:24 GMT Lines: 40 A few weeks ago I posted a request for help with a problem with my A500. It was locking up occasionally when I tried to use the floppy drives. I got three suggestions from the net: First, that it was a bug in trackdisk.device. Second, that it was a power supply problem. Third, that it was a bad 8520 chip. The first suggestion didn't seem to be relevant because I was using both SetPatch 1.3.2 and Tracksalve, both of which are supposed to take care of that bug. Furthermore, the problem gets much worse when the system has been on for a while and has heated up. Keeping a fan running to cool the system helps a lot. The second suggestion also didn't seem relevant, because the fan was blowing on the system rather than on the power supply. The third suggestion, a damaged 8520 chip, was also suggested to me by several people I talked to in person, including some who have had to replace several 8520s in the past. So I replaced both my 8520 chips. Unfortunately, replacing the 8520 chips had absolutely no effect on the problem. I'm now looking for other suggestions. Although the fan prevents the problem almost always, the noise of it is starting to annoy me. Also, the fan causes the image on my monitor to waver slightly. The waver is accompanied by a minor color shift. It's tolerable, but I don't know if it's safe for the monitor. (It's a 1084S, if anyone wants to speculate.) Worse, I doubt that the fan will be adequate in the summer. Does anyone know what the next step should be? To repeat the problem, my A500 locks up totally when I try to use the floppy drives after the system has been running for about an hour. (When it's cool, it's fine.) The problem happens most often when something is using DF1: and I try to invoke a new command from DF0:. As soon as the DF0: motor comes on the system locks up. (Both drive motors stay on.) I've also had the problem happen rarely when accessing just one drive after a period of inactivity, but it happens most often when I try to use both drives at once. I've had it happen when I'm trying to WRITE to DF0: also, and the files remain untouched -- it definitely seems to happen as soon as the motor comes on. -- From the disk of: | jms@vanth.uucp | "Glittering prizes and Jim Shaffer, Jr. | amix.commodore.com!vanth!jms | endless compromises 37 Brook Street | 72750.2335@compuserve.com | shatter the illusion of Montgomery, PA 17752 | (CompuServe as a last resort)| integrity!" (Rush)