Jibbajaba
Experienced Member
I hope this is the right forum in which to post this...
So today I moved my 486 into a new case. Hooked everything up, and it wouldn't boot. After a bunch of messing around, I then discovered that if I turn the floppy drive cable around on the back on the floppy drive, the system will boot, but then the floppy drive light stays on (because the cable is in backwards.) I kept tinkering with it and basically what I have discovered is that somehow through the process of moving everything over, the 1.44MB floppy got fried or otherwise seems to have gone bad. If I hook up only the 1.2MB drive as the "A" drive, the system boots normally and I can read 5.25" disks, but as soon as I plug the other floppy back in, the system won't boot.
Maybe this is not uncommon, but I have never seen it before. Can a bad floppy cause the system to not even boot? What's going on for this to happen? IS the BIOS waiting for some sort of signal from the drive before it commences booting?
A brand new floppy drive is probably going to run me like $5 at Fry's, so I don't care about that, but I have just never seen behavior like this before. I was really concerned that I had done something disasterous to my computer, so I am relieved to see that it is just a drive.
Chris
So today I moved my 486 into a new case. Hooked everything up, and it wouldn't boot. After a bunch of messing around, I then discovered that if I turn the floppy drive cable around on the back on the floppy drive, the system will boot, but then the floppy drive light stays on (because the cable is in backwards.) I kept tinkering with it and basically what I have discovered is that somehow through the process of moving everything over, the 1.44MB floppy got fried or otherwise seems to have gone bad. If I hook up only the 1.2MB drive as the "A" drive, the system boots normally and I can read 5.25" disks, but as soon as I plug the other floppy back in, the system won't boot.
Maybe this is not uncommon, but I have never seen it before. Can a bad floppy cause the system to not even boot? What's going on for this to happen? IS the BIOS waiting for some sort of signal from the drive before it commences booting?
A brand new floppy drive is probably going to run me like $5 at Fry's, so I don't care about that, but I have just never seen behavior like this before. I was really concerned that I had done something disasterous to my computer, so I am relieved to see that it is just a drive.
Chris