libwdi
uMTP-Responder
libwdi | uMTP-Responder | |
---|---|---|
7 | 2 | |
1,737 | 175 | |
- | 4.0% | |
0.0 | 7.0 | |
2 months ago | 7 days ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libwdi
-
Porting USB applications to the web. Part 1: libusb
They probably use WCID, which is a mechanism for devices to tell Windows that they are compatible with the generic WinUSB driver. Zadig is useful for older versions of windows, non-WCID devices, and when you want to override that auto-specified driver.
Here's more information from the author of Zadig: https://github.com/pbatard/libwdi/wiki/WCID-Devices
-
I need help with my saber files uploading to my saber
If you do that'll bring you here where you'll find everything you ever wanted to know about WCID.
- SDR Software for Windows Surface RT for ARM 32 bit
- Can’t get avrdude to work
-
Bluetooth Passthrough: Easier libusbK driver swapping with a config file and batch script.
Using this config files from zadig's github page, it (in my case) got all the correct settings from the start and all I need to do is click replace driver. Place the zadig.ini files in the same directory as your zadig.exe. You might have to choose the correct device.
-
Convert old USB1.0 bulk to serial.
USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.
uMTP-Responder
-
DeckMTP, a decky plugin for transfering files via USB
You might also notice that there's no SD card mount in the config. That's because it's added during runtime, since uMTP-Responder supports it. They show example usage on their github, and I show example usage of that in my start script, where it detects the SD card. The runtime way is temporary, though, and it disappears when it restarts.
What are some alternatives?
uhubctl - uhubctl - USB hub per-port power control
DeckMTP - A DeckyLoader plugin for enabling MTP transfer over USB
UsbDk - Usb Drivers Development Kit for Windows
transfer - An MTP-based variable transfer program for the TI-84+ CE and TI-83 Premium CE calculators.
libusb - A cross-platform library to access USB devices
KD100 - A Linux driver for the Huion KD100 Mini Keydial written in C
SDRPlusPlus - Cross-Platform SDR Software
riscv_em - Simple risc-v emulator, able to run linux, written in C.
PS5-Camera-Firmware-Loader - A cross-platform utility for loading custom firmware onto the PlayStation 5 camera, written in Rust
tinyusb - An open source cross-platform USB stack for embedded system
OctoPrint-FirmwareUpdater - OctoPrint plugin for flashing pre-compiled firmware images to a 3D printer.
hidapi - A Simple cross-platform library for communicating with HID devices