I just received my scratch and dent ws1095 and have tried 5 different usb cables and cannot even get computer to even see the scanner in my device manager. It doesn't make a sound when plugged into computer. I have two pro668's that work perfectly fine with this computer. Any suggestions, or do you think they shipped a ws1095 with bad usb port. I thought they checked these before they went out. Thanks for any help.
Whister 1095 Scratch and Dent USB Port problem
- Thread starter Mattguy
- Start date
- Status
Have you installed the driver?
Yes driver installed. The computer normally makes a ding when you install a usb cord to it. It doesn't even make one sound. Didn't know if anyone else had bad usb ports.
Make sure it’s the driver for this model exactly. The drivers aren’t universal across the product lines. I have two of the 1095s and they worked fine once I got the driver installed.
Thanks, I'll give it a try once again. But computer is not even recognizing the cable being plugged in.
The computer doesn’t pick up the cable, only the electricity on it. If there is no electricity on the wire, then the computer doesn’t even know it’s there.
Rob_In_MO
Member
You're not the only one. My new WS1098 does the same thing occasionally. When using EZ Scan I have to unplug it and plug it back in between operations.
DJ11DLN
Member
I have both a 1095 and a 1098. Mostly they are recognized as soon as I connect them, but sometimes it takes awhile. I don't know the reason for it but I learned that if I go off and take care of something else or just go have a coffee after plugging them in and come back in 5-10 minutes, they have been recognized and show up in the device manager they way they're supposed to. It hasn't failed since I've been doing this. I don't connect them often because updating my programming on the SD card is so much faster with a reader. That too varies from being recognized as soon as it's plugged into the USB port to failing and requiring several pull-and-stick attempts, to just sitting there for a few minutes and finally being recognized. For that reason (my camera card does the same thing in this reader) I'm suspecting a Windows, rather than Whistler, problem, but I have no way to prove that so it's just speculation.
Just a suggestion you might try.
Just a suggestion you might try.
- Status
