Discussion Locked

Reinstalling a floppy drive

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
After installing Win98SE over Win98 i am not sure if the floppydrive was working ok before or not but it does not work now , how does one reinstall the floppty under the new O/s ? Any help would be appreciated.

7 replies

by dmiles

Click Start,Settings,Contro Panel,double-click the System icon,select the Device Manager tab,see if the Floppy Disk is located in the list or a yellow exclamation is next to it.
If so then click to highlight and then click the properties button then update the floppy controller driver,by clicking on the button.
The other option is to open the CMOS control panel to the BIOS the configuration page will show,check to see if the flopyy is listed in the line with the order of boot devices.
Were you installing the OS from the CD-ROM only,then I cannot see how you lost the floppy unless it was not working.

by diskaus

Again a good idea but as it turned out it was bad disks not a bad drive , i will award the points to you as you were the first to answer , thankyou for your ideas

by drummergod12

I know it sounds stupid, but check to make sure that the ribbon cable is connected to the floppy and make sure that it isn't reversed.

by bdavis4139

Hi, Always start from a known "good". Take a floppy and cable assembly, which you just verified to be working from another machine, and substitute it into the non-working machine. Of course, if it works in the "non-working" machine, you know the problem is in the ribbon cable or the drive has problems. Then, double verify the problem. Place the bad floppy and cable assembly into the "known good" machine to see if the malfunction transferrs there. Sometimes, both machines work then! If the problem moves over, the substituted assembly is the culprit. Substitution troubleshooting always saves time. I hope this helps you make the fix. Don.

by diskaus

God suggestion but there was no need , it turned out to be bad floopy disks not the drive , thanks anyway

This discussion is closed to new replies.