Floppy Drive Recognition problem

[DOsser]

"Windows successfully loaded the device driver for this hardware but cannot find
the hardware device. (Code 41)" <Yellow exclamation point>

Configuration:
Windows XP Pro MCE SP1 with all updates
Sony Viao - 1GB mem.

Problem: The floppy drive used to work, and now doesn't. It was a few months
between those two, and there were many software installations between.

The system WILL boot from the floppy, and the BIOS recognizes it.

Actions I've taken, and attempted solutions that haven't had any effect:

Floppy drive itself removed and tested OK on another system.

Cables to floppy replaced with known good cable.

Floppy and Controller, in various combinations and with both software and
hardware, deleted, removed, reinstalled. Windows recognizes that the floppy
drive has been "added", but comes back to its being unusable.

Registry setting checked to insure that A: isn't in the "nodrive" category.

Tried disabling the "boot from floppy" in the bios.

As of now, there's nothing occupying the A: drive letter.

Any new ideas will be welcome!

- Dosser

 

[Mistoffolees]

"Windows successfully loaded the device driver for this hardware but
cannot find the hardware device. (Code 41)" <Yellow exclamation point>

Configuration:
Windows XP Pro MCE SP1 with all updates
Sony Viao - 1GB mem.

Problem: The floppy drive used to work, and now doesn't. It was a few
months between those two, and there were many software installations
between.

The system WILL boot from the floppy, and the BIOS recognizes it.

Actions I've taken, and attempted solutions that haven't had any effect:

Floppy drive itself removed and tested OK on another system.

Cables to floppy replaced with known good cable.

Floppy and Controller, in various combinations and with both software
and hardware, deleted, removed, reinstalled. Windows recognizes that
the floppy drive has been "added", but comes back to its being unusable.

Registry setting checked to insure that A: isn't in the "nodrive" category.

Tried disabling the "boot from floppy" in the bios.

As of now, there's nothing occupying the A: drive letter.

Any new ideas will be welcome!

- Dosser

There is a mass of contradictions in the preceding. Let's
start at the beginning by (1) Attaching one end of the
floppy diskette ribbon cable to the floppy diskette drive
and the other to the motherboard, with ID stripe on the
power connector side. Next, attach the floppy diskette
ribbon cable to the motherboard connector, with the ID
stripe aligned to Pin 1. (3) Start the computer and enter
bios setup; the floppy disk drive should be Drive A and
1.44 MB. (4) Boot the computer into Windows XP. If the
floppy diskette drive is not identified as Drive A, then
what is it shown as in My Computer? Any other abnormal
reports, displays or readings?

 

[DOsser]

There is a mass of contradictions in the preceding. Let's
start at the beginning by (1) Attaching one end of the
floppy diskette ribbon cable to the floppy diskette drive
and the other to the motherboard, with ID stripe on the
power connector side. Next, attach the floppy diskette
ribbon cable to the motherboard connector, with the ID
stripe aligned to Pin 1. (3) Start the computer and enter
bios setup; the floppy disk drive should be Drive A and
1.44 MB. (4) Boot the computer into Windows XP. If the
floppy diskette drive is not identified as Drive A, then
what is it shown as in My Computer? Any other abnormal
reports, displays or readings?

Thank you for your response. And yes, the symptoms certainly appeared to be
contradictory and mutually exclusive!

All was attached correctly with the appropriate BIOS and windows settings (was
checked and double-checked numerous times). The floppy drive appeared in the
Device Manager with its yellow exclamation mark, and therefore didn't appear in
"My Computer", Windows Explorer, or DOS.

BUT THE PROBLEM IS NOW SOLVED, after weeks of googling, trying
suppport.microsoft.com, other usenet support groups, etc.

Registry entry

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\
{4D36E980-E325-11CE-BFC1-08002BE10318}

Contained an item with the value name of "UpperFilters".
Removing that entry fixed the problem!

This is documented in the MS Knowledge base - you just have to somehow find the
right search terms to get to it!
Here's the KB page:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812489

- DOSser