Two things to check...

1) look in Device manager for any red or yellow "!" marks.
    Check to see if you have and "UNKNOWN DEVICE" if yes delete it

2) If your plugging your device into a HUB, try plugging directly to computer.

Post back!

Ziwpiz,

I have four SanDisk's at my office; only one is plugged into a hub (again all other devices on that hub working properly, including the Kodak dock for digital cam / printer too!), and the other three machines straight into back of computer.  Have never seen a yellow exclamation mark; the computer definately is recognizing the card reader; it knows it's there.  Exact same problem on all the machines, doesn't matter if plugged into a hub, or right into computer.  It knows the SanDisk is there, if you double-click on the drive WITHOUT a disk in there, it will say "insert disk"; but when you stick a disk (card) in there, it either freezes the computer up, or makes it move extremely slow.  Unplug the reader, the computer works fine again?

I have an IT guy that tried to help me figure it out; told me to go buy another card reader; I don't recall the brand name of the second reader I purchased, but identical problem(s). 

THANKS FOR THE RESPONSE!  It's exciting to have someone else scratching their head on this one!  I'm ready to take a bat to the SanDisk, but I know it isn't the reader, as it works on other Non-Dell machines.  There some sort of conflict somewhere? 

I'm going to try to phone SanDisk direct tomorrow and see if they have heard of any such issues.  I will keep you all updated. 

NOTE: With the exception of this problem, I have TREMENDOUSLY enjoyed my Dell's.  These have been the best computers I have ever owned.  I have upgraded them all to USB 2.0, added gigabit network cards, and most machines at the office have 1 gig of ram.  I just got these card readers, and thus far these are the only things that have given me any challenge to figure out...  I'll take this one challenge with open arms!!! HA HA!

you must install the service packs for XP , there was something going wrong with the USB-handling in the org. Windows XP

another good idea is to install the latest INTEL-chipset driver for your machine.

Both of them is best....

Dirk

PS: my SanDisk is running fine on Dell 8300 + XPpro SP1

Message Edited by Dirk V on 12-29-2003 01:43 PM

Dirk,

I am at my office today on the "troublesome" computer(s).  I right clicked on my computer Icon, and under the "general" tab I see:

Microsoft Windows XP Professional, Version 2002, Service Pack 1

The machine is a Dell Dimension DIM4400, Pentium(R) 4 CPU 1.60GHz, 1.00 GB of RAM.

As far as the Intel Chipset-Chipset driver; I'll go look on Intel's website.  Do you have a direct link for their drivers?

THANKS for the response!

hmm, Sp1 is installed ?

OK, then go to INTEL .

I've looked above in the systeme spec, your Dim4400 is using the Intel-845 chipset. You can find the driver:

http://downloadfinder.intel.com/scripts-df/Product_Filter.asp?ProductID=757

there is a read me, follow it.

After Installation, and reboot, try your SanDisk drive again.

Does it work?

You wrote you made an upgrade to USB 2.0 . Maybe this is your problem? You are using a combo card, i never trust them. 

Try to find out if there is a driver update for this card. The SanDisk doesn't need USB2.0, it will work with USB1.1 a little bit slower, but it works. Try this way too. 

If it will not work, disconnect all (!) USB- devices. Start the hardware manager (with option view by connection) and delete everything that smells like USB.

After the next reboot XP will find new Hardware: Your USB-ports with the new INTEL drivers.

Now it MUST run....

good luck, Dirk

Message Edited by Dirk V on 12-29-2003 07:01 PM

Allright Guys - It's fixed.

I phoned SanDisk direct; they told me to right-click my computer, and then scroll down to manage.  Under "Storage", click "Disk Management".   I then righ-clicked the "removable media" (which was Drive "E", the SanDisk for me) and switched the drive letter to "J" (I think any other letter will do provided it's not being used??).  I did this on all machines that weren't working, the reader works great and reads images fine now!!!  They offered no explination for the conflict, and said it's rare but is just something that has "come up" on occassion?

WEIRD, HUH?

THANKS TO ALL THOSE THAT REPLIED HERE!  I'M CURED!