How to identify your webcam (and then find its driver)

Hey,
Sry my bad

USB\VID_058F&PID_6130&MI_00

Thanks!

That one (VID) is by Alcor Micro,
and you will also sometimes see V550 (a Kodak model different VID).

The most complete list I have found of Alcor PIDs is this...

I have not yet found a driver for you.
Maybe with this information you can continue the search.
Report back if you find success (That way we won't keep looking)
... and where.

Thanks
---------------
-more information and questions...

alcor micro support info

Can you tell us any more about the camera?
...(like "is it a built in?")
Is it possibly a Q-Tec camera
http://www.qtec.info/products/group.htm.22.html

Might it be possible to reverse engineer a windows driver from a linux driver?
Just asking...

Hi alicarlos13

You're presenting a good challenge! Here's what i'd like to do in exploring a solution for you

• First, good work again B00kWyrm! This hardware ID does indeed indicate an Alcor Micro device inside the web cam
• Meaning Alcor is the chip vendor and enet (or enet360) is the company that actually built the webcam
• Note: That I did find a few enet or enet360 related websites but i'm not including the links as i;m suspicious of malware on the sites (one in english, two in, i think, chinese). I did (cautiously) look at the english site (as i can't read chinese) but didn't see anything of interest
• But I also noticed something curious about your hardware IDs.
  The MI_xx in the ID means it's a USB composite device (That's a USB device with multiple device interfaces). I'd like to double check and verify these IDs are indeed your webcam (and/or if any other Hardware and Device IDs are involved) because i'm not sure i've seen a USB web cam composite device before (tho maybe i'm just not remembering or maybe, in fact, your web cam happens to be a composite device). These steps will let me know for sure
  Could you please
  
  First, disconnect your webcam from the computer
  • Then click Start->Run, enter: msinfo32. Click the + sign next to Components to expand it
  • Click Problem Devices. Anything appear?
  • If yes, click on it, Ctrl-A to select all, Ctrl-C to copy it, Ctrl-V to paste into next post
  
  Next, re-connect your webcam
  Be sure you first close msinfo32 from above steps! Then repeat all the steps to get a NEW (and refreshed) msinfo32 and what is reported this time (with webcam connected). Then copy/paste the items into your next post

Once i can first double check the current ID data, i can explain how to also look for something called Compatible IDs which can also point us to driver solutions

Mine says VID_093A&PID_2468&rev_0100, and I've been searching for it's drivers all day, but to no avail. Also, It doesn't have a logo or anything written on it, so I haven't been able to search it that way. I can't seem to find a picture of it either, no matter what I search, any help would be appreciated.

Actually as LookinAround tries to help you (as he has successfully done, with many before)
Do you want to take a picture of it yourself, then save the pic to your computer, then upload the pic to www.tinypic.com then link it to here? That way we know what we're trying to fix :grinthumb

There's no place like home!

You'll find the answer for your webcam Hardware ID right here in TechSpot forums already

Are you running XP? Checkout the drivers in this thread!

The driver for Salty (who started the thread) should also work for you (post back to let me know for sure)

For readers who might be curious about how all these cryptic looking ID strings work to help you find a driver…..

First, refer back and re-read my starting post in this thread. I talk a little about about Windows Device Identification Strings, note:

1. Windows Plug-and-Play devices work because these devices all conform to an international standard for Plug-and-Play
2. Every vendor who makes a “Plug-And-Play” device must conform to that standard
3. Windows Device Identification Strings are part of the Plug-And-Play standard
4. There are several different types of Windows Device Identification Strings
   • Device Instance IDs
   • Hardware IDs
   • Compatible IDs
   • Note that Device Names are NOT Device Identification Strings!
5. A vendor determines the appropriate ID strings for their device BEFORE IT IS EVEN MANUFACTURED!
6. These ID strings are embedded/stored within the device when it’s built
7. When Windows detects a new hardware device it queries the device for its ID strings
8. Windows does not use (or need) any drivers to query a device and its ID strings! Drivers aren't needed because the method for query/response is defined in the Plug-and-Play standard and by design doesn't need drivers (getting the IDs is what allows Windows to go looking for drivers!)
9. Once Windows receives all its ID strings, it THEN uses those ID strings to search for the correct driver so it may provide full functionality, control and communication with the device
10. Windows will happen to display whatever device name it happens to find inside the driver AFTER it locates the driver. (Change the name in the driver to BALONEY and Windows will display BALONEY as the device name! The device name is purely a comment!)
11. Note: the ID strings come first, then the driver is found using the IDs. Finally, Windows displays the device name as whatever device name string it happens to find in the device's driver
12. Searching for drivers using device names MAY work.. but note that's a side-affect of a device name happening to appear within a driver. So, searching by name may work by coincidence, not by design, as there's no need for a device name be UNIQUE to only one driver nor that the driver even contain the RIGHT or FULL device name! That's why sometimes someone might find a driver that exactly matches the device name yet Windows says no matching hardware found! In such case, they happened to find a driver that matches on name but not IDs. And IDs are what's important.
13. The driver matching process is based soley on the ID strings!

Hi KKirby16

I looked back in the thread and was reminded of your post... Did you ever get the answer for your web cam?? (sorry don't recall if you did or didn')

