Hi Tormod,
thank you for your expertise; now I see clearer.
> < Why it crashed?
> I don't know.
I will send you a crash dump later.
> <If you want to use libusb-1.0 backend, you need to have libusb-1.0.dll in
> <the system and better use WinUSB driver for your device.
>
> I want the backend that is in the registry.
>pyusb by default looks for libusb1 first
< .... you must select backend explicitly.
Well how can I? I do not know which backend is available on my clients' machines.
I can only rely on the driver that was installed for my device and which is displayed
in the control panel. I suppose the control panel gets it through the registry.
<< Flexibility comes at a cost.
And what is the cost of reliability?
<And the pyusb application currently uses a DLL search to select default library
<backend, regardless of the device.
Well I rank the registry higher in authority than the library search order.
<Hermann, in your case you are probably better off selecting the
<libusb0 backend in your python application, if you know that your
<device requires libusb0.sys. Otherwise, register the device for WinUSB
<(with .inf file or Zadig), make sure a known good libusb1.dll is
<installed in the path (before any third party libusb1.dll) and select
<the libusb1 backend in your python application for good measure.
Well I am a bit confused when regarding recommendations for driver installation.
The tutorial recommends the inf-wizard and libusb0 and so I did and it works fine.
Well I can instruct my clients to do the same and hardcode pyusb0 into my program.
So much about flexibility.
<BTW, Hermann's example patch hardcodes "ControlSet002" which I believe
<should be "CurrentControlSet", unless there are better ways to find
I found this with a registry editor search. I do not understand enough to
judge the generality of this approach.
<(e.g. different serial numbers but same vid/pid) can have different
<Service values, and I am not sure how the patch deals with that.
I would not care, nobody will have two same oscilloscopes on its computer.
Thank you again for your effort, this makes my issue obsolete an I will not open it.
Sincerely Hermann
------------------------------------------------------------------------------
_______________________________________________
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyusb-users
------------------------------------------------------------------------------
_______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
