Re: [Nut-upsuser] Windows 2.6.0-1 usbhid-ups driver infinite loop on USB disconnect

2011-06-29 Thread Frédéric Bohé
Hello David, First, thanks for this post. The Windows port is still in beta stage and this kind of post if very useful. On Tue, 2011-06-28 at 20:54 -0400, David Bolen wrote: David Bolen db3l@gmail.com writes: Attached below is an excerpt of debugging output from usbhid-ups. It would

Re: [Nut-upsuser] Windows 2.6.0-1 usbhid-ups driver infinite loop on USB disconnect

2011-06-29 Thread Arnaud Quette
2011/6/29 Frédéric Bohé fredericb...@eaton.com Hello David, First, thanks for this post. The Windows port is still in beta stage and this kind of post if very useful. On Tue, 2011-06-28 at 20:54 -0400, David Bolen wrote: David Bolen db3l@gmail.com writes: Attached below is an

Re: [Nut-upsuser] Windows 2.6.0-1 usbhid-ups driver infinite loop on USB disconnect

2011-06-29 Thread David Bolen
Arnaud Quette aquette@gmail.com writes: 2011/6/29 Frédéric Bohé fredericb...@eaton.com Another bug. errno has to be filled with the result of GetLastError() to be really useful. wasn't it suppose to be already the case? along with the equivalent winsock WSAGetLastError() where

[Nut-upsuser] Windows 2.6.0-1 usbhid-ups driver infinite loop on USB disconnect

2011-06-28 Thread David Bolen
I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in

Re: [Nut-upsuser] Windows 2.6.0-1 usbhid-ups driver infinite loop on USB disconnect

2011-06-28 Thread David Bolen
David Bolen db3l@gmail.com writes: Attached below is an excerpt of debugging output from usbhid-ups. It would appear that the interrupt and query failures have reasonably appropriate errors, so maybe it's just a difference in how such errors reflect under Windows vs. *nix. Following up