libusb-win32-devel

[Libusb-win32-devel] Wrapping

[Roger B. <ro...@ro...>]

Just to let you know that I managed to wrap the library
using Swig.  My program is actually written in Python.
I am writing a small amount of Python code to make it
all object oriented.

The only real problem is this declaration near the end
of the file:

struct usb_device *usb_device(usb_dev_handle *dev);

SWIG can't handle the same symbol being both a 
structure name and a function name.  I would
recommend adding another differently named function.

Memory management also isn't too clear.  Is all
memory invalidated when usb_find_busses/devices
is called?  Or is new memory allocated and that old
stuff leaked?

I basically just need to hook the right semantics
into my code.

Roger

[Libusb-win32-devel] Skipped devices?

[Roger B. <ro...@ro...>]

Why does the libusb skip devices?  The attached screenshot
is part of what device manager shows me.  You can see two
cellphones, a USB to serial cable and a scanner.  libusb
only shows me two hubs and the two cellphones.

I suspect that is because it skips devices, but doesn't
say why.


LIBUSB_DLL: usb_os_init: dll version: 0.1.7.8
LIBUSB_DLL: usb_os_init: installed driver version: 11/20/2003, 0.1.7.8
LIBUSB_DLL: usb_os_init: running driver version: 0.1.7.8
LIBUSB_DLL: usb_os_find_busses: found bus-0
LIBUSB_DLL: usb_os_find_devices: skipping 6 devices
LIBUSB_DLL: usb_os_find_devices: found \\.\libusb0-0006--0451-1446 on bus-0
LIBUSB_DLL: usb_os_find_devices: found \\.\libusb0-0007--0451-2046 on bus-0
LIBUSB_DLL: usb_os_find_devices: found \\.\libusb0-0008--1004-6000 on bus-0
LIBUSB_DLL: usb_os_find_devices: found \\.\libusb0-0009--1004-6000 on bus-0
skipped 4 class/vendor specific interface descriptors
skipped 4 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors

Roger

Re: [Libusb-win32-devel] New to list

[JD C. <li...@tr...>]

FYI,
    I've been using it for my cross platform work for a little while 
now, with now apparent problems.

JD

nick wrote:

> Hi,
>
> I'm currently looking into cross-platform user-mode usb libraries to 
> help me write an application for both MacOSX and WinXP.. I couldn't 
> find archives for this list, so - what's the current status of 
> libusb-win32? Is it kept in sync with the main project?
>
> Given that my application will have to have a GUI under windows, I 
> guess I will need to use VC++, does this rule out the use of 
> libusb-win32?
>
> Cheers,
> Nick
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

   

Re: [Libusb-win32-devel] New to list

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

nick <nic...@ya...> schrieb am 24.11.03 13:21:10:
> 
> Hi,
> 
> I'm currently looking into cross-platform user-mode usb libraries to 
> help me write an application for both MacOSX and WinXP.. I couldn't 
> find archives for this list, so - what's the current status of 
> libusb-win32? Is it kept in sync with the main project?

Libusb-win32 is currently under active development, still in beta stage, 
and not as mature as the main project.
The project will be kept in sync with the main project as close as possible
to ensure full API und functional compatibility.

> 
> Given that my application will have to have a GUI under windows, I 
> guess I will need to use VC++, does this rule out the use of 
> libusb-win32?

No, you can use the library with VC++, although the library is build with the GNU C 
compiler. The binary distribution package provides import libraries for all major
compilers (GCC, BCC, and VC++) to make the usage easier. But you won't be able to
build the DLL itself using VC++ because VC++ isn't fully C99 compatible (I have only 
tested version 6 so far, maybe the latest version is better).

> 
> Cheers,
> Nick
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________________________
WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130

[Libusb-win32-devel] New to list

[nick <nic...@ya...>]

Hi,

I'm currently looking into cross-platform user-mode usb libraries to 
help me write an application for both MacOSX and WinXP.. I couldn't 
find archives for this list, so - what's the current status of 
libusb-win32? Is it kept in sync with the main project?

Given that my application will have to have a GUI under windows, I 
guess I will need to use VC++, does this rule out the use of 
libusb-win32?

Cheers,
Nick

RE: [Libusb-win32-devel] Uninstall [Virus checked]

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

Hi Dag,

To uninstall libusb-win32 do the following:

a) uninstalling the filter driver:
- start 'regedit.exe' on XP and W98 systems, on W2K systems use 
'regedt32.exe'
- make sure that you have the required rights to modify the registry
- on NT-style systems delete the key 'LowerFilters' under the path
'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}'
(it should currently be set to 'libusbfl')
- on W98 systems this key is located at 
'System\CurrentControlSet\Services\Class\USB'
- reboot the system

b) uninstalling the stub driver (if used):
- go to the control panel
- open the device manger
- remove your device entry

After that you can remove the driver and inf files from your system by
just deleting them.

BTW, I just released version 0.1.7.6 which fixes some stupid bugs. You 
should use
this version in the future.

Regards

Stephan

[Libusb-win32-devel] Uninstall

[Dag B. <da...@br...>]

Hi,

What is the correct procedure to uninstall libusb-win32? I tried version 
0.1.7.5 a couple of days ago, and my laptop wasn't to happy about it. It 
constantly burned 20% CPU and hanged when trying to shut down the 
machine. I would like to remove it from my laptop and try the new 
version on a more suitable development machine.

-- Dag

Re: [Libusb-win32-devel] XP and Win2k Troubles....

