Member Avatar for ianmanzy

Hi I am a newbie to this kind of thing as well as to this site and I need some help!!! I have come very close to making the new PS Eye (SLEH-00201) camera work on my laptop, but I really have no idea what I'm doing. I tried installing the drivers folks were using for the original Eye Toy (SLEH-00030) to start. Naturally that didn't work for a number of reasons (non-matching chipset control, USBVID & PID), so I dug deeper. The controller chipset on the PS Eye (OV534) is a different one than is used in the Eye Toy (OV519). There is a set of drivers for another camera using the same controller chip, the Omnivision Apollo Camera. I replaced the Vendor ID and the USB Product ID in the .INF file as I saw it done for the Eye Toy using drivers with the same chipset control. I chose the drivers to install for the device and everything went well until the very end. I got a code 10 and was told the device cannot start. Looks like the last part of the install was attempting to launch the EXE file in the drivers folder, which of course is not for this camera. So this is the last step I have taken. Not sure what to do now, so I thought I'd share this with the community and query and hope for feedback from the experts. Any words on this issue would be greatly appreciated.

Thanks

  • 4 Contributors
  • 4 Replies
  • 666 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by jerseyboy

Dani AI

Generated

As has already tried, adapting an existing driver by matching the camera’s Vendor/Product IDs is the right direction. Posts from , and point to the problem being a driver/firmware mismatch rather than a simple USB plug‑and‑play error. The checklist below focuses on the practical steps that usually clear the Code 10 / post‑install EXE problem on Windows XP.

Start by getting the exact hardware ID reported by Windows (Device Manager → device → Properties → Details → Hardware Ids). The string will look like USB\VID_1234&PID_5678. That exact string must appear in the INF’s Models section; a minimal example entry looks like:

%DeviceDesc% = CameraInstallSection, USB\VID_1234&PID_5678

A Code 10 that happens when the installer tries to launch an EXE usually means the driver package expects a vendor helper or firmware step that isn’t compatible. Two safe tactics: install the driver manually via Device Manager using “Have Disk…” and select only the INF (avoid running the vendor setup EXE), or open the INF in a text editor and inspect/remove nonessential directives (search for .exe, DefaultInstall, CopyFiles, AddService). Confirm the referenced .sys file exists in the same folder and that an AddService section installs the kernel driver; if not, the INF will fail even with a matching VID/PID.

If Windows still refuses the device, use a Linux LiveCD to check whether the camera presents a standard video stream (diagnostic step to see if a generic UVC driver will work) and try different USB ports or a powered hub in case of current draw issues. Always make a System Restore point before modifying drivers or INF files.

Member Avatar for bugmenot

Hi I am a newbie to this kind of thing as well as to this site and I need some help!!! I have come very close to making the new PS Eye (SLEH-00201) camera work on my laptop, but I really have no idea what I'm doing.

has done some work on fishing out the details for the camera's USB data. Try posting your message there.

Member Avatar for jerseyboy

I'm not sure either but if you figure something out let me know. I'll try myself to see if I can get it to work with windows.

Member Avatar for SoulPusher

The controller chipset on the PS Eye (OV534) is a different one than is used in the Eye Toy (OV519).

You are right in that it is another chipset than the OV519. What I learned in other forums attempting to get it working in linux is the following:

EyeToy: OV519 + OV7648
Playstation Eye: OV538 + OV7721

The other forum even says if you open it up it has OV538 silkscreened on the board.

As far as I can tell, there aren't even windows drivers released for the OV538 as of yet.
If any of you or anyone else reading this thread does get it working, please post!

Thanks.

Member Avatar for jerseyboy

I'm not to sharp when it comes to creating a driver in fact I have no idea how to creat one. I am doing a lot of research though. I found this maybe this will help you guys.
let me know if it helps with anything

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.