Posts Tagged ‘xp’

Windows 2000/XP Driver for (some) Veo Stingray and IBM PC Camera V5000 webcams

UPDATE: For Veo Stingray drivers, try these first. In case they disappear… Stingray 300V (Win98/ME/2000/XP) and Stingray 323V (Win2k/XP only). The one sold by AllElectronics uses the 323V driver.

I picked up an old “Veo Stingray” camera from surplus dealer AllElectronics. These things are pretty junk by modern standards (320×240 resolution, unsightly rounded “looking through a tube” image), but it does have the variable (manual) focus I needed for an imaging project, and the price was right. As for drivers… the company that makes this thing seems to have evaporated, and the particular variant (USB product ID 808B) seems to have never been heard of by anyone, even though there are some identical cameras with slightly different internal hardware (and different Product ID) floating around. They all are (were?) manufactured by Xirlink.

This particular variant can be identifed by USB VID 0545 (Xirlink), Product ID 808B.

Here is a solution that might work (but see update above first): This camera and several IBM PC Cameras use the same or similar chipsets (Sunplus SPCA5xx)…with a small tweak, the IBM camera driver can also be tricked into supporting the ‘808B’ Stingray (maybe others?) by adding its VID/PID to the driver .INF file. Kinda like slipping your cuckoo egg into another nest.

This file includes the IBM driver and tweaked .INF. The following devices are supported:


To install, follow the README.TXT included.

Win2K/XP Driver for Veo Stingray (808B) and IBM V5000

It looks like several open-source driver projects may support the Veo Stingray, IBM PC Cameras and similar SPCA50xx variants (not to mention the classic Dakota Digitals). Note, if your exact ID is not listed as supported, you may be able to get it working with a tweak similar to the above. Have a look at: (older project)
In addition, the package ‘gspca’ may work for these and many other SPCAxxx-based (and other!) webcams. See here for the gspca/spca5xx project and a list of supported cameras.

Daily Windows Rant

Error messages, people. Error messages. When an “error” occurs, it should be accompanied by an “error message”, which informs the user a) that an error did occur; b) what that error was. It does not even necessarily have to be understandable to mere mortals (although this would be really nice), because understanding it is the job of your IT Guy and/or someone before you who got that error, posted it on a help forum somewhere and got an answer. Thus, mere mortals will Google the error message, and if results == 0, post it to a help forum somewhere.

Now, a “Dee-Dunk” error (available only at your local PC speakers, assuming you have any and they are turned on at the moment, and the volume is turned up, and the error being reported isn’t a soundcard error*) is really hard to Google. Besides that, consider the conversation between the user and the IT guy:

IT Guy: What was the error message?
User: Well, it was kind of like um… a low rumbling, kind of like somebody dragging a department-store mannequin across a warehouse floor strewn with marbles, followed by an orchestra hit.
IT Guy: Was it a high orchestra hit or a low orchestra hit?**
User: Umm…

So for anyone who is dying to know: Under Windows XP, a “doodoodoo” error*** (sounds like the first half of a doo-dink notification repeated three times really fast) when attaching a hardware device means that the device is successfully identified, but its drivers are kinda-sorta-semi-quasi-blacklisted because somebody at one time clicked “STOP Installation” at one of those “This driver has not undergone Windows Logo Extortion Certification and will probably do really terrible things [Continue anyway] [STOP Installation]” screens. From that point forward, the user will never again be prompted to install the driver or change his mind, regardless of how many times the device is subsequently unplugged and plugged back in. To fix: Find the brokenly-installed device in Device Manager, dig down to driver details and ‘Reinstall Driver’; this will allow you to manually force a driver despite any previous accidental blacklistings.

*As with many work PCs, we did not bother hunting down a set of speakers to attach to, for example, our EE lab workstation. This is not unreasonable considering that it is a workstation, not a watch-youtube-station.

**The next version of Windows will communicate with the user entirely by winks, nudges and significant glances. (IT guy: “Are you sure it wasn’t a drum solo? ‘Cuz a drum solo error is really bad.”)

*** or doo-doo-doo or DoDoDo or doodoodoot or boobooboop, or however you would enter it in Google if you thought that might actually work