libusb-win32-devel

[Libusb-win32-devel] Question about unique ID

[michel m. <mic...@gm...>]

Hi  , this is a real USB newbie question ,

Is it possible to talk to a particular usb port on a hub instead of a device
?

Or is it possible to locate an attached device during enumeration to track
the changes on this port ?

Can this be done with libusbWin32 ?

Thanks

-- 
%<------------------------------------------------------->%
Michel memeteau
VOIP: sip:174...@pr...
0491886375 0624808051
jabber/GoogleTalk : fre...@ja...

Re: [Libusb-win32-devel] Windows 2000 and Vista support

[Bertrik S. <be...@si...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephan Meyer wrote:
>>> You are right, Vista-64bit won't let you install unsigned drivers. 
>>> This means that this platform is currently not supported.
>>> To resolve this issue, future versions of libusb-win32 will use Vistas 
>>> built-in kernel driver winusb.sys.
>> Ok, I wanted to propose the UMDF, but obviously, you are already aware
>> of it.
>>
>> As I wrote you in my private mail, I am no specialist in USB. OTOH, I
>> already wanted to start working with UMDF and KMDF myself.
>>
>> Thus, if you need any help in porting the driver, feel free to ask me.
>> If time permits, I will try to help you, if you want.
>>
> 
> Thanks, but it won't be necessary to port any kernel driver code since the 
> new DLL will use winusb.sys directly without UMDF, KMDF, or any other 
> useless stuff that Microsoft introduced recently.

I won't mind help testing that (no matter how beta).
I have some experience debugging USB stuff and I also have a
microcontroller board available (LPC2148) that I can program as
basically any kind of USB device for testing.
(USB 2.0 full-speed only, isochronous currently not supported).

Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGBoVQETD6mlrWxPURAg6NAJ95RSoteQRnwKGKj1XJcnIQo1/fKACgufDl
U/41NwT0ojUjzd/kEwWGzP0=
=q1w/
-----END PGP SIGNATURE-----

Re: [Libusb-win32-devel] Windows 2000 and Vista support

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

Hello Stephan,

* On Tue, Mar 20, 2007 at 07:16:12PM +0100 Stephan Meyer wrote:
 
> Thanks, but it won't be necessary to port any kernel driver code since
> the new DLL will use winusb.sys directly without UMDF, KMDF, or any
> other useless stuff that Microsoft introduced recently.

Oh, you want to use winusb.sys directly? This sounds very interesting.
Anyway, if I can help, just tell me.

Regards,
   Spiro.

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

Re: [Libusb-win32-devel] Windows 2000 and Vista support

[Stephan M. <ste...@we...>]

> > You are right, Vista-64bit won't let you install unsigned drivers. 
> > This means that this platform is currently not supported.
> > To resolve this issue, future versions of libusb-win32 will use Vistas 
> > built-in kernel driver winusb.sys.
> 
> Ok, I wanted to propose the UMDF, but obviously, you are already aware
> of it.
> 
> As I wrote you in my private mail, I am no specialist in USB. OTOH, I
> already wanted to start working with UMDF and KMDF myself.
> 
> Thus, if you need any help in porting the driver, feel free to ask me.
> If time permits, I will try to help you, if you want.
> 

Thanks, but it won't be necessary to port any kernel driver code since the 
new DLL will use winusb.sys directly without UMDF, KMDF, or any other 
useless stuff that Microsoft introduced recently.

Stephan



_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

Re: [Libusb-win32-devel] Windows 2000 and Vista support

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

Hello Stephan,

* On Tue, Mar 20, 2007 at 01:15:07PM +0100 Stephan Meyer wrote:
 
> Windows 2000 is fully supported, even Win98SE. I just installed the
> 0.1.12.1 release (compiled with mingw) on win2k-sp4 (vmplayer install)
> and it works like a charm.

Good to know. I am sorry that I did not test it myself, but currently, I
do not have a Win 2000 machine myself.

I was very surprised because the Win 2000 build environment did not
work.

> Don't use the DDK's Win2k build environment, use the XP or the
> Server 2003 build environment even if you want to compile for Win2k.

I have had the opposite experience: Drivers compiled with the XP and
2003 environment did not work with the "lower" versions.

 
> You are right, Vista-64bit won't let you install unsigned drivers. 
> This means that this platform is currently not supported.
> To resolve this issue, future versions of libusb-win32 will use Vistas 
> built-in kernel driver winusb.sys.

Ok, I wanted to propose the UMDF, but obviously, you are already aware
of it.

As I wrote you in my private mail, I am no specialist in USB. OTOH, I
already wanted to start working with UMDF and KMDF myself.

Thus, if you need any help in porting the driver, feel free to ask me.
If time permits, I will try to help you, if you want.


> > Do you plan to support 64 bit Windows at all?
> 
> XP-64bit and Server-2003-64bit are supported. Use the files
> libusb0_x64.dll and libusb0_x64.sys on these systems.

*grmph* Of course.

I already saw these files in the distribution, but I totally forgot
them. :(


Regards,
   Spiro.

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

Re: [Libusb-win32-devel] usb_claim_interface returns error code -22 on Windows

[<geo...@nt...>]

| Please do not use the old version any more. It's outdated.
| 
| Apart from that,  I won't recommend to use the filter feature 
| at all and
| use the device driver instead, because:
| 
| * it's very likely that the filter won't work on Vista
| * the device driver will work on Vista
| * the filter doesn't work properly with some devices (this is 
| a Windows issue)
| * the filter is a development tool, not intended to be used 
| by "professional"
|    applications
| * your users have to install a driver anyway, either the 
| filter or the device driver,
|    so they won't see any difference.
| 

Stephan,

many thanks for your recommendations. I will move to the last
version of libUSB and forget the filter driver.

Best regards,

Georges

Re: [Libusb-win32-devel] =?iso-8859-15?q?Windows_2000_and_Vista_suppo?= =?iso-8859-15?q?rt_=28was=3A_usb=5Fclaim=5Finterface_returns_error_code_-?= =?iso-8859-15?q?22_on_Windows=29?=

[Stephan M. <ste...@we...>]

> Hello,
> 
> * On Tue, Mar 20, 2007 at 11:02:10AM +0100 Stephan Meyer wrote:
> 
> > > OS version: Windows 2K 5.00.2195 SP4
> > > libUsb: 0.1.10.1
> > > Peripheral Manager: our HID device status is OK
> > > Task Manager: libusbd-nt.exe is running
> > > 
> > > I have installed the 0.1.12.0 version to check if it could
> > > fix the problem, but the things go even worse: the filter driver
> > > service starts then stops after a few seconds. This has been tested
> > > on a Windows XP machine with the same behavior: the service starts and
> > > stops.
> > 
> > Please do not use the old version any more. It's outdated.
> 
> This reminds me: What is the state of libusb-win32 for Windows 2000? I
> found that the latest release does not even install with the DDK
> (3790.1830) in the Windows 2000 build environment. Does it mean that
> Windows 2000 is not supported anymore?

Windows 2000 is fully supported, even Win98SE. I just installed the 0.1.12.1
release (compiled with mingw) on win2k-sp4 (vmplayer install) and it works
like a charm.

Don't use the DDK's Win2k build environment, use the XP or the
Server 2003 build environment even if you want to compile for Win2k.

> 
> What about Vista 64 bit? As far as I see, the driver is not signed,
> thus, it should refuse to install there. (I do not have Vista, so, I
> cannot check for myself).

You are right, Vista-64bit won't let you install unsigned drivers. 
This means that this platform is currently not supported.
To resolve this issue, future versions of libusb-win32 will use Vistas 
built-in kernel driver winusb.sys.

> 
> Do you plan to support 64 bit Windows at all?

XP-64bit and Server-2003-64bit are supported. Use the files
libusb0_x64.dll and libusb0_x64.sys on these systems.

> 
> Regards,
>    Spiro.
> 
> -- 
> Spiro R. Trikaliotis                              http://opencbm.sf.net/
> http://www.trikaliotis.net/                     http://www.viceteam.org/
> 
> -------------------------------------------------------------------------
> 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
> 


_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

[Libusb-win32-devel] Windows 2000 and Vista support (was: usb_claim_interface returns error code -22 on Windows)

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

Hello,

* On Tue, Mar 20, 2007 at 11:02:10AM +0100 Stephan Meyer wrote:

> > OS version: Windows 2K 5.00.2195 SP4
> > libUsb: 0.1.10.1
> > Peripheral Manager: our HID device status is OK
> > Task Manager: libusbd-nt.exe is running
> > 
> > I have installed the 0.1.12.0 version to check if it could
> > fix the problem, but the things go even worse: the filter driver
> > service starts then stops after a few seconds. This has been tested
> > on a Windows XP machine with the same behavior: the service starts and
> > stops.
> 
> Please do not use the old version any more. It's outdated.

This reminds me: What is the state of libusb-win32 for Windows 2000? I
found that the latest release does not even install with the DDK
(3790.1830) in the Windows 2000 build environment. Does it mean that
Windows 2000 is not supported anymore?

What about Vista 64 bit? As far as I see, the driver is not signed,
thus, it should refuse to install there. (I do not have Vista, so, I
cannot check for myself).

Do you plan to support 64 bit Windows at all?

Regards,
   Spiro.

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

Re: [Libusb-win32-devel] =?iso-8859-15?q?libusb-win32_weird_problem_w?= =?iso-8859-15?q?ith_0=2E1=2E12=2E0_on_XP_SP1=2C_but_works_with_0=2E1=2E10?= =?iso-8859-15?q?=2E1?=

[Stephan M. <ste...@we...>]

Thanks for the patch! I'll apply it and release
version 0.1.12.1.

Stephan


> Hello Stephan,
> 
> * On Sat, Mar 17, 2007 at 11:20:40AM +0100 Stephan Meyer wrote:
>  
> > The correct version is 0.1.12.0. I fixed it.
> 
> Thank you. I expected it that way, but I was not sure.
> 
> 
> > > Note that opencbm-xu1541.dll is dynamically loaded by opencbm.dll by
> > > using LoadLibrary(), GetProcAddress(), and FreeLibrary afterwards.
> > 
> > It should make no difference whether the DLLs are "statically linked" or
> > loaded at runtime.
> 
> I believe this, too. Anyway, I also thought that it should not make any
> difference regardless of which run-time library is used for which part,
> but it is not. Thus, I reported this for completeness.
>  
> > I'm no DLL expert either but it's usually good practice to link all system
> > libraries such as msvcrt.dll dynamically because:
> > 
> > * this saves memory and disk space
> > * speeds up application startup
> > * ensures that all components of an application use exactly the same 
> >    library/DLL versions
> 
> Well, at least the DDK samples do not use MSVCRT.DLL, but use the
> default (single-threaded statically linked library). That's the reason
> why I used this approach, too.
> 
> 
> > > Have a look into _usb_io_sync(), line 1170 of windows.c: It fails with
> > > error code 0xc0000005 (access violation). I can clearly see in the
> > > debugger that the memory referenced by the pointer out is valid, as is
> > > the data referenced by the pointer in. I can follow the OS function
> > > DeviceIoControl() until the SYSENTER. All pointers up to there are valid
> > > and correctly used. Doing the next step, I get the access violation.
> > 
> > Have you verified that all parameters passed to DeviceIoControl() are
> > valid and correct? Please check the 'ol' parameter. Is it corrently initialized
> > and is 'ol.hEvent' valid?
> 
> This was a very good hint!
> 
> I looked again and found that the input buffer "in" and "in_size" is not
> null if _usb_io_sync() is called. I set them to NULL in case we want to
> output anything on the USB bus, cf. the patch attached.  With this,
> everything works fine!
> 
> Note that the in buffer in is initialized with the input parameter bytes
> in usb_control_msg(). Now, the "bytes" parameter I give is just a
> constant string parameter. It seems my compiler puts it into a memory
> area which is not writable; thus, the 0xc0000005 "no access" occurs.
> 
> I am not sure if my fix is the right solution for everyone. I don't know
> if usb_control_msg() can give back data even if this is an output call.
> Anyway, at least for all my tests, it solved the problem for me.
> 
> 
> > > To be honest, I don't have a clue what is really going on, and how this
> > > can be solved.
> > > 
> > > Unfortunately, I cannot debug this better, as
> > > 
> > > 1. I don't have a second XP based machine to debug the call into
> > >    kernel-mode, too, and
> > > 
> > > 2. somehow, I have not managed to get libusb-win32 claim the device
> > >    inside of VMWare (which would allow me to debug the kernel calls,
> > >    too).
> > 
> > Where does the crash and the access violation occur? In user-space
> > or in kernel space? Do you get a BSOD?
> 
> As I told, the crash is gone if I link my DLL against MSVCRT.DLL, which
> I am doing currently.
> 
> The access violation is reported as a normal GetLastError() result. It
> occurs after the call to SYSENTER, thus, I am perfectly sure that it
> happens in kernel-mode.
> 
> I have done some more debugging: I added some outputs in the dispatch()
> routine in the driver libusb0.sys. It is not called from _usb_io_sync()
> if I get the access violation. So, I conclude that it is not your driver
> which reports this access violation, but the operating system.
> 
> Still, I don't know yet where exactly this happens, and which parameter
> is the culprit.
> 
> 
> So: With MSVCRT, I do not get any crash. Even if I do not use MSVCRT, I
> don't get a BSOD. I just get that pop-up window, telling me that there
> was a memory access (read) that should not have been there.
> 
> > If the access violation occurs in user-space then debugging in kernel-space
> > won't make much sense.
> 
> Yes, of course.
> 
> > > I thought I might have some problem with the initialization of the CRT.
> > > For this, I changed all DLL entry points in my code to DllEntry();
> > > anyway, the problems did not go away.
> > 
> > Thanks for the link. I changed the DLL's entry point to _DllMainCRTStartup@12 
> > as recommended by the article. A new version is attached. Please give it a try.
> 
> I am sorry, the attachment is empty here.
> 
> 
> So, to summarize: IF I link my DLL against MSVCRT, and I use the
> attached patch, everything works fine for me (now).
> 
> Regards,
>    Spiro.
> 
> -- 
> Spiro R. Trikaliotis                              http://opencbm.sf.net/
> http://www.trikaliotis.net/                     http://www.viceteam.org/
> 
> 
> <hr>
> -------------------------------------------------------------------------
> 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
> 
> <hr>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 


_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

Re: [Libusb-win32-devel] =?iso-8859-15?q?usb=5Fclaim=5Finterface_retu?= =?iso-8859-15?q?rns_error_code_-22_on_Windows?=

[Stephan M. <ste...@we...>]

> Hi there,
> 
> 
> I have browsed the whole mailing list archive before posting this.
> 
> Before complaining about libUSb, I have to say that I had a first 
> successful experience with this great library on a DFU class
> device both on Windows and Linux, so I thought it would be very
> easy to get our new HID project working...
> 
> After reading the LibUsb-Win32 WEB main page and many users messages
> I have understood the following:
> 
> - working with an USB HID class device, I don't need the libusb0.sys
>   driver to get in the way. Moreover, we have choosen the HID class
>   so that users of our demo application don't have to install any 
> driver.
> 
> - we only need libUsb0.dll and a filter driver which seems to be
>   activated by launching a libusbd-nt.exe service we can see running
>   through the Windows Tasks Manager.
> 
> - we can hide the filter driver launching process by starting it
>   from our installation program.

The service is not part of the latest release any more. The latest
version uses a different approach to install the filter.
You can install the filter manually by using the 'install-filter.exe'
command line tool. Type 'install-filter.exe -h' to see the available
options. You can also include the install in your application (see
install_filter.c for details). Please note: your users will need admin
rights to install the filter!  

> 
> Please tell me the above assumptions are wrong because this filter
> driver stuff seems to be a tricky part of libUsb.
> OK. Here is the problem description:
> 
>   usbDevice = device_init(vid, pid);
>  
>   deviceHandle = usb_open(usbDevice);
>   
>   usb_set_configuration(deviceHandle, CONFIGURATION); // config = 0

Try 'config = 1', it should work then.

>     
>   usb_claim_interface(deviceHandle, INTERFACE); // interface = 0
> 
> I have removed all tests to make things clearer.
> device_init, usb_open and usb_set_configuration return codes are OK.
> The usb_claim_interface returns the error code -22
> 
> OS version: Windows 2K 5.00.2195 SP4
> libUsb: 0.1.10.1
> Peripheral Manager: our HID device status is OK
> Task Manager: libusbd-nt.exe is running
> 
> I have installed the 0.1.12.0 version to check if it could
> fix the problem, but the things go even worse: the filter driver
> service starts then stops after a few seconds. This has been tested
> on a Windows XP machine with the same behavior: the service starts and
> stops.

Please do not use the old version any more. It's outdated.

Apart from that,  I won't recommend to use the filter feature at all and
use the device driver instead, because:

* it's very likely that the filter won't work on Vista
* the device driver will work on Vista
* the filter doesn't work properly with some devices (this is a Windows issue)
* the filter is a development tool, not intended to be used by "professional"
   applications
* your users have to install a driver anyway, either the filter or the device driver,
   so they won't see any difference.

> 
> Many thanks for your help and time!
> 
> Georges
>       
> 
> 
> -------------------------------------------------------------------------
> 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
> 


_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

[Libusb-win32-devel] usb_claim_interface returns error code -22 on Windows

[<geo...@nt...>]

Hi there,


I have browsed the whole mailing list archive before posting this.

Before complaining about libUSb, I have to say that I had a first 
successful experience with this great library on a DFU class
device both on Windows and Linux, so I thought it would be very
easy to get our new HID project working...

After reading the LibUsb-Win32 WEB main page and many users messages
I have understood the following:

- working with an USB HID class device, I don't need the libusb0.sys
  driver to get in the way. Moreover, we have choosen the HID class
  so that users of our demo application don't have to install any 
driver.

- we only need libUsb0.dll and a filter driver which seems to be
  activated by launching a libusbd-nt.exe service we can see running
  through the Windows Tasks Manager.

- we can hide the filter driver launching process by starting it
  from our installation program.

Please tell me the above assumptions are wrong because this filter
driver stuff seems to be a tricky part of libUsb.
OK. Here is the problem description:

  usbDevice = device_init(vid, pid);
 
  deviceHandle = usb_open(usbDevice);
  
  usb_set_configuration(deviceHandle, CONFIGURATION); // config = 0
    
  usb_claim_interface(deviceHandle, INTERFACE); // interface = 0

I have removed all tests to make things clearer.
device_init, usb_open and usb_set_configuration return codes are OK.
The usb_claim_interface returns the error code -22

OS version: Windows 2K 5.00.2195 SP4
libUsb: 0.1.10.1
Peripheral Manager: our HID device status is OK
Task Manager: libusbd-nt.exe is running

I have installed the 0.1.12.0 version to check if it could
fix the problem, but the things go even worse: the filter driver
service starts then stops after a few seconds. This has been tested
on a Windows XP machine with the same behavior: the service starts and
stops.

Many thanks for your help and time!

Georges
      

Re: [Libusb-win32-devel] libusb-win32 weird problem with 0.1.12.0 on XP SP1, but works with 0.1.10.1

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

Hello again Stephan,

another investigation:

* On Sat, Mar 17, 2007 at 03:19:46PM +0100 I wrote:
 
> I am not sure if my fix is the right solution for everyone. I don't know
> if usb_control_msg() can give back data even if this is an output call.
> Anyway, at least for all my tests, it solved the problem for me.

To me, it seems my fix is absolutely correct.

I looked into the SVN and found out that the relevant change was done
with revision 115
(http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb/src/windows.c?r1=109&r2=115),
where you changed from direct calls to DeviceIoControl() to calls to
usb_io_sync().

The line 690ff and 731ff (old implementation, revision 109) uses NULL
and 0 for the equivalent to the in and in_size parameters. The new
implementation (line 741, revision 115) does not reset in and in_size,
which results in the problem.

Interestingly, revision 115 was checked in on February 9, 2006 - which
perfectly fits with my observation that 0.1.10.1 (from 2005-03-09) works
perfectly, while 0.1.12 (from 2007-02-25) does not.

Regards,
   Spiro.

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

Re: [Libusb-win32-devel] libusb-win32 weird problem with 0.1.12.0 on XP SP1, but works with 0.1.10.1

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

Hello Stephan,

* On Sat, Mar 17, 2007 at 11:20:40AM +0100 Stephan Meyer wrote:
 
> The correct version is 0.1.12.0. I fixed it.

Thank you. I expected it that way, but I was not sure.


> > Note that opencbm-xu1541.dll is dynamically loaded by opencbm.dll by
> > using LoadLibrary(), GetProcAddress(), and FreeLibrary afterwards.
> 
> It should make no difference whether the DLLs are "statically linked" or
> loaded at runtime.

I believe this, too. Anyway, I also thought that it should not make any
difference regardless of which run-time library is used for which part,
but it is not. Thus, I reported this for completeness.
 
> I'm no DLL expert either but it's usually good practice to link all system
> libraries such as msvcrt.dll dynamically because:
> 
> * this saves memory and disk space
> * speeds up application startup
> * ensures that all components of an application use exactly the same 
>    library/DLL versions

Well, at least the DDK samples do not use MSVCRT.DLL, but use the
default (single-threaded statically linked library). That's the reason
why I used this approach, too.


> > Have a look into _usb_io_sync(), line 1170 of windows.c: It fails with
> > error code 0xc0000005 (access violation). I can clearly see in the
> > debugger that the memory referenced by the pointer out is valid, as is
> > the data referenced by the pointer in. I can follow the OS function
> > DeviceIoControl() until the SYSENTER. All pointers up to there are valid
> > and correctly used. Doing the next step, I get the access violation.
> 
> Have you verified that all parameters passed to DeviceIoControl() are
> valid and correct? Please check the 'ol' parameter. Is it corrently initialized
> and is 'ol.hEvent' valid?

This was a very good hint!

I looked again and found that the input buffer "in" and "in_size" is not
null if _usb_io_sync() is called. I set them to NULL in case we want to
output anything on the USB bus, cf. the patch attached.  With this,
everything works fine!

Note that the in buffer in is initialized with the input parameter bytes
in usb_control_msg(). Now, the "bytes" parameter I give is just a
constant string parameter. It seems my compiler puts it into a memory
area which is not writable; thus, the 0xc0000005 "no access" occurs.

I am not sure if my fix is the right solution for everyone. I don't know
if usb_control_msg() can give back data even if this is an output call.
Anyway, at least for all my tests, it solved the problem for me.


> > To be honest, I don't have a clue what is really going on, and how this
> > can be solved.
> > 
> > Unfortunately, I cannot debug this better, as
> > 
> > 1. I don't have a second XP based machine to debug the call into
> >    kernel-mode, too, and
> > 
> > 2. somehow, I have not managed to get libusb-win32 claim the device
> >    inside of VMWare (which would allow me to debug the kernel calls,
> >    too).
> 
> Where does the crash and the access violation occur? In user-space
> or in kernel space? Do you get a BSOD?

As I told, the crash is gone if I link my DLL against MSVCRT.DLL, which
I am doing currently.

The access violation is reported as a normal GetLastError() result. It
occurs after the call to SYSENTER, thus, I am perfectly sure that it
happens in kernel-mode.

I have done some more debugging: I added some outputs in the dispatch()
routine in the driver libusb0.sys. It is not called from _usb_io_sync()
if I get the access violation. So, I conclude that it is not your driver
which reports this access violation, but the operating system.

Still, I don't know yet where exactly this happens, and which parameter
is the culprit.


So: With MSVCRT, I do not get any crash. Even if I do not use MSVCRT, I
don't get a BSOD. I just get that pop-up window, telling me that there
was a memory access (read) that should not have been there.

> If the access violation occurs in user-space then debugging in kernel-space
> won't make much sense.

Yes, of course.

> > I thought I might have some problem with the initialization of the CRT.
> > For this, I changed all DLL entry points in my code to DllEntry();
> > anyway, the problems did not go away.
> 
> Thanks for the link. I changed the DLL's entry point to _DllMainCRTStartup@12 
> as recommended by the article. A new version is attached. Please give it a try.

I am sorry, the attachment is empty here.


So, to summarize: IF I link my DLL against MSVCRT, and I use the
attached patch, everything works fine for me (now).

Regards,
   Spiro.

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

Re: [Libusb-win32-devel] =?iso-8859-15?q?libusb-win32_weird_problem_w?= =?iso-8859-15?q?ith_0=2E1=2E12=2E0_on_XP_SP1=2C_but_works_with_0=2E1=2E10?= =?iso-8859-15?q?=2E1?=

[Stephan M. <ste...@we...>]

> [...]
>=20
>=20
> Unfortunately, I discovered a problem. If I use libusb-win32 0.1.10.1,
> everything works fine. If I use the version 0.1.10.2 (as it is called in=

> the download section; the INF calls itself 0.1.12.0), I have a big
> problem, which results in crashes sometimes, and in access violations in=

> other times.

The correct version is 0.1.12.0. I fixed it.

>=20
>=20
> I think some notes on the architecture might be appropriate. The tool
> (i.e., cbmctrl) uses a DLL (opencbm.dll), which itself uses another DLL
> as plugin (in this case, opencbm-xu1541.dll). That DLL imported
> libusb0.dll.
>=20
> Note that opencbm-xu1541.dll is dynamically loaded by opencbm.dll by
> using LoadLibrary(), GetProcAddress(), and FreeLibrary afterwards.

It should make no difference whether the DLLs are "statically linked" or
loaded at runtime.

> [...]
>=20
> Interestingly, the crashes almost always occur on program exit. To me,
> it seems the heap gets corrupted, which results in the crash.
>=20
> Note that my problems are with XP SP2. Another tester has the same
> problem. Somehow weird, another tester using Windows 2000 reports no
> problems at all!
>=20
>=20
> I started some debugging and found something. At least, I could
> make go away that crash. Now, all commands which only use "reading" from=

> the USB work - that is, calls to =5Fusb=5Fio=5Fsync() where "requesttype &
> USB=5FENDPOINT=5FIN" is true.
>=20
> What did I change=3F I looked into the sources file for libusb-win32 and
> found out that it uses MSVCRT.DLL as run-time library (instead of a
> statically linked run-time library).
>=20
> I changed opencbm.dll and opencbm-xu1541.dll to use the same DLL, and
> these crashes are gone now.
>=20
> Note that I am no expert on DLLs. Is this the expected behaviour=3F Should=

> it be the same=3F Why should "my" DLLs use the same run-time library as
> you=3F

I'm no DLL expert either but it's usually good practice to link all system=

libraries such as msvcrt.dll dynamically because:

* this saves memory and disk space
* speeds up application startup
* ensures that all components of an application use exactly the same=20
   library/DLL versions

>=20
> Unfortunately, the other problem (with access violations) remains for
> the commands where =5Fusb=5Fio=5Fsync() "requesttype & USB=5FENDPOINT=5FIN" is
> false.
>=20
> I debugged it as follows in WinDBG: I compiled libusb0.dll myself (using=

> make=5Fdll in the ddk=5Fmake/ directory, and utilizing the LIB, DLL and PDB
> I got).
>=20
> Have a look at libusb/src/windows.c
> (http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libus=
b/src/windows.c=3Frevision=3D148&view=3Dmarkup),
> function usb=5Fcontrol=5Fmsg() (lines 659ff):
>=20
> Everything works fine as long as the if() in line 770 (if(!(requesttype
> & USB=5FENDPOINT=5FIN))) is not true. Line 783ff (=5Fusb=5Fio=5Fsync()) succeeds,
> and everytings works.
>=20
> This is the reason why the access violation depends upon the requesttype=

> & USB=5FENDPOINT=5FIN value.
>=20
> If the if() in line 770 is true, lines 771-781 malloc()s a new memory
> area for the request req. req is a local variable, which is copied over
> the newly allocated memory. Additionally, the output data is copied
> after that request.
>=20
> I can see that the malloc() succeeds, and the copying works as expected
> (at least as I expect it), too. Nevertheless, the call in line 783
> (=5Fusb=5Fio=5Fsync()) fails now!
>=20
> Have a look into =5Fusb=5Fio=5Fsync(), line 1170 of windows.c: It fails with
> error code 0xc0000005 (access violation). I can clearly see in the
> debugger that the memory referenced by the pointer out is valid, as is
> the data referenced by the pointer in. I can follow the OS function
> DeviceIoControl() until the SYSENTER. All pointers up to there are valid=

> and correctly used. Doing the next step, I get the access violation.

Have you verified that all parameters passed to DeviceIoControl() are
valid and correct=3F Please check the 'ol' parameter. Is it corrently initia=
lized
and is 'ol.hEvent' valid=3F

>=20
> To be honest, I don't have a clue what is really going on, and how this
> can be solved.
>=20
> Unfortunately, I cannot debug this better, as
>=20
> 1. I don't have a second XP based machine to debug the call into
>    kernel-mode, too, and
>=20
> 2. somehow, I have not managed to get libusb-win32 claim the device
>    inside of VMWare (which would allow me to debug the kernel calls,
>    too).

Where does the crash and the access violation occur=3F In user-space
or in kernel space=3F Do you get a BSOD=3F
If the access violation occurs in user-space then debugging in kernel-spac=
e
won't make much sense.

>=20
>=20
> I am not sure if this is somehow related to restrictions of a DLL. I
> remembered that malloc() and printf() are problematic in a DLL. I came
> up with the following article in MSDN:
>=20
>    http://support.microsoft.com/=3Fscid=3Dkb%3Ben-us%3B94248&x=3D15&y=3D15
>=20
> I thought I might have some problem with the initialization of the CRT.
> For this, I changed all DLL entry points in my code to DllEntry();
> anyway, the problems did not go away.

Thanks for the link. I changed the DLL's entry point to =5FDllMainCRTStartup=
@12=20
as recommended by the article. A new version is attached. Please give it a=
 try.


>=20
>=20
> Any hints and ideas are welcome.
>=20
> Regards,
>    Spiro.
>=20
> --=20
> Spiro R. Trikaliotis                              http://opencbm.sf.net/=

> http://www.trikaliotis.net/                     http://www.viceteam.org/=

>=20
> ------------------------------------------------------------------------=
-
> 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=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DDEVDE=
V
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/=3Fmc=3D022222

[Libusb-win32-devel] libusb-win32 weird problem with 0.1.12.0 on XP SP1, but works with 0.1.10.1

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

Hello list members,

I am one of the authors of opencbm (http://sf.net/projects/opencbm). It
is a collection of tools (Linux and Windows kernel driver, shared
library, user tools) to access old Commodore equipment (floppies,
printers, etc.) on a modern PC.

All current releases support devices attached to the parallel port. We
are currently adding support for the xu1541
(http://www.harbaum.org/till/xu1541/), an USBTINY based ATMega8 device
to replace the parallel port.

If you want the current sources, you can get it through CVS with:

    cvs -z3 -d:pserver:ano...@op...:/cvsroot/opencbm co -r v0_4_0_48-xu1541_branch -P opencbm

and the xu1541 firmware (and the drivers) with
    cvs -z3 -d:pserver:ano...@op...:/cvsroot/opencbm co xu1541


The author of the xu1541 implemented support for Linux based systems
using libusb. It is now my task to port it over to Windows by using
libusb-win32.


Unfortunately, I discovered a problem. If I use libusb-win32 0.1.10.1,
everything works fine. If I use the version 0.1.10.2 (as it is called in
the download section; the INF calls itself 0.1.12.0), I have a big
problem, which results in crashes sometimes, and in access violations in
other times.


I think some notes on the architecture might be appropriate. The tool
(i.e., cbmctrl) uses a DLL (opencbm.dll), which itself uses another DLL
as plugin (in this case, opencbm-xu1541.dll). That DLL imported
libusb0.dll.

Note that opencbm-xu1541.dll is dynamically loaded by opencbm.dll by
using LoadLibrary(), GetProcAddress(), and FreeLibrary afterwards.

Additionally note that I am using the MS DDK compiler (3790.1830, 2003
SP1 DDK) and the DDK build tools for the project.

Thus, the outline is as follows:

    cbmctrl
       ^
       |    statically linked
       v 
    opencbm.dll
       ^
       |    dynamically linked (LoadLibrary, GetProcAddress())
       v 
    opencbm-xu1541.dll
       ^
       |    statically linked
       v 
    libusb0.dll



Interestingly, the crashes almost always occur on program exit. To me,
it seems the heap gets corrupted, which results in the crash.

Note that my problems are with XP SP2. Another tester has the same
problem. Somehow weird, another tester using Windows 2000 reports no
problems at all!


I started some debugging and found something. At least, I could
make go away that crash. Now, all commands which only use "reading" from
the USB work - that is, calls to _usb_io_sync() where "requesttype &
USB_ENDPOINT_IN" is true.

What did I change? I looked into the sources file for libusb-win32 and
found out that it uses MSVCRT.DLL as run-time library (instead of a
statically linked run-time library).

I changed opencbm.dll and opencbm-xu1541.dll to use the same DLL, and
these crashes are gone now.

Note that I am no expert on DLLs. Is this the expected behaviour? Should
it be the same? Why should "my" DLLs use the same run-time library as
you?



Unfortunately, the other problem (with access violations) remains for
the commands where _usb_io_sync() "requesttype & USB_ENDPOINT_IN" is
false.

I debugged it as follows in WinDBG: I compiled libusb0.dll myself (using
make_dll in the ddk_make/ directory, and utilizing the LIB, DLL and PDB
I got).

Have a look at libusb/src/windows.c
(http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb/src/windows.c?revision=148&view=markup),
function usb_control_msg() (lines 659ff):

Everything works fine as long as the if() in line 770 (if(!(requesttype
& USB_ENDPOINT_IN))) is not true. Line 783ff (_usb_io_sync()) succeeds,
and everytings works.

This is the reason why the access violation depends upon the requesttype
& USB_ENDPOINT_IN value.

If the if() in line 770 is true, lines 771-781 malloc()s a new memory
area for the request req. req is a local variable, which is copied over
the newly allocated memory. Additionally, the output data is copied
after that request.

I can see that the malloc() succeeds, and the copying works as expected
(at least as I expect it), too. Nevertheless, the call in line 783
(_usb_io_sync()) fails now!

Have a look into _usb_io_sync(), line 1170 of windows.c: It fails with
error code 0xc0000005 (access violation). I can clearly see in the
debugger that the memory referenced by the pointer out is valid, as is
the data referenced by the pointer in. I can follow the OS function
DeviceIoControl() until the SYSENTER. All pointers up to there are valid
and correctly used. Doing the next step, I get the access violation.

To be honest, I don't have a clue what is really going on, and how this
can be solved.

Unfortunately, I cannot debug this better, as

1. I don't have a second XP based machine to debug the call into
   kernel-mode, too, and

2. somehow, I have not managed to get libusb-win32 claim the device
   inside of VMWare (which would allow me to debug the kernel calls,
   too).


I am not sure if this is somehow related to restrictions of a DLL. I
remembered that malloc() and printf() are problematic in a DLL. I came
up with the following article in MSDN:

   http://support.microsoft.com/?scid=kb%3Ben-us%3B94248&x=15&y=15

I thought I might have some problem with the initialization of the CRT.
For this, I changed all DLL entry points in my code to DllEntry();
anyway, the problems did not go away.


Any hints and ideas are welcome.

Regards,
   Spiro.

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

Re: [Libusb-win32-devel] libusb-win32-releases 0.1.10.2, warning!

[Peter F. (L. <las...@gm...>]

Stephan Meyer wrote :
>...The problem is not the driver itself but Vista refusing to load it,
> probably because of the fact that the driver is 'not signed'.
It's possible to signed this driver?

> Installing the filter driver manually by using a special .inf file 
> works though. So the problem seems to be the way the installer works. 
> Maybe Vista doesn't allow to install filter drivers programatically any more.
How to do this? And where I can get the files for this?

Peter

-- 
Newsreader: http://mesnews.net/index-gb.php
Deutsche Hilfedatei: http://www.lastwebpage.de/download/mesnews-de.zip

Re: [Libusb-win32-devel] libusb-win32-releases 0.1.10.2, warning!

[Stephan M. <ste...@we...>]

This version works perfectly on Windows XP and lower. But I doesn't
seem to work on Vista.

Today, I installed Vista 32bit in VMPlayer, just to test the installer.
The installer itself works without any problems but the driver doesn't
load so that the whole USB system was unusable after the install (all
devices where marked with yellow exclamation marks in the device=20
manager). The problem is not the driver itself but Vista refusing to load =
it,
probably because of the fact that the driver is 'not signed'.

Installing the filter driver manually by using a special .inf file=20
works though. So the problem seems to be the way the installer works.=20
Maybe Vista doesn't allow to install filter drivers programatically any mo=
re.


Stephan


> Sorry for this but I must post a big warning about this, I am sure if
> this the right place for this.
> On http://sourceforge.net/project/showfiles.php=3Fgroup=5Fid=3D78138 I found:
> libusb-win32-releases 0.1.10.2 February 25, 2007
>=20
> I don't know if this Version works with XP correctly but with Vista
> 32Bit the following happens:
> Within the installation I got the message "Installing Kernel-Mode
> driver". After this all USB devices, inclusive mouse and Keyboard, were
> out of order!
> A reboot of the system, in safe mode too, not help.
> Fortunately I have not throwaway my old Mouse with PS/2, with this
> mouse it was possible for me to unintall libus-win32 through the
> startmenu.
>=20
> I post this here, because maybe someone read this here, before install
> this version. It's possible that is a problem with my system, who
> knows, (The old version works peferct within XP), but I guess it's a
> good idea to have a PS/2 mouse or keyboard somewhere before try this
> version. ;o)
>=20
> Peter
>=20
> --=20
> Newsreader: http://mesnews.net/index-gb.php
> Deutsche Hilfedatei: http://www.lastwebpage.de/download/mesnews-de.zip
>=20
>=20
>=20
>=20
> ------------------------------------------------------------------------=
-
> 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=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DDEVDE=
V
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!	=09
Mehr Infos unter http://freemail.web.de/home/landingpad/=3Fmc=3D021131

[Libusb-win32-devel] libusb-win32-releases 0.1.10.2, warning!

[Peter F. (L. <las...@gm...>]

Sorry for this but I must post a big warning about this, I am sure if
this the right place for this.
On http://sourceforge.net/project/showfiles.php?group_id=78138 I found:
libusb-win32-releases 0.1.10.2 February 25, 2007

I don't know if this Version works with XP correctly but with Vista
32Bit the following happens:
Within the installation I got the message "Installing Kernel-Mode
driver". After this all USB devices, inclusive mouse and Keyboard, were
out of order!
A reboot of the system, in safe mode too, not help.
Fortunately I have not throwaway my old Mouse with PS/2, with this
mouse it was possible for me to unintall libus-win32 through the
startmenu.

I post this here, because maybe someone read this here, before install
this version. It's possible that is a problem with my system, who
knows, (The old version works peferct within XP), but I guess it's a
good idea to have a PS/2 mouse or keyboard somewhere before try this
version. ;o)

Peter

-- 
Newsreader: http://mesnews.net/index-gb.php
Deutsche Hilfedatei: http://www.lastwebpage.de/download/mesnews-de.zip

Re: [Libusb-win32-devel] usb_bulk_read error

[Gavin B. <gb...@ax...>]

Stephan Meyer wrote:
> 
> Which verison of libusb-win32 and which compiler are you using?

I am using libusb win32 0.1.10.1, Borland C++ and the Keil firmware 
compiler uVision 3. We have a Cypress development board EZ-USB FX2 with 
an 8051 chip at it's heart.

Thank you,
		Gavin Brewer.

Re: [Libusb-win32-devel] usb_bulk_read error

[Stephan M. <ste...@we...>]

I've just released version 0.1.12.0.

Stephan

> BTW, has there been a recent release=3F I had been using snapshots with=20
> a Texas Instruments demo board (it uses PORUS as its USB stack; we=20
> also saw numerous asych errors, related or not), now on hold. I'd=20
> like to test again soon when I can; it would be nice to verify the=20
> open source driver with the OS stack...
>=20
> Not directly related to libusb, but bulk, we had problems with=20
> another vendor's (Eagle) bulk USB ADC device when using the new Core=20
> Duo chipsets, they had switched from isochronus that was in their=20
> last product and we saw corruption at high request rates.
>=20
> Ray
>=20
> At 09:44 AM 2/23/2007, you wrote:
> >It seems to be the same problem as this one:
> >
> >http://www.nabble.com/-Libusb-win32-devel--usb=5Finterrupt=5Fwrite--%3E-ENO=
MEM---tf2163265.html#a5981319
> >
> >Which verison of libusb-win32 and which compiler are you using=3F
> >
> >Stephan
> >
> >
> > > Guys,
> > >
> > > I have been writing firmware and PC end stubs for a USB-based
> > > development board. It has come to my attention that there may be a
> > > problem with the firmware that I have written.
> > >
> > > I receive the following error message upon calling usb=5Fbulk=5Fread:
> > >
> > > Bulk Read Vendor Request failed (-12).
> > > usb=5Fsubmit=5Fasync: error: Not enough storage is available to process =
this
> > > command
> > >
> > > Should I take this on face value, or is there something deeper going=
 on
> > > here=3F How should I modify my firmware in lieu of this fact=3F I would =
be
> > > grateful if someone could shed some light on this situation.
> > >
> > > Thank you,
> > >          Gavin Brewer.
> > >
> > >
> > > --------------------------------------------------------------------=
-----
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to=20
> > share your
> > > opinions on IT & business topics through brief surveys-and earn cash=

> > > http://www.techsay.com/default.php=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DD=
EVDEV
> > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> > > Libusb-win32-devel mailing list
> > > Lib...@li...
> > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> > >
> >
> >
> >=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> >Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> >http://smartsurfer.web.de/=3Fmc=3D100071&distributionid=3D000000000066
> >
> >
> >-----------------------------------------------------------------------=
--
> >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=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DDEVD=
EV
> >=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> >Libusb-win32-devel mailing list
> >Lib...@li...
> >https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>=20
>=20
> ------------------------------------------------------------------------=
-
> 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=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DDEVDE=
V
> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>=20


=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/=3Fmc=3D022222

Re: [Libusb-win32-devel] usb_bulk_read error

[RayS <ra...@bl...>]

BTW, has there been a recent release? I had been using snapshots with 
a Texas Instruments demo board (it uses PORUS as its USB stack; we 
also saw numerous asych errors, related or not), now on hold. I'd 
like to test again soon when I can; it would be nice to verify the 
open source driver with the OS stack...

Not directly related to libusb, but bulk, we had problems with 
another vendor's (Eagle) bulk USB ADC device when using the new Core 
Duo chipsets, they had switched from isochronus that was in their 
last product and we saw corruption at high request rates.

Ray

At 09:44 AM 2/23/2007, you wrote:
>It seems to be the same problem as this one:
>
>http://www.nabble.com/-Libusb-win32-devel--usb_interrupt_write--%3E-ENOMEM---tf2163265.html#a5981319
>
>Which verison of libusb-win32 and which compiler are you using?
>
>Stephan
>
>
> > Guys,
> >
> > I have been writing firmware and PC end stubs for a USB-based
> > development board. It has come to my attention that there may be a
> > problem with the firmware that I have written.
> >
> > I receive the following error message upon calling usb_bulk_read:
> >
> > Bulk Read Vendor Request failed (-12).
> > usb_submit_async: error: Not enough storage is available to process this
> > command
> >
> > Should I take this on face value, or is there something deeper going on
> > here? How should I modify my firmware in lieu of this fact? I would be
> > grateful if someone could shed some light on this situation.
> >
> > Thank you,
> >          Gavin Brewer.
> >
> >
> > -------------------------------------------------------------------------
> > 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
> >
>
>
>_____________________________________________________________________
>Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
>http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
>
>
>-------------------------------------------------------------------------
>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 plug events

[Joseph D. <jd...@ho...>]

Thank you very much, this looks to be exactly what I need.

-Joseph

On Fri, 23 Feb 2007 18:37:09 +0100
Stephan Meyer <ste...@we...> wrote:

> 
> Have a look this source code:
> 
> http://libusb-win32.cvs.sourceforge.net/libusb-win32/libusb/src/service/service_nt.c?hideattic=0&revision=1.5&view=markup
> 
> This is the source of a service that was part of older versions of
> libusb-win32. It does what you need.
> 
> Basically, you have to do the following:
> 
> * use RegisterDeviceNotification() to activate device notification events
> * listen to SERVICE_CONTROL_DEVICEEVENT (service) or WM_DEVICE_CHANGE
>   (normal app)  events
> * use libusb to rescan the whole bus for new devices
> * open new devices
> 
> Stephan
> 
> 
> > I'm not sure if this is the correct place to ask this or not, but how
> > do I detect when a usb device is plugged in?  I've successfully created
> > an .inf file to bind my device to the libusb-win32 driver.  I also have
> > an application that uses the libusb dll to interact with my device.
> > I'm planning on turning that application into a service, but I need to
> > execute some code whenever a device is plugged in.  How can I detect
> > when someone plugs in one of my devices?  Or is there a better way to
> > organize this?
> > 
> > -Joseph
> > 
> > 
> > -------------------------------------------------------------------------
> > 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
> > 
> 
> 
> _____________________________________________________________________
> Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
> 
> 
> -------------------------------------------------------------------------
> 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] Filter Driver for Windows Vista?

[Peter F. (L. <las...@gm...>]

Stephan Meyer wrote :
>...
> When do you get this error? When you install it or when you run your app?
>...
I guses whithin the installation,
-I download the last snapshot (libusb-win32-filter-bin-20060827.exe)
from sourceforge
-I start the installer with Admin rights.
-when the installer show me "Creating kernel service (this may take a
few seconds) the error message appear.
-when I cancel this error box and execute the test application within
the installation the same error appear. (Or if I exit the installer and
start my own application)

-- 
Newsreader: http://mesnews.net/index-gb.php
Deutsche Hilfedatei: http://www.lastwebpage.de/download/mesnews-de.zip

Re: [Libusb-win32-devel] usb_bulk_read error

[Stephan M. <ste...@we...>]

It seems to be the same problem as this one:

http://www.nabble.com/-Libusb-win32-devel--usb_interrupt_write--%3E-ENOMEM---tf2163265.html#a5981319

Which verison of libusb-win32 and which compiler are you using?

Stephan
 

> Guys,
> 
> I have been writing firmware and PC end stubs for a USB-based 
> development board. It has come to my attention that there may be a 
> problem with the firmware that I have written.
> 
> I receive the following error message upon calling usb_bulk_read:
> 
> Bulk Read Vendor Request failed (-12).
> usb_submit_async: error: Not enough storage is available to process this 
> command
> 
> Should I take this on face value, or is there something deeper going on 
> here? How should I modify my firmware in lieu of this fact? I would be 
> grateful if someone could shed some light on this situation.
> 
> Thank you,
> 	   Gavin Brewer.
> 
> 
> -------------------------------------------------------------------------
> 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
> 


_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

Re: [Libusb-win32-devel] libusb-win32 plug events

[Stephan M. <ste...@we...>]

Have a look this source code:

http://libusb-win32.cvs.sourceforge.net/libusb-win32/libusb/src/service/service_nt.c?hideattic=0&revision=1.5&view=markup

This is the source of a service that was part of older versions of
libusb-win32. It does what you need.

Basically, you have to do the following:

* use RegisterDeviceNotification() to activate device notification events
* listen to SERVICE_CONTROL_DEVICEEVENT (service) or WM_DEVICE_CHANGE
  (normal app)  events
* use libusb to rescan the whole bus for new devices
* open new devices

Stephan


> I'm not sure if this is the correct place to ask this or not, but how
> do I detect when a usb device is plugged in?  I've successfully created
> an .inf file to bind my device to the libusb-win32 driver.  I also have
> an application that uses the libusb dll to interact with my device.
> I'm planning on turning that application into a service, but I need to
> execute some code whenever a device is plugged in.  How can I detect
> when someone plugs in one of my devices?  Or is there a better way to
> organize this?
> 
> -Joseph
> 
> 
> -------------------------------------------------------------------------
> 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
> 


_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066