1.

Solve : How do I get rid of non-existent Removable Disk?

Answer»

Win 98 Windows Explorer shows a non-existent Removable Disk E: that is causing hangups, freezes and crashes in HP printer SOFTWARE. How can I GET rid of this non-existent disk?

Any suggestions would be appriciated.
Thanks, Ernie.Right click on > My Computer
                    > Properties
                    > Hardware
                    > Device Manager
                    > Brows & Select Your Removable Disk
                    > Driver
                    > UninstalledRemovable Disk did not appear in the Device Manager window.

It was much tougher than that. I had to delete a registry KEY in HKLM/Enum/ESDI it had a "UserDriveLetterAssignment" of "EE" for the non-existent Removable Drive E: (thats where Explorer was finding it?). Then I had to sort out the keys HKLM/Enum/FLOP and HKLM/Enum/SCSI to determine where my actual drives were and what they were labeled. Turns out Explorer was confusing my 3.5 Floppy Drive (should be A: ) with this non-existent E: It seems strange but the drive letters in Bios and Win 98 dont need to agree with each other. Anyway, at this point Explorer was now unaware of my 3.5 Floppy Drive, and assumed there is a 5.25 Floppy Drive. I had to tell Bios that my 3.5 existed and it was Drive A: and restarted.  

The only options in Bios were 720 or 1.44 floppy, I remember that previously was 2.88 so still investigating, But happy now it works with no phantom drives.

Ernie      OK
I was just making a surgestion
Well that work ernestbd nice of you to replyWell, more information for anyone who finds this useful.

Turns out that the HP All-In-One series printers have their flash card reader identified in the registry as a disk drive with
 HKEY_LOCAL_MACHINE\Enum\ESDI\HPZ\DOT4BRIDGE&DISK_HPZ12&0000DOT4&VID_03F0&PID_2911&MI_02&DOT4&STORE_HPZ&1DOT4USB&VID_03F0&PID_2911&MI_02&DOT4&1USB&VID_03F0&PID_2911&MI_02&2USB&VID_03F0&PID_2911&MY285D36KD0G

This allows the computer to assign the next available drive letter. It was  apparently determined when the HP software was originally loaded (in my case that was drive E). However, the drive only appears to windows explorer when the printer is turned ON.

The HP software hang ups were actually being caused by the inability to access the floppy drive. Since the registry and bios disagreed, windows couldn't access the drive when the HP software STARTED and tried to gather info about what was on that drive. Fixing the bios wasn't hard and now drive E really does exist...at least sometimes. Hope this helps somebody else.

Ernest.



Discussion

No Comment Found