• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

DELL 2405FPW card reader causes boot failures

tesfaye

2[H]4U
Joined
Apr 17, 2003
Messages
3,421
For some reason when I boot my machine with the USB cable connected I am unable to boot consistently. There are no cards in the card reader when it starts. I'm wondering if there is a way to prevent windows from mounting the card reader with no media inserted. Does anyone have any suggestions?
 
That's odd, I've had no trouble with mine so far. I've even been using it with my cam. Maybe there are some drivers for it on the CD? I didn't even check.
 
Can you boot with any other USB-type storage devices hooked up (camera, some printers, etc)? It could be a mobo issue.
 
Could it be a boot startup order? If you put your HD as your first boot device does it go away?
 
Question about the card reader: is it only a reader, or is it also a writer? (ie is it able to transfer/write data between different memory cards?
 
boardmonger and dextrous,
I think you guys are right, I need to check the boot order. I may have overlooked that since I had to reset my bios a week ago while attempting to boot at 285mhz. My motherboard didn't like it.

sophie, I haven't tried writing with the SD card since I only use it to read my camera cards but I will give it a shot and let you know.
 
Note that many times USB is not in the boot order but instead under integrated peripherals > usb or something similar there is an option to allow booting to USB. If this is the case, the machine will try to boot to the USB even though it is not listed in the boot order anywhere. Good luck.
 
Also note that a USB card reader can trip a Fedora install (it has happened to me)
 
I have the same problem with another card reader but it only happens when I have a card in it. And only some times.
 
dnenciu said:
I have the same problem with another card reader but it only happens when I have a card in it. And only some times.

Disable boot to USB support in the BIOS. This happens when the PC tries to boot to your memory card. Sometimes PCs hang when they see a card with no mbr.
 
You should have an option in your bios, under USB Mass storage

There will be an option in there, I've seen it set as default most times in a wide range of motherboards.

Turn OFF "usb emulation"

Let me know if that helps
 
Sorry to leave everyone hanging but it's been really busy at work and home. Anyhow, I had disabled all of the USB storage/boot/emulation settings in the bios and the computer booted but then it hung at the desktop. Windowblinds and Trend Micro loaded up but none of the other 10 apps that should have appeared in the system tray or the task list did. I went into the registry and removed the references to the drive letters for the Card reader device under \\HKLM\SYSTEM\MountedDevices and I will reboot and see what happens. I'm thinking something may be getting screwed up in there when windows boots and goes through the mounting process. I also think this may have something to do with booting with the SD card in the display and then booting again without it in place and at some point the drive mount point became corrupt or something. This is frustrating because I like the reader. It has saved me from the constant crashes that my Easyshare dock causes when I go to read the memory card. Thats unrelated however since it has crashed every computer that I have owned. Either the device is defective or most people don't bother to report problems with the dock.

Thanks for all of the suggestions. I will reboot and report back with my results.
 
Removing the references from the registry did the trick. Forcing Windows to remount with fresh values instead of using the existing settings helped.
 
Back
Top