I have found 1 or 2 places online that suggest that I may need to make a change or 2 to the. No one in the SDR# Yahoo group has been able to help. Win7 is not an option as I cannot afford to buy even 1 copy, and I am not sure how well it will run on my laptops.
Installing SP3 may not help, as I have read of many who cannot get WinUSB to install under WinXP Pro SP3. In my experience, installation of Windows service packs/upgrades/updates has caused massive problems in the past. I may have found a solution to the SDR# problem, but have not tried it. This is a homebuilt desktop machine with WinXP Pro SP2. On a third machine Zadig installed WinUSB, but SDR# won't run, the error being that it cannot initialize. This machine has WinXP Pro SP2 installed. I have looked into such errors and failures online to no avail so far. On a second IBM T43 laptop Zadig fails to install WINusb, with an error of invalit parameter. This machine has a fresh install of WinXP Pro SP3 (not done by me). That is Zadig installs the WinUSB driver, and SDR# runs. I have one computer (an IBM T43 laptop) that everything works on. I used to use Mcafee, but it caused many problems on my system. You just need to make sire it is enabled. All modern routers meant for home use have a built-in firewall. If you are using a router to connect to the internet you should disable the Windows firewall. I have Microsoft essentials and McAfee (free from Cox Communications) loaded on the computerr. I could not even get past the title of libdwi.
Perhaps my firewall/virus protection picked up the trojan hors and stopped the download. W9RAN, thanks for inspiring me to pursue this. My takeaway is that this is an area where being a little adventurous pays off. Incidentally, my dongle's PID and VID don't exactly match any of the products on the list of dongles known to work, and the description in Zadig was RTL2832U, not "Bulk-in, interface" as described in the guide to Windows software. I never had so much fun for such a small investment my dongle was $20 and I spent another $7 on a PAL-to-BNC adapter for the antenna. As soon as I moved the slider about halfway, I started picking up FM and weather broadcasts. Nosing around SDR#, I noticed a Configure button at the top, clicked that, and found an RF gain control turned, by default, all the way down (!?!). I used the tiny TV antenna which shipped with the dongle, but heard nothing at first, even after tuning to powerful local FM stations (using the WFM setting) and to our local NOAA weather radio station (using NFM). I plugged it in to a Gateway Netbook running XP, ran the script referred to in the article, installed the driver, and then ran SDR#. I picked up an inexpensive DVB-T dongle from Amazon ( but it is now out of stock) which was shipped directly from Shenzen, China. Turn Avira off, run Zadig, then turn it back on again. Basically, the report of a trojan in the USB installer that Zadig created is a false positive (see discussion, including results of an Avira staff test of the file, at ). I found my own solution, and thought that I would post it here in case anyone else stumbles across this thread.
Has anyone else encountered this problem and, more importantly, is there a workaround, another way to get the WinUSB driver onto my system and associated with the DVB-T device? Without the ability to install the driver for the dongle, I'm dead in the water. I'm running XP Home SP3 on a Gateway LT20 netbook with a 1.6GB Intel Atom processor.
When I ran Zadig to install the WinUSB driver, my Avira antivirus software picked up a trojan called TR/7 and would not let me proceed with the install.
As suggested both in the article and its update on QST In Depth, I downloaded a batchfile which downloaded the necessary software.
Robert Nickels article in the January QST was exciting, and inspired me to try out SDR using a DVB-T dongle acquired from Amazon.