libusb-win32-devel

Re: [Libusb-win32-devel] libusb-win32 and OpenUsb

[Spiro T. <an-...@sp...>]

Hello,

* On Sun, Nov 11, 2007 at 08:39:33AM +0800 Xiaofan Chen wrote:
> On Nov 11, 2007 12:23 AM, Spiro Trikaliotis
> <an-...@sp...> wrote:

> > I failed to see the advantage of using OpenUSB. Can you please elaborate
> > why one should want this?
> >
> 
> OpenUSB is supposed to be based on the libusb 1.0 API and has the
> aim to be thread safe and support isochronous transfer (libusb-win32
> already support iso transfer). It also has a compatibility layer so
> that libusb-0.1 based program will still run.

Oh... It seems I totally missed that OpenUSB wants to REPLACE libusb. I
had the impression that it is just another layer on top of libusb.

 
> One more thing, OpenUSB is backed by SUN, a corporration. This
> can be a good (or not so good) depending on your interpretation.

The only positive aspect I can think of: SUN might want to afford the
$$$ needed to sign the Windows driver. ;)

 
> To make OpenUSB cross-platform, Win32 is important. So I think if
> SUN really persists, they will come out a Win32 port. Then it
> might not be a good idea to have two incompatible API for
> Windows.

The Windows API is there, they are free to use that. (just kidding)

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Spiro T. <an-...@sp...>]

Hello Paarvai,

* On Sat, Nov 10, 2007 at 11:01:17AM -0800 Paarvai Naai wrote:

> The
> impression I had was that Microsoft wants to keep the kernel mode code
> signing (KMCS) separate from WHQL.  The INF gets signed and hashed as
> part of the WHQL process.

Indeed, you are right. I confused all of this.

> There is discussion in the kmsigning.doc that specifically says that
> you can release a driver *without* WHQL as long as you follow KMCS.

Yes, I was aware of this, but I totally forgot that signing the INF is
part of WHQL, not of KMCS.

> Sprio, did you look through that document above and find something
> contradictory, or are you working of some other reference?

I have had a look into that document more than once, but not recently.
What I had written was from my memory, and it seems I was confused "a
little bit".

So, please disregard my previous statements.

> Personally, I'm unclear on all of this and Microsoft's documentation
> hasn't been the greatest here.  Sadly, the only way to really be sure
> would be to try this all out or here from someone who has.

We could ask this question on the MS newsgroups; questions regarding
signing are rather common there. It might be better to search for
something there, as there have been many questions regarding this.

However, even if this is possible: We would still need someone who is
willing to sign the driver.

BTW: I have another driver project (http://sf.net/projects/opencbm)
where I would want at least the 64 bit driver to be signed. ;)

Gruß,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

Re: [Libusb-win32-devel] libusb-win32 and OpenUsb

[Xiaofan C. <xia...@gm...>]

On Nov 11, 2007 12:23 AM, Spiro Trikaliotis
<an-...@sp...> wrote:
> > http://openusb.sourceforge.net/
> >
> > OpenUSB currently only works under Solaris and Linux. But they
> > would like to extend the support to Mac OS X, Win32 and BSDs.
>
> I failed to see the advantage of using OpenUSB. Can you please elaborate
> why one should want this?
>

OpenUSB is supposed to be based on the libusb 1.0 API and has the
aim to be thread safe and support isochronous transfer (libusb-win32
already support iso transfer). It also has a compatibility layer so
that libusb-0.1 based program will still run.

I am not too much into the technical details of OpenUSB. I just
think it would be nice for libusb-win32 to be in-sync to l with
OpenUSB which is a fork of libusb 1.0 (libusb 1.0 is kind of dormant
now).

One more thing, OpenUSB is backed by SUN, a corporration. This
can be a good (or not so good) depending on your interpretation.
For me I think so far it is positive. OpenUSB is still in the development
stage but the API, the frontend and Solaris/Linux backend are almost
finished.

To make OpenUSB cross-platform, Win32 is important. So I think if
SUN really persists, they will come out a Win32 port. Then it
might not be a good idea to have two incompatible API for
Windows.

Xiaofan
http://mcuee.blogspot.com

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Paarvai N. <ope...@gm...>]

>From what I have read the INF does not need to be signed.  I might be
wrong so I want to try this in-house and see what the result is.  The
impression I had was that Microsoft wants to keep the kernel mode code
signing (KMCS) separate from WHQL.  The INF gets signed and hashed as
part of the WHQL process.  The links I posed earlier were:

http://www.microsoft.com/whdc/winlogo/drvsign/kmsigning.mspx
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/kmsigning.doc

There is discussion in the kmsigning.doc that specifically says that
you can release a driver *without* WHQL as long as you follow KMCS.
And then, there is discussion on KMCS and how it only requires that
the KMOD be signed, its hash placed in the CAT file, and the CAT file
signed.

Sprio, did you look through that document above and find something
contradictory, or are you working of some other reference?
Personally, I'm unclear on all of this and Microsoft's documentation
hasn't been the greatest here.  Sadly, the only way to really be sure
would be to try this all out or here from someone who has.

Paarvai


On Nov 10, 2007 8:20 AM, Spiro Trikaliotis
<an-...@sp...> wrote:
> Hello,
>
> * On Fri, Nov 09, 2007 at 10:47:27AM -0800 Paarvai Naai wrote:
>
> > The interesting question that remains is whether the INF file needs to
> > be signed to actually allow the driver to install and load.  Do you
> > know anything about this?
>
> I don't know for sure as I do not own a 64 bit machine (nor Vista 64
> bit). Anyway, from my understanding,
>
> 1. in order for the driver (.sys) to load, it must be signed;
>
> 2. in order for Vista (64bit) to accept your .inf, it must be signed,
>    too.
>
> If this is correct, the question is: Are we able to install a USB
> driver (WDM, not legacy kernel-mode driver) without an INF? AFAIK, this
> is not possible, but I may be wrong.
>
> But, again, remember: This is only guessing, as I do not own a system to
> test this.
>
>
> Regards,
>    Spiro.
>
> --
> Spiro R. Trikaliotis                              http://opencbm.sf.net/
> http://www.trikaliotis.net/                     http://www.viceteam.org/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] libusb-win32 and OpenUsb

[Spiro T. <an-...@sp...>]

Hello Xiaofan,

* On Fri, Nov 02, 2007 at 08:01:17AM +0800 Xiaofan Chen wrote:

> http://openusb.sourceforge.net/
> 
> OpenUSB currently only works under Solaris and Linux. But they
> would like to extend the support to Mac OS X, Win32 and BSDs.

I failed to see the advantage of using OpenUSB. Can you please elaborate
why one should want this?

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

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

Stephan Meyer wrote:
> A configuration value of '0' is invalid (see USB spec
> for details). So the only solution is to fix your device's
> firmware.

You're absolutely right, but it doesn't solve the users
problem, and they can't solve it either, since they
aren't responsible for creating the device. libusb-win32 looks
bad if the device used to work, and (presumably) still works
with other usb drivers.

Is there a way of making libusb-win32 more robust in the
face of such (badly behaved) devices, rather than simply
failing ?

Graeme Gill.

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Spiro T. <an-...@sp...>]

Hello,

* On Fri, Nov 09, 2007 at 10:47:27AM -0800 Paarvai Naai wrote:
 
> The interesting question that remains is whether the INF file needs to
> be signed to actually allow the driver to install and load.  Do you
> know anything about this?

I don't know for sure as I do not own a 64 bit machine (nor Vista 64
bit). Anyway, from my understanding,

1. in order for the driver (.sys) to load, it must be signed;

2. in order for Vista (64bit) to accept your .inf, it must be signed,
   too.

If this is correct, the question is: Are we able to install a USB
driver (WDM, not legacy kernel-mode driver) without an INF? AFAIK, this
is not possible, but I may be wrong.

But, again, remember: This is only guessing, as I do not own a system to
test this.

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

Re: [Libusb-win32-devel] libusb-win32 webpage and wiki

[Xiaofan C. <xia...@gm...>]

On Nov 9, 2007 5:53 PM, Stephan Meyer <Ste...@ia...> wrote:
> Thank's for the suggestion. I wasn't aware of the fact
> that Sourceforge added a Wiki to their services.
> I'll activate it, transfer the content, and redirect
> the old site to the wiki.

