< I have edited libusb wiki to warn against using libusb0.sys
< with libusb Windows.
Thank you.
One likeand one follower!
--
___
pyusb-users mailing list
On Thu, Aug 25, 2016 at 9:33 AM, Xiaofan Chen wrote:
> On Tue, Aug 23, 2016 at 5:20 AM, Tormod Volden wrote:
>
>>
>> Now when it comes to the libusb <-> kernel hardware driver interaction
>> on Windows, it is not easy to get the full overview of
Hi Xiaofan Chen
I will try that.
H.H.
--
___
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyusb-users
On Tue, Aug 23, 2016 at 5:20 AM, Tormod Volden wrote:
>
> Now when it comes to the libusb <-> kernel hardware driver interaction
> on Windows, it is not easy to get the full overview of possibilities,
> requirements and failure modes. Quoting from
>
Hi Jeff,
I have opened an issue on this topic. Please read it and try to falsify or verfy my thesis.
I will not be back to my mailbox before september, so you have ample time.
So long
Hermann
--
On 8/23/2016 5:23 AM, Hermann Hamann wrote:
Hi, thank you
you control, which is one of the reasons why everyone
Well, why then the library search? It is completely superfluous if I
fix anything at installation.
Sincerely
Hermann
I believe the automatic backend selection is to make scripts
Hi, thank you
Well, why then the library search? It is completely superfluous if I fix anything at installation.
Sincerely
Hermann
--
___
pyusb-users
On Fri, Aug 19, 2016 at 11:15 AM, Hermann Hamann wrote:
> Hi, Tormod
>
> This is the crashdump :
>
>
> C:\Portable\wdso>python wdso.py
>
> wdso 0.9.8
> found productId 0x0834
> [Errno 5] Input/output error
> Process USB_server:
> Traceback (most recent call last):
> File
Your real problem is that you don't know beforehand which driver your
device will be using. If you're doing the driver install as part of an
installer (e.g. using wdi-simple.exe) or instructing your users to use
zadig.exe then you should already know which driver has been installed.
I would
Hi
> ..and debug the real problem
What is my real problem?
H.H.
--
___
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
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.
>
>
>
> I want the backend that is in the registry.
>pyusb by default looks for libusb1 first
< you must select backend explicitly.
Well
On Thu, Aug 18, 2016 at 11:07 AM, Hermann Hamann wrote:
>
> If it helps you:
>
> C:\Program Files\RTLSDR Scanner>dir lib*.*
> 12.04.2013 20:04 68.608 libusb-1.0.dll
Probably "C:\Program Files\RTLSDR Scanner" is in the global %PATH%, so
it is not so "private".
> < Why it crashed?
> I don't know.
On Thu, Aug 18, 2016 at 7:57 PM, Xiaofan Chen wrote:
> On Thu, Aug 18, 2016 at 5:07 PM, Hermann Hamann wrote:
>>
>> Hi
>>
>> > I have read so in the internet. I will post reference later.
>>
>> >
>> If it helps you:
>>
>> C:\Program Files\RTLSDR
On Thu, Aug 18, 2016 at 5:07 PM, Hermann Hamann wrote:
>
> Hi
>
> I have read so in the internet. I will post reference later.
>
>
> If it helps you:
>
> C:\Program Files\RTLSDR Scanner>dir lib*.*
> Volume in Laufwerk C: hat keine Bezeichnung.
> Volumeseriennummer:
Hi Chris,
Yes.
Hi
I have read so in the internet. I will post reference later.
If it helps you:
C:\Program Files\RTLSDR Scanner>dir lib*.*
Volume in Laufwerk C: hat keine Bezeichnung.
Volumeseriennummer: ECEC-C891
Verzeichnis von C:\Program Files\RTLSDR Scanner
12.04.2013 20:04 68.608 libusb-1.0.dll
On Sat, Aug 13, 2016 at 3:34 PM, Hermann Hamann wrote:
> Dear maintainers,
> my client and I have the same USB-Device. I have written a program for it.
> It runs fine on both Linux systems. It runs fine on my Windows but crashes
> on my client's.
> Both have installed the
On Wed, Aug 17, 2016 at 12:31 AM, Hermann Hamann
wrote:
> Hi
> < would you mind opening a issue?
> I will do so, but it may take some time.
> I have absolutely no background in Windows and there will be a lot of
> googling before
> I can present hard facts.
>
> Therefore I
Hi
< would you mind opening a issue?
I will do so, but it may take some time.
I have absolutely no background in Windows and there will be a lot of googling before
I can present hard facts.
Therefore I ask the Window gurus among the users to answer me some questions:
1. What is the
Hi,
PyUSB relies on ctypes for finding libraries, which relies on Windows
library search policy, if it finds libusb1 first, then that's what it
assumes as the backend. backend parameter was designed for cases like
yours, when the default backend discovery policy doesn't apply.
Anyway, you code
Dear maintainers,
my client and I have the same USB-Device. I have written a program for it.
It runs fine on both Linux systems. It runs fine on my Windows but crashes on my client's.
Both have installed the driver with inf-wizard and the system control shows libusb0.dll on
both machines.
21 matches
Mail list logo