Hi guys,
now you can relax; this is my last submission.
It contains some wishes for a next release.
The Candidates Buglet
This buglet is not a real error but an example of poor programming style,
which makes the life of the application programmer more d
Hi Jeff
Dienstag, 11. Oktober 2016 um 14:55 Uhr
"Jeffrey Nichols"
This is not right. I ship a product and do never know what driver the enduser will use.
I an make a suggestion but cannot be sure that it is obeyed. And I might even change my mind.
The only way to make the applicati
Hi,
The use of the pyusb0 service is a bit troublesome, because you have to specify the desired library by hand.
I always had the dream of automatically use the installed library.
Well, here is how.
You must know the Vid and Pid of your device. With that you can look up the registry for the in
guide.
Feel free to comment on everything.
This document is in libreoffice format, so that everyone can add comments (in red ink)
to it.
Sincerely Hermann Hamann
InstallationGuide.odt
Description: application/vnd.oasis.opendocument.text
Hi,
To install or to not install, that is the question.
I was recently bitten by some lethal errors using pyusb. These were not in the pyusb code but came from lower layers as a consequence of misusing them.
The following correspondence with the maintenance crew was unsuccessful because the serv
Hi,
>> * Are there plans for a new version of pyusb1 in the near future?
> Maybe a minor bug fix version, but not big changes.
I am happy to learn about bug fixes. If you run short of bugs I will be ready to send you some.
>> * Are there plans for a Windows Installation Guide?
> a
Hi,
I am preparing an Installation Guide for my DSO program.
I do not want to do obsolete or redundant work.
Therfore I ask the following:
* Are there plans for a new version of pyusb1 in the near future?
* Are there plans for a Windows Installation Guide?
Sincerely Hermann
--
< I have edited libusb wiki to warn against using libusb0.sys
< with libusb Windows.
Thank you.
One likeand one follower!
--
___
pyusb-users mailing list
pyusb-users@lists
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
Hi dear maintainers.
I have compiled the results of the pick wrong library issue and some investigations in an issue on github.
However I could not attach the PDF file and therefore provide it here.
Please study it carefully.
I will not be here until september, so you have enough time
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
--
_
Hi, thank you
Well, why then the library search? It is completely superfluous if I fix anything at installation.
Sincerely
Hermann
--
___
pyusb-users mailin
Hi
> ..and debug the real problem
What is my real problem?
H.H.
--
___
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/lis
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 "C:\Python27\lib\multiprocessing\process.py", line 258, in _bootstrap
self.run()
File "C:\Python2
Hi Xiaofan
This problem does not occur on my machine but my client's.
I have no influence on that setup, and it works for him.
>> < Why it crashed?
>> I don't know.
I will post the crash dump later.
> The registry thingy has nothing to do with your problem.
Therefore I asked what
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 ho
Hi Chris,
Yes.
https://bitbucket.org/clach04/coldtears_clock/wiki/Windows
Thank you.
OK
--
___
pyusb-users mailing list
pyusb-users@lists.source
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
the registry for?
2. Is it valid programming style to disregard registry entries?
3. Has anyone succesfully used a non registered driver?
Thank you in advance
Hermann Ham
s not answer the question which defaults are appropiate in the normal case.
On Windows the registry entry is the most appropriate default.
I hope this can help you to amend pyusb1 (which is a great tool anyway).
Sincerely Hermann Hamann
--
Hello dear maintainers,
Google finds now about 5 hits on "no backend". So it is time to make an end to this problem.
The Problem is two missing lines in the (excellent!) tutorial:
---
If you encounter
Hello Tormod,
thank you for your response.
I hope the following remarks will get you further.
> The source revision control system log has taken over this function.
Fine, but it did not help you ☺.
>> The original is from walac-pyusb-39816be.
> 39816be is actually the most recent reposito
Hi,
sorry for my late answer.
Well, everyone has to carry his burden, not only maintainers (as opposed to
Galather 6.2).
My burden is my 99 years old mum, who suffers from dementia and other pains of
old age and needs attention around the clock.
This leaves me 1 or 2 hours a week for concent
am too old and too stupid to learn on the fly how to use a github pull request
to push some files.
So I use the stone age way to attach the modified files core.py and libusb1.py to this mail, hoping,
that some kind soul will find them and treat them as required.
Sincerely
Hermann Hamann
like to distribute my software with a modified pyusb.
Sincerely
Hermann Hamann
Here follows the modifications I made:
-
# in backend1.py, similar for other backends
from ctypes import *
from struct import unpack
getBuffer = pythonapi.PyObject_GetBuffer
25 matches
Mail list logo