Thanks. I just tried to add three pages and it is actually quite easy to use.
http://libusb-win32.wiki.sourceforge.net/space/changes

Xiaofan

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Paarvai N. <ope...@gm...>]

Hi Sprio,

I think what Graeme probably meant to say was that Microsoft allows
drivers to be self-signed as opposed to being self-signed and then
also signed by Microsoft.  Thank you for clarifying that since it is
definitely an important distinction.

The interesting question that remains is whether the INF file needs to
be signed to actually allow the driver to install and load.  Do you
know anything about this?

Best regards,
Paarvai


On Nov 9, 2007 9:47 AM, Spiro Trikaliotis
<an-...@sp...> wrote:
> Hello,
>
> * On Fri, Nov 09, 2007 at 09:27:10PM +1100 Graeme Gill wrote:
>
> > Since Microsoft seem to have at least shifted their policy to
> > allow companies other than themselves to sign drivers ("Self-Signing"),
> > this seems more feasible that it once was, but it's still
> > a significant barrier to non-commercial developers.
>
> Note that a driver signed by MS is different to a self-signed driver.
>
> At least on Vista 64 bit, you *must* use a self-signed driver, or the
> driver will not load. This way, MS ensures that you know from whom the
> driver is. That's the purpose of the self-signed drivers.
>
> The "special flags for booting the system" or there mostly for
> developers, not for the average user (IMHO). The other option is to
> attach a kernel-mode debugger to your machine; this way, you can load
> your unsigned driver, too.
>
> The signature MS gives to your driver tells you that the driver passed
> WHQL (http://www.microsoft.com/whdc/winlogo/getstart/default.mspx) -
> that is, your driver "survives" some automated tests.
>
>
> Regards,
>    Spiro.
>
> --
> Spiro R. Trikaliotis                              http://opencbm.sf.net/
> http://www.trikaliotis.net/                     http://www.viceteam.org/
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Spiro T. <an-...@sp...>]

Hello,

* On Fri, Nov 09, 2007 at 09:25:42AM -0800 Paarvai Naai wrote:
 
> Yes, it does appear that the publisher can self-sign once they have
> obtained a software publishing certificate (SPC) from Microsoft.  The
> process of obtaining the SPC requires a Verisign certificate which
> costs ~$500.

AFAIR, it was $500 p.a.

When your certificate expires, you cannot load the driver anymore. (But
you can let VeriSign or someone else "timestamp" the signature, so it
does not expire. But this costs, again.)

In the meantime, MS also allows for other certificates but Verisign.
Nevertheless, the problem itself remains.

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Spiro T. <an-...@sp...>]

Hello,

* On Fri, Nov 09, 2007 at 09:27:10PM +1100 Graeme Gill wrote:
 
> Since Microsoft seem to have at least shifted their policy to
> allow companies other than themselves to sign drivers ("Self-Signing"),
> this seems more feasible that it once was, but it's still
> a significant barrier to non-commercial developers.

Note that a driver signed by MS is different to a self-signed driver.

At least on Vista 64 bit, you *must* use a self-signed driver, or the
driver will not load. This way, MS ensures that you know from whom the
driver is. That's the purpose of the self-signed drivers.

The "special flags for booting the system" or there mostly for
developers, not for the average user (IMHO). The other option is to
attach a kernel-mode debugger to your machine; this way, you can load
your unsigned driver, too.

The signature MS gives to your driver tells you that the driver passed
WHQL (http://www.microsoft.com/whdc/winlogo/getstart/default.mspx) -
that is, your driver "survives" some automated tests.

 
Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Paarvai N. <ope...@gm...>]

Hi Graeme,

Yes, it does appear that the publisher can self-sign once they have
obtained a software publishing certificate (SPC) from Microsoft.  The
process of obtaining the SPC requires a Verisign certificate which
costs ~$500.

Paarvai

On Nov 9, 2007 2:27 AM, Graeme Gill <gr...@ar...> wrote:
> Stephan Meyer wrote:
>
> > It's not possible to sign just a driver (.sys file).
> > You always have to sign the combination of the driver and the device
> > specific .inf file.
>
> Since Microsoft seem to have at least shifted their policy to
> allow companies other than themselves to sign drivers ("Self-Signing"),
> this seems more feasible that it once was, but it's still
> a significant barrier to non-commercial developers.
>
> Is there any distinction between how unsigned .sys and
> unsigned .inf files are handled ?
>
> As I understand it, the administrator simply cannot load an
> unsigned .sys file, unless the operating system has
> been booted up with some special flags that permit this.
>
> Does anyone know if the same apply to .inf files, or is it
> merely that the administrator will get an warning/OK dialog for
> an unsigned .inf file ?
>
> If not, then there seems less point in continuing to develop
> a winusb.sys version of libusb-win32.
>
> Graeme Gill.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Antwort: 64-bit support

[Paarvai N. <ope...@gm...>]

Hi Stephan,

Thanks for the quick reply.  My response below:

On Nov 9, 2007 1:49 AM, Stephan Meyer <Ste...@ia...> wrote:
> * install the latest DDK
> * open a DDK 64bit build environment

Does this have to be the Windows Server 2003 SP1 DDK or can it be the
latest WDK?


> Yes you can. Just copy the 32bit DLL to Windows' 'syswow64' folder.

Does the 32-bit DLL have to be built with the DDK or will the MinGW
version work?  I am guessing that the MinGW one will work too.


> It's not possible to sign just a driver (.sys file).
> You always have to sign the combination of the driver and the device
> specific .inf file.

Actually it is my understanding that you have to have a signed CAT
file but the CAT file does not need to have hashes for anything but
the KMOD (.sys file) to pass through the Kernel Mode Code Signing
(KMCS) requirements.  Please see:

http://download.microsoft.com/download/d/c/3/dc32d46e-58e7-46b8-8689-a3b17606b53a/kernel_mode_code_signing_x-64_windows_vista.ppt
http://www.microsoft.com/whdc/winlogo/drvsign/kmsigning.mspx
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/kmsigning.doc

This makes sense anyway since if one were to use winusb.sys, they
don't need to sign their INF and DLL (unless they wish to have WHQL
certification).  In the same way, if a publisher makes a SYS, DLL, and
INF file, they would simply have to sign the SYS file and the
situation would be then similar to using a 3rd party SYS file.

I know that using winusb.sys is probably the best long-term approach,
but having an official libusb-win32 signed driver seems like a great
short-term stop gap.  I am not totally sure, but I believe our company
would be willing to sponsor the cost of a Verisign certificate in that
case.

Best regards,
Paarvai

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

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

> As you can see, the bConfigurationValue is 0, not 1. Is that the 
problem?
> And if it is, why does it work with the older version of the lib? Do I 
have
> to change the value to 1 (which might be a problem as I can't flash the
> controller...)?

A configuration value of '0' is invalid (see USB spec
for details). So the only solution is to fix your device's
firmware.

It worked with the old DLL because the old version of 
usb_set_configuration() treated the 'config' parameter as
an index, which was wrong. Whereas the new version treats
the parameter as a value that must be equal to one of the
descriptor's bConfigurationValue values.

Stephan