[JD C. <li...@tr...>]

Thanks for the help Stephan!

I was just a bit confused on my installation order. At first I thought 
that my application constituted the USB driver you spoke of. (It sounded 
like the stub driver didn't need to be installed.) But I'm happy to say 
that it worked once I installed stub driver after changing the device 
and product ID's.

Thanks again for the work, it going to be very useful.

JD

Stephan Meyer wrote:

> "J.D. Cole" <jd...@tr...> schrieb am 09.10.03 12:52:15:
>  
>
>> Howdy,
>> I've been trying to get your drivers each of my machines, XP and 2k, 
>> to no avail. I'm just trying to use the binaries provided, but I'm 
>> wondering: do I still need the DDK to install from the bin's?
>>   
>
>
> No the DDK is not required for just using the library/drivers.
>
>  
>
>> I'll be happy to give any feedback and will definitely be trying 
>> fixes out ASAP. I basically followed the directions from the readme 
>> verbatim, minus the part about compiling.
>>
>> 1. As administrator (and this goes for both machines) I right clicked 
>> and installed the libusbfl.inf, no complaints from the box.
>> 2. Rebooted and logged on as a normal user.
>> 3. Ran testlibusb, it gave the initial header, i.e. device desc, 
>> product num, etc., but showed no devices. (For the record I had tried 
>> this process with a number of different devices, including my mouse.)
>>   
>
>
> What do you mean by "showed no devices"? It normaly only prints the 
> descriptors
> it retrieved from the available devices. If it does this, the filter 
> driver works.
>
>  
>
>> 4.a. Win2k misbehaved the most when I plugged in a device which I'm 
>> developing. It wouldn't open the device manager anymore and took 
>> long, if not forever, to reboot or shutdown.
>>   
>
>
>  
>
>> 4.b. XP was a little more gentle, it displayed my device with the 
>> official "?" on the Dev. manager. I even tried installing the driver 
>> via the manager....no luck.
>>   
>
>
> Which driver did you install for this device? It should be the stub 
> driver with
> a modified inf-file as described in the README.
>
> Have you tried DebugView from www.sysinternals.com to capture the 
> drivers debug messages
> (needs the *-checked-* versions of the drivers to be installed). Maybe 
> you could post
> some log message here.
>

Re: [Libusb-win32-devel] XP and Win2k Troubles....

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

"J.D. Cole" <jd...@tr...> schrieb am 09.10.03 12:52:15:
> 
> Howdy,
> I've been trying to get your drivers each of my machines, XP and 2k, 
> to no avail. I'm just trying to use the binaries provided, but I'm 
> wondering: do I still need the DDK to install from the bin's?

No the DDK is not required for just using the library/drivers.

> 
> I'll be happy to give any feedback and will definitely be trying fixes 
> out ASAP. I basically followed the directions from the readme verbatim, 
> minus the part about compiling.
> 
> 1. As administrator (and this goes for both machines) I right clicked 
> and installed the libusbfl.inf, no complaints from the box.
> 2. Rebooted and logged on as a normal user.
> 3. Ran testlibusb, it gave the initial header, i.e. device desc, product 
> num, etc., but showed no devices. (For the record I had tried this 
> process with a number of different devices, including my mouse.)

What do you mean by "showed no devices"? It normaly only prints the descriptors
it retrieved from the available devices. If it does this, the filter driver works.

> 4.a. Win2k misbehaved the most when I plugged in a device which I'm 
> developing. It wouldn't open the device manager anymore and took long, 
> if not forever, to reboot or shutdown.

> 4.b. XP was a little more gentle, it displayed my device with the 
> official "?" on the Dev. manager. I even tried installing the driver via 
> the manager....no luck.

Which driver did you install for this device? It should be the stub driver with
a modified inf-file as described in the README.

Have you tried DebugView from www.sysinternals.com to capture the drivers debug messages
(needs the *-checked-* versions of the drivers to be installed). Maybe you could post
some log message here.

> 
> I am stoked that you've done the work on this thing, though, and hope I 
> can help get this thing into gear.
> 
> JD
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________________________
Zwei Mal Platz 1 mit dem jeweils besten Testergebnis! WEB.DE FreeMail
und WEB.DE Club bei Stiftung Warentest! http://f.web.de/?mc=021183

[Libusb-win32-devel] XP and Win2k Troubles....

[J.D. C. <jd...@tr...>]

Howdy,
    I've been trying to get your drivers each of my machines, XP and 2k, 
to no avail. I'm just trying to use the binaries provided, but I'm 
wondering: do I still need the DDK to install from the bin's?

I'll be happy to give any feedback and will definitely be trying fixes 
out ASAP. I basically followed the directions from the readme verbatim, 
minus the part about compiling.

1. As administrator (and this goes for both machines) I right clicked 
and installed the libusbfl.inf, no complaints from the box.
2. Rebooted and logged on as a normal user.
3. Ran testlibusb, it gave the initial header, i.e. device desc, product 
num, etc., but showed no devices. (For the record I had tried this 
process with a number of different devices, including my mouse.)
4.a. Win2k misbehaved the most when I plugged in a device which I'm 
developing. It wouldn't open the device manager anymore and took long, 
if not forever, to reboot or shutdown.
4.b. XP was a little more gentle, it displayed my device with the 
official "?" on the Dev. manager. I even tried installing the driver via 
the manager....no luck.

I am stoked that you've done the work on this thing, though, and hope I 
can help get this thing into gear.

JD