Looking more at this...

Mario Lang, on ven. 07 avril 2017 21:38:16 +0200, wrote:
> Samuel, can you tell if this would be a useful change to adopt?
> 
> --- a/Autostart/Windows/brltty-libusb.inf
> +++ b/Autostart/Windows/brltty-libusb.inf
> @@ -46,7 +46,7 @@ libusb_files_dll_x64 = 10,system32
>  libusb0.sys
>  
>  [libusb_files_sys_x64]
> -libusb0.sys,libusb0_x64.sys
> +libusb0_x64.sys

Yes, it makes sense, the 32bit driver (libusb0.sys) is probably not
useful on 64bit windows.

> @@ -55,7 +55,7 @@ libusb0.dll
>  libusb0.dll
>  
>  [libusb_files_dll_x64]
> -libusb0.dll,libusb0_x64.dll
> +libusb0_x64.dll

I don't really know. I'd tend to think that one wants to have the 32bit
version of the dll too, but we ship it along brltty.exe already anyway.
I'd say "can not hurt", then.

> @@ -87,7 +87,7 @@ AddReg = libusb_add_reg_hw
>  AddService = libusb0, 0x00000002, libusb_add_service
>  
>  [LIBUSB_DEV.NTAMD64.Services]
> -AddService = libusb0, 0x00000002, libusb_add_service
> +AddService = libusb0, 0x00000002, libusb_add_service_amd64
>  
>  [libusb_add_reg]
>  HKR,,DevLoader,,*ntkern
> @@ -114,6 +114,14 @@ StartType      = 3
>  ErrorControl   = 0
>  ServiceBinary  = %12%\libusb0.sys
>  
> +[libusb_add_service_amd64]
> +DisplayName    = "LibUsb-Win32 - Kernel Driver 03/31/2007, 0.1.12.1"
> +ServiceType    = 1
> +StartType      = 3
> +ErrorControl   = 0
> +ServiceBinary  = %12%\libusb0_x64.sys

Yes, that makes sense, we want the 64bit driver, not the 32bit driver.

Samuel
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Reply via email to