> 
> Well, since the application on the controller is not written by me I 
can't
> give you the code. But I can post what TestLibUsb gives me:
> 
>   wTotalLength:         46
>   bNumInterfaces:       1
>   bConfigurationValue:  0
>   iConfiguration:       0
>   bmAttributes:         80h
>   MaxPower:             50
>     bInterfaceNumber:   0
>     bAlternateSetting:  0
>     bNumEndpoints:      4
>     bInterfaceClass:    255
>     bInterfaceSubClass: 0
>     bInterfaceProtocol: 0
>     iInterface:         0
>       bEndpointAddress: 01h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0
>       bEndpointAddress: 81h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0
>       bEndpointAddress: 02h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0
>       bEndpointAddress: 82h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0
> 
> As you can see, the bConfigurationValue is 0, not 1. Is that the 
problem?
> And if it is, why does it work with the older version of the lib? Do I 
have
> to change the value to 1 (which might be a problem as I can't flash the
> controller...)?
> 
> Best regards
> 
> 
> 
> Stephan Meyer-2 wrote:
> > 
> > dev->config[0].bConfigurationValue should be >=1.
> > Could you please post your configuration descriptor(s)?
> > 
> > Stephan
> > 
> >> 
> >> Hi,
> >> 
> >> > is '1' a valid configuration value?
> >> well, it should be as the application can be run with the older 
version 
> > of
> >> libusb...
> >> I tried using your code and now the application runs over the
> >> usb_set_configuration. But now the next call (the one to
> >> usb_claim_interface()) returns an error...
> >> Here is the message:
> >> "usb_claim_interface: could not claim interface 0, invalid 
configuration 
> > 0".
> >> 
> >> So as I understand configuration 0 is set by the set_configuration 
and 
> > is
> >> not valid. But why?? I mean it does work (with the older version of 
the
> >> library)!
> >> 
> >> Thanks in advance
> >> 
> >> 
> >> Stephan Meyer-2 wrote:
> >> > 
> >> >> err = usb_set_configuration(m_dev, 1);
> >> > 
> >> > * is '1' a valid configuration value?
> >> >   This value must by the config-descriptors 'bConfigurationValue'
> >> > * try usb_set_configuration(m_dev, 
dev->config[0].bConfigurationValue) 
> > 
> >> > 
> >> > Stephan
> >> > 
> >> > 
> >> >> 
> >> >> Hi,
> >> >> 
> >> >> the error message is
> >> >> "usb_set_configuration: could not set config 1: win error: The 
> > parameter 
> >> > is
> >> >> incorrect.".
> >> >> 
> >> >> Michael
> >> >> 
> >> >> 
> >> >> Stephan Meyer-2 wrote:
> >> >> > 
> >> >> > What's the error message returned
> >> >> > by usb_strerror()?
> >> >> > 
> >> >> > Stephan
> >> >> > 
> >> >> > 
> >> >> >> 
> >> >> >> Hi,
> >> >> >> 
> >> >> >> I have a VisualC++ 6.0-application (MFC) for Windows XP.
> >> >> >> This application is supposed to communicate with a 
microcontroller 
> > 
> >> > using
> >> >> >> Bulk writes over USB.
> >> >> >> With an older version of libusb (can't tell you the version, 
but 
> > it's 
> >> > 
> >> >> > from
> >> >> >> 05 August 2006) the application works fine. Now I downloaded 
the 
> >> > newest
> >> >> >> version of libusb (not the filter-driver!) and created a new 
> >> > inf-file.
> >> >> >> After installing the new driver the application does not work 
any 
> >> > more!
> >> >> >> The relevant code is:
> >> >> >> ---------------------------------------------------
> >> >> >> usb_init();
> >> >> >> usb_find_busses();
> >> >> >> usb_find_devices();
> >> >> >> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
> >> >> >> {
> >> >> >>    struct usb_device *dev;
> >> >> >>    for (dev = m_bus->devices; dev; dev = dev->next)
> >> >> >>    {
> >> >> >>       if (dev->descriptor.bDeviceClass == 0xff)   //find for 
> > vendor 
> >> >> >> specific class
> >> >> >>       {
> >> >> >>          m_dev = usb_open(dev);
> >> >> >>          if (m_dev)
> >> >> >>          {
> >> >> >>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
> >> >> >>             (dev->descriptor.idProduct == USB_PRODUCT))
> >> >> >>             {
> >> >> >>                int err;
> >> >> >>                err = usb_set_configuration(m_dev, 1);
> >> >> >>                if (err)
> >> >> >>                {
> >> >> >>                   char* s= usb_strerror();
> >> >> >>                   m_strInitStatus = s;
> >> >> >>                   UpdateData(FALSE);
> >> >> >>                   return;
> >> >> >>                }
> >> >> >>                err = usb_claim_interface(m_dev, 0);
> >> >> >>                if (err)
> >> >> >>                {
> >> >> >>                   char* s= usb_strerror();
> >> >> >>                   m_strInitStatus = s;
> >> >> >>                   UpdateData(FALSE);
> >> >> >>                   return;
> >> >> >>                }
> >> >> >>             }
> >> >> >>          }
> >> >> >>       }
> >> >> >>    }
> >> >> >> }
> >> >> >> 
> >> >> > 
> >> >> 
> >> > 
> >> 
> > 
> 
------------------------------------------------------------------------------------
> >> >> >> 
> >> >> >> With the new version of libusb the usb_set_configuration(...) 
call 
> > 
> >> >> > returns
> >> >> >> with an error and tells me, that configuration 1 could not be 
set 
> >> >> > because
> >> >> >> the parameter is invalid...
> >> >> >> If I use the new libusb0.dll, the new libusb.lib and the OLD 
> >> > libusb0.sys 
> >> >> > the
> >> >> >> application works fine again.
> >> >> >> 
> >> >> >> Can someone please tell me where I am going wrong?
> >> >> >> Thank you in advantage for your help
> >> >> >> -- 
> >> >> >> View this message in context: 
http://www.nabble.com/application-
> >> >> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> >> >> >> tf4770195.html#a13644735
> >> >> >> Sent from the LibUSB Dev - Win32 mailing list archive at 
> > Nabble.com.
> >> >> >> 
> >> >> >> 
> >> >> >> 
> >> >> > 
> >> > 
> > 
-------------------------------------------------------------------------
> >> >> >> This SF.net email is sponsored by: Splunk Inc.
> >> >> >> Still grepping through log files to find problems?  Stop.
> >> >> >> Now Search log events and configuration files using AJAX and a 
> >> > browser.
> >> >> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> >> >> _______________________________________________
> >> >> >> Libusb-win32-devel mailing list
> >> >> >> Lib...@li...
> >> >> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >> >> > 
> >> >> > 
> >> >> > 
> >> > 
> > 
-------------------------------------------------------------------------
> >> >> > This SF.net email is sponsored by: Splunk Inc.
> >> >> > Still grepping through log files to find problems?  Stop.
> >> >> > Now Search log events and configuration files using AJAX and a 
> >> > browser.
> >> >> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> >> > _______________________________________________
> >> >> > Libusb-win32-devel mailing list
> >> >> > Lib...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >> >> > 
> >> >> > 
> >> >> 
> >> >> -- 
> >> >> View this message in context: http://www.nabble.com/application-
> >> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> >> >> tf4770195.html#a13664629
> >> >> Sent from the LibUSB Dev - Win32 mailing list archive at 
Nabble.com.
> >> >> 
> >> >> 
> >> >> 
> >> > 
> > 
-------------------------------------------------------------------------
> >> >> This SF.net email is sponsored by: Splunk Inc.
> >> >> Still grepping through log files to find problems?  Stop.
> >> >> Now Search log events and configuration files using AJAX and a 
> > browser.
> >> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> >> _______________________________________________
> >> >> Libusb-win32-devel mailing list
> >> >> Lib...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >> > 
> >> > 
> >> > 
> > 
-------------------------------------------------------------------------
> >> > This SF.net email is sponsored by: Splunk Inc.
> >> > Still grepping through log files to find problems?  Stop.
> >> > Now Search log events and configuration files using AJAX and a 
> > browser.
> >> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> > _______________________________________________
> >> > Libusb-win32-devel mailing list
> >> > Lib...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context: http://www.nabble.com/application-
> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> >> tf4770195.html#a13665547
> >> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> >> 
> >> 
> >> 
> > 
-------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems?  Stop.
> >> Now Search log events and configuration files using AJAX and a 
browser.
> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> _______________________________________________
> >> Libusb-win32-devel mailing list
> >> Lib...@li...
> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > 
> > 
> > 
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a 
browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > 
> > 
> 
> -- 
> View this message in context: http://www.nabble.com/application-
> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> tf4770195.html#a13665771
> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> 
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

[Ampfing <Mic...@gm...>]

Well, since the application on the controller is not written by me I can't
give you the code. But I can post what TestLibUsb gives me:

  wTotalLength:         46
  bNumInterfaces:       1
  bConfigurationValue:  0
  iConfiguration:       0
  bmAttributes:         80h
  MaxPower:             50
    bInterfaceNumber:   0
    bAlternateSetting:  0
    bNumEndpoints:      4
    bInterfaceClass:    255
    bInterfaceSubClass: 0
    bInterfaceProtocol: 0
    iInterface:         0
      bEndpointAddress: 01h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 81h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 02h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 82h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0

