HyperDrive troubleshooting

JeffC

Tinkerer
Sep 26, 2021
122
79
28
Seattle, WA
I have a 512k with a 20mb HyperDrive I picked up a few months back, the HyperDrive was non-functional when I bought it. The drive itself did not work, a component on the controller board (the board on the drive, not the HyperDrive daughterboard) had melted and damaged the board. I just picked up a replacement MiniScribe 8425, the same model as the original drive. I was told the drive was working, and I'm inclined to believe the seller. When powered up the drive spins up freely, and the head moves back and forth freely during its startup check, though I can not be certain the drive works, and I don't have anything else that uses an MFM drive that I could test it with.

I installed the new drive, and beyond the drive spinning up and the heads moving back and forth once, there is no sign of activity. I removed the HyperDrive daughterboard from the logic board and re-seated the Killy clip in case there was a connection issue from corrosion or something, there was no change in behavior. The board and Killy clip both showed no signs of corrosion. I checked the voltage coming out of the auxiliary power supply, and it showed a very steady 5.0v and 12.2v.

I had the idea of checking the MFM interface cables for activity using a scope. I have a scope, but know essentially nothing about using it, other than a couple videos I watched on scope basics. I checked all the pins of both the connectors going to the drive, and they all showed the same signal, I would charactarize it as noise, but I really don't know what I'm looking at. It looked identical for all pins. I was hoping to see some sort of signal that was different, that would suggest the HyperDrive daughterboard was trying to talk to the drive.

I booted the machine with the HyperDrive system disk and ran the utility, it said the drive needed to be formatted, I clicked format and immediately got an error saying the drive needed dealer service. There was no sign of activity from the drive during this process.

Does anyone have any thoughts on further troubleshooting?

Thanks
 

Attachments

  • PXL_20221112_162826246.jpg
    PXL_20221112_162826246.jpg
    1.7 MB · Views: 42