If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rating: | Display Modes |
#16
|
|||
|
|||
Can you help me on an older system netbook question?
Hello, just did the download of suggested utility but when I was trying to begin the search, camera device disappeared from system. Sometimes device shows up then vanishes. Like if something had remote control over it. "Paul" escreveu na mensagem ... http://www.makeuseof.com/tag/find-program-using-webcam/ 1) Device Manager (Start : Run : devmgmt.msc) Locate webcam. (On this machine, it's under Imaging Devices but it could be somewhere else.) Do Properties on the webcam. Use the Details tab of the Properties dialog. Use "Physical Device Object Name". WinXP doesn't have such a property listed, but Win8 does. My Venus webcam is \Device\000000a8 at the moment. 2) Use Sysinternals.com Process Explorer (procexp.exe). Look for something using \Device\000000A8. There is a search dialog to find the program using that handle. The purpose of this, is to find what program is using the webcam. HTH, Paul |
Ads |
#17
|
|||
|
|||
Can you help me on an older system netbook question?
Used utility to find process, like Paul's explanation, found different
svchost.exe instances at different times. Once was process with PID number 1748, ended process, then tried again and there was another process with different PID. I presume process is starting automatically with different PID's. "Paulson" escreveu na mensagem ... Hello, just did the download of suggested utility but when I was trying to begin the search, camera device disappeared from system. Sometimes device shows up then vanishes. Like if something had remote control over it. "Paul" escreveu na mensagem ... http://www.makeuseof.com/tag/find-program-using-webcam/ 1) Device Manager (Start : Run : devmgmt.msc) Locate webcam. (On this machine, it's under Imaging Devices but it could be somewhere else.) Do Properties on the webcam. Use the Details tab of the Properties dialog. Use "Physical Device Object Name". WinXP doesn't have such a property listed, but Win8 does. My Venus webcam is \Device\000000a8 at the moment. 2) Use Sysinternals.com Process Explorer (procexp.exe). Look for something using \Device\000000A8. There is a search dialog to find the program using that handle. The purpose of this, is to find what program is using the webcam. HTH, Paul |
#18
|
|||
|
|||
Can you help me on an older system netbook question?
Paulson wrote:
Used utility to find process, like Paul's explanation, found different svchost.exe instances at different times. Once was process with PID number 1748, ended process, then tried again and there was another process with different PID. I presume process is starting automatically with different PID's. Each of the svchosts, holds system services. Process Explorer should be able to "look inside" a svchost and see a list of services. The biggest svchost holds about fifteen different network services. The PID (process ID value) should stay constant for the entire session. But the next time you boot, the PID value could be different. But the separation of the services is constant, with one svchost having more than the others. The services have "classes" and ones of the same class, live in the same svchost. http://i58.tinypic.com/b7jr15.gif What I can't tell you right off hand, is whether all the usual analysis capabilities exist for checking stuff in there. Normally, you don't go putting code in there, unless it is an anonymous service. (Google hid something in a svchost once, so there is a precedent for messing around there.) I have noticed here, that my webcam can register as a "network device", even though it isn't a network device. Whether that's what the svchost connection is, I don't know. Even if a service in a svchost was looking at your camera, it shouldn't make it "busy" unless it is using the camera. And that would be a bad sign... Paul |
#19
|
|||
|
|||
Can you help me on an older system netbook question?
Paul wrote:
Paulson wrote: Used utility to find process, like Paul's explanation, found different svchost.exe instances at different times. Once was process with PID number 1748, ended process, then tried again and there was another process with different PID. I presume process is starting automatically with different PID's. Each of the svchosts, holds system services. Process Explorer should be able to "look inside" a svchost and see a list of services. The biggest svchost holds about fifteen different network services. The PID (process ID value) should stay constant for the entire session. But the next time you boot, the PID value could be different. But the separation of the services is constant, with one svchost having more than the others. The services have "classes" and ones of the same class, live in the same svchost. http://i58.tinypic.com/b7jr15.gif What I can't tell you right off hand, is whether all the usual analysis capabilities exist for checking stuff in there. Normally, you don't go putting code in there, unless it is an anonymous service. (Google hid something in a svchost once, so there is a precedent for messing around there.) I have noticed here, that my webcam can register as a "network device", even though it isn't a network device. Whether that's what the svchost connection is, I don't know. Even if a service in a svchost was looking at your camera, it shouldn't make it "busy" unless it is using the camera. And that would be a bad sign... Paul An article here, claims your camera is packaged by Chicony. Presumably they make the subassembly that sits at the top of the panel. (And it could be, that more than one model of webcam was used in production.) https://gbdrbob.wordpress.com/2011/1...-eee-pc-1000h/ And I didn't know you could list all the webcam drivers on the site, like this. http://support.asus.com/Download.asp...mera&p=3&os=29 The newest Chicony is the third one down. Since they seem to stop with Windows 8, I'm guessing Windows 8 has these built-in. Version V061.005.200.440 USB\VID_04f2&PID_b071 CNF7129(OV9665+260B) You would want to check device manager to see if that matches the properties of the camera. A camera consists of two parts. The sensor chip (Omnivision 9665). And a controller. The controller has a data bus on one side for the sensor, and USB pins on the other side. The controller in some cases does MJPEG compression. The controller chip does not have a "fixed" VID/PID. The company making the webcam PCB, can change the VID/PID using an EEPROM. That makes it rather hard to predict what numbers you'll find. The above values are a guess provided by the article. I can't really be sure whether the "260B" value is made by Sonix or some other company. The list of USB IDs available, doesn't match on that value. There is no need to install any driver, if that driver is already evident in Win8 Device Manager. Something like sncduvc.sys or snp2uvc.sys. It still doesn't explain why your camera is "busy". It also doesn't explain why Asus had that "Ecap" program listed on their download page for the 1000H netbook. Paul |
#20
|
|||
|
|||
Can you help me on an older system netbook question?
It's closer. I read somewhere the camera was made by Chicony but even that
isn't clear. Tried some of those drivers provided in the page you posted, none of them has same hardware ID. The utility you suggested on previous post, process explorer, gave me the sensation the object was token by NT Authority Account. I don't understand this very well, as you say, device is busy with something. Can't use it. Tried Skype, Windows Movie Maker and other utilities, all of them gave the same error. I think I must quit changing the situation. "Paul" escreveu na mensagem ... The controller chip does not have a "fixed" VID/PID. The company making the webcam PCB, can change the VID/PID using an EEPROM. That makes it rather hard to predict what numbers you'll find. The above values are a guess provided by the article. I can't really be sure whether the "260B" value is made by Sonix or some other company. The list of USB IDs available, doesn't match on that value. There is no need to install any driver, if that driver is already evident in Win8 Device Manager. Something like sncduvc.sys or snp2uvc.sys. It still doesn't explain why your camera is "busy". It also doesn't explain why Asus had that "Ecap" program listed on their download page for the 1000H netbook. Paul |
#21
|
|||
|
|||
Can you help me on an older system netbook question?
Paulson wrote:
It's closer. I read somewhere the camera was made by Chicony but even that isn't clear. Tried some of those drivers provided in the page you posted, none of them has same hardware ID. The utility you suggested on previous post, process explorer, gave me the sensation the object was token by NT Authority Account. I don't understand this very well, as you say, device is busy with something. Can't use it. Tried Skype, Windows Movie Maker and other utilities, all of them gave the same error. I think I must quit changing the situation. There are at least three interfaces to grab images from the webcam. TWAIN, WIA, DirectShow. The "thing" in the SVCHOST you are seeing, could be WIA. If you look in the "Services" panel in Windows, you may see one for "WIA Services". You could try disabling that, so that the Service in the SVCHOST cannot interfere with your attempts to connect via DirectShow. http://img.microsoft.com/library/med...e/hwspxp01.gif Doing so, should not be essential. The reason for me making this suggestion, is that some other piece of software on your machine, is using WIA, and making the device handle busy. By disabling the WIA service temporarily (by using the Stop button in Services for that service), the idea is to free up the device handle, such that other DirectShow applications (like maybe AMCAP), can gain access to the camera. Normally, WIA would not interfere, unless you were using a WIA based application. (Some of the software interfaces, are named here.) http://www.drdobbs.com/windows/apis-...ions/240156834 Just a theory, Paul |
#22
|
|||
|
|||
Can you help me on an older system netbook question?
Hi, did check directX, system has directX 9c installed. Tried camera preview
without WIA service. Same error. Maybe it's a no solution problem. I don't want to reinstall Windows XP. I'll survive without webcam. "Paul" escreveu na mensagem ... Paulson wrote: It's closer. I read somewhere the camera was made by Chicony but even that isn't clear. Tried some of those drivers provided in the page you posted, none of them has same hardware ID. The utility you suggested on previous post, process explorer, gave me the sensation the object was token by NT Authority Account. I don't understand this very well, as you say, device is busy with something. Can't use it. Tried Skype, Windows Movie Maker and other utilities, all of them gave the same error. I think I must quit changing the situation. There are at least three interfaces to grab images from the webcam. TWAIN, WIA, DirectShow. The "thing" in the SVCHOST you are seeing, could be WIA. If you look in the "Services" panel in Windows, you may see one for "WIA Services". You could try disabling that, so that the Service in the SVCHOST cannot interfere with your attempts to connect via DirectShow. http://img.microsoft.com/library/med...e/hwspxp01.gif Doing so, should not be essential. The reason for me making this suggestion, is that some other piece of software on your machine, is using WIA, and making the device handle busy. By disabling the WIA service temporarily (by using the Stop button in Services for that service), the idea is to free up the device handle, such that other DirectShow applications (like maybe AMCAP), can gain access to the camera. Normally, WIA would not interfere, unless you were using a WIA based application. (Some of the software interfaces, are named here.) http://www.drdobbs.com/windows/apis-...ions/240156834 Just a theory, Paul |
#23
|
|||
|
|||
Can you help me on an older system netbook question?
Paulson wrote:
After this particular event I don't feel much more desire to buy more gadgets to be responsible for them. Perhaps an IP camera to watch the weather. So do you have a VID/PID value ? Is there an entry in Device Manager for Imaging Device ? You have to start with the details, to find a matching driver. http://i59.tinypic.com/2aevvrl.gif Paul |
#24
|
|||
|
|||
Can you help me on an older system netbook question?
This are the details on Usbtreeview utility:
Device ID: USB\VID_0C45&PID_62C0&MI_00\6&CFD3D6B&1&0000 iManufacturer: Sonix Technology Co., Ltd. iProduct: USB 2.0 Camera I can go to regedit, HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Cl ass\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F} Use {6BDD1FC6-810F-11D0-BEC7-08002BE2092F} to find process in Process Explorer utility The result is: svchost.exe 3984 Key HKLM\SYSTEM\ControlSet001\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0000 or Process PID 3984 In Device Manager I can see the image device, "Dispositivo de vídeo USB" (Windows XP Portuguese version) In Properties I can see these driver files, ks.sys usbvideo.sys dshowext.ax iyuv_32.dll ksproxy.ax kstvtune.ax ksuser.dll kswdmcap.ax ksxbar.ax msh263.drv msyuv.dll tsbyuv.dll vfwwdm32.dll vidcap.ax "Paul" escreveu na mensagem ... Paulson wrote: After this particular event I don't feel much more desire to buy more gadgets to be responsible for them. Perhaps an IP camera to watch the weather. So do you have a VID/PID value ? Is there an entry in Device Manager for Imaging Device ? You have to start with the details, to find a matching driver. http://i59.tinypic.com/2aevvrl.gif Paul |
#25
|
|||
|
|||
Can you help me on an older system netbook question?
Paulson wrote:
This are the details on Usbtreeview utility: Device ID: USB\VID_0C45&PID_62C0&MI_00\6&CFD3D6B&1&0000 iManufacturer: Sonix Technology Co., Ltd. iProduct: USB 2.0 Camera I can go to regedit, HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Cl ass\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F} Use {6BDD1FC6-810F-11D0-BEC7-08002BE2092F} to find process in Process Explorer utility The result is: svchost.exe 3984 Key HKLM\SYSTEM\ControlSet001\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0000 or Process PID 3984 In Device Manager I can see the image device, "Dispositivo de vídeo USB" (Windows XP Portuguese version) In Properties I can see these driver files, ks.sys usbvideo.sys dshowext.ax iyuv_32.dll ksproxy.ax kstvtune.ax ksuser.dll kswdmcap.ax ksxbar.ax msh263.drv msyuv.dll tsbyuv.dll vfwwdm32.dll vidcap.ax OK, that's *exactly* the same set of driver files as is used right now by my Venus webcam. The webcam that doesn't work in GIMP Image Editor, but does work in AMCAP capture program. If you add a manufacturer driver, it may add a TWAIN driver. Adding this, should give you a WIA-TWAIN entry in GIMP and allow you to take a still picture. It still doesn't explain why other applications cannot use your camera. HP Webcam Driver for two camera entries. They're likely to be the same camera parts, but the identity was changed by the manufacturer. The OC45 is Sonix (bought by Microdia). The second might be the Chicony part number (04F2). Your VID is for the Sonix one. As I said before, some USB devices, the identifier can be changed by the manufacturer, easily, with a simple EEPROM external to the camera chip. And it's very difficult to then track down what camera chip and sensor chip are actually being used. [SN.NTx86.5.1] -- 5.1 = WinXP, 6.0 = Vists %SN.USBVideo.DeviceDesc% = SN.USBVideo.XP,USB\VID_0C45&PID_62C0&MI_00 --- Your camera %SN.USBVideo.DeviceDesc% = SN.USBVideo.XP,USB\VID_04f2&PID_b018&MI_00 ;SN9C213B+OV2640 ftp://ftp.hp.com/ftp1/pub/softlib/so...er_5.8.9.2.exe So what does that driver give you: 1) No change to basic UVC camera operation. Software like DShow based software (AMCAP) should have always worked, even without the driver. When this driver package is installed, you should see a few more entries added to the basic list of 13 items. 2) It looks like that one adds a TWAIN driver. Which will not help you with Skype, but may make the camera work with GIMP image editor, or other image editors. 3) May or may not include a control panel so you can change more settings. Since the driver is coming from HP, it should be free of malware. And the purpose of this test, is to see if we can get a picture *somehow* from your camera. HTH, Paul |
#26
|
|||
|
|||
Can you help me on an older system netbook question?
Thought it was easy. You seem to understand a lot. Thank you for trying.
"Paul" escreveu na mensagem ... Paulson wrote: This are the details on Usbtreeview utility: Device ID: USB\VID_0C45&PID_62C0&MI_00\6&CFD3D6B&1&0000 iManufacturer: Sonix Technology Co., Ltd. iProduct: USB 2.0 Camera I can go to regedit, HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Cl ass\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F} Use {6BDD1FC6-810F-11D0-BEC7-08002BE2092F} to find process in Process Explorer utility The result is: svchost.exe 3984 Key HKLM\SYSTEM\ControlSet001\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0000 or Process PID 3984 In Device Manager I can see the image device, "Dispositivo de vídeo USB" (Windows XP Portuguese version) In Properties I can see these driver files, ks.sys usbvideo.sys dshowext.ax iyuv_32.dll ksproxy.ax kstvtune.ax ksuser.dll kswdmcap.ax ksxbar.ax msh263.drv msyuv.dll tsbyuv.dll vfwwdm32.dll vidcap.ax OK, that's *exactly* the same set of driver files as is used right now by my Venus webcam. The webcam that doesn't work in GIMP Image Editor, but does work in AMCAP capture program. If you add a manufacturer driver, it may add a TWAIN driver. Adding this, should give you a WIA-TWAIN entry in GIMP and allow you to take a still picture. It still doesn't explain why other applications cannot use your camera. HP Webcam Driver for two camera entries. They're likely to be the same camera parts, but the identity was changed by the manufacturer. The OC45 is Sonix (bought by Microdia). The second might be the Chicony part number (04F2). Your VID is for the Sonix one. As I said before, some USB devices, the identifier can be changed by the manufacturer, easily, with a simple EEPROM external to the camera chip. And it's very difficult to then track down what camera chip and sensor chip are actually being used. [SN.NTx86.5.1] -- 5.1 = WinXP, 6.0 = Vists %SN.USBVideo.DeviceDesc% = SN.USBVideo.XP,USB\VID_0C45&PID_62C0&MI_00 --- Your camera %SN.USBVideo.DeviceDesc% = SN.USBVideo.XP,USB\VID_04f2&PID_b018&MI_00 ;SN9C213B+OV2640 ftp://ftp.hp.com/ftp1/pub/softlib/so...er_5.8.9.2.exe So what does that driver give you: 1) No change to basic UVC camera operation. Software like DShow based software (AMCAP) should have always worked, even without the driver. When this driver package is installed, you should see a few more entries added to the basic list of 13 items. 2) It looks like that one adds a TWAIN driver. Which will not help you with Skype, but may make the camera work with GIMP image editor, or other image editors. 3) May or may not include a control panel so you can change more settings. Since the driver is coming from HP, it should be free of malware. And the purpose of this test, is to see if we can get a picture *somehow* from your camera. HTH, Paul |
#27
|
|||
|
|||
Can you help me on an older system netbook question?
De Varella e Almeida wrote:
Thought it was easy. You seem to understand a lot. Thank you for trying. The objective here, is to get some kind of response out of the camera. Even if everything doesn't work on the first day, getting some sort of image from it, is a start. On my Win7 laptop, the built-in webcam pictures are horrid. They're dark and unevenly lighted. So I no longer have to worry about whether all the drivers work on the laptop, because it is such a bad camera. It's not worth using for anything. Maybe you will have better luck. As your camera has a higher-resolution sensor, and maybe it cost $1 more than mine. Paul |
#28
|
|||
|
|||
Can you help me on an older system netbook question?
On Sun, 18 Jan 2015 22:08:54 -0500, Wolf K wrote:
On 2015-01-18 8:21 PM, De Varella e Almeida wrote: With IP cameras you can access them a 100 miles away through internet. Well, not that this comment solves your problem, but actually you can access any camera if you can access the device that it is connected to. You can do it with a smartphone, from anywhere in the world. You can access any device whatsoever if it is connected to some other device that is linked into the internet. You just need to know how.... I think you've illustrated the difference between so-called IP cameras and other cameras. IP cameras are assigned an IP address directly, and they can be accessed over a network via that IP address. Non-IP cameras need to be connected to some kind of a host, and it's the host that is then accessed via its IP address. To put it another way, IP cameras have a network interface rather than (for example) a USB port, and frequently have a web server built in. Using a web browser, you can browse to the IP address of the camera and see what the camera sees. |
#29
|
|||
|
|||
Can you help me on an older system netbook question?
Wolf K wrote:
Char Jackson wrote: IP cameras have a network interface rather than (for example) a USB port, and frequently have a web server built in. Using a web browser, you can browse to the IP address of the camera and see what the camera sees. So If I know the IP address, I can access that camera, whether or not the owner "approves", right? Depends on the authentication of the camera's web server and what the owner's firewall allows ... |
Thread Tools | |
Display Modes | Rate This Thread |
|
|