libusb-win32-devel

[Libusb-win32-devel] libusb-win32-releases 0.1.10.2

[Graeme G. <gr...@ar...>]

I tried updating to release 0.1.10.2, to fix a problem with a version
of a device that stops responding because of the call to get configuration
in usb_os_open(), but the new version now seems to generate a "removing
hardware with out stopping" type warning, every time the device is
removed. This is irritating, so I've switched back to the previous
version (after removing the get configuration call).

What's changed to cause this warning to occur now ? Is there
a way of turning this off in the new version ?

thanks,

Graeme Gill.

Re: [Libusb-win32-devel] libusb-win32-releases 0.1.10.2

[Stephan M. <Ste...@ia...>]

Make sure that you regenerate your .inf file and reinstall
your device using this file. The "feature" you mentioned 
will be turned off by the new .inf file.

Stephan


> 
> I tried updating to release 0.1.10.2, to fix a problem with a version
> of a device that stops responding because of the call to get 
configuration
> in usb_os_open(), but the new version now seems to generate a "removing
> hardware with out stopping" type warning, every time the device is
> removed. This is irritating, so I've switched back to the previous
> version (after removing the get configuration call).
> 
> What's changed to cause this warning to occur now ? Is there
> a way of turning this off in the new version ?
> 
> thanks,
> 
> Graeme Gill.
> 
> 
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share 
your
> opinions on IT & business topics through brief surveys-and earn cash
> 
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] libusb-win32-releases 0.1.10.2

[Graeme G. <gr...@ar...>]

Stephan Meyer wrote:

> Make sure that you regenerate your .inf file and reinstall
> your device using this file. The "feature" you mentioned 
> will be turned off by the new .inf file.

Thanks for the prompt reply. On examination, a few things have
changed in the .inf files (x64 etc), so yes, it seems like a good idea
to update them.

Graeme Gill.

Re: [Libusb-win32-devel] libusb-win32-releases 0.1.10.2

[Graeme G. <gr...@ar...>]

Graeme Gill wrote:
> Thanks for the prompt reply. On examination, a few things have
> changed in the .inf files (x64 etc), so yes, it seems like a good idea
> to update them.

Just noting that I've had to revert back to the previous
version because one device (the Colorimètre HCFR) doesn't
work on the new libusb-win32. I'm not sure how to go about
diagnosing why this is so. It basically doesn't appear
on the system with the new driver.

Graeme Gill.

Re: [Libusb-win32-devel] Problems with 0.1.12.1

[Graeme G. <gr...@ar...>]

Graeme Gill wrote:
> Just noting that I've had to revert back to the previous
> version because one device (the Colorimètre HCFR) doesn't
> work on the new libusb-win32.

Some further information. I installed the 0.1.12.1 driver again,
and fired up Snoopypro, hoping to capture the differences between
the previous version that worked, and this version.

Unfortunately this didn't do any good. It showed that the device
keeps getting re-enumerated every second, so Snoopypro just
pops up a new trace window each second, empty of any USB
transactions.

I turned on __usb_debug in the driver, and strangely when I run
the application this occasionally gets the device to work (but not every time).
I get the following messages when this happens:

LIBUSB_DLL: info: usb_os_init: dll version: 0.1.12.1
LIBUSB_DLL: info: usb_os_init: driver version: 0.1.12.1
LIBUSB_DLL: info: usb_os_find_busses: found bus-0
LIBUSB_DLL: info: usb_os_find_devices: found \\.\libusb0-0001--0x04db-0x005b on bus-0
LIBUSB_DLL: error: usb_reap: timeout error

After this the device remains available until I reset it or reconnect it.

Graeme Gill.