View Single Post
  #41  
Old August 29th 10, 07:41 PM posted to microsoft.public.windowsxp.hardware
AdeW
external usenet poster
 
Posts: 29
Default Amcap (USBPCCamPlus) doesn't seem to work, does it work for you?

On Jul 19, 9:25*pm, Paul wrote:
AdeW wrote:
I managed to finally get to use one of the PCs running WindowsXP and
ran USB device viewer. I've added the saved txt file here...


http://public.blu.livefilestore.com/...kdjdel695jJY4-....


http://cid-64f5892d2f88d17f.office.l...Public/usb%20d...


This hyperlink for the txt file should hopefully work.


The "USBPCCamPlus_v5.18.1.005_120standard(1.3M).ex e" installs the
snpstd3.inf file, and it has an entry for that camera type also.
The camera consists of a controller chip (SN9C120) and a sensor
chip (HV7131R).

USB\VID_0c45&PID_613c *; SN9C120 + HV7131R

So the same driver package should be working with that camera.

You should also see confirmation of the driver installation,
by looking in setupapi.log . Look for the 613c there. Also
inspect Device Manager again, to understand the current state
of the hardware you have plugged in.

The HV7131R is a 640x480 active pixel CMOS sensor.

A search for the terms Pccam168 and hv7131r, show they're part of the
same camera mechanism.

* * Paul


I eventually got round to finding a computer (called t3) which had
never had the dental camera plugged in. Normally i just let the
computer search for HP Basic starter camera driver but instead i
installed the troublesome software
USBPCCamPlus_v5.18.1.005_120standard(1.3M).exe from
http://www.google.com/url?sa=D&q=htt...-RGhk6lyAeIbAw

I've uploaded screen shot JPGs and files collectively here
https://cid-64f5892d2f88d17f.office....0&sa=610365145

they're also more individually here
https://cid-64f5892d2f88d17f.office....0&sa=408653088
https://nvneuq.blu.livefilestore.com...ownload&psid=1
https://nvneuq.blu.livefilestore.com...cap.TXT?psid=1

My 613c dental camera is in the snpstd3.inf and setupapi.log files
although PcCam168 isn't in either file.

When i plug this camera in it now says it found "USB PC Camera
[sn9c120]" when it usually just say "USB Camera". The jpg shows the
device manager still calls it "USB Camera" but with an exclamation
mark(!) and code 28 error: "the drivers for this device are not
installed". Device Instance Id on the jpg says ...

USB\VID_0c45&PID_613e\5&28CODE0&0&2

can't find 5&28CODE0&0&2 anywhere but 28CODE must be a reference to
code 28 error

I stopped at actually installing the driver for sn9c120 because of the
"not passed windows logo testing" message - although this same message
appeared for USBPCCamPlus_v5.18.1.005_120standard(1.3M).exe. I decided
to analyse the setupapi.log and snpstd3.inf files at this point.

I think the installation must have changed the identity of the camera.
It must think its sn9c120 now but its got it wrong i think. Whenever
I've plugged it in it has never said sn9c120 - well apart from once
when i pressed alt tab on another computer t6 with snapshot button
which i never installed the troublesome software but just HP Basic
starter camera driver.

There is this line in snpstd3.inf which mentions 613c
%USBPCamV2Desc% = SN.PCamV2.XP,USB\VID_0c45&PID_613c ; SN9C120 +
HV7131R

setupapi.log has reference to 613c

#-019 Searching for hardware ID(s): usb\vid_0c45&pid_613c&rev_0101,usb
\vid_0c45&pid_613c

#I289 Removing device "USB\VID_0C45&PID_613C\5&28C0DE0&0&2".

#I022 Found "USB\VID_0c45&PID_613c" in C:\WINDOWS\inf\oem4.inf;
Device: "USB PC Camera (SN9C120)"; Driver: "USB PC Camera (SN9C120)";
Provider: "Sonix"; Mfg: "Sonix"; Section name: "SN.PCamV2.XP".

#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.

What does driver node not trusted mean?
+ + + + +
In USB Device view which i tried after installing it also has the !
exclamation mark and "no open pipes". I don't know if it would have
said this before i installed the troublesome software anyway - i
didn't try it. What does no open pipes mean?

Open Pipes: 0
*!*ERROR: No open pipes!
idVendor: 0x0C45 = Sonix Technology Co., Ltd.
idProduct: 0x613C
Ads