Logitech Quickcam Sphere

  • Thread starter Thread starter Adora Belle Dearheart
  • Start date Start date
A

Adora Belle Dearheart

I was just wondering if anyone else has been using the Logitech QuickCam
Sphere and run into any problems with it, or if anyone can shed some
light on this issue.
There seem to be two models of Sphere, and the original version I had
works fine. I was recently given one which didn't work - still a Sphere,
looks just about identical, but requires different drivers. This new
camear works on one set of hardware I have under both XPPro and XPe with
no problems. On the other set of hardware, however, it only works under
XPPro. Under XPe, the camera has worked, but mostly simply shows up as
'usb composite device' and cannot be installed. Usually the unit will
get stuck while trying to copy a required driver file. If it doesn't
stick there, the unit will often be unable to shut down or boot with the
camera connected.
 
Adora said:
I was just wondering if anyone else has been using the Logitech QuickCam
Sphere and run into any problems with it, or if anyone can shed some
light on this issue.
There seem to be two models of Sphere, and the original version I had
works fine. I was recently given one which didn't work - still a Sphere,
looks just about identical, but requires different drivers. This new
camear works on one set of hardware I have under both XPPro and XPe with
no problems. On the other set of hardware, however, it only works under
XPPro. Under XPe, the camera has worked, but mostly simply shows up as
'usb composite device' and cannot be installed. Usually the unit will
get stuck while trying to copy a required driver file. If it doesn't
stick there, the unit will often be unable to shut down or boot with the
camera connected.
Click to expand...

...it seems likely that the problem is with USB2 devices generally rather
than just the camera, as my USB hard disk caddy doesn't work either.
Anyone know what hugely obvious thing I've forgotten?
 
Adora,

I think you know more about this stuff than I do, but since you asked,
I'm going to kick out a few ideas, in the hopes that one will jog
something for you, or for someone else

The really obvious: do you have all the latest drivers?

Some conflicting .inf file info between the two? Maybe the device is
found first in the .inf file for the previous model, but the entries in
that file don't work for the new one?

Maybe clean out related entries in
HKLM\System\CurrentControlSet\Enum\USB? Sometimes I have had luck by
comparing registry keys on the working and non working systems...

And the ugly: Try it on a fresh install.

SteveS
SteveSATeyeDASHimagingDOTcom
 
steves said:
Adora,

I think you know more about this stuff than I do, but since you asked,
I'm going to kick out a few ideas, in the hopes that one will jog
something for you, or for someone else

The really obvious: do you have all the latest drivers?

Some conflicting .inf file info between the two? Maybe the device is
found first in the .inf file for the previous model, but the entries in
that file don't work for the new one?

Maybe clean out related entries in
HKLM\System\CurrentControlSet\Enum\USB? Sometimes I have had luck by
comparing registry keys on the working and non working systems...

And the ugly: Try it on a fresh install.
Click to expand...
I've tried a number of things... I'm currently trying it with the USB
controller drivers we know are buggy. It's looking likely that it'll
work, with a little gentle persuasion. Which is a bit of a pain, really,
seeing as using those drivers, the keyboard stops working if you set the
windows sounds to 'no sounds'.
 
Back
Top