libusb-win32-devel

[Libusb-win32-devel] Query regarding Libusb dll usage

[Manish R. <ram...@gm...>]

Hello Libusb Team,

 Needed information regarding the usage of Libusb in my application.

We are using the below versions:

        LibUsbDotNet dll version: 2.2.29

        USB Driver version: 1.2.6.0

Could you please let us know if there is any restriction on the
distribution of these libraries along with my application?
Best Regards,
Manish Ram

[Libusb-win32-devel] libusbdotnet reviewers and contributors welcome

[Xiaofan C. <xia...@gm...>]

I am not so sure if there are many libusbdotnet users here. In case you
are interested, you may want to take a look at the PR here.which
is one of the main missing features of the master branch (async
transfer support).
https://github.com/LibUsbDotNet/LibUsbDotNet/pull/193

There are other missing features like the Device Notification.
https://github.com/LibUsbDotNet/LibUsbDotNet/issues/32

There are also some issues not yet sorted out, for both the master
branch (v3) and v2 branch.
https://github.com/LibUsbDotNet/LibUsbDotNet/issues

-- 
Xiaofan

[Libusb-win32-devel] Fwd: libwdi supports for Windows on ARM64

[Xiaofan C. <xia...@gm...>]

It is great that Pete has got libwdi/Zadig working under Windows on ARM64.
https://github.com/pbatard/libwdi/issues/155#issuecomment-1445231926

This should help you running libusb API based applications on
Windows on ARM64,

Please take note libusbK.sys will not be modified to support ARM64.

However, you may want to try libusbK based application (x86_64)
under Windows on ARM64 to see if that works or not.

Or you can also try the libusbK Windows ARM64 testing binary
(no libusbK.sys( to see if that works or not.
https://github.com/mcuee/libusbk/issues/40#issuecomment-1421815330

--
Xiaofan

[Libusb-win32-devel] libusb-win32 future versions will not support Windows 7

[Xiaofan C. <xia...@gm...>]

Please take note libusb-1.2.7.3 release will be the last version to
support Windows 7.
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.7.3/
https://github.com/mcuee/libusb-win32/releases/tag/snapshot_1.2.7.3

The reason is due to the change of Microsoft driver signing policy.
https://github.com/mcuee/libusb-win32/issues/26

-- 
Xiaofan

Re: [Libusb-win32-devel] Issues Connecting Device

[PriestMarmore <ped...@gm...>]

Damn, I can't believe this, I'm such a fool. I done this at the beginning
but I think I've done it on another device that had a yellow triangle
showing up. It worked. Thanks!!

On Fri, Jan 6, 2023 at 1:11 AM Xiaofan Chen <xia...@gm...> wrote:

> You may want to follow the process here.
> 1) Right-click the Windows Start button and click Device Manager.
> 2) In the tree view, right-click the device and click Uninstall device.
> 3) A dialog named Uninstall Device will pop up. If present, check the
> box Attempt to remove the driver for this device. Click Uninstall to
> continue un-installing this driver.
> 4) Unplug your USB device from your computer, and plug it back in for
> re-installation.
>
> Best regards,
> Xiaofan
>
> On Fri, Jan 6, 2023 at 8:51 AM PriestMarmore <ped...@gm...>
> wrote:
> >
> >  I have an external HDD that doesn't connect to my desktop when I boot
> on Windows but connects to my laptop on windows and both my laptop and
> desktop on Ubuntu. I tried to change the partition type, format the disk,
> format windows and my BIOS. I can't connect my hdd still.
> >  When I connect to the PC the desktop acknowledges the disk with a sound
> but it doesn't show up anywhere else except on "Device Manager" as
> "External USB 3.0" under the category "libusbK Usb Devices". I search
> online and this is where I came. I tried to download the program but
> nothing although I don't even know if I downloaded the correct version.
> >  This might be totally off-topic but I went to the Windows forums and
> several subreddits and no one knows how to help me out and I'm running out
> of ideas (unless it has to do with some "obscure" option on the BIOS)
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Issues Connecting Device

