Can't get Windows XP SP3 to recognise my Canon SX120 IS digital ca

[Julia Hopkins]

Many thanks - I'll have a look and let you know if this helps

Julia

 

[Julia Hopkins]

Thanks

Nothing obvious at first sight, but I do need to check for hidden files when
I am next at home - maybe that will reveal something - I'll let you know

Julia

 

[Julia Hopkins]

Thanks

It's a good suggestion, but unfortunately yes I have, without result I'm
afraid. I tried various combinations of the order of connection / switching
camera on etc, all to no avail. But as soon as I use a diffrent PC, also
running XP SP3, and using the same cable, it works immediately whatever order
I do things in. Strange, and more than a little frustrating! But I'll keep
on trying - any other helpful suggestions very welcome

Julia

 

[Julia Hopkins]

Thanks

I'll try the AC adapter idea - sounds a bit unlikely, but you never know,
got to be worth a try, and I have seen a suggestion in a different forum
about an apparently similar issue to mine that suggested removing batteries,
so there may be something in the camera power options. I'll let you know

Julia

 

[Julia Hopkins]

Thanks

But sorry, you're going to have to help me out a little here (I'm very much
an amateur techie, if that) - how will I know if WIA is running - should it
be in Task Manager when I connect the camera?

Julia

 

[Julia Hopkins]

Thanks

It isn't there at all, whichever USB port I try

But - and this is what makes is so strange - other devices are recognised
via any of the USB ports on this PC

And - stranger still - the camera is recognised by other PC's also running
Windows XP SP3 using the same USB cable

So it's like it's not the camera or cable per se, and it's not the PC per
se, it is absolutely the interaction between them that's not working.

I'll keep working through all these hepful suggestions that I'm getting -
there's a solution out there somewhere!

Julia

 

[John John - MVP]

Look in the Services Management Console. To open the console enter
services.msc in the Start Menu Run box. In the console scroll down the
list to "Windows Image Acquisition (WIA)" and make sure that the service
is running. If it isn't already set to Automatic start you could set
the startup type for the service to Automatic and reboot the machine
(Double click on the service to open its properties page and to change
the startup type).

John

 

[Unknown]

Do you have a driver for the camera? If so, delete it (if previously
installed). Then, load the driver without the camera
attached. Power off and reboot with the camera attached.

 

[Julia Hopkins]

Great - thanks - I'll give this a go when I get back home, and let you know
how I get on

Julia

 

[Guest]

Great - thanks  - I'll give this a go when I get back home, and let youknow
how I get on

Julia

Probably an off the wall suggestion but what about copying the
settings from the camera compatible computer to a thumb drive the down
load it to the recalcitrant computer?
The only reason for using a power adapter would be if you had a large
amount of data to work on, imo.
A card reader would be cheaper than an AC adapter anyway if one will
work since apparently the offending computer seems to be choosy about
what devices it will recognize.
All cameras I have used display a short menu beginning with "PC" high
light at the top even if the camera is turned off when they are
connected. Press "OK" and the device is recognized as another Drive
letter.

 

[Julia Hopkins]

Thanks

OK - I'll give this a go when I'm next at home and let you know how I get on

Julia

 

[Julia Hopkins]

Thanks

Off the wall or not, I will try it if the other helpful suggestions on this
thread don't resolve the problem. I'll let you know how I get on

Julia

 

[Julia Hopkins]

Thank you to everybody who has offered suggestions to date. The problem is
not yet resolved, but I think that we are closing in on it! I can now say
that the camera is found in Device Manager, but with this message:

"Windows cannot start this hardware device because its configuration
information (in the registry) is incomplete or damaged (code 19)"

Unistalling / Reinstalling the software that came with the camera has no
effect, nor does using the Windows Troubleshoot option in Device Manager.

So, with this new information, any more ideas anybody?

Thanks - Julia

 

[Julia Hopkins]

Sorry, what I said below about the camera not being found in Device Manager
was wrong. It is found, with this message:

"Windows cannot start this hardware device because its configuration
information (in the registry) is incomplete or damaged (code 19)"

Uninstallng / Reinstalling the software that came wth it has no effect, nor
does running the Troubleshoot option in Device Manager. Any other deas?

Julia

 

[Julia Hopkins]

Nothing odd in Device Manager, but I did find the camera, along with the
message:

"Windows cannot start this hardware device because its configuration
information (in the registry) is incomplete or damaged (code 19)"

Uninstalling / Reinstalling the software that came with it had no effect,
nor did the Troubleshoot option in Device Manager. Any other ideas?

Thanks - Julia

 

[Julia Hopkins]

I have now ascertained that the camera is communicating with the PC, but
there is a problem - in Device Manager it says:

"Windows cannot start this hardware device because its configuration
information (in the registry) is incomplete or damaged (code 19)"

Uninstalling / Reinstalling the camera software has no effect, nor does the
Device Manager Troubleshoot option. Any other ideas?

Thanks - Julia

 

[Julia Hopkins]

It was set to automatic and it was started. So thanks for he idea, and I did
learn something from it, but not the solution I'm afriad. See other posts in
this thread rom me today for the latest update - any futher suggestions
gratefully accepted!

Julia

 

[Julia Hopkins]

Thank you

Yes, I am an iTunes user, so there might be something in that. I'm away
again for a little while now, but as soon as I get back I'll work thrugh your
helpful suggestions

Thansk - Julia

 

[Julia Hopkins]

I have finally fixed ths issue!

I did it by following the advice at
http://pcsupport.about.com/od/findbyerrormessage/a/code-19-error.htm

The fix is at Step 3

Thanks everybody for your help

Julia