I recently got a cheap (very) usb endoscope from eBay and it doesn't work on my machine and I strongly suspect that is because i'm running WinXP. For I've seen a Youtube vid about the identical item and it's working fine for him on Win7. And there's other hits I've had on Google where guys are having problems. USB devices don't usually have a driver, I know. You just plug them in and they work. The installation disk that Youtube guy was so frightened to use contains not drivers but a viewing prog. A thing called Rscap_1.10.exe That's a Realtek thing.

Digicamcontrol Mac Os more. I just had a thought – I should try chasing them up for something, shouldn't I? But the thing is Rscap can't see the thing. Nor can Windows Movie Maker. Nor anything else I've got. Though XP sees something. It reports new hardware found and soon follows that with a message that it has malfunctioned etc. So has anyone any advice on how maybe I could get it to work?

I have a similar device and it works on Winxp. I can't remember for sure if I had to find a driver when I first got it, but I don't think so.

Jul 9, 2016 - 2 min - Uploaded by Screenguy3Hook up your endoscope without a bunch of hassle or third party software. In just a few simple.

The disc that came with it also has RsCap on it, but it is RsCap_1.11.exe. There is nothing else on the disk I have not really used RsCap before but I tried it now and I got it to work. Initially it came up with some error, but it started working when I selected an audio device under 'devices' (in addition to the 'USB Video Device' that was already checked). That does not make much sense to me.

I also just noticed that when I plug it in, an entry for 'USB Video Device' suddenly appears in Windows Explorer. If I click on that, and the device is not in use in another program, it opens a video preview window, which works, but you don't seem to be able to do much with that.

Maybe this thread should be moved to Windows. There is a copy of RsCap in a zip file here: I think that is the same as the one that I have on the disk here – it is the same size and date.

If I select 'about' when running it is says version 1.08 (?). It looks like it was based on Amcap which I think was was some sort of example program provided by Microsoft way back. Somehow I don't think your problem is with RsCap though. I just tried plugging the device in again after the system was rebooted overnight. The preview in Windows Explorer was not working, just giving an obscure message that the device might be already in use, which it wasn't. RsCap put up a message box 'Error: 800705aa: Cannot run preview graph.' Another program I tried also said 'Cannot run preview graph' but also said something about lack of system resources.

I had a lot of other stuff open at that time, so I shut a few things down, and now it is working OK in RsCap and other programs too. Maybe it was the same error I got initially yesterday with RsCap – I didn't really make a note of what it said. It might have to do with your windows install. I have one of these generic USB Borescopes, and it plugs and plays on a Windows XP Home Netbook. Checking the System drivers, it says its using Microsoft – USB Video Device #5. The Driver date is 7-1-2001. Version 5.1.2600.5512.

I can view through windows explorer, but if I need to screen capture, I use a third party program. I think you only need to use RSCap to capture pics/vids.

I have to find the mini CD that came with mine, but I think it only had the capture program on it, no drivers. I've been trying to get a driver to work with an Android device but have had no luck to date. I plugged my USB borescope into another XP Pro machine, and it plugs and plays as well. The driver used is USB Video Device #7 Driver version 5.1.2600.5512 Driver date 1/07/2001. When you get the error message, did you have a look at Control Panel/System/Device Manager/Imaging devices, and see what comes up as the Exclamation Mark there? There's no markings on my USB borescope, only it is 4 LED, 640x480 focal distance 4-7cm or 6cm-infinite on the box. I found the CD, and it only has RSCap on it, which I've never used.

My setup doesn't seem to be exactly the same as yours but I went to control panel/system/hardware/device manager and I failed to find anything that might be it. I've got exclamations on items in 'other devices', 'scsi and raid controllers' and 'network adapters. None of them seem to fit the bill. I think it is the Realtek 2832U Device but that's shown as working properly.

And it seems to be an audio device. Why do I think it's that?

Because Rscap.exe is a Realtek product, that's all. I've had slightly strange email conversation with the vendor via ebay, the way you do sometimes with the Chinese who aren't right on top of the English but I think the jist of it is that they are going to send me a driver. They sent me one before and it was just Rscap.exe. Maybe this time.

Edit, later: I found it in device manager. It comes up as 'unknown device' in 'universal serial bus controllers'. This is xp sp3 I'm running even later, another edit: Yep, I found your driver listed as the driver for each of two 'root hubs' listed in device manager. I tried to install that driver to my 'unknown device' but couldn't find a way to do it.

I got close to it but it wanted an 'inf' file instead of the driver. I couldn't provide it.

I've got exclamations on items in 'other devices', 'scsi and raid controllers' and 'network adapters. You might have a driver conflict that's causing your issues on the XP machine. I think it is the Realtek 2832U Device but that's shown as working properly. And it seems to be an audio device.

Why do I think it's that? Because Rscap.exe is a Realtek product, that's all. Not necessarily. The Driver is used in other brands of equipment, and the realtek 2832U Device is typically associated with a Digital TV Tuner Dongles –. Looks like it is used in Medion DTV and Asus DTV dongles amongst others.