Hi alicarlos13

Haven't heard back from you yet. But i do have an update. While i'd still like to see the Problem Report output for the two case i described earlier in my posts... I have now noticed that, YES, in fact some web cam Hardware IDs do include the MI_xx in their ID string.

But , if you could just try generating those Problem Reports would still help

Hi guys have the webcam demons been laid to rest?.
Just wanted to say hi and am always reminded of the help when I use my shitty webcam that has worked unfailingly since the help from this forum.
A quick question though,where can I find a helpful forum on Netbooks and their relevent processors,am thinking of buying one. The search functions on this topic tend to lead to......
Thanks again

Hi Timothy Raj :wave:

Glad to hear your web cam is still working!

As for your netbook questions, try posting your questions in the Mobile Computing forum is probably your best bet

Thanks a lot, will head there and look around. Take care.

Please help identify this generic USB camera

Hi! I found this thread when trying to determine what drivers to get for this extremely generic USB camera. Despite the instructions I've had no success at all.

The camera is simply branded "Digital" and was made in China. It has absolutely no other codes or IDs on it at all, and I know nothing more about it.

In Windows it detects as: "PC Camera"

Below are additional details about it, and pictures:

Hardware IDs
USB\VID_0979&PID_0224&REV_0100
USB\VID_0979&PID_0224

Compatible IDs
USB\Class_00&SubClass_00&Prot_00
USB\Class_00&SubClass_00
USB\Class_00

Device Instance Path
USB\VID_0979&PID_0224\5&19124716&0&3

i27.tinypic.com/aku2hc.jpg

i31.tinypic.com/29n8emt.jpg

i32.tinypic.com/x1af49.jpg

Many thanks for any suggestions!

See if this driver (click here) works for you

Thanks for that suggestion. I tried to install the referenced drivers in both Windows Vista and Windows 7 and each time it gives the error in device manager:

"A service installation section in this INF is invalid."

However, your discovery of it being a "Toy Camera" led me to locate the exact camera, it is known as the "35g Pen Digital Still Camera."

Unfortunately I'm still having troubles finding drivers for this device.

Edit: I tried to install the AIPTEK Trio Cam driver as that camera looks virtually identical. I tried to install those drivers in XP, Vista, and Windows 7 but that could not detect the device either. Hmm.

Hmmm... You say you tried on "both Windows Vista and Windows 7".

1) I assume that means you tried installing the driver on two different computers? (one running Vista, the other Windows 7)

2) Click for how to determine whether you are running 32 or 64 bit windows. Please indicate if you are 32 or 64 bit for each computer

I ask as the message you quoted about "INF invalid" i think implies the driver is not a match for the version of Windows you have running. I'd like to double check your Windows OS version and if you are running a 32 or 64 bit version of Windows

/* EDIT */
So for each computer you're using indicate:
What Windows OS is running? the SP service pack level? and if it's a 32 or 64 bit version of Windows (check 32 or 64 using instructions in the link i provided above)

Yes, I tried on two separate computers / hard drives... They are each running 64-bit Windows (one with Vista, one with Windows 7). Vista has SP2, Windows 7 is still RC. When I installed the driver, if I recall, it detected 64-bit and selected that option for the OS.

I do still have one other computer with Windows XP (32-bit) that I will try as soon as I can. If nothing more, I would at least like to get the stored pictures from the device but I don't suppose that's an easy task without the drivers? I wish I had a mac because, from reading, Mac OS sometimes gives more detailed information about the specific device than Windows which could help locate more accurate drivers.

Hi Nexious

1) I suspect the camera has been repackaged and sold under a variety of different names. I think you'll also find many potential driver hits searching for JL2005A Toy Camera

2) I tried to download the driver i gave you in the link in my own post! (so i could look at the driver installation file which dictates the Hardware IDs and Operating Systems that the driver will support) but the download fails! (maybe the server is down now, don't know, will try again tomorrow). So even tho the driver's web page claims Vista 32/64 bit support I suspect the driver installation file doesn't. Many of the older web cams are only supported on Windows XP but not Vista

3) You might also try this link . I was able to download and look at this specific driver and its installation file. The Hardware ID matches but it will only install on XP. (maybe only 32 bit). Just select the "Download free by viewing ads" and look in bottom right corner of each ad to click on No Thanks. You only need see 3 or 4 ads to get to the download

/* edit */
and btw.. check out this camera manual pdf file..

sorry but i need help

hi ive been trying to look for the drivers of my webcam for a long long time and i was lucky enought to bump into this thread..however i still cannot find the drivers for my webcam please help

this is my hardware id

USB\VID_2770&Pid_930c&Rev_0100

USB\VID_2770&Pid_930c

pleasee help and thank you

Well, I'm not real sure about this one
1) Many of the sites i found were, i think, in Chinese (which i can't read)
2) Appears the sensor in your cam is used in many different webcams

But here's my best guess for you cam... try the driver for the Trust USB2 HiRes Webcam WB-3500T

1) Is your cam the same as the one in the picture?
2) Even if not, the hardware IDs match so you can still try to download and install/use the driver.

I hope it works for you.

Thannksss!

Duddeeee u r absolutely the best ive been trying so long to get this to work thank you thank you thank you!!!!