As you can see, the bConfigurationValue is 0, not 1. Is that the problem?
And if it is, why does it work with the older version of the lib? Do I have
to change the value to 1 (which might be a problem as I can't flash the
controller...)?

Best regards



Stephan Meyer-2 wrote:
> 
> dev->config[0].bConfigurationValue should be >=1.
> Could you please post your configuration descriptor(s)?
> 
> Stephan
> 
>> 
>> Hi,
>> 
>> > is '1' a valid configuration value?
>> well, it should be as the application can be run with the older version 
> of
>> libusb...
>> I tried using your code and now the application runs over the
>> usb_set_configuration. But now the next call (the one to
>> usb_claim_interface()) returns an error...
>> Here is the message:
>> "usb_claim_interface: could not claim interface 0, invalid configuration 
> 0".
>> 
>> So as I understand configuration 0 is set by the set_configuration and 
> is
>> not valid. But why?? I mean it does work (with the older version of the
>> library)!
>> 
>> Thanks in advance
>> 
>> 
>> Stephan Meyer-2 wrote:
>> > 
>> >> err = usb_set_configuration(m_dev, 1);
>> > 
>> > * is '1' a valid configuration value?
>> >   This value must by the config-descriptors 'bConfigurationValue'
>> > * try usb_set_configuration(m_dev, dev->config[0].bConfigurationValue) 
> 
>> > 
>> > Stephan
>> > 
>> > 
>> >> 
>> >> Hi,
>> >> 
>> >> the error message is
>> >> "usb_set_configuration: could not set config 1: win error: The 
> parameter 
>> > is
>> >> incorrect.".
>> >> 
>> >> Michael
>> >> 
>> >> 
>> >> Stephan Meyer-2 wrote:
>> >> > 
>> >> > What's the error message returned
>> >> > by usb_strerror()?
>> >> > 
>> >> > Stephan
>> >> > 
>> >> > 
>> >> >> 
>> >> >> Hi,
>> >> >> 
>> >> >> I have a VisualC++ 6.0-application (MFC) for Windows XP.
>> >> >> This application is supposed to communicate with a microcontroller 
> 
>> > using
>> >> >> Bulk writes over USB.
>> >> >> With an older version of libusb (can't tell you the version, but 
> it's 
>> > 
>> >> > from
>> >> >> 05 August 2006) the application works fine. Now I downloaded the 
>> > newest
>> >> >> version of libusb (not the filter-driver!) and created a new 
>> > inf-file.
>> >> >> After installing the new driver the application does not work any 
>> > more!
>> >> >> The relevant code is:
>> >> >> ---------------------------------------------------
>> >> >> usb_init();
>> >> >> usb_find_busses();
>> >> >> usb_find_devices();
>> >> >> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
>> >> >> {
>> >> >>    struct usb_device *dev;
>> >> >>    for (dev = m_bus->devices; dev; dev = dev->next)
>> >> >>    {
>> >> >>       if (dev->descriptor.bDeviceClass == 0xff)   //find for 
> vendor 
>> >> >> specific class
>> >> >>       {
>> >> >>          m_dev = usb_open(dev);
>> >> >>          if (m_dev)
>> >> >>          {
>> >> >>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
>> >> >>             (dev->descriptor.idProduct == USB_PRODUCT))
>> >> >>             {
>> >> >>                int err;
>> >> >>                err = usb_set_configuration(m_dev, 1);
>> >> >>                if (err)
>> >> >>                {
>> >> >>                   char* s= usb_strerror();
>> >> >>                   m_strInitStatus = s;
>> >> >>                   UpdateData(FALSE);
>> >> >>                   return;
>> >> >>                }
>> >> >>                err = usb_claim_interface(m_dev, 0);
>> >> >>                if (err)
>> >> >>                {
>> >> >>                   char* s= usb_strerror();
>> >> >>                   m_strInitStatus = s;
>> >> >>                   UpdateData(FALSE);
>> >> >>                   return;
>> >> >>                }
>> >> >>             }
>> >> >>          }
>> >> >>       }
>> >> >>    }
>> >> >> }
>> >> >> 
>> >> > 
>> >> 
>> > 
>> 
> ------------------------------------------------------------------------------------
>> >> >> 
>> >> >> With the new version of libusb the usb_set_configuration(...) call 
> 
>> >> > returns
>> >> >> with an error and tells me, that configuration 1 could not be set 
>> >> > because
>> >> >> the parameter is invalid...
>> >> >> If I use the new libusb0.dll, the new libusb.lib and the OLD 
>> > libusb0.sys 
>> >> > the
>> >> >> application works fine again.
>> >> >> 
>> >> >> Can someone please tell me where I am going wrong?
>> >> >> Thank you in advantage for your help
>> >> >> -- 
>> >> >> View this message in context: http://www.nabble.com/application-
>> >> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
>> >> >> tf4770195.html#a13644735
>> >> >> Sent from the LibUSB Dev - Win32 mailing list archive at 
> Nabble.com.
>> >> >> 
>> >> >> 
>> >> >> 
>> >> > 
>> > 
> -------------------------------------------------------------------------
>> >> >> This SF.net email is sponsored by: Splunk Inc.
>> >> >> Still grepping through log files to find problems?  Stop.
>> >> >> Now Search log events and configuration files using AJAX and a 
>> > browser.
>> >> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> >> >> _______________________________________________
>> >> >> Libusb-win32-devel mailing list
>> >> >> Lib...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>> >> > 
>> >> > 
>> >> > 
>> > 
> -------------------------------------------------------------------------
>> >> > This SF.net email is sponsored by: Splunk Inc.
>> >> > Still grepping through log files to find problems?  Stop.
>> >> > Now Search log events and configuration files using AJAX and a 
>> > browser.
>> >> > Download your FREE copy of Splunk now >> http://get.splunk.com/
>> >> > _______________________________________________
>> >> > Libusb-win32-devel mailing list
>> >> > Lib...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>> >> > 
>> >> > 
>> >> 
>> >> -- 
>> >> View this message in context: http://www.nabble.com/application-
>> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
>> >> tf4770195.html#a13664629
>> >> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
>> >> 
>> >> 
>> >> 
>> > 
> -------------------------------------------------------------------------
>> >> This SF.net email is sponsored by: Splunk Inc.
>> >> Still grepping through log files to find problems?  Stop.
>> >> Now Search log events and configuration files using AJAX and a 
> browser.
>> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> >> _______________________________________________
>> >> Libusb-win32-devel mailing list
>> >> Lib...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>> > 
>> > 
>> > 
> -------------------------------------------------------------------------
>> > This SF.net email is sponsored by: Splunk Inc.
>> > Still grepping through log files to find problems?  Stop.
>> > Now Search log events and configuration files using AJAX and a 
> browser.
>> > Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > _______________________________________________
>> > Libusb-win32-devel mailing list
>> > Lib...@li...
>> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>> > 
>> > 
>> 
>> -- 
>> View this message in context: http://www.nabble.com/application-
>> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
>> tf4770195.html#a13665547
>> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
>> 
>> 
>> 
> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/application-works-with-older-libusb-win32-but-not-with-version-0.1.12.1-tf4770195.html#a13665771
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

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

dev->config[0].bConfigurationValue should be >=1.
Could you please post your configuration descriptor(s)?

Stephan

> 
> Hi,
> 
> > is '1' a valid configuration value?
> well, it should be as the application can be run with the older version 
of
> libusb...
> I tried using your code and now the application runs over the
> usb_set_configuration. But now the next call (the one to
> usb_claim_interface()) returns an error...
> Here is the message:
> "usb_claim_interface: could not claim interface 0, invalid configuration 
0".
> 
> So as I understand configuration 0 is set by the set_configuration and 
is
> not valid. But why?? I mean it does work (with the older version of the
> library)!
> 
> Thanks in advance
> 
> 
> Stephan Meyer-2 wrote:
> > 
> >> err = usb_set_configuration(m_dev, 1);
> > 
> > * is '1' a valid configuration value?
> >   This value must by the config-descriptors 'bConfigurationValue'
> > * try usb_set_configuration(m_dev, dev->config[0].bConfigurationValue) 