Unless you have a fancy USB borescope, I don't they were generally built with a microphone for audio capture, just the video and LED lights. Well that's interesting. The Tun Miniport Adapter with an exclamation uses the same driver you quoted. That isn't the Imaging Device driver you need, but it might be the cause of your conflicts. A quick google results in this (from here ) and (): Ok, hope the following will help those who might run into the same problem.

(1) Cause: Exact cause is unknown, maybe is caused by corrupted registry files due to remove and re-install applications. (2) Symptom: Yellow exclamation mark for Microsoft Tun Miniport Adaptor #2 in Device Manager. (3) Short-term solution: Removing TCP/IP version 6 may also remove the adapter, and thus the conflict. But this is not a 'solution' per se. (4) Long-term solution as follows: Thanks for the tips and discussion in here: by Bazza25 who mentioned related driver info: (tunmp.sys c: windows system32 drivers netip6.pnf c: windows inf nettun.pnf c: windows inf) Note: My solution involves 'delete' registry files so use it at your own risk. Step 1: Remove TCP/IP version 6 protocol and reboot. Step 2: In Normal mode, move tunmp.sys from its current location and another location.

Step 3: Boot into Safe Mode (without Network) Step 4: Run 'Regedit' and search for every reference to Microsoft Tun Miniport Adaptor and delete them (backup first) Note: You may also find some entries in ControlSet2, ControlSet3. And you may not delete some of them, but it's ok. The most important thing is to delete those entries in the current controlset. Step 5: Go to Device Manager and remove Microsoft Tun Miniport Adaptor (Note: If you did not delete registry entries and did not move tunmp.sys to another location, you can not remove this adapter as it will be preloaded). Step 6: Boot to Normal Mode Step 7: See if you have other conflicts and all other Network adapters have been properly recognized. Step 8: If so, Move tunmp.sys back to its original location. Note: Just for precautious, turn off your AV and Firewall and disconnect from the net.

Step 9: Now you can add TCP/IP version 6 protocol back without any error. Additional notes: I guess the issue is that, unlike other network adapters, Microsoft Tun Miniport Adaptor can only have one entry and cannot have #2, #3, and so on, or otherwise, it will mess up the driver version even using both are pointing to the same file – tunmp.sys. I also noticed that at one time, Adapter #2 did not have conflict but it was the first Microsoft Tun Miniport Adaptor that had the yellow exclaim mark. So based on those, I decided to take a more drastic approach to delete all registry entries and to 'cheat' Windows that there is none in the system. So when I added back TCP/IP version 6 (which will automatically created this adapter entry), it will not have #2 but only one.

Hope this helps. Well thanks for that, I thought it was great and rushed to implement it. But it didn't work because it wouldn't let me uninstall the Miniport. It let me start but it wouldn't let me finish, saying that it might be needed to boot the system. I was in safe mode. I was disconnected from the web.

I had renamed tunmp.sys and netip6.pnf and nettun.pnf and I had uninstalled tcp/ip v6 – ipconfig shows it is still uninstalled. That tcpipv6 thing rings bell.

I was getting errors that mentioned it. No such on this bootup after all that. Those files remain renamed. The tunminiport remains conflicted. My blaze dtv won't work now, either.

It's all a strange happenstance. And it has got worse: I didn't make a backup of the registry when I deleted the entries for the miniport and now device manager says it cannot start the miniport because the registry entry is missing or invalid or something. And I can't delete it. And I couldn't reinstall it via hardware install. I have also bought a very cheap china endoscope and got the same problem. The problem seams to be related to USB compability.

Maybee it is so easy as a bad USB Contact. Below are the tests I made: 1. Tested it on my desktop: Computer did not recognice device 2.

Tested on my laptop: Worked perfectly 3. Tested on an separate powered USB hub connected to the backside of my desktop (The same as in 1).

Worked perfectly 4. Tested again direct to the front of my desktop: Computer did not recognice device 5. Tested with lower LED intensity (Less Power consumption) on front of my desktop: Computer did not recognice device 6. Connected it to the same front USB Connection on my desktop, but through an USB voltmeter (look at it as an extension Cable, with a voltmeter on it): WORKED PERFECTLY!!!!! Maybe a solution here, better late than never.

Bought one of these Android/PC endoscopes – just arrived today with instructions that are useless for downloading a rar file from kkmoon but it no longer exists. Found this after a bit of searching From – Vimicro Camera Drivers Download Center from this page:- to this file at the bottom of the list of 9 Windows drivers (+ an uninstaller). ZS0211 ZS0211_Setup_WHQL_01215 Win 2000 Win XP 32/64 Win Vista 32/64 Tried the first few then went to the last on the list, the newest driver 2008 12 15. Works on my old XP notebook. Also lists 8 Mac camera drivers (Mac OS X 10.4 or later Mac G4 / G5 QuickTime 6. Vw T5 Transporter Bedienungsanleitung Pdf Writer on this page. 0 or later).