First make sure that the format option on this system is set the same as the other systems. Second go to device manager and remove the floppy drive controller and reboot the system. Allow windows to reinstall this device and attempt to use again.
I'd replace the drive 1st. Generally, if you have a controller failure, the drive doesn't function. If you have read/write errors, it is usually a hardware failure of the drive.
Thanks to both MadThinker and dageerus for your replies.
In response to MadThinker, I'm not sure what you mean by "the format option on this system." My procedure has worked in the past and still occasionally works successfully, so I assume that there is no compatibility problem. On this Pentium 3/Windows ME system, the only floppy format options that appear when I right click the a: drive are "Full Format" and "No Label" both of which I choose.
I did remove the floppy driver and allow windows to reinstall this driver. I have never done that before, and I was surprised that the behavior of the system did in fact change. The system rejected four of my test floppies with the message "Windows could not format this disk. Either the selected capacity is not valid, or the disk is damaged." I have never seen that message before.
However, four other diskettes were in fact formatted successfully, and written with a one megabyte text file. On all four diskettes, this file could be successfully read by the system that formatted the diskette. However, when I took these four diskettes to another system, only one could be read successfully. This is actually an improvement over the recent past, but obviously still not reliable.
So, while there has been a little improvement, the problem still exists. Does anyone have any other ideas? and why would the problem improve at all merely from reloading the floppy disk driver?
To dageezeerus, I had already replaced the floppy drive itself, as I said in my first note, and the problem did not seem to change or improve. So I removed the new floppy disk drive and put the old one back in, and the problem again did not change.
So I would appreciate any other ideas that anyone has. And is there a floppy drive diagnostic anywhere that might identify the problem?
MadThinker
516 Posts
0
June 2nd, 2004 14:00
DELL-Donald K
2 Intern
•
4K Posts
0
June 4th, 2004 01:00
rfarmer
21 Posts
0
June 4th, 2004 16:00
In response to MadThinker, I'm not sure what you mean by "the format option on this system." My procedure has worked in the past and still occasionally works successfully, so I assume that there is no compatibility problem. On this Pentium 3/Windows ME system, the only floppy format options that appear when I right click the a: drive are "Full Format" and "No Label" both of which I choose.
I did remove the floppy driver and allow windows to reinstall this driver. I have never done that before, and I was surprised that the behavior of the system did in fact change. The system rejected four of my test floppies with the message "Windows could not format this disk. Either the selected capacity is not valid, or the disk is damaged." I have never seen that message before.
However, four other diskettes were in fact formatted successfully, and written with a one megabyte text file. On all four diskettes, this file could be successfully read by the system that formatted the diskette. However, when I took these four diskettes to another system, only one could be read successfully. This is actually an improvement over the recent past, but obviously still not reliable.
So, while there has been a little improvement, the problem still exists. Does anyone have any other ideas? and why would the problem improve at all merely from reloading the floppy disk driver?
To dageezeerus, I had already replaced the floppy drive itself, as I said in my first note, and the problem did not seem to change or improve. So I removed the new floppy disk drive and put the old one back in, and the problem again did not change.
So I would appreciate any other ideas that anyone has. And is there a floppy drive diagnostic anywhere that might identify the problem?
Thanks again for any response.
DELL-Donald K
2 Intern
•
4K Posts
0
June 4th, 2004 17:00