floppy disk(s) fail (40)  | | 
February 12th, 2004, 02:39 AM
|
#1 (permalink)
| | Junior Member
Join Date: Feb 2004
Posts: 4
|
New mb shuttle an35n ultra. existing hd with win xp. when boot starts i get logo, it finds hd but displays floppy disk(s) fail (40). award bios web site says something like the controller cannot be found. is that the mdb has a bad floppy controller. both cable and floppy check out good on another system. any hints on problem? also if i F1 to continue the system just recycles back to post messages. | 
|  | |
February 12th, 2004, 03:13 AM
|
#2 (permalink)
| | Retired mostly.
Join Date: Oct 2001 Location: Finland
Posts: 5,144
|
Probably got the fd cable upside down.
Or, the fd controller really is broken. | |
| | |
February 12th, 2004, 03:14 AM
|
#3 (permalink)
| | Ultimate Member
Join Date: Oct 2001
Posts: 10,821
|
any possible way you had the cable on wrong? is it a "keyed" cable..with the little notch sticking out etc? if either end is reversed it will mess up.
Also is there an option to turn the floppy off in the bios? maybe if its turned off it'll give that error?
__________________
"Even a fool is thought to be wise if he is silent"
| |
| | |
February 12th, 2004, 03:43 AM
|
#4 (permalink)
| | Junior Member
Join Date: Feb 2004
Posts: 4
|
checked cables & floppy on another system both are good. pin 5 is missing on floppy controller connector. that is standard format for ffd controller connector. bios is set to auto for detection of controllers. os load does not seem to occur. nforce2 chipset should enable boot from a floppy if hd is unformatted. if i unplug hd still get same error. seems to be either bios bug or controller on mb is faulty. any way to test controller before i take it all apart and return mb to store. | |
| | |
February 12th, 2004, 03:50 AM
|
#5 (permalink)
| | Ultimate Member
Join Date: Oct 2001
Posts: 10,821
|
well..by testing the cable and floppy you have already done pretty much all the testing u can do....as long as u are sure u had it hooked up right.
I might would check the manual and website faq just in case they have some sort of weird bios deal with the floppy | |
| | |
February 12th, 2004, 03:55 AM
|
#6 (permalink)
| | Mean Moderator
Join Date: Oct 2001 Location: N of Music City, USA
Posts: 7,791
|
You could also try disabling "Floppy Seek" on boot up to bypass the problem 'til you figure it out.
__________________
This signature intentionally left blank. | |
| | |
February 12th, 2004, 03:58 AM
|
#7 (permalink)
| | OH NO!
Join Date: Oct 2001 Location: Monett Missouri
Posts: 4,300
|
I think the only time I have seen that error the FDD Controllor on the MOBO was bad 
Like Evil said,turn off the Floppy Seek,maybe it'll work.
I would RMA it if it's a new board.
__________________
The impossible takes more time,and costs more money.
| |
| | |
February 13th, 2004, 09:45 PM
|
#8 (permalink)
| | Junior Member
Join Date: Feb 2004
Posts: 4
|
somehow issue was with the bios. i loaded os xp via cd and then used a downloaded bios flash to reload broken bios. now floppy works.
root cause was ??? in the bios. works fine now, even after many on off cycles and stress testing of the new computer build. never had to fix a broken bios before. | |
| | |
February 9th, 2006, 02:06 AM
|
#9 (permalink)
| | Junior Member
Join Date: Feb 2004
Posts: 4
|
seems i have same problem with a new asus mb. floopy disk fail (40) cables, drive and power are good. anyone have same issue that a bios reflash not fix | |
| | | Thread Tools | Search this Thread | | | | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | | Most Active Discussions  | | | | |   Recent Discussions  | | | | |
 |
hardware
prices 
