Pete Batard
                                            Pete Batard
                                        
                                    Follow the steps from [here](https://github.com/pbatard/libwdi/wiki/FAQ#help-zadig-replaced-the-driver-for-the-wrong-device-how-do-i-restore-it) to restore the driver. You simply successfully replaced the camera native driver with WinUSB, which, of course, means that it can only be accessed by...
Make sure you plug it into every single USB port your camera was ever plugged, and perform the uninstallation steps again. Or you can also try "Show hidden devices" in...
I'm going to defer this issue for now as it doesn't look like there's much of an impact and I'd like to know what the actual differences are. Most of...
From what I can see, the version of `boot.asm` from which ms-sys (and therefore Rufus) derives its `br_fat16fd_0x3e.h` code is the one that existed up to SVN revision 1482, i.e....
I get you, but this creates 2 issues: 1. Everything needs to be re-tested in Rufus because possibly, the boot record may require a newer version of the kernel to...
Well, I got to chose my battles (meaning I have to choose what I spend my limited time on) and submitting a patch to ms-sys and then following up on...
I'm going to defer this issue, as this is unlikely to affect many people, so it's going to be a _"When I don't have something more important to do"_ matter....
Thanks for this PR. The one problem I have with it is that I don't think I want to apply the last patch because it references a non-official release of...
Okay, then I'll wait for the 1.4.0 release then (which I don't mind, as I'm afraid this patchset is still low priority for me, but I'll try to get through...
So what is the __official__ URL for libusb-win32 now? If it has changed, then I will have to update **all** the URLs that are referenced in libwdi and Zadig before...