Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
What does this mean???????
I've just installed an old FDD from a P133 into a PIII 450 setup. The drive seems hooked up fine so I really don't know what the f*(% is going on. cheers
triple check the cable and power (pin 1 to pin 1) To see what some error messages are related to, go to Microsoft's support page and look for Article ID: Q137335, or "95 Windows kbenv kbtshoot" (without the parenthesis)
0 
Howdy, Normaly when this error message pops up the floppy drive is dead. In my experince everytime the famous 40 error has shown up it was the cause of a dead floppy drive but do check your cable, you will not if its backwards if the light stays on, on the front of the floppy drive. Anyways, I still think its dead.
Laters,
Kevin The Tech Dude.
0
I dont think that the floppy is dead As i am
having the same problem , So i replaced the floppy drive with another and it still did not work
If you find out whats wrong e-mail me
0
I have the same problem too.
I tried with 3 different cables and floopy and still get the same problem.
Any info will be appreciate.
0
I start my computer up and it gives me the floppy disk(s) error (40)
I do not know what the problem is, but I have checked the cords, I have tried with many cables also. I have made sure the j1 pinstripe is in line. Could you tell me how to fix this in every scenario that you know. thank you
0
I am having the same problem and I tried a new floppy but didn't work either. I verified everything. I hope is not damage caused by a virus when it gets on the configuration. I tried scanning with Norton Anti-virus 5.0 and it says its ok, but I still have no floppy.
0
I believe that the error 40 can relate to more then one problem.
Here is how i solved it....
In the bios I deactivated the onboard FDD controller. I then put a controller card in my system and connected the floppy.
This might not apply to all but in my situation the onboard FDD controller was the problem. I'm running a pentium 75 for those who want to know.
0
disabling the boot up in cmos gets rid of the error for me, but i still cant boot off of the drive
0
Ah hah, fixed it! But my problem may have been different. I removed a 5.25" floppy from the computer a short time ago, and didn't realize that it was what was causing the error (its nonexistence, that is). So I finally went in to the BIOS and changed the drives around and made sure the 3.5" was connected to the correct cable, and it worked fine.
0
Yea G-Day Same prob...It was werking fine then I put it in a mates machine and whaked it in 30 min later and thats when it decided to freak.So yea wats the deal neal...
gromness
0  |
 nappi.vxd & serwave.v...
|
Drag and Drop Problems
|
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