> > 
> > Stephan
> > 
> > 
> >> 
> >> Hi,
> >> 
> >> the error message is
> >> "usb_set_configuration: could not set config 1: win error: The 
parameter 
> > is
> >> incorrect.".
> >> 
> >> Michael
> >> 
> >> 
> >> Stephan Meyer-2 wrote:
> >> > 
> >> > What's the error message returned
> >> > by usb_strerror()?
> >> > 
> >> > Stephan
> >> > 
> >> > 
> >> >> 
> >> >> Hi,
> >> >> 
> >> >> I have a VisualC++ 6.0-application (MFC) for Windows XP.
> >> >> This application is supposed to communicate with a microcontroller 

> > using
> >> >> Bulk writes over USB.
> >> >> With an older version of libusb (can't tell you the version, but 
it's 
> > 
> >> > from
> >> >> 05 August 2006) the application works fine. Now I downloaded the 
> > newest
> >> >> version of libusb (not the filter-driver!) and created a new 
> > inf-file.
> >> >> After installing the new driver the application does not work any 
> > more!
> >> >> The relevant code is:
> >> >> ---------------------------------------------------
> >> >> usb_init();
> >> >> usb_find_busses();
> >> >> usb_find_devices();
> >> >> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
> >> >> {
> >> >>    struct usb_device *dev;
> >> >>    for (dev = m_bus->devices; dev; dev = dev->next)
> >> >>    {
> >> >>       if (dev->descriptor.bDeviceClass == 0xff)   //find for 
vendor 
> >> >> specific class
> >> >>       {
> >> >>          m_dev = usb_open(dev);
> >> >>          if (m_dev)
> >> >>          {
> >> >>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
> >> >>             (dev->descriptor.idProduct == USB_PRODUCT))
> >> >>             {
> >> >>                int err;
> >> >>                err = usb_set_configuration(m_dev, 1);
> >> >>                if (err)
> >> >>                {
> >> >>                   char* s= usb_strerror();
> >> >>                   m_strInitStatus = s;
> >> >>                   UpdateData(FALSE);
> >> >>                   return;
> >> >>                }
> >> >>                err = usb_claim_interface(m_dev, 0);
> >> >>                if (err)
> >> >>                {
> >> >>                   char* s= usb_strerror();
> >> >>                   m_strInitStatus = s;
> >> >>                   UpdateData(FALSE);
> >> >>                   return;
> >> >>                }
> >> >>             }
> >> >>          }
> >> >>       }
> >> >>    }
> >> >> }
> >> >> 
> >> > 
> >> 
> > 
> 
------------------------------------------------------------------------------------
> >> >> 
> >> >> With the new version of libusb the usb_set_configuration(...) call 

> >> > returns
> >> >> with an error and tells me, that configuration 1 could not be set 
> >> > because
> >> >> the parameter is invalid...
> >> >> If I use the new libusb0.dll, the new libusb.lib and the OLD 
> > libusb0.sys 
> >> > the
> >> >> application works fine again.
> >> >> 
> >> >> Can someone please tell me where I am going wrong?
> >> >> Thank you in advantage for your help
> >> >> -- 
> >> >> View this message in context: http://www.nabble.com/application-
> >> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> >> >> tf4770195.html#a13644735
> >> >> Sent from the LibUSB Dev - Win32 mailing list archive at 
Nabble.com.
> >> >> 
> >> >> 
> >> >> 
> >> > 
> > 
-------------------------------------------------------------------------
> >> >> This SF.net email is sponsored by: Splunk Inc.
> >> >> Still grepping through log files to find problems?  Stop.
> >> >> Now Search log events and configuration files using AJAX and a 
> > browser.
> >> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> >> _______________________________________________
> >> >> Libusb-win32-devel mailing list
> >> >> Lib...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >> > 
> >> > 
> >> > 
> > 
-------------------------------------------------------------------------
> >> > This SF.net email is sponsored by: Splunk Inc.
> >> > Still grepping through log files to find problems?  Stop.
> >> > Now Search log events and configuration files using AJAX and a 
> > browser.
> >> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> > _______________________________________________
> >> > Libusb-win32-devel mailing list
> >> > Lib...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context: http://www.nabble.com/application-
> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> >> tf4770195.html#a13664629
> >> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> >> 
> >> 
> >> 
> > 
-------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems?  Stop.
> >> Now Search log events and configuration files using AJAX and a 
browser.
> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> _______________________________________________
> >> Libusb-win32-devel mailing list
> >> Lib...@li...
> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > 
> > 
> > 
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a 
browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > 
> > 
> 
> -- 
> View this message in context: http://www.nabble.com/application-
> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> tf4770195.html#a13665547
> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> 
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

[Ampfing <Mic...@gm...>]

Hi,

> is '1' a valid configuration value?
well, it should be as the application can be run with the older version of
libusb...
I tried using your code and now the application runs over the
usb_set_configuration. But now the next call (the one to
usb_claim_interface()) returns an error...
Here is the message:
"usb_claim_interface: could not claim interface 0, invalid configuration 0".

So as I understand configuration 0 is set by the set_configuration and is
not valid. But why?? I mean it does work (with the older version of the
library)!

Thanks in advance


Stephan Meyer-2 wrote:
> 
>> err = usb_set_configuration(m_dev, 1);
> 
> * is '1' a valid configuration value?
>   This value must by the config-descriptors 'bConfigurationValue'
> * try usb_set_configuration(m_dev, dev->config[0].bConfigurationValue) 
> 
> Stephan
> 
> 
>> 
>> Hi,
>> 
>> the error message is
>> "usb_set_configuration: could not set config 1: win error: The parameter 
> is
>> incorrect.".
>> 
>> Michael
>> 
>> 
>> Stephan Meyer-2 wrote:
>> > 
>> > What's the error message returned
>> > by usb_strerror()?
>> > 
>> > Stephan
>> > 
>> > 
>> >> 
>> >> Hi,
>> >> 
>> >> I have a VisualC++ 6.0-application (MFC) for Windows XP.
>> >> This application is supposed to communicate with a microcontroller 
> using
>> >> Bulk writes over USB.
>> >> With an older version of libusb (can't tell you the version, but it's 
> 
>> > from
>> >> 05 August 2006) the application works fine. Now I downloaded the 
> newest
>> >> version of libusb (not the filter-driver!) and created a new 
> inf-file.
>> >> After installing the new driver the application does not work any 
> more!
>> >> The relevant code is:
>> >> ---------------------------------------------------
>> >> usb_init();
>> >> usb_find_busses();
>> >> usb_find_devices();
>> >> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
>> >> {
>> >>    struct usb_device *dev;
>> >>    for (dev = m_bus->devices; dev; dev = dev->next)
>> >>    {
>> >>       if (dev->descriptor.bDeviceClass == 0xff)   //find for vendor 
>> >> specific class
>> >>       {
>> >>          m_dev = usb_open(dev);
>> >>          if (m_dev)
>> >>          {
>> >>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
>> >>             (dev->descriptor.idProduct == USB_PRODUCT))
>> >>             {
>> >>                int err;
>> >>                err = usb_set_configuration(m_dev, 1);
>> >>                if (err)
>> >>                {
>> >>                   char* s= usb_strerror();
>> >>                   m_strInitStatus = s;
>> >>                   UpdateData(FALSE);
>> >>                   return;
>> >>                }
>> >>                err = usb_claim_interface(m_dev, 0);
>> >>                if (err)
>> >>                {
>> >>                   char* s= usb_strerror();
>> >>                   m_strInitStatus = s;
>> >>                   UpdateData(FALSE);
>> >>                   return;
>> >>                }
>> >>             }
>> >>          }
>> >>       }
>> >>    }
>> >> }
>> >> 
>> > 
>> 
> ------------------------------------------------------------------------------------
>> >> 
>> >> With the new version of libusb the usb_set_configuration(...) call 
>> > returns
>> >> with an error and tells me, that configuration 1 could not be set 
>> > because
>> >> the parameter is invalid...
>> >> If I use the new libusb0.dll, the new libusb.lib and the OLD 
> libusb0.sys 
>> > the
>> >> application works fine again.
>> >> 
>> >> Can someone please tell me where I am going wrong?
>> >> Thank you in advantage for your help
>> >> -- 
>> >> View this message in context: http://www.nabble.com/application-
>> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
>> >> tf4770195.html#a13644735
>> >> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
>> >> 
>> >> 
>> >> 
>> > 
> -------------------------------------------------------------------------
>> >> This SF.net email is sponsored by: Splunk Inc.
>> >> Still grepping through log files to find problems?  Stop.
>> >> Now Search log events and configuration files using AJAX and a 
> browser.
>> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> >> _______________________________________________
>> >> Libusb-win32-devel mailing list
>> >> Lib...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>> > 
>> > 
>> > 
> -------------------------------------------------------------------------
>> > This SF.net email is sponsored by: Splunk Inc.
>> > Still grepping through log files to find problems?  Stop.
>> > Now Search log events and configuration files using AJAX and a 
> browser.
>> > Download your FREE copy of Splunk now >> http://get.splunk.com/
>> > _______________________________________________
>> > Libusb-win32-devel mailing list
>> > Lib...@li...
>> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>> > 
>> > 
>> 
>> -- 
>> View this message in context: http://www.nabble.com/application-
>> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
>> tf4770195.html#a13664629
>> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
>> 
>> 
>> 
> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/application-works-with-older-libusb-win32-but-not-with-version-0.1.12.1-tf4770195.html#a13665547
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

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

