-
visioneer 7100
I have a compaq evo d 300v, and I am having trouble getting my visioneer 7100 usb scanner to work right I keep getting a message "The current picture cannot be copied" and than it ask's me if I want to try again. I try again and I have the same problem. I have tr5ied scanning other itmes and have the same problem. I ahve tried removing and reinstalling the software and have had no luck. I would appreciate the help with this problem.
-
What operating system are you using, and what scanner software? Usually that error message shows up when the OS thinks you are transferring a pic from a camera or a digital card..not when you are scanning
-
I am uisng windows xp, and I am using the software that comes with windows xp, the scanner and camera wizard.
-
Now I am getting an error message "windows cannot detect a camera or scanner"
-
I checked the device manager and it does show up in device manager, when I remove the cable it disappears from the device manager, when I reisntall the cable it reappears.
-
It show up in device manager as the appropriate scanner model?
-
Yes it does show up as the appropriate mdoel
-
paul62, Visioneer suggests running their removal utilities after uninstalling the driver and before reinstalling. You can find them here along with instructions.
-
-
I tried removing the driver and installing the new one, and now windows adleast detects the scanner, but I am still having the original problem. I am getting the message the picture cannot be copied.
-
Did you use all 3 removal/cleanup tools per post #8 ?
There are some other optional tools here; http://support.visioneer.com/product...es_2000_XP.asp
Basically, you need to start CLEAN!
-
I have used all three f the tools and I still am having a problem.
-
-
-
I tried the scanner on another computer, but I was having trouble getting the correct driver installed so I got nowhere with that. I got the correct disk for my computer and reinstalled the opeating system, and got it completely updated, and I still have the same problem, is there any likely hood that the problem is in the bios?