Re: lifecam vx6000



Hi Paul
Thanks for the links. See the UVCView report below. The PID and VID are not
the same as in the INF file, they are as you reported. Are we on to something
here?


Nigel



===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x00 -> This is an Interface Class
Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0C45 = Sonix Technology Co., Ltd.
idProduct: 0x62BF
bcdDevice: 0x0100
iManufacturer: 0x00
iProduct: 0x01
English (United States) "USB20 Camera "
iSerialNumber: 0x00
bNumConfigurations: 0x01
===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x00 -> This is an Interface Class
Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0C45 = Sonix Technology Co., Ltd.
idProduct: 0x62BF
bcdDevice: 0x0100
iManufacturer: 0x00
iProduct: 0x01
English (United States) "USB20 Camera "
iSerialNumber: 0x00
bNumConfigurations: 0x01


"Paul" wrote:

Nige wrote:
Sorry Paul, I should have said the webcam worked for nearly 4 months before
this problem appeared. My pc is XP SP2. Apparently the problem arose after a
recent windows update. what i cant understand is why windows doesnt see it as
a vx6000 as if it sees a "usb20" camera, thats what its going to want drivers
for

One posting I found the first time I looked, suggests the VX6000 doesn't have
a serial number. (Some USB devices have a serial number, and that makes it
easier for the OS to track it, as the device is moved from port to port.)

The VID and PID were listed here. 045e:00f4. Which apparently maps to a
Sonix/Microdia chip inside the camera. That ID information, is one of
the ingredients for the OS to install a driver, from the Microsoft
software package you installed.

http://www.linux-projects.org/modules/newbb/viewtopic.php?topic_id=287&forum=6#forumpost1066

Since the chip is described, as 9C20X, it might be one like this.

http://www.sonix.com.tw/sonix/product.do?p=SN9C202

*******
SN9C202 Drivers
SN9C201_5.7.23.000_Latest_Win98/ME/2000/XP32&64/Vista32&64

http://www.sonix.com.tw/sonix/download.do?d=2051,2

==> USB20PCCam_5.7.23.000.exe 12,358,393 bytes

SN9C202 Drivers
SN9C202_5.7.22.000_WHQL_Win98/ME/2000/XP32&64/Vista32&64

http://www.sonix.com.tw/sonix/download.do?d=2050,2
(Presumably this is the previous version)
*******

Will those work ? I haven't a clue. Installing them, could
do more harm than good. It all depends on whether you expect
Microsoft to fix the issue. The thing is, the Sonix driver
may know about specific webcams (like what image sensor is used),
or it might not. The drivers might be removable via add/remove
or perhaps you could prepare a restore point just before installing
them.

To look at the config info coming from the camera, you can use UVCView.
This is an archived version, as Microsoft removed the page from their
web site. This should allow you to see the 045e:00f4 part, and if
the Sonix package has an INF file in it, you could compare the information
coming from the camera, to see if it matches an entry in the INF.

http://web.archive.org/web/20060509061220/http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe

I cannot really do anything with the USB20PCCam_5.7.23.000.exe
file here, as it looks like an Installshield package.

If I was experimenting with that here, I'd probably use a spare
disk with an OS install on it, as a test.

Contact info for Microsoft hardware, starts here.
http://www.microsoft.com/hardware/contact/default.mspx

I followed that link, and ended up here. The techniques suggested
appear generic in nature, and yet the text at the very bottom
of the page implies the info is provided for Microsoft hardware
customers.

http://support.microsoft.com/kb/933311/en-us

You could also have a look at their contact page here (but aren't
going to like the options).

http://support.microsoft.com/common/international.aspx?rdpath=1&gprid=11859

Paul


"Paul" wrote:

Nige wrote:
my pc wont see my vx6000 webcam. I see on forums others are having the same
problem. It sees a "usb20" webcam when I connect the unit. I have uninstalled
and reinstalled the latest software, as well as trying older software, but
Windows always sees the cam as a "usb20". Have tried the microsoft email
support, which doesnt work by the way. Anybody got any ideas on this issue?
When you go here, and go to downloads, is there a different package depending
on whether your copy of WinXP is SP1 or SP2 ?

http://www.microsoft.com/hardware/default.aspx

If you installed SP2, perhaps you need a different version of package for
the VX6000.

Paul


.



Relevant Pages

  • Re: help please with toshiba PDR-M60 camera connection
    ... The info in the First Time Install section is ... The USB connection was designed for use with Microsoft Windows ... Image Expert can be installed before or after the USB drivers for the ... right of the screen in the bar, it looks like a little camera. ...
    (microsoft.public.windowsxp.photos)
  • Re: Installation of hardware
    ... Note your camera is essentially a USB drive. ... XP comes with drivers for USB mass storage. ... An Windows repair install helps then. ... Try a different USB port. ...
    (microsoft.public.windowsxp.hardware)
  • RE: cant install the printer driver in SBS2003
    ... the newsgroups are staffed weekdays by Microsoft Support professionals to ... does not support Kernel mode print drivers. ... newsgroups so that they can be resolved in an efficient and timely manner. ... can't install the printer driver in SBS2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to install the printer
    ... Microsoft Enterprise Platform Support ... > Some drivers are getting installed but some drivers are ... > actually we install 2 type of drivers. ...
    (microsoft.public.windows.server.clustering)
  • Re: lifecam vx6000
    ... the ingredients for the OS to install a driver, ... software package you installed. ... SN9C202 Drivers ... Microsoft to fix the issue. ...
    (microsoft.public.windowsxp.hardware)