> err = usb_set_configuration(m_dev, 1);

* is '1' a valid configuration value?
  This value must by the config-descriptors 'bConfigurationValue'
* try usb_set_configuration(m_dev, dev->config[0].bConfigurationValue) 

Stephan


> 
> Hi,
> 
> the error message is
> "usb_set_configuration: could not set config 1: win error: The parameter 
is
> incorrect.".
> 
> Michael
> 
> 
> Stephan Meyer-2 wrote:
> > 
> > What's the error message returned
> > by usb_strerror()?
> > 
> > Stephan
> > 
> > 
> >> 
> >> Hi,
> >> 
> >> I have a VisualC++ 6.0-application (MFC) for Windows XP.
> >> This application is supposed to communicate with a microcontroller 
using
> >> Bulk writes over USB.
> >> With an older version of libusb (can't tell you the version, but it's 

> > from
> >> 05 August 2006) the application works fine. Now I downloaded the 
newest
> >> version of libusb (not the filter-driver!) and created a new 
inf-file.
> >> After installing the new driver the application does not work any 
more!
> >> The relevant code is:
> >> ---------------------------------------------------
> >> usb_init();
> >> usb_find_busses();
> >> usb_find_devices();
> >> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
> >> {
> >>    struct usb_device *dev;
> >>    for (dev = m_bus->devices; dev; dev = dev->next)
> >>    {
> >>       if (dev->descriptor.bDeviceClass == 0xff)   //find for vendor 
> >> specific class
> >>       {
> >>          m_dev = usb_open(dev);
> >>          if (m_dev)
> >>          {
> >>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
> >>             (dev->descriptor.idProduct == USB_PRODUCT))
> >>             {
> >>                int err;
> >>                err = usb_set_configuration(m_dev, 1);
> >>                if (err)
> >>                {
> >>                   char* s= usb_strerror();
> >>                   m_strInitStatus = s;
> >>                   UpdateData(FALSE);
> >>                   return;
> >>                }
> >>                err = usb_claim_interface(m_dev, 0);
> >>                if (err)
> >>                {
> >>                   char* s= usb_strerror();
> >>                   m_strInitStatus = s;
> >>                   UpdateData(FALSE);
> >>                   return;
> >>                }
> >>             }
> >>          }
> >>       }
> >>    }
> >> }
> >> 
> > 
> 
------------------------------------------------------------------------------------
> >> 
> >> With the new version of libusb the usb_set_configuration(...) call 
> > returns
> >> with an error and tells me, that configuration 1 could not be set 
> > because
> >> the parameter is invalid...
> >> If I use the new libusb0.dll, the new libusb.lib and the OLD 
libusb0.sys 
> > the
> >> application works fine again.
> >> 
> >> Can someone please tell me where I am going wrong?
> >> Thank you in advantage for your help
> >> -- 
> >> View this message in context: http://www.nabble.com/application-
> >> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> >> tf4770195.html#a13644735
> >> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> >> 
> >> 
> >> 
> > 
-------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems?  Stop.
> >> Now Search log events and configuration files using AJAX and a 
browser.
> >> Download your FREE copy of Splunk now >> http://get.splunk.com/
> >> _______________________________________________
> >> Libusb-win32-devel mailing list
> >> Lib...@li...
> >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > 
> > 
> > 
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a 
browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > 
> > 
> 
> -- 
> View this message in context: http://www.nabble.com/application-
> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> tf4770195.html#a13664629
> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> 
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

[Ampfing <Mic...@gm...>]

Hi,

the error message is
"usb_set_configuration: could not set config 1: win error: The parameter is
incorrect.".

Michael


Stephan Meyer-2 wrote:
> 
> What's the error message returned
> by usb_strerror()?
> 
> Stephan
> 
> 
>> 
>> Hi,
>> 
>> I have a VisualC++ 6.0-application (MFC) for Windows XP.
>> This application is supposed to communicate with a microcontroller using
>> Bulk writes over USB.
>> With an older version of libusb (can't tell you the version, but it's 
> from
>> 05 August 2006) the application works fine. Now I downloaded the newest
>> version of libusb (not the filter-driver!) and created a new inf-file.
>> After installing the new driver the application does not work any more!
>> The relevant code is:
>> ---------------------------------------------------
>> usb_init();
>> usb_find_busses();
>> usb_find_devices();
>> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
>> {
>>    struct usb_device *dev;
>>    for (dev = m_bus->devices; dev; dev = dev->next)
>>    {
>>       if (dev->descriptor.bDeviceClass == 0xff)   //find for vendor 
>> specific class
>>       {
>>          m_dev = usb_open(dev);
>>          if (m_dev)
>>          {
>>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
>>             (dev->descriptor.idProduct == USB_PRODUCT))
>>             {
>>                int err;
>>                err = usb_set_configuration(m_dev, 1);
>>                if (err)
>>                {
>>                   char* s= usb_strerror();
>>                   m_strInitStatus = s;
>>                   UpdateData(FALSE);
>>                   return;
>>                }
>>                err = usb_claim_interface(m_dev, 0);
>>                if (err)
>>                {
>>                   char* s= usb_strerror();
>>                   m_strInitStatus = s;
>>                   UpdateData(FALSE);
>>                   return;
>>                }
>>             }
>>          }
>>       }
>>    }
>> }
>> 
> ------------------------------------------------------------------------------------
>> 
>> With the new version of libusb the usb_set_configuration(...) call 
> returns
>> with an error and tells me, that configuration 1 could not be set 
> because
>> the parameter is invalid...
>> If I use the new libusb0.dll, the new libusb.lib and the OLD libusb0.sys 
> the
>> application works fine again.
>> 
>> Can someone please tell me where I am going wrong?
>> Thank you in advantage for your help
>> -- 
>> View this message in context: http://www.nabble.com/application-
>> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
>> tf4770195.html#a13644735
>> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
>> 
>> 
>> 
> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/application-works-with-older-libusb-win32-but-not-with-version-0.1.12.1-tf4770195.html#a13664629
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

Re: [Libusb-win32-devel] Antwort: 64-bit support

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

Stephan Meyer wrote:

> It's not possible to sign just a driver (.sys file).
> You always have to sign the combination of the driver and the device
> specific .inf file. 

Since Microsoft seem to have at least shifted their policy to
allow companies other than themselves to sign drivers ("Self-Signing"),
this seems more feasible that it once was, but it's still
a significant barrier to non-commercial developers.

Is there any distinction between how unsigned .sys and
unsigned .inf files are handled ?

As I understand it, the administrator simply cannot load an
unsigned .sys file, unless the operating system has
been booted up with some special flags that permit this.

Does anyone know if the same apply to .inf files, or is it
merely that the administrator will get an warning/OK dialog for
an unsigned .inf file ?

If not, then there seems less point in continuing to develop
a winusb.sys version of libusb-win32.

