Click to See Complete Forum and Search --> : Scanner won't respond


hudsonsmith
July 15th, 2003, 12:33 PM
I have a Canon D660U USB scanner. The lamp does not come on at boot and it will not respond to any buttons. The device is detected when I plug it in and it does appear in device manager (working properly), however, when I pull up the scanner properties in control panel, the status is indicated as "unavailable". OS is W2K SP4. I have tried:
1. cycling power (both scanner and computer)
2. switching usb ports
3. removing device, uninstalling & reinstalling drivers (have most current available)
I have had this scanner for a couple of year and have never had a problem until now. I can't recall if I have used it since installing SP4.

NooNoo
July 15th, 2003, 01:02 PM
It's dead jim :( Or at least the lamp is.l suggest you contact canon (https://www.usa.canon.com/html/conCprSupport.jsp?modelid=6629&pname=CanoScan%20D660U&type=email&item=6639&qc=true) to confirm and price out a replacement lamp.

hudsonsmith
July 15th, 2003, 08:17 PM
Kudos to Canon tech support. Turns out the Still Image Service was not started. I now seem to recall that I changed it from automatic to manual - one would think that it should start on demand, but there you go.

confus-ed
July 16th, 2003, 06:58 AM
Originally posted by hudsonsmith
Kudos to Canon tech support. Turns out the Still Image Service was not started. I now seem to recall that I changed it from automatic to manual - one would think that it should start on demand, but there you go.

Plug & pray ought to turn it on each time it 'finds' it ... so you got me too ... services with dependencies often fail to start set at mannual as other dependant services may not be started concurrently ... but you have to think to look in the right logs to see & that's if you knew they reported there & turned it on originally ! - maybe canon ought to write a proggie that starts all the required services for you - rather than rack it up as a support issue ... but thats expecting a lot ! :D ... like you say at least they knew ! ...

BTW would re-installing the device & its drivers not have forced Still Image Services to start ? It isn't there by default before any scanner/cameras are there ... the install proggie will have called it so it ought to have taken it away too !The Still Image Service is not installed by default, but is automatically installed, via plug-n-play, when a user attaches a
still image device (i.e. digital camera, scanner, etc.) to a windows 2000 host. ... but again I guess that's expecting a lot ... :rolleyes:

hudsonsmith
July 18th, 2003, 05:37 PM
Originally posted by confus-ed
BTW would re-installing the device & its drivers not have forced Still Image Services to start ? It isn't there by default before any scanner/cameras are there ... the install proggie will have called it so it ought to have taken it away too ! ... but again I guess that's expecting a lot ... :rolleyes:

Apparently not, as I had tried re-installing the device and drivers prior to finding the cause. Perhaps it only installs the service but doesn't change the start method.

confus-ed
July 19th, 2003, 03:18 AM
Originally posted by hudsonsmith
Apparently not, as I had tried re-installing the device and drivers prior to finding the cause. Perhaps it only installs the service but doesn't change the start method.

Well that's pants ... I have lots of systems where you can leave this service at mannual, when the preloader routine fires (the scanner interface) it fires the appropriate service either Still Image Service for 2k or WIA (windows image aquistion) for xp .... that's what the flipping 'mannual' option is for !! So that any dependcies can be fired by another process or service programatically & when you've stopped using them they are stopped :rolleyes: ....

Here & with this scanner you now know it needs to be 'automatic' despite how it ought to work... :( :eek2: