libusb-win32-devel

Re: [Libusb-win32-devel] Intel Bluetooth replaced with libusbk driver not responding after sleep/restart

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

On Mon, Apr 23, 2018 at 4:02 AM, Luke Lone <lon...@ho...> wrote:
> Hello,
> I am just a user, not a developer.
>
> System configuration: Lenovo Thinkpad T470 with Intel Dual Band Wireless-AC
> 8260 and Windows 10 x64.
> I'm using the libusbk drivers 3.0.7.0 to connect a Wiimote Plus to the
> Dolphin console emulator via Bluetooth.
>
> The driver is working perfectly after installation with Zadig utility, but
> it stops working after the PC restarts or sleeps. I have to uninstall and
> reinstall the driver in order to make it work again, which is quite
> annoying.
>
> What do you think may be the cause? I suspect that the libusbk driver is
> unable to reactivate the bluetooth antenna/device when it is turned off. Do
> you have any suggestion on how I could fix it? The PC has a hotkey Fn+F10
> that normally enables/disables Bluetooth. When I press it, the mouse pointer
> spins for a moment, but nothing changes.
>
> Other threads I found about similar issues suggest that the problem could be
> with the application using the driver, rather than the driver itself, but
> first I wanted to hear your opinion.
>

I think its not the fault of libusbk driver. But the application now has to use
certain command to activate the bluetooth device. For example, try to
simulate the Fn+F10 action of the Windows (which works with the
Windows Bluetooth driver) to enables/disables bluetooth. Looks like
some types of reverse engineering work is needed.

It is said many open-source application is able to emulate what the
proprietary driver/application is doing but usually the power manager
aspect is not easy because it is quite complicated under Windows.


-- 
Xiaofan

[Libusb-win32-devel] Intel Bluetooth replaced with libusbk driver not responding after sleep/restart

[Luke L. <lon...@ho...>]

Hello,
I am just a user, not a developer.

System configuration: Lenovo Thinkpad T470 with Intel Dual Band Wireless-AC 8260 and Windows 10 x64.
I'm using the libusbk drivers 3.0.7.0 to connect a Wiimote Plus to the Dolphin console emulator via Bluetooth.

The driver is working perfectly after installation with Zadig utility, but it stops working after the PC restarts or sleeps. I have to uninstall and reinstall the driver in order to make it work again, which is quite annoying.

What do you think may be the cause? I suspect that the libusbk driver is unable to reactivate the bluetooth antenna/device when it is turned off. Do you have any suggestion on how I could fix it? The PC has a hotkey Fn+F10 that normally enables/disables Bluetooth. When I press it, the mouse pointer spins for a moment, but nothing changes.

Other threads I found about similar issues suggest that the problem could be with the application using the driver, rather than the driver itself, but first I wanted to hear your opinion.

Thank you and regards,
Luke

Re: [Libusb-win32-devel] Crash in reads with short timeout - race.

[Travis <lib...@gm...>]

Greetings,

Let's check the return code.  What about this:
static int _usb_cancel_io(usb_context_t *context)
{
     int ret;
     ret = _usb_abort_ep(context->dev, context->req.endpoint.endpoint);
     if (ret == 0)
     {
         WaitForSingleObject(context->ol.hEvent, 1000);
     }
     else
     {
         WaitForSingleObject(context->ol.hEvent, 0);
     }
     return ret;
}

Use 1000 ms I think.  That should always be plenty and it will keep it 
from dead locking.

Regards,
Travis

On 4/12/2018 5:14 PM, Peter Dons Tychsen via Libusb-win32-devel wrote:
> Hi Xiaofan,
>
>> Thanks a lot for your detailed information. I will see if Travis
>> still monitors
>> this mailing list and can comment on this fix.
> It would be great if Travis (or someone else) could verify and apply
> the fix.
>
>> The good thing is that it only touches the library (DLL) part and not
>> the driver part (which requires digital signature).
> Yup. Signing is a pain. Especially for people that do not have a valid
> cert to sign with.
>
>> I think CancellIOEx() is available since Vista. But it does not
>> matter
>> if you still need XP.
> Yep, my bad. Only XP/2003 does not have it. Still cannot use it
> however, for that reason.
>
> Thanks,
>
> /pedro
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Use same INF for multiple devices (same VID / PID)?

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

