Yeah I've noticed that too. Salvaged one for the 3400c I think, but not for the Kanga. So it's not recurring corrosion from that in this case. Look I don't know. Hopefully yours comes out fine, but I don't think it's worth the risk - particularly since who really cares about PRAM batteries (especially now).
Is there a way to totally bypass the SCSI bus on boot and force it to ATA? I tried forcing to SCSI ID and holding down mouse button [both via internal key/track, bc it doesn't seem to recognize ADB keys] to no effect.
I'll take a look at where the traces from the ATA bus are coming from. Weirdly despite the symptoms, it clearly is an ATA bus problem - who (who knows more about this than I) knows how the ATA bus initially interacts - like what's the process, and what would be missing (signal-wise ?) that would cause it to fail to be recognized, but then later recognized once the SCSI bus powers up?
Is there a way to totally bypass the SCSI bus on boot and force it to ATA? I tried forcing to SCSI ID and holding down mouse button [both via internal key/track, bc it doesn't seem to recognize ADB keys] to no effect.
I'll take a look at where the traces from the ATA bus are coming from. Weirdly despite the symptoms, it clearly is an ATA bus problem - who (who knows more about this than I) knows how the ATA bus initially interacts - like what's the process, and what would be missing (signal-wise ?) that would cause it to fail to be recognized, but then later recognized once the SCSI bus powers up?
Last edited by a moderator: