Since I could never afford an LS-120 drive back in the day (too young) I have recently obtained a few to marvel at.
However I am having a bit of trouble getting them to work. The BIOS detects the drive fine - I have it set up as master on the first IDE channel - however as soon as I insert a (1.44MB) disk, the problems start.
The drive spins up, the LED comes on, and then briefly blinks off about once a second. When it momentarily blinks off, the drive makes a seeking noise, very similar to when a conventional floppy moves to the next track. This behaviour actually made me think at first that the drive was reading the whole disk into a buffer to improve performance, but unfortunately this is not the case.
The eject button has no effect at this point, and in fact holding down the eject button seems to freeze the whole PC until I let go. The drive stops making noises and the LED stops flicking off once a second (staying lit), but the PC also stops responding until I let go of the drive's eject button.
When there is a disk in the drive and it is behaving in this manner, the BIOS no longer detects the drive, and it also fails to detect the Zip drive I have as slave on the same IDE channel.
If I reboot the PC, the drive resets and acts as it does when the disk is first inserted, but immediately returns to this behaviour.
I have two LS-120 drives, and they both behave in this fashion. It seems odd they would both be broken in the same way, so I'm wondering whether anyone has seen this kind of behaviour before?
Here is what I have tried so far:
- Confirmed the drive was set to Master - yes
- Removed the slave device so the LS-120 was the only device on the IDE channel - no change
- Tried different 1.44MB disks - same behaviour, the disks tested do boot in a 1.44MB drive so they aren't corrupt - no LS-120 disks to try yet
- Removed the IDE cable from the drive - same behaviour, only the drive no longer resets when the PC reboots
Given that the drive behaves like this when it is powered without being connected to any IDE bus, it seems like it must be something wrong with the drive.
Any suggestions on what to try now?