Graeme Gill.

Re: [Libusb-win32-devel] libusb-win32 webpage and wiki

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

Thank's for the suggestion. I wasn't aware of the fact
that Sourceforge added a Wiki to their services.
I'll activate it, transfer the content, and redirect
the old site to the wiki.

Stephan


> libusb-win32 web site seems to stay in 2004 and now it is
> 2007. It might be a good idea to remove the news section
> and update the other sections.
> 
> It seems to me a libusb-win32 wiki will also help to remove the
> burden of the developer on many beginner questions.
> 
> In the wiki, there can be a FAQ section, document section,
> example section, wrapper section (python, perl, ruby, etc).
> Users can also be redirected to basic USB sites.
> The differences between libusb-win32 and libusb can also be
> pointed out. It can also include the future development of
> libusb-win32 1.0.
> 
> Actually this may also help experienced users of libusb.
> 
> How do you like the idea? I can not help coding since
> I do not know much about coding but I (and many others)
> can help on the wiki side.
> 
> Sourceforge supports wiki feature.
> http://sourceforge.net/docman/display_doc.php?docid=1881&group_id=1
> 
> I am involved in Piklab project and the wiki is kind of useful.
> Example:
> http://piklab.sourceforge.net/wiki/index.php/USB_port_problems
> 
> By the way, the OpenUSB project just opens an empty
> wiki after my suggestion.
> http://openusb.wiki.sourceforge.net/
> 
> Xiaofan
> http://mcuee.blogspot.com
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] Antwort: 64-bit support

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

> Hi all,
> 
> I know this is an oft asked question, but I did some searching on the
> mailing list and did not find very clear answers to a few questions
> that I had.  I'd appreciate if anyone here can help clarify these
> issues for me:
> 
> 1) What is the build process for a 64-bit version of libusb-win32?
> There were no clear steps that I saw.  Does a DDK have to be
> installed?  Which one?  What compiler is to be used?  A short bullet
> list of what to do here would be much appreciated.

* install the latest DDK
* open a DDK 64bit build environment
* download libusb-win32's latest sources
* navigate to the ddk_make folder
* run make_all.bat from the DDK's build environment

> 
> 2) If I do build the 64-bit version of the sys and dll, can I use the
> unaltered 32-bit version of the dll for use by 32-bit applications on
> the 64-bit OS?

Yes you can. Just copy the 32bit DLL to Windows' 'syswow64' folder.

> 
> 3) I have read in numerous posts that the 64-bit libusb-win32 will not
> work on Vista 64 due to the lack of a signed driver.  It seems that as
> long as I have a VeriSign certificate, I should be able to sign the
> driver.  Has anyone tried this and been able to use libusb-win32 on a
> Vista 64 machine as a result?

I haven't tested this yet.

> 
> 4) I know there is an effort to move to winusb.sys but it seems like
> progress on this has been slow.  Is there a way the libusb-win32 can
> have a stop gap in the meantime?  For example, is the libusb-win32
> development team open to having a company sponsor the fees required to
> obtaining a VeriSign certificate so that any future released versions
> of the libusb-win32 64-bit drivers are properly signed?

It's not possible to sign just a driver (.sys file).
You always have to sign the combination of the driver and the device
specific .inf file. 

> 
> I look forward to some information on this topic.  Thank you in advance.
> 
> Best regards,
> Paarvai
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 18, Issue 3

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

See 
http://www.nabble.com/-Libusb-win32-devel--HID-device-problem-tf2149995.html#a6006965

Stephan



> Hi Xiaofan,
> 
> I tried your command line suggestion, but after I hit enter, nothing
> happens, and I got the prompt back.  How do I debug if there is a 
> problem with installation?  Below is my inf file; would you please 
> have a look to see if I made anything obviously wrong/ 
> 
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> ;C:\Program Files\SlimLinePcuDriver\driver>rundll32 libusb0.dll,
> usb_install_driver_np_rundll sl_tpcu.inf 
> 
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> 
> [Version]
> Signature = "$Chicago$"
> provider  = %manufacturer%
> DriverVer = 03/09/2005,0.1.10.1
> CatalogFile = sl_tpcu.cat
> 
> Class = LibUsbDevices
> ClassGUID = {EB781AAF-9C70-4523-A5DF-642A87ECA567}
> 
> [ClassInstall]
> AddReg=ClassInstall.AddReg 
> 
> [ClassInstall32]
> AddReg=ClassInstall.AddReg
> 
> [ClassInstall.AddReg]
> HKR,,,,"LibUSB-Win32 Devices"
> HKR,,Icon,,"-20"
> 
> [Manufacturer]
> %manufacturer%=Devices
> 
> 
;-------------------------------------------------------------------------- 

> ; Files
> 
;--------------------------------------------------------------------------
> 
> [SourceDisksNames]
> 1 = "Libusb-Win32 Driver Installation Disk",,
> 
> [SourceDisksFiles]
> libusb0.sys = 1,, 
> libusb0.dll = 1,,
> 
> [DestinationDirs]
> LIBUSB.Files.Sys = 10,System32\Drivers
> LIBUSB.Files.Dll = 10,System32
> 
> [LIBUSB.Files.Sys]
> libusb0.sys
> 
> [LIBUSB.Files.Dll]
> libusb0.dll
> 
> 
;-------------------------------------------------------------------------- 

