Hello all,
Just to add to the Diablo3D / Diablo3S compatibility:
I've just been working on a failed Diablo3D. It was using a head-map of 0145 and I was struggling to find a suitable donor. I tried using a Diablo3S, with suitable DCM and microjogs. It provided some unusual results. It was possible to initialise the HDD to RDY, however, SA access was intermittent. If I blocked access to the SA (any method) then I could read Copy 0 modules. However, all the other heads were unresponsive. There was no write functionality for Head 0. If I allowed access to the SA the HDD would ID, but take a long time to read modules, sometimes it would click, and spin-down, then up then re-calibrate. Generally, it behaved in quite an odd way. I gave up, and swapped the heads back into the donor, and the heads still worked OK.
In the end, I used a 3TB Disablo3D which used 6 heads. With some physical alteration to the head assembly to account for the missing platter in the patient, it was possible to initialise the patient HDD on the first power on and read normally.
Best regards,
John