Win XP Drive

[Ponch]

Start-up bios screen say's .........Floppy Diskette Failure (along with all else is fine).

The Setup Reads ....Floppy= 3.5 1.44 MB

Set that one to "none" instead and you get rid of "Floppy Disk Failure".

[callbobby69]

All Done . Replaced it .....works great (same model and version). Thanks all . Close this thread .

[jaclaz]

NO MATTER whether a driver is installed or not, one of the linked to program should detect the USB device and it's Vid and Pid.

I don't care whether there are conflicts, I want to know how the floppy drive "identifies" itself.

If you cannot get the above, it is possible that the device or the USB bus are malfunctioning.

Once you get them, you can "tweak" an .inf file to "assign" the found that particular Vid & Pid to a given driver.

So, after all was a malfunctioning device?

For the record, checking the device with ChipGenius or similar utility should:

1) check how the device is seen by windows, or more properly how windows receives the data the device sends, it's ID, etc. which indirectly also:

2) checks that the device is not underpowered or failed (an underpowered device or a defective cable/connection or device itself will possibly send "garbage" instead of a proper Vid, Pid and Manufacturer/Model ID string)

jaclaz

Edited August 27, 2008 by jaclaz

[JedMeister]

NO MATTER whether a driver is installed or not, one of the linked to program should detect the USB device and it's Vid and Pid.

I don't care whether there are conflicts, I want to know how the floppy drive "identifies" itself.

If you cannot get the above, it is possible that the device or the USB bus are malfunctioning.

Once you get them, you can "tweak" an .inf file to "assign" the found that particular Vid & Pid to a given driver.

So, after all was a malfunctioning device?

For the record, checking the device with ChipGenius or similar utility should:

1) check how the device is seen by windows, or more properly how windows receives the data the device sends, it's ID, etc. which indirectly also:

2) checks that the device is not underpowered or failed (an underpowered device or a defective cable/connection or device itself will possibly send "garbage" instead of a proper Vid, Pid and Manufacturer/Model ID string)

jaclaz

In other words callbobby69, next time you ask for advice please follow it! It seems we were all suspicious of a hardware fault but jaclaz was good enough (and knowledgeable enough) to provide an opportunity to diagnose that from your PC. Instead you chose to ignore it. If you did not understand then perhaps you could've asked for more detailed instructions or more information instead of just ignoring his suggestions.

Oh well jaclaz, thanks anyway as I for one learned something in this thread!

[jaclaz]

Oh well jaclaz, thanks anyway as I for one learned something in this thread!

You're welcome.

jaclaz

[callbobby69]

It appears that Jedmeister is just one of those guys who has to have the last word in order to feel in control even when he is informed that someone has followed every single suggestion , he feels it necessary to be a b***h and and make up his own little story as to how things went or were applied when he has no idea as to what the subject actually went did .