Well I Had two other USB devices plugged into the computer before... a scanner and a webcam.  I removed them both
prior to installation of the camera, because the manual says it might not work correctly if I am using other USB
devices.

Well, Canon just suggested disbling any unknown devices in my device list under safe mode, then trying a reinstall.
But they also recommend fresh batteries first.  I'll check both, and I'll make sure everything is clean.


Thanks,
Matt


Tesselator wrote:

> "Cathy/Matthew MacDonald" <cathy.macdonald2@sympatico.ca> wrote in message news:3F672B6E.6F359336@sympatico.ca...
> > Dear friends,
> >
> > I am attempting to get the Powershot a40 camera ready for a friend. He
> > has had problems connecting it to his computer. When the camera is
> > connected to the USB port, the computer fails to
> > recognise it at all (it does not appear in device list) and when trying
> > to retrieve pictures via the Zoombrowser EX program, it gives me the
> > following error message:
> >
> > "No camera detected. There may be a problem with the camera
> > communications or the camera is not ready. Press of to select
> > communication settings to reconnect or cancel to stop reconnection."
> >
> > The camera has several pictures inside. The USB cable is connected
> > properly. It is connected to a computer with windows 98 SE installed.
> > The camera is connected directly to the computer's USB port, not through
> > a hub.
> >
> > The only alternative I haven't considered is the "Insufficient battery
> > charge" possibility. However, he has no power cable to connect it (he
> > purchased the camedra refurbished), and this is not a current
> > option.
> >
> > I have tried downloading various different TWAIN drivers in hopes that a
> > faulty or outdated driver could cause the problem. This has not worked
> > for me either.
> >
> > I'd really like to get his camera working ASAP, does anyone have any
> > further suggestions?
>
> Yes, try connecting /any/ other USB device to the computer and see if
> it works.
>
> If it does...  then it's /probably/ a software (driver?) issue, a bad
> cable, or a dirty connector.
>
> Just some guesses...