> ; Device driver
> 
;--------------------------------------------------------------------------
> 
> [LIBUSB_DEV]
> CopyFiles = LIBUSB.Files.Sys, LIBUSB.Files.Dll
> AddReg    = LIBUSB_DEV.AddReg
> 
> [LIBUSB_DEV.NT] 
> CopyFiles = LIBUSB.Files.Sys, LIBUSB.Files.Dll
> 
> [LIBUSB_DEV.HW]
> DelReg = LIBUSB_DEV.DelReg.HW
> 
> [LIBUSB_DEV.NT.HW]
> DelReg = LIBUSB_DEV.DelReg.HW
> 
> [LIBUSB_DEV.NT.Services]
> AddService = libusb0, 0x00000002, LIBUSB.AddService
> 
> [LIBUSB_DEV.AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,libusb0.sys
> 
> [LIBUSB_DEV.DelReg.HW]
> HKR,,"LowerFilters"
> 
> 
;-------------------------------------------------------------------------- 

> ; Services
> 
;--------------------------------------------------------------------------
> 
> [LIBUSB.AddService]
> DisplayName    = "LibUsb-Win32 - Kernel Driver 03/09/2005, 0.1.10.1 "
> ServiceType    = 1
> StartType      = 3
> ErrorControl   = 0
> ServiceBinary  = %12%\libusb0.sys
> 
> 
;--------------------------------------------------------------------------
> ; Devices
> 
;-------------------------------------------------------------------------- 

> 
> [Devices]
> "SlimLine TPCU_xx Keyboard"=LIBUSB_DEV, USB\VID_0471&PID_0206
> ;"SlimLine TPCU_xx Keyboard"=LIBUSB_DEV, 
USB\VID_0471&PID_0206&Rev_0000&Col01
> ;"SlimLine TPCU_xx Mouse"=LIBUSB_DEV, 
USB\VID_0471&PID_0206&Rev_0000&Col02 
> ;"SlimLine TPCU_xx Joystic"=LIBUSB_DEV, 
USB\VID_0471&PID_0206&Rev_0000&Col03
> 
> [Strings]
> manufacturer = "Thales Avionics"
> 
> 
> 
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> 
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> Thank you very much for your help
> 
> Vu
> 
> On Nov 7, 2007 12:05 PM, < 
lib...@li...
> > wrote:
> Send Libusb-win32-devel mailing list submissions to
>        lib...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit 
>        https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> or, via email, send a message with subject or body 'help' to 
>        lib...@li...
> 
> You can reach the person managing the list at
>         lib...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Libusb-win32-devel digest..."
> 
> 
> Today's Topics: 
> 
>   1. Re: Libusb-win32-devel Digest, Vol 17, Issue 4 (Vu Nguyen)
>   2. Re: Libusb-win32-devel Digest, Vol 17, Issue 4 (Xiaofan Chen)
> 
> 
> ---------------------------------------------------------------------- 
> 
> Message: 1
> Date: Tue, 6 Nov 2007 18:17:59 -0800
> From: "Vu Nguyen" <vu...@gm...>
> Subject: Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 17, 
>        Issue 4
> To: lib...@li...
> Message-ID:
>        < 935...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi Xiaofan,
> 
> It has been a while since I got your answer;  My device is a HID 
keyboard 
> and mouse device;  I tried to update the driver as you suggested with 
the
> INF file I created, but WindowsXP does not take my INF file;
> I used innoSetup to install the libUsb driver also;
> I also looked at the device manager for it HW ID and match that in the 
INF 
> file, but nothing works;
> Is there something I missed?
> 
> Thank you in advance.
> 
> Vu
> 
> 
> > > On 10/3/07, Vu Nguyen <vu...@gm...> wrote:
> > > > I have a hid keyboard device running windowsXP with libusb version 

> > > 0.1.12.1;
> > > > I need to send vendor specific command to my device;
> > > >
> > > > I tried to claim the interface so I called the 
usb_set_configuration() 
> > > > function first.  it hangs and never returns;
> > >
> > > You need to use device driver and not the filter driver,
> > > which means you have to "update" the HID driver to
> > > the libusb-win32 driver. Therefore you lose the function
> > > of using the original application.
> > >
> > > The new libusb1 development version will have an HID
> > > backend and will solve this problem. However it is not 
> > > working yet.
> > >
> > > Xiaofan
> > >
> > >
> > >
> > > ------------------------------
> > >
> > >
> > 
------------------------------------------------------------------------- 
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a 
browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > >
> > > ------------------------------
> > >
> > > _______________________________________________
> > > Libusb-win32-devel mailing list 
> > > Lib...@li...
> > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel 
> > >
> > >
> > > End of Libusb-win32-devel Digest, Vol 17, Issue 3
> > > *************************************************
> > >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> >
> > ------------------------------
> >
> > 
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. 
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a 
browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> >
> > ------------------------------
> >
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >
> >
> > End of Libusb-win32-devel Digest, Vol 17, Issue 4
> > *************************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> 
> ------------------------------ 
> 
> Message: 2
> Date: Wed, 7 Nov 2007 11:02:40 +0800
> From: "Xiaofan Chen" <xia...@gm...>
> Subject: Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 17, 
>        Issue 4
> To: lib...@li...
> Message-ID:
>        < a27...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On 11/7/07, Vu Nguyen <vu...@gm...> wrote:
> > It has been a while since I got your answer;  My device is a HID 
keyboard 
> > and mouse device;  I tried to update the driver as you suggested with 
the
> > INF file I created, but WindowsXP does not take my INF file;
> > I used innoSetup to install the libUsb driver also;
> > I also looked at the device manager for it HW ID and match that in the 
INF 
> > file, but nothing works;
> > Is there something I missed?
> >
> >
> 
> Last time I had some problems with PICkit 2 as well since Windows
> does not like the INF file generated by the INF wizard.
> 
> Stephan taught me to use the following and it worked. You can try
> to install/update the driver by using the DLL's (undocumented)
> usb_install_driver_np function?
> 
> You can call it from the command line through its rundll interface 
> rundll32 libusb0.dll,usb_install_driver_np_rundll your_inf_file.inf
> 
> Try it and see if this works for you.
> 
> Regards,
> Xiaofan
> http://mcuee.blogspot.com 
> 
> 
> ---------- Forwarded message ----------
> From: Stephan Meyer <ste...@we...>
> Date: Aug 25, 2006 1:22 AM
> Subject: Re: [Libusb-win32-devel] HID device problem 
> To: lib...@li...
> 
> 
> 
> Have you tried to install/update the driver by using the DLL's
> (undocumented) usb_install_driver_np function? 
> 
> You can call it from the command line through its rundll interface:
> 
> rundll32 libusb0.dll,usb_install_driver_np_rundll your_inf_file.inf
> 
> 
> 
> ------------------------------
> 
> 
------------------------------------------------------------------------- 
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> 
> ------------------------------
> 
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 
> End of Libusb-win32-devel Digest, Vol 18, Issue 3 
> *************************************************
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

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

What's the error message returned
by usb_strerror()?

Stephan


> 
> Hi,
> 
> I have a VisualC++ 6.0-application (MFC) for Windows XP.
> This application is supposed to communicate with a microcontroller using
> Bulk writes over USB.
> With an older version of libusb (can't tell you the version, but it's 
from
> 05 August 2006) the application works fine. Now I downloaded the newest
> version of libusb (not the filter-driver!) and created a new inf-file.
> After installing the new driver the application does not work any more!
> The relevant code is:
> ---------------------------------------------------
> usb_init();
> usb_find_busses();
> usb_find_devices();
> for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
> {
>    struct usb_device *dev;
>    for (dev = m_bus->devices; dev; dev = dev->next)
>    {
>       if (dev->descriptor.bDeviceClass == 0xff)   //find for vendor 
> specific class
>       {
>          m_dev = usb_open(dev);
>          if (m_dev)
>          {
>             if ((dev->descriptor.idVendor == USB_VENDOR) && 
>             (dev->descriptor.idProduct == USB_PRODUCT))
>             {
>                int err;
>                err = usb_set_configuration(m_dev, 1);
>                if (err)
>                {
>                   char* s= usb_strerror();
>                   m_strInitStatus = s;
>                   UpdateData(FALSE);
>                   return;
>                }
>                err = usb_claim_interface(m_dev, 0);
>                if (err)
>                {
>                   char* s= usb_strerror();
>                   m_strInitStatus = s;
>                   UpdateData(FALSE);
>                   return;
>                }
>             }
>          }
>       }
>    }
> }
> 
------------------------------------------------------------------------------------
> 
> With the new version of libusb the usb_set_configuration(...) call 
returns
> with an error and tells me, that configuration 1 could not be set 
because
> the parameter is invalid...
> If I use the new libusb0.dll, the new libusb.lib and the OLD libusb0.sys 
the
> application works fine again.
> 
> Can someone please tell me where I am going wrong?
> Thank you in advantage for your help
> -- 
> View this message in context: http://www.nabble.com/application-
> works-with-older-libusb-win32-but-not-with-version-0.1.12.1-
> tf4770195.html#a13644735
> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
> 
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] application works with older libusb-win32 but not with version 0.1.12.1

[Ampfing <Mic...@gm...>]

Hi,

I have a VisualC++ 6.0-application (MFC) for Windows XP.
This application is supposed to communicate with a microcontroller using
Bulk writes over USB.
With an older version of libusb (can't tell you the version, but it's from
05 August 2006) the application works fine. Now I downloaded the newest
version of libusb (not the filter-driver!) and created a new inf-file.
After installing the new driver the application does not work any more!
The relevant code is:
---------------------------------------------------
usb_init();
usb_find_busses();
usb_find_devices();
for (m_bus = usb_get_busses(); m_bus; m_bus = m_bus->next)
{
	struct usb_device *dev;
	for (dev = m_bus->devices; dev; dev = dev->next)
	{
		if (dev->descriptor.bDeviceClass == 0xff)	//find for vendor specific class
		{
			m_dev = usb_open(dev);
			if (m_dev)
			{
				if ((dev->descriptor.idVendor == USB_VENDOR) && 
				(dev->descriptor.idProduct == USB_PRODUCT))
				{
					int err;
					err = usb_set_configuration(m_dev, 1);
					if (err)
					{
						char* s= usb_strerror();
						m_strInitStatus = s;
						UpdateData(FALSE);
						return;
					}
					err = usb_claim_interface(m_dev, 0);
					if (err)
					{
						char* s= usb_strerror();
						m_strInitStatus = s;
						UpdateData(FALSE);
						return;
					}
				}
			}
		}
	}
}
------------------------------------------------------------------------------------

With the new version of libusb the usb_set_configuration(...) call returns
with an error and tells me, that configuration 1 could not be set because
the parameter is invalid...
If I use the new libusb0.dll, the new libusb.lib and the OLD libusb0.sys the
application works fine again.

Can someone please tell me where I am going wrong?
Thank you in advantage for your help
-- 
View this message in context: http://www.nabble.com/application-works-with-older-libusb-win32-but-not-with-version-0.1.12.1-tf4770195.html#a13644735
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.