modem7
10k Member
Today I killed three 40 track double sided diskette drives with a single piece of software.
I am very curious and hope that someone here can explain how that is technically possible.
Here's how events unfolded.
Ran DR-DOS' (Caldera) DISKCOPY.COM on a PC clone computer to create disk image files from master disks, and then create disk copies from the image files.
Creating the image files went according to plan.
But on writing to about the fifth disk copy, the 40 track drive died. Symptom: Reads disks okay but won't write.
Thought I was unlucky and substituted the drive (with a different model drive).
Replacement drive tested okay with read/write operations.
A few more disk copies are created then the second drive fails. Symptom: Makes the right noises, etc. but won't read.
Turned off/on computer. No change.
Not sure what's going on here. Bad floppy controller? Will sort it out later.
Move to my 5170 (which has a 40 track as B, taking with me a copy of DISKCOPY.COM and the image files.
This time drive failure is immediate when I used DISKCOPY.COM to create a disk. Symptom: Reads disks okay but won't write (same as first drive).
Failure of the three drives confirmed using a third computer.
I can't be that unlucky, surely, but I'm certainly not going to experiment with a fourth drive.
I factor in the failures maybe that I was running DR-DOS' (Caldera) DISKCOPY.COM under MS-DOS rather than DR-DOS.
Maybe my copy of DISKCOPY.COM was bad.
Failures only occured during write operations.
What puzzles me is how the floppy controllers could be programmed/ordered in such a way as to damage the diskette drives.
Anyone got any informed ideas? Or was I just incredibly unlucky?
I am very curious and hope that someone here can explain how that is technically possible.
Here's how events unfolded.
Ran DR-DOS' (Caldera) DISKCOPY.COM on a PC clone computer to create disk image files from master disks, and then create disk copies from the image files.
Creating the image files went according to plan.
But on writing to about the fifth disk copy, the 40 track drive died. Symptom: Reads disks okay but won't write.
Thought I was unlucky and substituted the drive (with a different model drive).
Replacement drive tested okay with read/write operations.
A few more disk copies are created then the second drive fails. Symptom: Makes the right noises, etc. but won't read.
Turned off/on computer. No change.
Not sure what's going on here. Bad floppy controller? Will sort it out later.
Move to my 5170 (which has a 40 track as B, taking with me a copy of DISKCOPY.COM and the image files.
This time drive failure is immediate when I used DISKCOPY.COM to create a disk. Symptom: Reads disks okay but won't write (same as first drive).
Failure of the three drives confirmed using a third computer.
I can't be that unlucky, surely, but I'm certainly not going to experiment with a fourth drive.
I factor in the failures maybe that I was running DR-DOS' (Caldera) DISKCOPY.COM under MS-DOS rather than DR-DOS.
Maybe my copy of DISKCOPY.COM was bad.
Failures only occured during write operations.
What puzzles me is how the floppy controllers could be programmed/ordered in such a way as to damage the diskette drives.
Anyone got any informed ideas? Or was I just incredibly unlucky?