ericg@ucschu.ucsc.edu (Eric Goodman) (09/18/90)
This problem has been solved, but I'm really confused as to what went
wrong in the first place.
I opened my ST to reseat some of the chips (GLUE, MMU) because of some
video problems I was getting with my color TV (it was suggested that that
might help cure the problem. It hasn't, but that's another story... :-( )
which I use as a monitor. Anyway, I opened it up, disconnected the
internal disk drive, reseated the chips, and when I put the thing back
together and booted, the drive would spin, but it couldn't read any disks
("Drive A is not responding"). So I re-disconnected most of the same
things (sorry, I don't remember which ones I left out here), and
re-reconnected it. Same problem. I repeated this process about 8-12
times. Finally, I let it sit for 6 hours (two football games) , redid the
process one more time, and now it works. The questions:
1) What connections are so finicky that I had to try so many times before
they were good? I've worked on _MUCH_ more sensitive equipment without
getting this type of problem.
2) I didn't see any socketed ROM'S, I thought they came in sockets.
My system is a 520STFM, TOS 1.2, motherboard blitter ready, with a New
World Board 2Meg memory expansion.
It's a
Eric Goodman, UC Santa Cruz
ericg@ucschu.ucsc.edu ericg@ucschu.bitnet
Eric_Goodman.staff@macmail.ucsc.edu ...!ucbvax!ucscc!ucschu!ericg