View Single Post
Old 08-25-2012, 10:24 AM   #116
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Pixelpille View Post
- - - snip - - -
"When using K3Flasher ... "
Code:
E: reading data from device: LIBUSB_ERROR_NO_DEVICE
E: aborting. It is suggested you power-cycle the device.
Are they supposed to say anything like "wohoo, something happened" ?
K3Flasher is built against libusb-1.0 which does not provide notification of a device's appearance or disappearance.

That sort of notification system is proposed for libusb-1.1

So with libusb-1.0 the best that can be done is to try to use a device once known to be there, only to discover that it is gone.

And since USB client devices rarely say: "Goodbye" before unplugging, even with libusb-1.1 it may not be possible to give a more informative message than "Gone".
knc1 is offline   Reply With Quote