Hi Rafael,

> Currently I seem to be able to install each device with the same INF
> file, but the driver is not remembered between devices, meaning every
> time I switch devices, I have to reinstall the INF file.

In Windows, there are 2 ways that USB devices are remembered:

1) Using the VID/PID if the serial number is _not_ present. In this
case you can swap between several identical devices (on the same port)
without having Windows prompt you for a new password. Device are also
remembered pr port, so Windows will query for a driver the first time
each port sees this VID/PID combination.

2) Using the serial number _if_ present (normally unique pr. device).
In this case Windows will query for a driver every time a new device is
seen. This is however remembered across ports, so moving the device
from port to port will not generate a query for a driver if it is the
same device.

You are likely stuck in scenario #2. For Vista and forward you can set
the registry key "IgnoreHWSerNum", which forces scenario #1 for that
particular device.

https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-de
vice-specific-registry-settings

You can set that key using a utility (small program in C/C#/whatever),
in your INF file, or in your USB device using "OS descriptors" (if you
have created the USB device).

https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/micros
oft-defined-usb-descriptors

You can modify the registry in INF like this:

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-f
ile-entry-values-that-modify-device-properties

Hope this helps.

Thanks,

/pedro

Re: [Libusb-win32-devel] Crash in reads with short timeout - race.

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

Hi Xiaofan,

> Thanks a lot for your detailed information. I will see if Travis
> still monitors
> this mailing list and can comment on this fix.

It would be great if Travis (or someone else) could verify and apply
the fix.

> The good thing is that it only touches the library (DLL) part and not
> the driver part (which requires digital signature).

Yup. Signing is a pain. Especially for people that do not have a valid
cert to sign with.

> I think CancellIOEx() is available since Vista. But it does not
> matter
> if you still need XP.

Yep, my bad. Only XP/2003 does not have it. Still cannot use it
however, for that reason.

Thanks,

/pedro

[Libusb-win32-devel] Use same INF for multiple devices (same VID / PID)?

[Rafael S. <rs...@be...>]

Hi,
How can I build an INF file for several instances of the same piece of
hardware?
Currently I seem to be able to install each device with the same INF file,
but the driver is not remembered between devices, meaning every time I
switch devices, I have to reinstall the INF file.

Is there a way I can make the driver a bit more generic so I don't have to
reinstall it every time I plug one of the devices in?

Note that if I use the same device and re-plug it, the driver is
remembered...

Thanks,
R

Re: [Libusb-win32-devel] Re-packing installer fails - 7zip issues?

[Rafael S. <rs...@be...>]

I'll give this a shot, thanks for the pointer though.

Should I file this somewhere?

Cheers,
R

On Mon, Apr 9, 2018 at 3:01 PM, Travis <lib...@gm...> wrote:

> Greetings,
>
> Well that's annoying.  Apparently 7zip changed their syntax a good long
> while ago.
>
> Thankfully, You can still get the one you need!  Get version 9.20.
> https://sourceforge.net/projects/sevenzip/files/7-Zip/9.20/
>
> Regards,
> Travis
>
>
> On 4/9/2018 12:43 PM, Rafael Send wrote:
>
>> Hi,
>> I'm attempting to use InfWizard to create an installer for a custom USB
>> device (this alone works fine), but I need it to be silent. To that end I'm
>> attempting to modify the dpinst.xml file with the silent option (which also
>> works on its own), but I can't repackage an installer.
>> The re-pack.cmd script always fails with a 7zip error ("-ai switch not
>> valid for this command").
>>
>> I've tried manually performing that step, but I have not been able to
>> repackage a working installer.
>>
>> Is this a known current bug?
>>
>> Cheers,
>> Rafael
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Re-packing installer fails - 7zip issues?

[Rafael S. <rs...@be...>]

Has no-one tried this function in the last 8 years and reported this bug?
Interesting...

R

On Mon, Apr 9, 2018 at 3:01 PM, Travis <lib...@gm...> wrote:

> Greetings,
>
> Well that's annoying.  Apparently 7zip changed their syntax a good long
> while ago.
>
> Thankfully, You can still get the one you need!  Get version 9.20.
> https://sourceforge.net/projects/sevenzip/files/7-Zip/9.20/
>
> Regards,
> Travis
>
>
> On 4/9/2018 12:43 PM, Rafael Send wrote:
>
>> Hi,
>> I'm attempting to use InfWizard to create an installer for a custom USB
>> device (this alone works fine), but I need it to be silent. To that end I'm
>> attempting to modify the dpinst.xml file with the silent option (which also
>> works on its own), but I can't repackage an installer.
>> The re-pack.cmd script always fails with a 7zip error ("-ai switch not
>> valid for this command").
>>
>> I've tried manually performing that step, but I have not been able to
>> repackage a working installer.
>>
>> Is this a known current bug?
>>
>> Cheers,
>> Rafael
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Re-packing installer fails - 7zip issues?

[Travis <lib...@gm...>]

Greetings,

Well that's annoying.  Apparently 7zip changed their syntax a good long 
while ago.

Thankfully, You can still get the one you need!  Get version 9.20.
https://sourceforge.net/projects/sevenzip/files/7-Zip/9.20/

Regards,
Travis

On 4/9/2018 12:43 PM, Rafael Send wrote:
> Hi,
> I'm attempting to use InfWizard to create an installer for a custom 
> USB device (this alone works fine), but I need it to be silent. To 
> that end I'm attempting to modify the dpinst.xml file with the silent 
> option (which also works on its own), but I can't repackage an installer.
> The re-pack.cmd script always fails with a 7zip error ("-ai switch not 
> valid for this command").
>
> I've tried manually performing that step, but I have not been able to 
> repackage a working installer.
>
> Is this a known current bug?
>
> Cheers,
> Rafael
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] Re-packing installer fails - 7zip issues?

[Rafael S. <rs...@be...>]

Hi,
I'm attempting to use InfWizard to create an installer for a custom USB
device (this alone works fine), but I need it to be silent. To that end I'm
attempting to modify the dpinst.xml file with the silent option (which also
works on its own), but I can't repackage an installer.
The re-pack.cmd script always fails with a 7zip error ("-ai switch not
valid for this command").

I've tried manually performing that step, but I have not been able to
repackage a working installer.

Is this a known current bug?

Cheers,
Rafael

Re: [Libusb-win32-devel] Crash in reads with short timeout - race.

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

On Mon, Apr 2, 2018 at 12:32 AM, Peter Dons Tychsen via
Libusb-win32-devel <lib...@li...> wrote:
>
> The first revision that had this was:
>
> https://github.com/mcuee/libusb-win32/commit/6eaec78aed8e34e1aaf2e835b7
> 01497d352bc3e6#diff-b5691da501465b646e19ae693a116e5e

Wow, that was in the early days of libusb-win32.

> It was later reformatted into being a part of _usb_cancel_io().
>
> However, WaitForSingleObject() is not called correctly. If you want to
> be sure that the cancel has been executed, you must call
> WaitForSingleObject() with a timeout that is large enough to ensure
> that the request is processed. In many cases on a loaded system, this
> ends tragically.
>
> A simple statement can crash, e.g.:
>
> -- snip --
>
> void test(void)
> {
>   uint8_t data[20];
>   usb_interrupt_read(handle, ep_int_in, data, 20, 1);
> }
>
> -- snip --
>
> The above code crashes in some cases, as the read is in some rare cases
> executed *after* leaving usb_interrupt_read() and test(), which then
> corrupts the local stack as "data" is not valid any more.
>
> To fix this, simply use INFINITE as timeout, as you can *not* return
> from _usb_cancel_io until the operation has been truely cancelled. It
> is also described on MSDN for WaitForSingleObject() that the only was
> to be sure is to call it with INFINITE.
>
> I have tested the fix on lots of setups, and i think the fix is OK, and
> does not seem to create other new side-effects.

Thanks a lot for your detailed information. I will see if Travis still monitors
this mailing list and can comment on this fix.

The good thing is that it only touches the library (DLL) part and not
the driver part (which requires digital signature).

> It was also partially fixable by cancelling all I/O to the driver using
> CancelIo(). However, this will cancel all I/O and will ruin other
> running endpoints (async readers and such), so that will not work.
> Newer version of windows have CancelIoEx() which can cancel a specific
> I/O operation, but this is only available in 2008/win7 and forward, and
> i need this to still run on xp/vista.

I think CancellIOEx() is available since Vista. But it does not matter
if you still need XP.


-- 
Xiaofan

[Libusb-win32-devel] Crash in reads with short timeout - race.

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

Hi libusb,

If anyone could review and eventually apply the fix below it would be
great, as i am probably not the only only getting this rare crash.

I still use the old libusb-win32 (still works great by the way) on some
of my older projects, and i have had an annoying crash bug which i
never got fixed.

I decided to use some time finding the "easter egg" that was causing
this. After lots of debugging, it turned out that there is a race in
the DLL.

When calling e.g. usb_interrupt_read() that times out it will call:

1) usb_interrupt_read
2) _usb_transfer_sync
3) usb_reap_async
4) _usb_reap_async
5) _usb_cancel_io

