|
From: Dave H. <DAV...@ni...> - 2007-06-07 06:49:03
|
> -----Original Message-----
> From: lib...@li...=20
> [mailto:lib...@li...] On=20
> Behalf Of Bertrik Sikken
> Sent: 2007 June 06 17:53
> To: lib...@li...
> Subject: Re: [Libusb-win32-devel] Help, please
>=20
> Stephan Meyer wrote:
> > Try to replace:
> >=20
> > uci =3D usb_claim_interface (udev, 0);
> >=20
> > with
> >=20
> > usb_set_configuation(udev, 1);
> > uci =3D usb_claim_interface (udev, 0);
> >=20
> > It should work then.
>=20
> I think I recently saw a recommendation on the libusb list to NOT
> do an explicit usb_set_configuration. If I remember correctly
> Linux already picks a configuration for you (usually devices
> only have one configuration anyway).
I don't have to do this on Linux, but I do on Win32.
> What is the proper thing to do when writing something for
> both Linux and Windows?
Yes, I'd like to know too, please. I'm writing for both.
I've only just started with Win32 and I've discovered
3 incompatibilities. All solved, of course, thanks to
some extremely rapid help; but it would be easiest for
everybody if there weren't any incompatibilities.
Dave
***************************************************************************=
***************************************************************************=
***************************************************************************=
****************
NICE CTI Systems UK Limited ("NICE") is registered in England under company=
number, 3403044. The registered office of NICE is at Tollbar Way, Hedge E=
nd, Southampton, Hampshire SO30 2ZP.
Confidentiality: This communication and any attachments are intended for th=
e above-named persons only and may be confidential and/or legally privilege=
d. Any opinions expressed in this communication are not necessarily those o=
f NICE. If this communication has come to you in error you must take no act=
ion based on it, nor must you copy or show it to anyone; please delete/dest=
roy and inform the sender by e-mail immediately.
Monitoring: NICE may monitor incoming and outgoing e-mails.
Viruses: Although we have taken steps toward ensuring that this e-mail and=
attachments are free from any virus, we advise that in keeping with good c=
omputing practice the recipient should ensure they are actually virus free.
***************************************************************************=
***************************************************************************=
***************************************************************************=
*******************
=20
|