gave a link for Version 22 Vista drivers which said will work for Windows 10 and 7/8. However, the link is dead and there appears to be no Diamond support page for this product.
Does anyone know where to get drivers for this? I've attached a couple of photos of the box, and one of the hardware.
Otherwise, I could get a Win 7 Dell PC from a local refurb chain (Action Computers in Denver) for a couple of hundred dollars, and use that Win 7 system to install the CD drivers.
Last edited by HDEditor; 01-22-2025 at 01:51 PM.
Reason: added hardware pic from Amazon
Drivers do not exist past Win7 (using Vista drivers), and do not work for current Win8/10/11 release. Windows updates nuked the drivers about 5-6 years ago.
You really need an offline system to capture video anyway. Just create the Win7 box.
Thanks. Found my old Windows 7 32-bit Ultimate DVD, so the OS problem is taken care of.
Quick question: I found a Datavideo DAC-100 at a Goodwill. What are your thoughts on putting it between the S-VHS player and the ATI TV Wonder HD 600 USB?
DAC-100 is just a lousy 1990s DV box, not much different than Canopus ADVC 50/55/100/110/300 boxes.
No TBC exists in it.
Note: Not everything DataVideo made was a TBC, or had TBC in it. In fact, most did not. Even the "also has TBC" devices are not what people think they were. The TBCs existed for the device itself, not for you externally. In some cases, that makes a huge difference, as the TBC does not function as you need, want, or think it should. "TBC" is a wide term.
With a quality S-VHS VCR with line TBC, and a quality capture card (but will still trip up on frame timing errors), you really need a proper actual TBC. Not a "sorta kinda not-really does it" device. That's the uber-budget route, and is generally paired with lower-end VCRs, though still decent capture cards. The "not really a TBC" devices actually degrade the quality of the better JVC/Panasonic VCRs, duplicate some function (but worse), and still lack any actual frame TBC. Far too many myths and misinformation now exists on the nature of gear (thanks to Youtube, and so many of the Youboobs posting there).
BTW, most ATI 600 USB cards are not being sold complete. Without all the cabling, it's an expensive paperweight. There are far too many bare sticks out there, and the cables are not something that are easily replaced. These cards (and even the clones) have become hard to find complete now, and even I'm now down to my last card in the marketplace (probably no more after it).
Sorry for bumping this thread (if it was burried because it's still pretty recent). What I'm providing is in the scope of the original thread.
Using the link provided in the OP to the MS forums, I've used Archive.org's Wayback Machine to get the last Windows 7 driver for the card (attached to the post below). I did nothing in particular and it installed fine on Windows 11 Pro. It shows up in Device Manager and can be used in OBS Studio (I know LordSmurf does not recommand using OBS but, let's be real, for most people, that's going to be the easy way out). The audio input works as well. It is not tested with Virtual Dub 1.9.x though but I would be surprised if it didn't work. If anything, it's VirtualDub itself that might not work.
I hope that it helps someone out! However, a disclaimer: you realize that doing this will not capture interlaced video or will only capture on-the-fly deinterlaced video. If that matters to you, it's better to follow LordSmurf's advice and use older hardware for capture.
The following users thank SHGMC_2 for this useful post:
HDEditor (02-25-2025),
lordsmurf (02-24-2025)
Sorry for bumping this thread (if it was burried because it's still pretty recent). What I'm providing is in the scope of the original thread.
Using the link provided in the OP to the MS forums, I've used Archive.org's Wayback Machine to get the last Windows 7 driver for the card (attached to the post below). I did nothing in particular and it installed fine on Windows 11 Pro. It shows up in Device Manager and can be used in OBS Studio (I know LordSmurf does not recommand using OBS but, let's be real, for most people, that's going to be the easy way out). The audio input works as well. It is not tested with Virtual Dub 1.9.x though but I would be surprised if it didn't work. If anything, it's VirtualDub itself that might not work.
I hope that it helps someone out! However, a disclaimer: you realize that doing this will not capture interlaced video or will only capture on-the-fly deinterlaced video. If that matters to you, it's better to follow LordSmurf's advice and use older hardware for capture.
I download this yesterday. In my first test, no change. Still unstable. More testing needed, but at very least it still has some % of unreliable results and OS/system rejection.
I got the ATI 600 USB working on Windows 11 using the Vidbox NW06/NW03 driver.
-Download from here: https://vidbox.company/driver/ Direct link: https://vidbox.company/down_files/VIDBOX_PC_Driver.zip
-Extract the folder "Driver Contents" to a location on your computer (the desktop works)
-Plug-in the 600USB
-Double click the unknown device in Device Manager, click "Update Drivers"
-Click "Browse my computer for drivers"
-Click "Let Me pick from a list of available drivers on my computer"
-Click "Have Disk" and browse to the path where you saved the driver files.
-From the list select "USB 2883 Device".
-Click "Yes" to the Update Driver warning. Despite what it says, its the correct driver, ATI just assigned a different device ID to their USB stick.
Your ATI 600 USB should appear in VirtualDub and other DirectShow capture programs as "USB 2883 Device".
Note the reason why the Diamond drivers linked in the post above don't work is that the digital signature file called "emwhql.cat" is missing. Its likely these drivers were never signed or the file went missing somehow.
-- merged --
To further add, the VidBox drivers are MUCH newer then the drivers found for the other Empia devices. These are dated 2019 and even appear to support Windows 10/11's memory integrity feature.
The following users thank NJRoadfan for this useful post:
ChrisW6ATV (12-11-2025),
lordsmurf (12-06-2025)
I was the one that accidentally found the Vidbox driver worked for my Tevion, I finally stopped fighting drivers, it just worked!
It also works in Windows 11, and the Tevion is a close cousin to the ATI600.
The following users thank BarryTheCrab for this useful post:
ChrisW6ATV (12-13-2025)
I got the ATI 600 USB working on Windows 11 using the Vidbox NW06/NW03 driver.
-Download from here: https://vidbox.company/driver/ Direct link: https://vidbox.company/down_files/VIDBOX_PC_Driver.zip
-Extract the folder "Driver Contents" to a location on your computer (the desktop works)
-Plug-in the 600USB
-Double click the unknown device in Device Manager, click "Update Drivers"
-Click "Browse my computer for drivers"
-Click "Let Me pick from a list of available drivers on my computer"
-Click "Have Disk" and browse to the path where you saved the driver files.
-From the list select "USB 2883 Device".
-Click "Yes" to the Update Driver warning. Despite what it says, its the correct driver, ATI just assigned a different device ID to their USB stick.
Your ATI 600 USB should appear in VirtualDub and other DirectShow capture programs as "USB 2883 Device".
Note the reason why the Diamond drivers linked in the post above don't work is that the digital signature file called "emwhql.cat" is missing. Its likely these drivers were never signed or the file went missing somehow.
-- merged --
To further add, the VidBox drivers are MUCH newer then the drivers found for the other Empia devices. These are dated 2019 and even appear to support Windows 10/11's memory integrity feature.
I am not having the same luck. I tried downloading the vidbox drivers as posted above but when pointing to the directory where the driver was extracted I get the message windows was unable to install your ATI TV Wonder 600. This is on Windows 11. I did not see a USB 2883 device in the list.
Ok after reading the directions and step by step multiple times I did not follow them properly and was able to install the driver. Now to play with virtualdub which i havent used in years.
I wish to report (so far) complete success with the Vidbox USB 2883 Device driver(s) with a Hauppauge HVR-950 (ATI 600 USB "clone" with the identical hardware inside), on a Windows 7 32-bit computer.
The computer has a Gigabyte GA-MA78GM-S2H motherboard with Athlon 64 X2 4200+ CPU and 2GB of dual-channel RAM. The OS is Windows 7 32-bit Media Center Edition (but with Media Center itself uninstalled in the "Windows Options" list, just for possible better stability). The hard drive is a Western Digital SATA drive with Indexing turned off (in the drive's right-click Properties window, as I do on all of my computers for stability). VirtualDub 1.9.11 "stock install" from the download file provided here by LordSmurf/admin(s) (and thank you for providing it!).
First, for some reason I could not get audio working from either of two HVR-950s I have, using the WinTV 8 driver installer from this site (dated 2010) or the driver(s) from the Hauppauge device's included disk (dated 2007). I did try the motherboard's onboard-sound line input and that worked but with wildly out-of-sync audio (as should be expected perhaps). Just to check, I also installed and tested the HVR-950 (with its included driver(s)) on a Windows XP machine I built for an AIW Radeon 7500 AGP board; the 950's sound works on that machine in VirtualDub but the machine (with a Duron 1200 CPU) is so underpowered that the capture attempts in VD quickly crashed each time, with 50% or more of "added frames" before the crashes and other instability.
On the Windows 7 machine, the Vidbox driver(s) installed just as described above, and everything "behaves" in VirtualDub (set for 720x480, HuffYUV, YUY2 4:2:2 interleved, 16/48 PCM, and line input from a Zenith ATSC tuner box). A/V sync was perfect in the one (90-second) capture I tried so far. (I am using the Zenith box first so I can get basic "good-video" capture working reliably before I go on to the analog-tape and time-base-correction functions working.)
Thank you to BarryTheCrab for finding/testing the Vidbox drivers, and to NJRoadfan for posting the details here, as well as to LordSmurf and the Digital FAQ Forum community for getting me to this point (so far). Let me know if I should post any other information or try any specific tests.
I have to do more comparison testing with other capture cards and the "native" ATI drivers on older versions of Windows, but I noticed some weird macro blocking artifacts with pinks and reds in video with the Vidbox drivers. Its almost like the video is being captured at 4:2:0 color space instead of the advertised 4:2:2 color space.
I don't have too much capture experience with the 600USB to determine if this is normal, hence why I will test with the ATI drivers in older versions of Windows to rule that out.
-- merged --
Ugh, there is something "wrong" with these drivers. See the attached examples.
Example 1: Note the artifacts around the teal and purple sections of the shirt with the VidBox drivers. The ATI 600 drivers under XP and the All-In-Wonder don't exhibit this.
Example 2: Once again note the artifacts around the lead dancer's shirt with the VidBox drivers.
Something at the driver level is messing with the chroma sub-sampling. This is the same ATI 600 USB, just with different drivers. Source VCR was a Panasonic AG-1980 and a crappy EP tape. Note that these artifacts become VERY noticeable if you deinterlace the video.
Vidbox drivers on Windows 11. I don't think they support an OS as old as Windows XP.
-- merged --
OK, I spent WAY too much time on this, but I finally found working drivers. These come from Microsoft's Windows Update Catalog and are digitally signed. eMPIA drivers from 2015 without the weird chroma bug the 2019 VidBox drivers have. The install procedure is the same. Might want to clean up this thread to reflect this.
Note: I did find a version of the 2009 drivers with the proper signing but they do not work in Windows 11. They will glitch out and drop frames.
The following users thank NJRoadfan for this useful post:
YouSaidA (01-13-2026)
Hi, I am following your notes since my Windows 7 post above, NJRoadfan. I appreciate your ongoing efforts with all of this, and I will try more tests on my Windows 7/Hauppauge machine, too, and add notes here when I get to that point. Your newest pictures from the 2015 drivers look much better.
I have to zoom in pretty good on your comparison pictures, but once I do, the chroma errors are quite obvious on the Vidbox/Windows 11 capture frames. I need to find one or more video samples here (NTSC analog stuff) to use the way you are using your VHS EP tape, so that I will have good references to see this kind of failures.
Years ago, when I first learned of what has been called "chroma bug" or "CUE (chroma upsampling error)" in the DVD-playing world, the Toy Story DVD menu screen was used to show comparable "good versus bad" performance in DVD players (or computer players/MPEG-2 codecs and similar).
Whats annoying is this adds a new wrinkle to the whole "good vs. bad" capture device. Many of them might actually give preferred capture quality, but with what driver? The best I can figure, the Vidbox drivers are somehow forcing the capture chip to output 4:2:0, since the included software is geared towards capturing directly to compressed formats.
This is of course, terrible, since the driver itself is only reporting sending 4:2:2 to the host.
The following users thank NJRoadfan for this useful post:
BarryTheCrab (12-14-2025),
ChrisW6ATV (12-14-2025)
All using W11, JVC S7800u, TBC on, no frame TBC employed. Used HuffYUV, I also tried my Vidbox NW07 with the newest driver but it just would not give a/v sync right from the first frame. I just tossed it in the trash.
Trying VDub 1.9 and 2, changing destination folder/drive, tried Lagareth, it would not comply. May fidget with that later, just a very busy time of year to chase things.
I did some digging on the various ezCAP sites. I'm putting this up mostly because its an even newer eMPIA driver then the VidBox one and doesn't have the chroma sub-sampling bug. These are from November 2019 and support Windows 10/11 memory isolation.
Barry, I think these later drivers might be buggy and be the source of the AV sync issues. Whenever I start a capture with the Vidbox driver or this 2019 ezCAP driver with the ATI 600HD, the driver appears to reset the capture hardware. This results in a tearing glitch at the start of a capture like someone flipped to the video source.
I would try the 2015 driver above and see if it solves your sync issues.
The following users thank NJRoadfan for this useful post:
BarryTheCrab (12-14-2025),
ChrisW6ATV (12-14-2025)
I did some digging on the various ezCAP sites. I'm putting this up mostly because its an even newer eMPIA driver then the VidBox one and doesn't have the chroma sub-sampling bug. These are from November 2019 and support Windows 10/11 memory isolation.
Barry, I think these later drivers might be buggy and be the source of the AV sync issues. Whenever I start a capture with the Vidbox driver or this 2019 ezCAP driver with the ATI 600HD, the driver appears to reset the capture hardware. This results in a tearing glitch at the start of a capture like someone flipped to the video source.
I would try the 2015 driver above and see if it solves your sync issues.
Looks terrible, at least for me. Why do not use well tested and accepted OS/cards/drivers?
Thank you!
In the spirit of full disclosure, that effin box produces a click-click electrical pop and it won’t stop.
Previously I’ve shutdown heat, other PCs, A/C, lamps, changed extension cords, cut the power to the neighbors and the Elks club across the street but the click-click never ceased.
Maybe the unit I have is defective, that can’t be happening to everyone. Too bad, it’s a nice form factor, handsome unit but this particular piece does not give me faith to try another.