This is where it goes south. To cancel the I/O operation it calls:

_usb_abort_ep() to send the LIBUSB_IOCTL_ABORT_ENDPOINT to the driver
synchroniously. Even though the LIBUSB_IOCTL_ABORT_ENDPOINT is sent
synchroniously to the driver, the driver just forwards the request to
"usbd" further down the IRP chain as a "reset endpoint" request, which
has asynchrinous elements to it. So all-in-all you cannot regard the
request as cancelled when returning from _usb_abort_ep().

To fix this it was introduced that using WaitForSingleObject() would be
used to wait for the cancel to go through.

The first revision that had this was:

https://github.com/mcuee/libusb-win32/commit/6eaec78aed8e34e1aaf2e835b7
01497d352bc3e6#diff-b5691da501465b646e19ae693a116e5e

It was later reformatted into being a part of _usb_cancel_io().

However, WaitForSingleObject() is not called correctly. If you want to
be sure that the cancel has been executed, you must call
WaitForSingleObject() with a timeout that is large enough to ensure
that the request is processed. In many cases on a loaded system, this
ends tragically.

A simple statement can crash, e.g.:

-- snip --

void test(void)
{
  uint8_t data[20];
  usb_interrupt_read(handle, ep_int_in, data, 20, 1);
}

-- snip --

The above code crashes in some cases, as the read is in some rare cases
executed *after* leaving usb_interrupt_read() and test(), which then
corrupts the local stack as "data" is not valid any more.

To fix this, simply use INFINITE as timeout, as you can *not* return
from _usb_cancel_io until the operation has been truely cancelled. It
is also described on MSDN for WaitForSingleObject() that the only was
to be sure is to call it with INFINITE.

I have tested the fix on lots of setups, and i think the fix is OK, and
does not seem to create other new side-effects.

It was also partially fixable by cancelling all I/O to the driver using
CancelIo(). However, this will cancel all I/O and will ruin other
running endpoints (async readers and such), so that will not work.
Newer version of windows have CancelIoEx() which can cancel a specific
I/O operation, but this is only available in 2008/win7 and forward, and
i need this to still run on xp/vista.

So this solution is the most compatible.

I have attached a patch.

Comments are welcome.

Thanks,

/pedro

Re: [Libusb-win32-devel] DeviceIOControl and LibUSBDriverIO Error.

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

On Wed, Mar 28, 2018 at 7:38 PM, Mayur Purandare
<may...@gm...> wrote:
> Thank you for your reply and Extremely sorry for replying late.
>
> Yes, We use libusb-Win32 driver.
>
> When we debugged the application, noticed that these errors are getting
> thrown from driver layer.
>
> Even we tried to change the driver to libusbK however it was always giving
> me the invalid parameter error.
>

In that case, it could be that the device is the problem.

You may want to use the debug version of libusb-win32 or libusbk driver
and then use debugview to print out the debug message.


-- 
Xiaofan

Re: [Libusb-win32-devel] DeviceIOControl and LibUSBDriverIO Error.

[Mayur P. <may...@gm...>]

Thank you for your reply and Extremely sorry for replying late.

Yes, We use libusb-Win32 driver.

When we debugged the application, noticed that these errors are getting
thrown from driver layer.

Even we tried to change the driver to libusbK however it was always giving
me the invalid parameter error.



On Thu, Mar 22, 2018 at 7:49 PM, Xiaofan Chen <xia...@gm...> wrote:

> On Thu, Mar 22, 2018 at 10:14 PM, Xiaofan Chen <xia...@gm...> wrote:
> > On Mon, Mar 19, 2018 at 11:17 AM, Mayur Purandare
> >> We observed that after some time. (One hour approximately), the
> >> communication gets disconnected with following error.
> >>
> >> Win32Error: DeviceIOControl Code 00222058 failed. The device cannot
> >> recognize the command.
> >> LibUsbIO 22: The device cannot recognize the command. -16367.
> >>
>
> This is strange. The IOCTL code for libusb0.sys is defined here.
> https://github.com/mcuee/libusb-win32/blob/master/
> libusb/src/driver/driver_api.h
>
> Are you using the libusb-win32 device driver?
>
> --
> Xiaofan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] DeviceIOControl and LibUSBDriverIO Error.

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

On Thu, Mar 22, 2018 at 10:14 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Mon, Mar 19, 2018 at 11:17 AM, Mayur Purandare
>> We observed that after some time. (One hour approximately), the
>> communication gets disconnected with following error.
>>
>> Win32Error: DeviceIOControl Code 00222058 failed. The device cannot
>> recognize the command.
>> LibUsbIO 22: The device cannot recognize the command. -16367.
>>

This is strange. The IOCTL code for libusb0.sys is defined here.
https://github.com/mcuee/libusb-win32/blob/master/libusb/src/driver/driver_api.h

Are you using the libusb-win32 device driver?

-- 
Xiaofan

Re: [Libusb-win32-devel] DeviceIOControl and LibUSBDriverIO Error.

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

On Mon, Mar 19, 2018 at 11:17 AM, Mayur Purandare
<may...@gm...> wrote:
> Hello,
>
> We are using LibUsbDotNet C# and LibUsb-Win32 driver.
>
> We communicate with the hardware after 1000 ms.
>
> We observed that after some time. (One hour approximately), the
> communication gets disconnected with following error.
>
> Win32Error: DeviceIOControl Code 00222058 failed. The device cannot
> recognize the command.
> LibUsbIO 22: The device cannot recognize the command. -16367.
>
> Is there any setting that I am missing here.

FYI libusbdotnet has been taken over by Frederik Carlier and the
new repo is in github.
https://github.com/corecompat/libusbdotnet

I myself will not be able to support anything related to
libusbdotnet.

I am not so sure if Frederik is monitoring this list or not.
You may try the above github site.


-- 
Xiaofan

[Libusb-win32-devel] DeviceIOControl and LibUSBDriverIO Error.

[Mayur P. <may...@gm...>]

Hello,

We are using LibUsbDotNet C# and LibUsb-Win32 driver.

We communicate with the hardware after 1000 ms.

We observed that after some time. (One hour approximately), the
communication gets disconnected with following error.

Win32Error: DeviceIOControl Code 00222058 failed. The device cannot
recognize the command.
LibUsbIO 22: The device cannot recognize the command. -16367.

Is there any setting that I am missing here.

Please guide on this.

Thank you.

Regards
Mayur

Re: [Libusb-win32-devel] Bulk msg returns false

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

On Tue, Mar 13, 2018 at 10:02 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Tue, Mar 13, 2018 at 9:50 PM, Dima Nodelman <dim...@gm...> wrote:
>> Hi
>> I'm using libusbk driver for c# and I have a problem, when reading a bulk
>> msg using Stmk_read, I'm getting false response value.
>>
>> The full flow is that I need to read about 5000 bulk msg in sequence,
>> approximately 800 msg are read fine but then all of a sudden I'm getting the
>> method returns false and the cumunication breaks.
>> Is there some log of the driver that I can check what happens?
>
> Yes you can generate the log using the debug version of libusbK.
> You need to use DebugView.
>
> Search the mailing list archive for details.
>

Some reference here.
https://github.com/mcuee/libusbk/issues/2


-- 
Xiaofan

Re: [Libusb-win32-devel] Bulk msg returns false

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

On Tue, Mar 13, 2018 at 9:50 PM, Dima Nodelman <dim...@gm...> wrote:
> Hi
> I'm using libusbk driver for c# and I have a problem, when reading a bulk
> msg using Stmk_read, I'm getting false response value.
>
> The full flow is that I need to read about 5000 bulk msg in sequence,
> approximately 800 msg are read fine but then all of a sudden I'm getting the
> method returns false and the cumunication breaks.
> Is there some log of the driver that I can check what happens?

Yes you can generate the log using the debug version of libusbK.
You need to use DebugView.

Search the mailing list archive for details.


-- 
Xiaofan

[Libusb-win32-devel] Bulk msg returns false

[Dima N. <dim...@gm...>]

Hi
I'm using libusbk driver for c# and I have a problem, when reading a bulk
msg using Stmk_read, I'm getting false response value.

The full flow is that I need to read about 5000 bulk msg in sequence,
approximately 800 msg are read fine but then all of a sudden I'm getting
the method returns false and the cumunication breaks.
Is there some log of the driver that I can check what happens?

Thanks in advance
Dima

Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

[Mayur P. <may...@gm...>]

Hello Jonathan,

We are using EV certificate for signing.

Thank you...

~Mayur

On Wed, Feb 28, 2018 at 10:20 PM, Carter, Jonathan <Jon...@id...>
wrote:

