Re: [libusb] Unable to clear LIBUSB_ERROR_PIPE on first run after installing the device driver

[Pete B. <pe...@ak...>]

Oh, how I wish I could stop peeking at this mailing list every now and 
again, and relish in the idea that I don't have to tackle Peter's 
continuing attempts to test the waters and see how much he can get away 
with, before his attempts to seize control of a narrative devolve into 
an actual nuisance for this project...

On 2017.07.12 22:13, Peter Stuge wrote:
> Sounds like this is a bug in the libusb Windows code.

Biased much?

You've been a member of this list way too long to know that, without 
further information from OP, there exist at least 4 layers where the 
issue might reside:

- OP's firmware, which we have no knowledge of, and which may be custom
- OP's code, which we have not seen, and which may be doing something 
that might trigger this behaviour (even if unlikely)
- The libusb0 driver layer, since OP *very explictly* pointed out that 
he was using libusb0, and that is something I would expect any long 
standing mailing-list member to latch on
- The library code that interfaces with the libusb0 driver

If, without any additional information, your conclusion is to point the 
finger at a single layer I really have to wonder what the heck you are 
still trying to accomplish on this project because, *CLEARLY*, your goal 
is not to help its users.

Instead, here is the minimum level of advice I would expect to come, as 
an initial reply, from someone who is supposed to have long standing 
knowledge of libusb and who actually wants to help:

1. Ask OP whether he is using a custom firmware
2. Ask OP what version of the library he is using
3. Ask OP whether he can provide us a debug libusb log from his app
4. Ask OP whether he may be able to replicate this behaviour with xusb 
or any means that can try to eliminate OP's code as the culprit
5. Ask OP whether he may be able to replicate this behaviour with a 
different device (eliminate OP's firmware)
6. And, most importantly, ask OP whether he has tried with WinUSB 
instead of libusb0. Again, you're supposed to have been on this list 
long enough to know that the first thing we ask, when someone mentions 
that they are using libusb0.sys (given that there are known 
instabilities when using this driver with libusb) is to try a different 
driver.

Oh, and you could also have tried to be helpful by asking the finer 
details, which I would also expect you to know, such as whether 
libusb0.sys was installed as a filter driver (another source of issues), 
in which case you may advise OP to try with the usbdk layer of libusb if 
they prefer, instead of WinUSB, try to accomplish the same with a 
different OS, and so on.

But of course, by performing the above, one runs the risk of finding out 
that this may have little to do with a "a bug in the libusb Windows 
code", and it's of course hard to see why anyone would pass a good 
opportunity of throwing FUD around (which, personally, when enacted by 
the same person on a reoccurring basis, is something that I would tend 
to qualify as "trolling behaviour"... but what do I know)?

I'll just conclude with some more free advice, which I think may be 
needed: Pointing out someone's repeated shortcomings, when they are 
clearly preventing users of a project from receiving the appropriate 
level of help, is neither ad hominem nor trolling.

Regards,

/Pete