[Xiaofan C. <xia...@gm...>]

Or you can follow the more detailed guide here.
https://github.com/pbatard/libwdi/wiki/FAQ#Help_Zadig_replaced_the_driver_for_the_wrong_device_How_do_I_restore_it

On Fri, Jan 6, 2023 at 9:10 AM Xiaofan Chen <xia...@gm...> wrote:
>
> You may want to follow the process here.
> 1) Right-click the Windows Start button and click Device Manager.
> 2) In the tree view, right-click the device and click Uninstall device.
> 3) A dialog named Uninstall Device will pop up. If present, check the
> box Attempt to remove the driver for this device. Click Uninstall to
> continue un-installing this driver.
> 4) Unplug your USB device from your computer, and plug it back in for
> re-installation.
>
> Best regards,
> Xiaofan
>
> On Fri, Jan 6, 2023 at 8:51 AM PriestMarmore <ped...@gm...> wrote:
> >
> >  I have an external HDD that doesn't connect to my desktop when I boot on Windows but connects to my laptop on windows and both my laptop and desktop on Ubuntu. I tried to change the partition type, format the disk, format windows and my BIOS. I can't connect my hdd still.
> >  When I connect to the PC the desktop acknowledges the disk with a sound but it doesn't show up anywhere else except on "Device Manager" as "External USB 3.0" under the category "libusbK Usb Devices". I search online and this is where I came. I tried to download the program but nothing although I don't even know if I downloaded the correct version.
> >  This might be totally off-topic but I went to the Windows forums and several subreddits and no one knows how to help me out and I'm running out of ideas (unless it has to do with some "obscure" option on the BIOS)

Re: [Libusb-win32-devel] Issues Connecting Device

[Xiaofan C. <xia...@gm...>]

You may want to follow the process here.
1) Right-click the Windows Start button and click Device Manager.
2) In the tree view, right-click the device and click Uninstall device.
3) A dialog named Uninstall Device will pop up. If present, check the
box Attempt to remove the driver for this device. Click Uninstall to
continue un-installing this driver.
4) Unplug your USB device from your computer, and plug it back in for
re-installation.

Best regards,
Xiaofan

On Fri, Jan 6, 2023 at 8:51 AM PriestMarmore <ped...@gm...> wrote:
>
>  I have an external HDD that doesn't connect to my desktop when I boot on Windows but connects to my laptop on windows and both my laptop and desktop on Ubuntu. I tried to change the partition type, format the disk, format windows and my BIOS. I can't connect my hdd still.
>  When I connect to the PC the desktop acknowledges the disk with a sound but it doesn't show up anywhere else except on "Device Manager" as "External USB 3.0" under the category "libusbK Usb Devices". I search online and this is where I came. I tried to download the program but nothing although I don't even know if I downloaded the correct version.
>  This might be totally off-topic but I went to the Windows forums and several subreddits and no one knows how to help me out and I'm running out of ideas (unless it has to do with some "obscure" option on the BIOS)

[Libusb-win32-devel] Issues Connecting Device

[PriestMarmore <ped...@gm...>]

 I have an external HDD that doesn't connect to my desktop when I boot on
Windows but connects to my laptop on windows and both my laptop and desktop
on Ubuntu. I tried to change the partition type, format the disk, format
windows and my BIOS. I can't connect my hdd still.
 When I connect to the PC the desktop acknowledges the disk with a sound
but it doesn't show up anywhere else except on "Device Manager" as
"External USB 3.0" under the category "libusbK Usb Devices". I search
online and this is where I came. I tried to download the program but
nothing although I don't even know if I downloaded the correct version.
 This might be totally off-topic but I went to the Windows forums and
several subreddits and no one knows how to help me out and I'm running out
of ideas (unless it has to do with some "obscure" option on the BIOS)

Re: [Libusb-win32-devel] Related to libusbk driver (On Windows 10 Arm64)

[Stefan B. <Ste...@ma...>]

I guess you will need an ARM version of the libusbK binaries, which to my best knowledge don’t exist. Have a look here: https://github.com/pbatard/libwdi/issues/155 and https://github.com/mcuee/libusbk/issues/35

Regards,

Stefan

From: Rinkesh Patel via Libusb-win32-devel <lib...@li...>
Sent: Monday, June 27, 2022 9:32 PM
To: lib...@li...
Cc: Rinkesh Patel <rin...@ta...>
Subject: Re: [Libusb-win32-devel] Related to libusbk driver (On Windows 10 Arm64)


You don't often get email from lib...@li...<mailto:lib...@li...>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

May be you need to used Signed driver..or turn the Sign Driver feature Off on windows 10


Thanks and Regards,

Rinkesh Patel

Senior Specialist l Healthcare & Life Sciences
Cell: +1 (571) 635-9590
TATA ELXSI
www.tataelxsi.com<http://www.tataelxsi.com>

________________________________
From: Sourabh Jadhav <jad...@gm...<mailto:jad...@gm...>>
Sent: Friday, June 24, 2022 2:24 AM
To: lib...@li...<mailto:lib...@li...> <lib...@li...<mailto:lib...@li...>>
Subject: Re: [Libusb-win32-devel] Related to libusbk driver (On Windows 10 Arm64)


You don't often get email from jad...@gm...<mailto:jad...@gm...>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

________________________________
**This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________


Hello sir/ma'am,
                               I am sourabh, Actually I am using windows 10 Arm version on my Raspberry Pi 4, I am trying to Install libusbk driver but it give me the error message:: Driver Installation:FAILED (Attempted to use 32 bit installer on a 64 bit machine).

My system is 64 bit system.

Please tell me what I am doing wrong in this.
Thank you.

________________________________
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
________________________________



[https://www.matrix-vision.com/files/mv11/MATRIX_VISION_Balluff.gif]

MATRIX VISION GmbH · Talstraße 16 · 71570 Oppenweiler · Germany
Phone +49 7191 9432-422 · Fax +49 7191 9432 288 · ste...@ma...<mailto:ste...@ma...> · www.matrix-vision.com<https://www.matrix-vision.com>

[Facebook]<https://www.facebook.com/matrix.vision.gmbh>  [Xing] <https://www.xing.com/companies/matrixvisiongmbh>   [LinkedIn] <https://de.linkedin.com/company/matrix-vision-gmbh>   [Youtube] <https://www.youtube.com/c/MATRIXVISIONGmbH>   [Presse] <https://www.matrix-vision.com/presse.html>


Place of incorporation/Sitz der Gesellschaft: Oppenweiler, Germany · Register court/Registergericht: Amtsgericht Stuttgart, Germany
Trade register/Handelsregister: HRB 271090 · Managing director/Geschäftsführer: Florian Hermle
VAT ID/USt-ID: DE811 492 081

Re: [Libusb-win32-devel] Related to libusbk driver (On Windows 10 Arm64)

[Rinkesh P. <rin...@ta...>]

May be you need to used Signed driver..or turn the Sign Driver feature Off on windows 10


Thanks and Regards,

Rinkesh Patel

Senior Specialist l Healthcare & Life Sciences

Cell: +1 (571) 635-9590
TATA ELXSI
www.tataelxsi.com<http://www.tataelxsi.com>


________________________________
From: Sourabh Jadhav <jad...@gm...>
Sent: Friday, June 24, 2022 2:24 AM
To: lib...@li... <lib...@li...>
Subject: Re: [Libusb-win32-devel] Related to libusbk driver (On Windows 10 Arm64)

You don't often get email from jad...@gm.... Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
________________________________
**This is an external email. Please check the sender’s full email address (not just the sender name) and exercise caution before you respond or click any embedded link/attachment.**
________________________________


Hello sir/ma'am,
                               I am sourabh, Actually I am using windows 10 Arm version on my Raspberry Pi 4, I am trying to Install libusbk driver but it give me the error message:: Driver Installation:FAILED (Attempted to use 32 bit installer on a 64 bit machine).

My system is 64 bit system.

Please tell me what I am doing wrong in this.
Thank you.

________________________________
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
________________________________

Re: [Libusb-win32-devel] Related to libusbk driver (On Windows 10 Arm64)

[Sourabh J. <jad...@gm...>]

Hello sir/ma'am,
>                                I am sourabh, Actually I am using windows
> 10 Arm version on my Raspberry Pi 4, I am trying to Install libusbk driver
> but it give me the error message:: Driver Installation:FAILED (Attempted to
> use 32 bit installer on a 64 bit machine).
>
> My system is 64 bit system.
>
> Please tell me what I am doing wrong in this.
> Thank you.
>
>

Re: [Libusb-win32-devel] Regarding Libusb support

[Xiaofan C. <xia...@gm...>]

That is interesting to know. Can you post the error message? You
can try to set USB_DEBUG=255 to see if you get some debug
messages from libusb0.dll.

You may want to update libusbdotnet first to see if that helps.You can build
the dll using the latest v2 branch of libusbdotnet (not the main branch which
is not that mature).
https://github.com/LibUsbDotNet/LibUsbDotNet/tree/v2

Or you can use my unofficial build here.
https://github.com/mcuee/LibUsbDotNet/releases

If that does not help, you can try to update libusb-win32 to the latest
1.2.7.3 version. It fixed a few issues of libusb 1.2.6.0 version.

Best regards,
Xiaofan

On Thu, Jun 2, 2022 at 9:35 PM Manish Ram <ram...@gm...> wrote:
>
> Hello Libusb Team,
>
> I am using Libusb for my application. Below are the version details:
>
> LibUsbDotNet dll version: 2.2.8
> USB Driver version: 1.2.6.0
>
> It was working fine till date but now after the windows update on my PC, the application stopped communicating to my usb device.
>
> It seems now we need to update the usb dll and driver.
>
> So, could you please guide us on how to get the latest dll and library which will work on windows 10 update and windows 11.
>
> Expecting quick response from you which will help me to make my application work again.
>
> Best Regards,
> Manish Ram
> Email: ram...@gm...
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] Regarding Libusb support

[Manish R. <ram...@gm...>]

Hello Libusb Team,

I am using Libusb for my application. Below are the version details:

LibUsbDotNet dll version: 2.2.8
USB Driver version: 1.2.6.0

It was working fine till date but now after the windows update on my PC,
the application stopped communicating to my usb device.

It seems now we need to update the usb dll and driver.

So, could you please guide us on how to get the latest dll and library
which will work on windows 10 update and windows 11.

Expecting quick response from you which will help me to make my application
work again.

Best Regards,
Manish Ram
Email: r <bok...@gm...>am....@gm...

[Libusb-win32-devel] Fwd: [libusb] Announcing libusb v1.0.26

[Xiaofan C. <xia...@gm...>]

FYI as well.

---------- Forwarded message ---------
From: Tormod Volden <lis...@gm...>
Date: Mon, Apr 11, 2022 at 2:08 AM
Subject: [libusb] Announcing libusb v1.0.26
To: <lib...@li...>


We are pleased to announce the final release of libusb 1.0.26.

This release comes relatively quickly after the 1.0.25 release to
mitigate regressions regarding references between transfers and device
structures that were causing applications to crash. In some cases
applications were misusing the libusb API and warnings will be
generated instead, to help such applications getting fixed. A big
thanks goes to Benjamin Berg for analyzing and fixing these issues.

Isochronous streaming now works on WinUSB again, this was an older regression.

Overall, the goals for this release were: Fix all regressions, don't
introduce new ones, build fixes and small, safe changes.

ChangeLog since previous version 1.0.25:

* Fix regression with transfer free's after closing device
* Fix regression with destroyed context if API is misused
* Workaround for applications using missing default context
* Fix hotplug enumeration regression
* Fix Windows isochronous transfer regression since 1.0.24
* Fix macOS exit crash in some multi-context cases
* Build fixes for various platforms and configurations
* Fix Windows HID multi-interface product string retrieval
* Update isochronous OUT packet actual lengths on Windows
* Add interface bound checking for broken devices
* Add umockdev tests on Linux

The 1.0.26 release was made possible by the contributions from a dozen
patch submitters (see below git shortlog) plus everyone who
contributed with issue reporting, discussions and testing.

The source code tarball can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.26/libusb-1.0.26.tar.bz2

An archive of Windows/macOS binaries can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.26/libusb-1.0.26-binaries.7z

Note that the release tarball includes a configure script so unlike a
git checkout it is not necessary to bootstrap with autoconf.

To attract developer attention, feedback and testing I would also like
to take the opportunity to mention a few of the WIP features for
future releases (GitHub ticket numbers in parentheses):
Proper Android support (874), WebAssembly+WebUSB support (1057),
Windows composite functions (965), WinUSB RAWIO support (1069).

On behalf of the libusb development community,
Tormod

--


Andrew Goodney (1):
      darwin: Use usbi_get_monotonic_time() wrapper

Benjamin Berg (7):
      core: Unset device ctx if it has been destroyed
      io: Track device in usbi_transfer
      core: Suppress hotplug events during initial enumeration
      tests: Add some umockdev based tests
      Add container build for umockdev
      core: Install first context as implicit default (and warn about its use)
      darwin: Fix crash in log handler when stopping event thread

Fabrice Fontaine (1):
      configure.ac: link with -latomic if needed

Keith Ahluwalia (1):
      windows: Fix WinUSB isochronous transfer regression

Martin Ling (1):
      darwin: Document OS-specific behaviour of libusb_cancel_transfer

Mathias Hjärtström (1):
      windows: Fix product string retrieval on HID composite devices

Ryan Hileman (1):
      Add interface bounds checks in darwin and windows endpoint functions

Seneral (1):
      windows: Correct isochronous frame calculation for full-speed devices

Shawn Hoffman (1):
      windows: Silence zero-sized array warning in libusb.h for msvc

Tormod Volden (14):
      windows: Link gcc helpers statically on MinGW
      darwin: Avoid possibly undefined version macro in configure.ac
      darwin: Avoid cast warnings in time calculation
      windows: Add Windows 11 to list of defined releases
      windows: Discern Windows 11 (if manifest allows)
      windows: Add "or later" to debug print of Windows version 8
      appveyor: Retain MinGW and cygwin build artifacts
      darwin: Always use GetPipePropertiesV3 when available
      darwin: Fix Makefile build on macOS 10.11 and older
      libusb 1.0.26-rc1
      CI: Add MinGW build on MSYS2 (Windows)
      windows: Fix type mismatch in winusbx_copy_transfer_data
      windows: Update isochronous OUT packet actual length
      libusb 1.0.26

Yegor Yefremov (2):
      linux_usbfs: Fix maybe-uninitialized error with -O3
      android: Fix typo and syntax in comments

osy (1):
      darwin: Reset by re-enumerate on non-macOS platforms

[Libusb-win32-devel] Fwd: [libusb] Announcing libusb v1.0.25

[Xiaofan C. <xia...@gm...>]

FYI as well.

---------- Forwarded message ---------
From: Tormod Volden <lis...@gm...>
Date: Tue, Feb 1, 2022 at 4:44 AM
Subject: [libusb] Announcing libusb v1.0.25
To: <lib...@li...>


Dear libusb community,

We are happy to announce the libusb 1.0.25 release!

>From the ChangeLog:
* Linux: Fix regression with some particular devices
* Linux: Fix regression with libusb_handle_events_timeout_completed()
* Linux: Fix regression with cpu usage in libusb_bulk_transfer
* Darwin (macOS): Add support for detaching kernel drivers with authorization.
* Darwin (macOS): Do not drop partial data on timeout.
* Darwin (macOS): Silence pipe error in set_interface_alt_setting().
* Windows: Fix HID backend missing byte
* Windows: Fix segfault with libusbk driver
* Windows: Fix regression when using libusb0 driver
* Windows: Support LIBUSB_TRANSFER_ADD_ZERO_PACKET on winusb
* New NO_DEVICE_DISCOVERY option replaces WEAK_AUTHORITY option
* Various other bug fixes and improvements

The 1.0.25 release is thanks to the work of more than 30 contributors,
see below git shortlog. A big thanks also goes to everyone who
reported issues, discussed solutions and performed testing.

The source code tarball can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.25/libusb-1.0.25.tar.bz2

An archive of Windows binaries can be downloaded here:
https://github.com/libusb/libusb/releases/download/v1.0.25/libusb-1.0.25.7z

On behalf of the libusb development team,
Tormod

Re: [Libusb-win32-devel] libusbk-inf-wizard and Zadig under Windows 11

[Xiaofan C. <xia...@gm...>]

On Wed, Sep 15, 2021 at 5:33 PM Xiaofan Chen <xia...@gm...> wrote:
>
> Just wondering if anyone here has tested Zadig or libusbk-inf-wizard
> under the upcoming Windows 11.
>
> As per Pete (author of libwdi/Zadig), Zadig does not work
> now. libusbk-inf-wizard will be in the same boat as it
> uses libwdi as well.
>
> Ref: https://community.osr.com/discussion/293115/windows-11-and-alternative-driver-installation-method-in-libwdi
>

Just an update so that people will not be confused in the future.

At that time WIndows was not yet officially released.
libusbk-inf-wizard and Zadig
works under Windows 11 release version.

For people running the insider version of Windows 11,
libusbk-inf-wizard and Zadig may
not work.

Ref: https://github.com/pbatard/libwdi/issues/155



-- 
Xiaofan

[Libusb-win32-devel] Survey: Windows OS version used with libusb-win32

[Xiaofan C. <xia...@gm...>]

We actually support Windows 2000 onwards in the last release version
of libusb0.sys
1.2.6.0 version. The git repo has removed Windows 2000 support.
https://github.com/mcuee/libusb-win32/commit/7c907628ec6bb3758d43ff691e19d7ca7410102e

However, we have a new issue with regard to next release, digital signature
for the libusb0.sys.

Discussion here:
https://github.com/mcuee/libusb-win32/issues/24

It seems to me that at most we can support Windows 7 onwards from now on.
Users of Windows XP and Windows Vista will have to use libusb-win32
1.2.6.0 release.

Anyone still using Windows XP or Windows Vista? Have you tried the
snapshot release 1.2.7.3 here?
https://github.com/mcuee/libusb-win32/releases/tag/snapshot_1.2.7.3

For Windows Vista 32 bit, most likely it will work with the special
build of Zadig.
For Windows Vista 64 bit, it may or may not work with the special
build of Zadig.

For Windows XP 32bit, it may well work as well, please use old version
of Zadig 2.2
version to install libusb0.sys 1.2.6.0, then use the libusb-win32
1.2.7.3 snapshot release
installer (libusb-win32-devel-filter-1.2.7.3.exe) to upgrade libusb0.sys and
libusb0.dll to 1.2.7.3 version.

For Windows XP 64 bit, you can try the same step as Windows XP 32 bit to
see if that works or not.

It will be greatly appreciated that you can report your success or failure here.
https://github.com/mcuee/libusb-win32/issues/24

-- 
Xiaofan

[Libusb-win32-devel] libusb-1.2.7.3 snapshot release signed with digital signature

[Xiaofan C. <xia...@gm...>]

Thanks to the great work of Peter Dons Tychsen (current libusb-win32 developer).
He has released libusb-win32 snapshot release  2021113 (version 1.2.7.3). He
has also signed the libusb0.sys file with the valid digital certificate.

Download link:
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20211113/

inf-wizard has been removed. You can use the Zadig_2.7 version I built
from libwdi 1.4.1 release here which includes libusb0.sys 1.2.7.3 support.
https://sourceforge.net/projects/libusb-win32/files/Zadig_libwdi/

Mirror in github:
https://github.com/mcuee/libusb-win32/releases/tag/snapshot_1.2.7.3

The snapshot release should work under Windows 8/8.1/10/11. We
hope it works for Windows 7 as well but please test and let us know the
result. I believe it may not work under Windows XP or Vista.

You can report the success or failure here. Thanks.
https://github.com/mcuee/libusb-win32/issues/24

-- 
Xiaofan

Re: [Libusb-win32-devel] libusb-1.2.7.2 snapshot release signed with digital signature

[Xiaofan C. <xia...@gm...>]

New Zadig 2.7 build with libusb0.sys 1.2.7.2 snapshot release.
https://github.com/mcuee/libwdi/releases/tag/v1.4.1

I built Zadig 2.7 from libwdi 1.4.1 release source codes with VS2019 and tested
it with Windows 10 and 11.

I am not so sure if it works under Windows 7/8/8.1. It will not work
under Windows XP.
Unlikely it will work under Windows Vista either. Please report your success
or failure. Thanks.

Best regards,
Xiaofan

Re: [Libusb-win32-devel] libusb-1.2.7.2 snapshot release signed with digital signature

[Xiaofan C. <xia...@gm...>]

Just wondering if anyone has tried to use the Zadig snapshot to
install libusb0.sys
1.2.7.2 snapshot version on different version of Windows.

I have only tested Windows 10 and Windows 11 and it works fine.

There is a report that it does not seem to work under Windows 7. If
that is the case, please report here or in github issue #24..
https://github.com/mcuee/libusb-win32/issues/24

You will need to install Windows 7 updates for SHA2.
https://support.microsoft.com/en-us/topic/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus-64d1c82d-31ee-c273-3930-69a4cde8e64f

For Windows 7 users, you may try the following as well.
1) Using Zadig 2.6 or 2.7 release to install libusb0.sys 1.2.6.0 device driver.
2) Using the libusb-win32 1.2.7.2 installer to upgrade libusb0.sys and
libusb0.dll

If you are still using Windows XP or Vista, most likely it may not work
well. But please report the success or failure as well.

I am not so sure about Windows 8 or Windows 8.1. Please report
your success or failure as well if you use Windows 8 or 8.1. I tend
to belive most of the Windows 8/8.1 users have upgraded to Windows 10.

BTW, I build the Zadig snapshot using VS2019. So you may need
VS2019 run time.

Best regards,
Xiaofan

Re: [Libusb-win32-devel] libusb-1.2.7.2 snapshot release signed with digital signature

[Xiaofan C. <xia...@gm...>]

On Mon, Oct 25, 2021 at 4:51 PM Xiaofan Chen <xia...@gm...> wrote:
>
> Thanks to the great work of Peter Dons Tychsen (current libusb-win32 developer).
> He has released libusb-win32 snapshot release  20211025 (version 1.2.7.2). He
> has also signed the libusb0.sys file with the valid digital certificate.
>
> Download link:
> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20211025/
>
> As mentioned in the wiki, inf-wizard does not work. So please use the
> Zadig snapshot here if you want to install the latest libusb0.sys for your
> device.
> Download zadig_git_99a38ae62ba0.exe from the following link.
> https://sourceforge.net/projects/libusb-win32/files/Zadig_libwdi/
>
> Reference discussion:
> https://github.com/mcuee/libusb-win32/issues/24

github mirror of the above snapshot release:
https://github.com/mcuee/libusb-win32/releases/tag/snapshot_1.2.7.2

-- 
Xiaofan

[Libusb-win32-devel] libusb-1.2.7.2 snapshot release signed with digital signature

[Xiaofan C. <xia...@gm...>]

Thanks to the great work of Peter Dons Tychsen (current libusb-win32 developer).
He has released libusb-win32 snapshot release  20211025 (version 1.2.7.2). He
has also signed the libusb0.sys file with the valid digital certificate.

Download link:
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20211025/

As mentioned in the wiki, inf-wizard does not work. So please use the
Zadig snapshot here if you want to install the latest libusb0.sys for your
device.
Download zadig_git_99a38ae62ba0.exe from the following link.
https://sourceforge.net/projects/libusb-win32/files/Zadig_libwdi/

Reference discussion:
https://github.com/mcuee/libusb-win32/issues/24

-- 
Xiaofan

Re: [Libusb-win32-devel] Is it possible to share a LibUSB-Win32 handle between applications?

[Peter D. T. <don...@td...>]

Hi Foersler,

On Sun, 2021-09-19 at 22:08 +0200, G. Foersler wrote:
> Could the problem be that the main application is 64 bit and the
> library is 32 bit? Do I need a 64 bit library? Sounds weird if the name
> is libusb-win32...

The "win32" refers to the win32 API in Windows, and has little to do
with being 32 bit or 64 bit. You must use the 32 bit version of the
library for 32 bit apps, and 64 bit version for 64 bit apps.

> I can integrate some C++ functions into the main applications that
> have access to its memory space.
> Maybe I can then share the handle.

I doubt that is going to work. Again, you cannot share handles across
applications on any sane O/S. You can share handles across threads, but
not processes. Create a pipe and send the data to/from that.

Thanks,

/pedro

Re: [Libusb-win32-devel] Is it possible to share a LibUSB-Win32 handle between applications?

[G. F. <gfo...@gm...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi,</div>

<div><br/>
&gt; Yeah, as Xianfan states, its not possible with this or any other<br/>
&gt; similar libarary. You cannot handover handles to<br/>
&gt; resources/devices/files from one application to another. That would be<br/>
&gt; a major security hole if you could. Most O/S only allow this is very<br/>
&gt; limited form.<br/>
&nbsp;</div>

<div>I can integrate some C++ functions into the main applications that have access to its memory space.</div>

<div>Maybe I can then share the handle.</div>

<div>Problem is actually that mingw refuses to build the code.</div>

<div>&nbsp;</div>

<div>The linker seems to complain about &quot;undefined reference to &#96;usb_init&#39; and all the other libusb refernces.</div>

<div>I tried to point it to the libusb.a file but it does not recognize it.</div>

<div>&nbsp;</div>

<div>Could the problem be that the main application is 64 bit and the library is 32 bit? Do I need a 64 bit library? Sounds weird if the name is libusb-win32...</div>

<div>&nbsp;</div>

<div>Sorry if I sound stupid, but regarding compilers, libraries and so I really am.</div>

<div>&nbsp;</div>

<div>&nbsp;</div></div></body></html>

Re: [Libusb-win32-devel] Is it possible to share a LibUSB-Win32 handle between applications?

[Peter D. T. <don...@td...>]

Hi all,

On Wed, 2021-09-15 at 09:55 +0800, Xiaofan Chen wrote:
> I believe this is not possible based on the current codes.
> 
> What you can try is to create the first application as a Windows
> service, and then the second application uses that Windows service.

Yeah, as Xianfan states, its not possible with this or any other
similar libarary. You cannot handover handles to
resources/devices/files from one application to another. That would be
a major security hole if you could. Most O/S only allow this is very
limited form.

You can solve it using pipes or sockets. Pipes and sockets are easy to
create. This even adds the flixibity of working across networks.

Thanks,

/pedro