SDR Sharp: Difference between revisions

From Yggenyk
Jump to navigation Jump to search
(Created page with "* [http://www.rtl-sdr.com/sdrsharp-plugins/ LIST OF SDRSHARP PLUGINS] RTL-SDR.COM * [http://www.sdrsharpplugins.com/ SDR# Plugins] The home of some of the most popular free pl...")
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Android}}
<google>ENGELSK</google>
RTL2832U
* [http://www.codeproject.com/Articles/822703/Features-of-DVB-T-application-development-using-Cs Features of DVB-T2 application development using C# and DirectShow.NET library]
====Windows====
* [http://www.rtl-sdr.com/sdrsharp-plugins/ LIST OF SDRSHARP PLUGINS] RTL-SDR.COM
* [http://www.rtl-sdr.com/sdrsharp-plugins/ LIST OF SDRSHARP PLUGINS] RTL-SDR.COM
* [http://www.sdrsharpplugins.com/ SDR# Plugins] The home of some of the most popular free plugins for SDR# Software Defined Radio.
* [http://www.sdrsharpplugins.com/ SDR# Plugins] The home of some of the most popular free plugins for SDR# Software Defined Radio.
====Android====
* [https://play.google.com/store/apps/details?id=com.wilsonae.android.usbserial&hl=en ADS-B on USB SDR RTL]
====Removing libwdi drivers====
Like many of other folks, I've used the libwdi package with a "Zadig" tool for manipulating the drivers.
So, if  you are trying to remove libwdi installed USB drivers (libusbK, libusb-win32, winusb) with zadig, and it returns error you can try the pnputil.exe tool. It's included with windows.
It's easy to achieve what you want with:
1. List all 3rd party inf packages by:<br>
> pnputil.exe -e > somefile.txt
2. Then look for "libwdi" string in somefile.txt
Example:
Published name :            oem134.inf<br>
Driver package provider :  libusbx.org<br>
Class :                    Urządzenia uniwersalnej magistrali szeregowej<br>
Driver date and version :  06/02/2012 6.1.7600.16385<br>
Signer name :              USB\VID_046D&PID_C019 (libwdi autogenerated)<br>
Now all you need is the command below for reach entry found:<br>
> pnptuil.exe -d oem134.inf<br>
PS. Make sure the devices using the drivers above are not connected and that you running commands with admin priveleges assigned. (command prompt in admin mode).

Latest revision as of 12:59, 7 December 2016

<google>ENGELSK</google>

RTL2832U



Windows

Android


Removing libwdi drivers

Like many of other folks, I've used the libwdi package with a "Zadig" tool for manipulating the drivers.

So, if you are trying to remove libwdi installed USB drivers (libusbK, libusb-win32, winusb) with zadig, and it returns error you can try the pnputil.exe tool. It's included with windows.

It's easy to achieve what you want with:


1. List all 3rd party inf packages by:
> pnputil.exe -e > somefile.txt


2. Then look for "libwdi" string in somefile.txt Example:

Published name : oem134.inf
Driver package provider : libusbx.org
Class : Urządzenia uniwersalnej magistrali szeregowej
Driver date and version : 06/02/2012 6.1.7600.16385
Signer name : USB\VID_046D&PID_C019 (libwdi autogenerated)

Now all you need is the command below for reach entry found:
> pnptuil.exe -d oem134.inf

PS. Make sure the devices using the drivers above are not connected and that you running commands with admin priveleges assigned. (command prompt in admin mode).

id=siteTree