Activity for libusb-win32
-
libusb-win32 updated /Readme.txt
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Xiaofan Chen modified ticket #16
allow zero length control transfer (without buffer)
-
Thanks. We no longer use Sourceforge for development. Please use github instead. Thanks. Ref: https://github.com/mcuee/libusb-win32/issues/21
-
Tormod Volden created ticket #16
allow zero length control transfer (without buffer)
-
Exposing usb overlapped event
-
Distinguishing between SEM_TIMEOUT and OPERATION_ABORTED
-
usb_free_async should check CloseHandle return value
-
libusb_dyn.c is missing stubs for several of the libusb-win32 functions
-
Uninstall doesn't remove filter driver
-
Installer exit status
-
-
-
-
-
-
-
-
-
-
-
You can also submit tickets through github. https://github.com/mcuee/libusb-win32
-
You can also submit tickets through github. https://github.com/mcuee/libusb-win32
-
Please use mailing list to discuss further libusb-win32 issues. And the installer is no longer supported. You can use Zadig or the installer from libusbk.
-
Please use mailing list to discuss further libusb-win32 issues. And this libusb-win32-devel-filter-1.2.6.0.exe is no longer supported. You can use Zadig or the one from libusbk.
-
Stanislav Tomas modified ticket #87
Installer exit status
-
Installer exit status
-
Erik created ticket #86
Uninstall doesn't remove filter driver
-
Peter Dons Tychsen modified ticket #85
Windows 10 incompatibility for libusb-win32 1.2.6.0 binary with Code integrity checks
-
FIXED
-
Windows 10 incompatibility for libusb-win32 1.2.6.0 binary with Code integrity checks
-
Hi Karthiga, No problem. Great to hear that it helped. This also makes the driver more secure, as all memory is NX now. Thanks, /pedro
-
karthiga posted a comment on ticket #85
I encounter some issue to sign with our certificat. Once i success to test this driver, i will let you know about the result. Thanks again.
-
Hi Peter, I finally successed to sign with EV certificate and the device works properly with verifier activated with code integrity checks and is recognized as complaint with windows 10 HCVI mode by the Device Guard and Credential Guard hardware readiness tool . Thanks again for your great work and prompt release ! Karthiga.
-
Your welcome. Make sure you post the result of your testing. Also, if it does not work please post your minidump, and not a screendump of it. Thanks, /pedro
-
Windows 10 incompatibility for libusb-win32 1.2.6.0 binary with Code integrity checks
-
Thank you so much for your prompt support and this new release.
-
-
I put the snaphot release here: https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20190918/ You will need to sign it afterwards, but guess you are already doing that. Please report if this works or not.
-
-
-
-
-
Hi This is fixed in git: https://github.com/mcuee/libusb-win32/commit/9afd01fc136f1f91d94a194889886b9ebb47be1c Thanks, /pedro
-
Windows 10 incompatibility for libusb-win32 1.2.6.0 binary with Code integrity checks
-
Help required on LibusbK throughput measurement
-
Clost this for now. Please use libusb-win32 mailing list for further discussions.
-
BTW, please do not use Sourcefore for futher support requests. Please subscribe to libusb-win32 mailing list for futher discussions. Thanks.
-
You do not install libusb as a full driver. You need to install the base package (libusb installer or libusbk installer) to install libusb0.sys into the system. You are not install libusb0.sys as any device's driver yet (device driver or filter driver) by doing that. It is the same for other filter driver like usbdk. By installing the filter driver, it is just modifying the registry to add to the driver stack.
-
Tyler Bell posted a comment on ticket #84
Hmm... alright, but that seems like a fairly large gap in logic: install libusb as a full driver before you can use it as a filter driver. Presumably, the choice to use filter driver mode is because you want to augment an already functioning, non-libusb device(also presumably, microsoft doesn't install libusb for you...) In this case you don't want to install libusb as a full driver which is the requirement? What's the recommended workflow on a customers system?
-
BTW, Stmk_Write and Stmk_Read are just convinent functions to wrap around the overlapped I/O for libusbK. You may try the overlapped I/O (async API) to see if that helps. http://libusbk.sourceforge.net/UsbK3/group__ovlk.html On the other hand, I think you are not using the Stmk_Write and Stmk_Read efficiently. But I am not so familiar with libusbK API functions myself. That is why I think it is better to use libusb-win32 mailing list for support. In reality, libusbK is a seperate project from libusb-win32...
-
To Kris: I agree with Peter. You can try libusb-1.0 WinUSB with the async API to see if that helps.
-
To Kris: libusb-win32 mailing list is the right place to go for technical support since it goes to more people and more people will benefit from the discussion. You need to subscribe to the mailing list in order to post. https://sourceforge.net/projects/libusb-win32/lists/libusb-win32-devel
-
You could e.g. try using libusb-win32 with libusb0 and you could try libusb-1.0 with WinUSB.
-
Hi K, I am not saying you need to switch driver. However, it is always a good idea to try various versions of the libs and drivers to figure out if it is the device or the library that is causing problems.
-
Is here a data size limitataion when reading data in bulk mode
-
Closing old entry. No more using this place for technical support. Please use libusb-win32 mailing list for future discussions.
-
Buld read operation failed on win7 OS
-
Closing old entry. No more using this place for technical support. Please use libusb-win32 mailing list for future discussions.