> Did you sign with an EV cert or a regular cert? You need EV for kernel
> mode drivers.
>
>
>
> *From:* Mayur Purandare [mailto:may...@gm...]
> *Sent:* Wednesday, February 28, 2018 12:56 AM
> *To:* lib...@li...
> *Subject:* Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on
> windows 10.
>
>
>
> Hello Jonathan,
>
>
>
> Thank you very much for the reply.
>
>
>
> I tried the way you suggested. However I am still getting the same error
> on windows 10.
>
>
>
> It is that I need it to be attested from Windows Hardware Developer
> Center?
>
>
>
> Can this driver be submitted to the Windows Hardware Developer Center as
> this is licenced under General Public License?
>
>
>
> Thanks..
>
>
>
> ~Mayur
>
>
>
> On Tue, Feb 27, 2018 at 11:08 PM, Carter, Jonathan <
> Jon...@id...> wrote:
>
> Here’s how I signed mine…
>
> First I made a CAT file for the INF because the one the wizard made was
> empty:
>
> -          Get Windows Driver Kit
>
> -          cd C:\Program Files (x86)\Windows Kits\10\bin\x86
>
> -          Inf2Cat /driver:C:\pathToYourINF /os:10_X64,10_X86,6_3_X64,6_3_
> X86,8_X64,8_X86,7_X64,7_X86
>
> -          This makes it valid for all windows versions
>
>
>
> Then I put that with my INF and signed the package.
>
> You should be able to right click it and install but you can also use
> DPINST
>
>
>
> Good luck
>
>
>
> *From:* Mayur Purandare [mailto:may...@gm...]
> *Sent:* Monday, February 26, 2018 11:21 PM
> *To:* Lib...@li...
> *Subject:* [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows
> 10.
>
>
>
> Hello,
>
>
>
> We are using libusb-win32 driver to communicate with our hardware.
>
>
>
> When we installed it on Windows 7, it showed a warning message for unknown
> published.
>
>
>
> To remove this warning we signed the driver with commercial certificate
> and the warning did not come thereafter.
>
>
>
> However, when we tried to deploy the same driver on Windows 10, it is
> showing the Error : "The windows cannot verify the digital signature for
> this device" code 52.
>
>
>
> Request you to please help on this.
>
>
>
> thank you..
>
>
>
>
>
> Regards
>
>
>
> Mayur
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>

Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

[Mayur P. <may...@gm...>]

Hello Xiaofan ,

Thank you very much for the reply.

I will try out this option.

~Mayur

On Wed, Feb 28, 2018 at 7:40 PM, Xiaofan Chen <xia...@gm...> wrote:

> On Wed, Feb 28, 2018 at 4:56 PM, Mayur Purandare
> <may...@gm...> wrote:
> > Hello Jonathan,
> >
> > Thank you very much for the reply.
> >
> > I tried the way you suggested. However I am still getting the same error
> on
> > windows 10.
> >
> > It is that I need it to be attested from Windows Hardware Developer
> Center?
>
> You can refer to the FAQ here.
> https://www.osronline.com/showthread.cfm?link=287745
>
> If your computer has secure boot enabled, you will have to go through
> WHQL or attestation signing.
>
> > Can this driver be submitted to the Windows Hardware Developer Center as
> > this is licenced under General Public License?
> >
> I do not think this is a real issue. If you are worried, you can use
> libusb driver
> (libusbk.sys) which is almost interchannable with libusb-win32 device
> driver
> (libusb0.sys). It has the BSD license option.
>
> --
> Xiaofan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

[Carter, J. <Jon...@id...>]

Did you sign with an EV cert or a regular cert? You need EV for kernel mode drivers.

From: Mayur Purandare [mailto:may...@gm...]
Sent: Wednesday, February 28, 2018 12:56 AM
To: lib...@li...
Subject: Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

Hello Jonathan,

Thank you very much for the reply.

I tried the way you suggested. However I am still getting the same error on windows 10.

It is that I need it to be attested from Windows Hardware Developer Center?

Can this driver be submitted to the Windows Hardware Developer Center as this is licenced under General Public License?

Thanks..

~Mayur

On Tue, Feb 27, 2018 at 11:08 PM, Carter, Jonathan <Jon...@id...<mailto:Jon...@id...>> wrote:
Here’s how I signed mine…
First I made a CAT file for the INF because the one the wizard made was empty:

-          Get Windows Driver Kit

-          cd C:\Program Files (x86)\Windows Kits\10\bin\x86

-          Inf2Cat /driver:C:\pathToYourINF /os:10_X64,10_X86,6_3_X64,6_3_X86,8_X64,8_X86,7_X64,7_X86

-          This makes it valid for all windows versions


Then I put that with my INF and signed the package.
You should be able to right click it and install but you can also use DPINST

Good luck

From: Mayur Purandare [mailto:may...@gm...<mailto:may...@gm...>]
Sent: Monday, February 26, 2018 11:21 PM
To: Lib...@li...<mailto:Lib...@li...>
Subject: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

Hello,

We are using libusb-win32 driver to communicate with our hardware.

When we installed it on Windows 7, it showed a warning message for unknown published.

To remove this warning we signed the driver with commercial certificate and the warning did not come thereafter.

However, when we tried to deploy the same driver on Windows 10, it is showing the Error : "The windows cannot verify the digital signature for this device" code 52.

Request you to please help on this.

thank you..


Regards

Mayur

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...<mailto:Lib...@li...>
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

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

On Wed, Feb 28, 2018 at 10:10 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Wed, Feb 28, 2018 at 4:56 PM, Mayur Purandare
> <may...@gm...> wrote:
>> Hello Jonathan,
>>
>> Thank you very much for the reply.
>>
>> I tried the way you suggested. However I am still getting the same error on
>> windows 10.
>>
>> It is that I need it to be attested from Windows Hardware Developer Center?
>
> You can refer to the FAQ here.
> https://www.osronline.com/showthread.cfm?link=287745
>
> If your computer has secure boot enabled, you will have to go through
> WHQL or attestation signing.
>
>> Can this driver be submitted to the Windows Hardware Developer Center as
>> this is licenced under General Public License?
>>
> I do not think this is a real issue. If you are worried, you can use
> libusb driver

Typo, libusbK driver

> (libusbk.sys) which is almost interchannable with libusb-win32 device driver
> (libusb0.sys). It has the BSD license option.
>



-- 
Xiaofan

Re: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10.

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

On Wed, Feb 28, 2018 at 4:56 PM, Mayur Purandare
<may...@gm...> wrote:
> Hello Jonathan,
>
> Thank you very much for the reply.
>
> I tried the way you suggested. However I am still getting the same error on
> windows 10.
>
> It is that I need it to be attested from Windows Hardware Developer Center?

You can refer to the FAQ here.
https://www.osronline.com/showthread.cfm?link=287745

If your computer has secure boot enabled, you will have to go through
WHQL or attestation signing.

> Can this driver be submitted to the Windows Hardware Developer Center as
> this is licenced under General Public License?
>
I do not think this is a real issue. If you are worried, you can use
libusb driver
(libusbk.sys) which is almost interchannable with libusb-win32 device driver
(libusb0.sys). It has the BSD license option.

-- 
Xiaofan