I'd focus on improving this situation before trying other, generic fixes. I still think the best thing to to is to get the drive to try and free up itself rather than moving the head servo on your own.
My advice: be patient.
Thank you!This is a great thread...keep up the good work!
Correct. I plugged in the ground, and the new CRT's picture looks lovely.Hmm about the Widget --- so after repeated resets, or startups and shutdowns, the heads don't seem to advance any further than they did originally?
Don't forget the white ground wire that comes off of the CRT socket. It's easy to forget. (Ask me how I know.)
It happens immediately upon hitting the power switch. Before the screen even illuminates it generates an error tone, and when the screen illuminates that error 52 is showing. It certainly does not get through the CPU and Memory test first, as it otherwise would.52 is an "I/O board COPS error", and I'm not sure why an expansion card should cause that kind of trouble. How soon does it come up --- right during the power-on tests? Does it happen during the I/O board test or later when the expansion cards are under test?
Well, this solution has several nice features. Not the least of which is that it's dead silent, and leverages a lot of the work that @stepleton has done on Cameo/Aphid. Also, it's rather nice looking hardware.
Not giving up on the Widget, either. We'll sort that one out, one way or another.
Well, crap. I broke 2 pins off one of the Widget hard drive's ribbon cable connectors. I can only find one of the pins, too. Soldering those back on will be quite the challenge.
Well, crap. I broke 2 pins off one of the Widget hard drive's ribbon cable connectors. I can only find one of the pins, too. Soldering those back on will be quite the challenge.
I had purchased a replacement motherboard, controller, servo, and read/write boards in case one of those was the culprit.
Will probably have to use the hard drive emulator exclusively from here on out.
This is why I can't have nice things.![]()