libusb-win32-devel

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

[Vu N. <vu...@gm...>]

Hi Xiaofan,

It works, because nothing happened I thought it did not work

Thank you very much again
Vu

On Nov 8, 2007 9:12 AM, <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: usb_set_configuration() hangs (soundman32)
>   2. 64-bit support (Paarvai Naai)
>   3. Re: Libusb-win32-devel Digest, Vol 18, Issue 3 (Vu Nguyen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 8 Nov 2007 07:43:11 -0800 (PST)
> From: soundman32 <nei...@go...>
> Subject: Re: [Libusb-win32-devel] usb_set_configuration() hangs
> To: lib...@li...
> Message-ID: <136...@ta...>
> Content-Type: text/plain; charset=us-ascii
>
>
> I have the same issue and I'm not using a filter driver.
>
> I can query the device and it tells me it is using configuration 1, but
> still usb_set_configuration(dev, 1) hangs the process and requires a
> reboot.
>
> Neil
>
> --
> View this message in context:
> http://www.nabble.com/usb_set_configuration%28%29-hangs-tf4556199.html#a13649512
> Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 8 Nov 2007 09:04:33 -0800
> From: "Paarvai Naai" <ope...@gm...>
> Subject: [Libusb-win32-devel] 64-bit support
> To: lib...@li...
> Message-ID:
>        <521...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 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.
>
> 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?
>
> 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?
>
> 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?
>
> I look forward to some information on this topic.  Thank you in advance.
>
> Best regards,
> Paarvai
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 8 Nov 2007 09:12:04 -0800
> From: "Vu Nguyen" <vu...@gm...>
> Subject: Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 18,
>        Issue 3
> To: lib...@li...
> Message-ID:
>        <935...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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
> > *************************************************
> >
> -------------- 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 18, Issue 4
> *************************************************
>

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

[Vu N. <vu...@gm...>]

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
> *************************************************
>

[Libusb-win32-devel] 64-bit support

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

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.

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?

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?

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?

I look forward to some information on this topic.  Thank you in advance.

Best regards,
Paarvai

Re: [Libusb-win32-devel] usb_set_configuration() hangs

[soundman32 <nei...@go...>]

I have the same issue and I'm not using a filter driver. 

I can query the device and it tells me it is using configuration 1, but
still usb_set_configuration(dev, 1) hangs the process and requires a reboot. 

Neil 

-- 
View this message in context: http://www.nabble.com/usb_set_configuration%28%29-hangs-tf4556199.html#a13649512
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 17, Issue 4

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

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

Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 17, Issue 4

[Vu N. <vu...@gm...>]

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
> *************************************************
>

Re: [Libusb-win32-devel] BSOD on Windows XP, possibly libusb-win32

[Adam K. <akr...@ro...>]

Thanks for the comments, Dan. I'm distributing libusb-win32 snapshot 
20060827. The x32 components are cross-compiled using mingw32 from Linux, 
and the x64 components are distributed from Stephan's binary package. I 
should consider upgrading to 0.1.12.1, but have resisted since I have no 
reported issues with the snapshot (until now, possibly).

--Adam

Dan Ellis wrote:
> Doesn't really look like libusb to me. I sometimes get BSODs with
> libusb when using it under python, but I think that may be since I
> started doing multithreaded stuff. I usually see libusb in the call
> stack, or at least usbhub. It occurs when python quits, as if python
> has held a handle open and trying to close it is causing a problem.
> In fact the stack backtrace usually reveals a NULL pointer somewhere
> along the line.
>
> Which version of libusb-win32 are you using?
>
> Dan.
>
> Adam Kropelin wrote:
>> A user just reported this XP BSOD in Apcupsd. libusb-win32 is the
>> only kernel driver Apcupsd uses (directly). Is there any evidence in
>> the info below to implicate (or exonerate) libusb-win32? Given the
>> misaligned instruction pointer (EIP should be 32-bit aligned on x86,
>> right?) I'm tempted to suspect bad RAM or another form of memory
>> corruption.
>>
>> Any ideas from the experts?
>>
>> Thanks!
>> --Adam
>>
>>> I got a BSOD today of 0x0000008e (0xc0000005, 0x805a1993,
>>> 0xb50f7cdc, 0x00000000). Running the kernal dump file through the
>>> Windows Debugger revealed the following:
>>>
>>> 3: kd> !analyze -v
>>>
> **********************************************************************
>>> *********
>>> *
>>> *
>>> *                        Bugcheck Analysis
>>> *
>>> *
>>> *
>>>
> **********************************************************************
>>> *********
>>>
>>> KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) This is a very common
>>> bugcheck. Usually the exception address pinpoints the
>>> driver/function that
>>> caused the problem.  Always note this address as well as the link
>>> date of the driver/image that contains this address.
>>> Some common problems are exception code 0x80000003.  This means a
>>> hard coded breakpoint or assertion was hit, but this system was
>>> booted /NODEBUG.  This is not supposed to happen as developers
>>> should never have hardcoded breakpoints in retail code, but ...
>>> If this happens, make sure a debugger gets connected, and the system
>>> is booted /DEBUG.  This will let us see why this breakpoint is
>>> happening. Arguments:
>>> Arg1: c0000005, The exception code that was not handled
>>> Arg2: 805a1993, The address that the exception occurred at
>>> Arg3: b50f7cdc, Trap Frame
>>> Arg4: 00000000
>>>
>>> Debugging Details:
>>> ------------------
>>>
>>> Page 1557c not present in the dump file. Type ".hh dbgerr004" for
>>> details PEB is paged out (Peb.Ldr = 7ffdc00c).  Type ".hh dbgerr001"
>>> for details PEB is paged out (Peb.Ldr = 7ffdc00c).  Type ".hh
>>> dbgerr001" for details
>>>
>>> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
>>> referenced memory at "0x%08lx". The memory could not be "%s".
>>>
>>> FAULTING_IP:
>>> nt!NtRequestWaitReplyPort+3
>>> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>>>
>>> TRAP_FRAME:  b50f7cdc -- (.trap 0xffffffffb50f7cdc) ErrCode =
>>> 00000002 eax=000000c8 ebx=805a1990 ecx=00000000 edx=0150ecc4
>>> esi=0150ecd0 edi=b50f7d64 eip=805a1993 esp=b50f7d50 ebp=b50f7d64
>>> iopl=0         nv up ei ng nz na po nc cs=0008  ss=0010  ds=0023
>>> es=0023  fs=0030  gs=0000
>>> efl=00010282
>>> nt!NtRequestWaitReplyPort+0x3:
>>> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>>> ds:0023:76396d11=?? Resetting default scope
>>>
>>> DEFAULT_BUCKET_ID:  DRIVER_FAULT
>>> BUGCHECK_STR:  0x8E
>>> PROCESS_NAME:  apcupsd.exe
>>>
>>> MISALIGNED_IP:
>>> nt!NtRequestWaitReplyPort+3
>>> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>>>
>>> LAST_CONTROL_TRANSFER:  from 804fe7e3 to 804f9f13
>>>
>>> STACK_TEXT:
>>> b50f78a4 804fe7e3 0000008e c0000005 805a1993 nt!KeBugCheckEx+0x1b
>>> b50f7c6c 80541415 b50f7c88 00000000 b50f7cdc
>>> nt!KiDispatchException+0x3b1
>>> b50f7cd4 805413c6 b50f7d64 805a1993 badb0d00
>>> nt!CommonDispatchException+0x4d b50f7d50 805409ac 00000194 0150ecd0
>>> 0150ecd0 nt!Kei386EoiHelper+0x18a b50f7d50 7c90eb94 00000194
>>> 0150ecd0 0150ecd0 nt!KiFastCallEntry+0xfc
>>> WARNING: Frame IP not in any known module. Following frames may be
>>> wrong. 0150ee08 00000000 00000000 00000000 00000000 0x7c90eb94
>>>
>>> STACK_COMMAND:  kb
>>>
>>> FOLLOWUP_IP:
>>> nt!NtRequestWaitReplyPort+3
>>> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>>>
>>> SYMBOL_STACK_INDEX:  0
>>> SYMBOL_NAME:  nt!NtRequestWaitReplyPort+3
>>> FOLLOWUP_NAME:  MachineOwner
>>> IMAGE_NAME:  hardware
>>> DEBUG_FLR_IMAGE_TIMESTAMP:  0
>>> MODULE_NAME: hardware
>>> FAILURE_BUCKET_ID:  IP_MISALIGNED
>>> BUCKET_ID:  IP_MISALIGNED
>>> Followup: MachineOwner
>>
>>
>>
>>
> ------------------------------------------------------------------------
> -
>> 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 

Re: [Libusb-win32-devel] Interfaces for device Suspend and Resume

[Dan E. <dan...@ne...>]

No there isn't, it would be a very useful addition.

Dan.

Waqar Ahmad wrote:
>
> Hello Everyone,
>
> I was wondering is there a way to suspend and resume a connected 
> device in libusb? Any help will be considered great in this regard.
>
> Regards,
> Waqar
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.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] Interfaces for device Suspend and Resume

[Waqar A. <waq...@ya...>]

Hello Everyone, 

I was wondering is there a way to suspend and resume a connected device in libusb? Any help will be considered great in this regard. 

Regards, 
Waqar

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Libusb-win32-devel] BSOD on Windows XP, possibly libusb-win32

[Dan E. <dan...@ne...>]

Doesn't really look like libusb to me. I sometimes get BSODs with libusb
when using it under python, but I think that may be since I started
doing multithreaded stuff. I usually see libusb in the call stack, or at
least usbhub. It occurs when python quits, as if python has held a
handle open and trying to close it is causing a problem. In fact the
stack backtrace usually reveals a NULL pointer somewhere along the line.

Which version of libusb-win32 are you using?

Dan.

Adam Kropelin wrote:
 > A user just reported this XP BSOD in Apcupsd. libusb-win32 is the
 > only kernel driver Apcupsd uses (directly). Is there any evidence in
 > the info below to implicate (or exonerate) libusb-win32? Given the
 > misaligned instruction pointer (EIP should be 32-bit aligned on x86,
 > right?) I'm tempted to suspect bad RAM or another form of memory
 > corruption.    
 >
 > Any ideas from the experts?
 >
 > Thanks!
 > --Adam
 >
 >> I got a BSOD today of 0x0000008e (0xc0000005, 0x805a1993,
 >> 0xb50f7cdc, 0x00000000). Running the kernal dump file through the
 >> Windows Debugger revealed the following:
 >>
 >> 3: kd> !analyze -v
 >>
**********************************************************************
 >> *********
 >> *
 >> *
 >> *                        Bugcheck Analysis
 >> *
 >> *
 >> *
 >>
**********************************************************************
 >> *********
 >>
 >> KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) This is a very common
 >> bugcheck. Usually the exception address pinpoints the
 >> driver/function that
 >> caused the problem.  Always note this address as well as the link
 >> date of the driver/image that contains this address.
 >> Some common problems are exception code 0x80000003.  This means a
 >> hard coded breakpoint or assertion was hit, but this system was
 >> booted /NODEBUG.  This is not supposed to happen as developers
 >> should never have hardcoded breakpoints in retail code, but ...
 >> If this happens, make sure a debugger gets connected, and the system
 >> is booted /DEBUG.  This will let us see why this breakpoint is
 >> happening. Arguments:
 >> Arg1: c0000005, The exception code that was not handled
 >> Arg2: 805a1993, The address that the exception occurred at
 >> Arg3: b50f7cdc, Trap Frame
 >> Arg4: 00000000
 >>
 >> Debugging Details:
 >> ------------------
 >>
 >> Page 1557c not present in the dump file. Type ".hh dbgerr004" for
 >> details PEB is paged out (Peb.Ldr = 7ffdc00c).  Type ".hh dbgerr001"
 >> for details PEB is paged out (Peb.Ldr = 7ffdc00c).  Type ".hh
 >> dbgerr001" for details
 >>
 >> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
 >> referenced memory at "0x%08lx". The memory could not be "%s".
 >>
 >> FAULTING_IP:
 >> nt!NtRequestWaitReplyPort+3
 >> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
 >>
 >> TRAP_FRAME:  b50f7cdc -- (.trap 0xffffffffb50f7cdc) ErrCode =
 >> 00000002 eax=000000c8 ebx=805a1990 ecx=00000000 edx=0150ecc4
 >> esi=0150ecd0 edi=b50f7d64 eip=805a1993 esp=b50f7d50 ebp=b50f7d64
 >> iopl=0         nv up ei ng nz na po nc cs=0008  ss=0010  ds=0023
 >> es=0023  fs=0030  gs=0000
 >> efl=00010282
 >> nt!NtRequestWaitReplyPort+0x3:
 >> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
 >> ds:0023:76396d11=?? Resetting default scope
 >>
 >> DEFAULT_BUCKET_ID:  DRIVER_FAULT
 >> BUGCHECK_STR:  0x8E
 >> PROCESS_NAME:  apcupsd.exe
 >>
 >> MISALIGNED_IP:
 >> nt!NtRequestWaitReplyPort+3
 >> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
 >>
 >> LAST_CONTROL_TRANSFER:  from 804fe7e3 to 804f9f13
 >>
 >> STACK_TEXT:
 >> b50f78a4 804fe7e3 0000008e c0000005 805a1993 nt!KeBugCheckEx+0x1b
 >> b50f7c6c 80541415 b50f7c88 00000000 b50f7cdc
 >> nt!KiDispatchException+0x3b1
 >> b50f7cd4 805413c6 b50f7d64 805a1993 badb0d00
 >> nt!CommonDispatchException+0x4d b50f7d50 805409ac 00000194 0150ecd0
 >> 0150ecd0 nt!Kei386EoiHelper+0x18a b50f7d50 7c90eb94 00000194 0150ecd0
 >> 0150ecd0 nt!KiFastCallEntry+0xfc
 >> WARNING: Frame IP not in any known module. Following frames may be
 >> wrong. 0150ee08 00000000 00000000 00000000 00000000 0x7c90eb94
 >>
 >> STACK_COMMAND:  kb
 >>
 >> FOLLOWUP_IP:
 >> nt!NtRequestWaitReplyPort+3
 >> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
 >>
 >> SYMBOL_STACK_INDEX:  0
 >> SYMBOL_NAME:  nt!NtRequestWaitReplyPort+3
 >> FOLLOWUP_NAME:  MachineOwner
 >> IMAGE_NAME:  hardware
 >> DEBUG_FLR_IMAGE_TIMESTAMP:  0
 >> MODULE_NAME: hardware
 >> FAILURE_BUCKET_ID:  IP_MISALIGNED
 >> BUCKET_ID:  IP_MISALIGNED
 >> Followup: MachineOwner
 >
 >
 >
 >
------------------------------------------------------------------------
-
 > 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] BSOD on Windows XP, possibly libusb-win32

[Adam K. <akr...@ro...>]

A user just reported this XP BSOD in Apcupsd. libusb-win32 is the only 
kernel driver Apcupsd uses (directly). Is there any evidence in the info 
below to implicate (or exonerate) libusb-win32? Given the misaligned 
instruction pointer (EIP should be 32-bit aligned on x86, right?) I'm 
tempted to suspect bad RAM or another form of memory corruption.

Any ideas from the experts?

Thanks!
--Adam

> I got a BSOD today of 0x0000008e (0xc0000005, 0x805a1993, 0xb50f7cdc, 
> 0x00000000).
> Running the kernal dump file through the Windows Debugger revealed the 
> following:
>
> 3: kd> !analyze -v
> *******************************************************************************
> * 
> *
> *                        Bugcheck Analysis 
> *
> * 
> *
> *******************************************************************************
>
> KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
> This is a very common bugcheck.  Usually the exception address pinpoints
> the driver/function that caused the problem.  Always note this address
> as well as the link date of the driver/image that contains this address.
> Some common problems are exception code 0x80000003.  This means a hard
> coded breakpoint or assertion was hit, but this system was booted
> /NODEBUG.  This is not supposed to happen as developers should never have
> hardcoded breakpoints in retail code, but ...
> If this happens, make sure a debugger gets connected, and the
> system is booted /DEBUG.  This will let us see why this breakpoint is
> happening.
> Arguments:
> Arg1: c0000005, The exception code that was not handled
> Arg2: 805a1993, The address that the exception occurred at
> Arg3: b50f7cdc, Trap Frame
> Arg4: 00000000
>
> Debugging Details:
> ------------------
>
> Page 1557c not present in the dump file. Type ".hh dbgerr004" for details
> PEB is paged out (Peb.Ldr = 7ffdc00c).  Type ".hh dbgerr001" for details
> PEB is paged out (Peb.Ldr = 7ffdc00c).  Type ".hh dbgerr001" for details
>
> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
> referenced memory at "0x%08lx". The memory could not be "%s".
>
> FAULTING_IP:
> nt!NtRequestWaitReplyPort+3
> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>
> TRAP_FRAME:  b50f7cdc -- (.trap 0xffffffffb50f7cdc)
> ErrCode = 00000002
> eax=000000c8 ebx=805a1990 ecx=00000000 edx=0150ecc4 esi=0150ecd0 
> edi=b50f7d64
> eip=805a1993 esp=b50f7d50 ebp=b50f7d64 iopl=0         nv up ei ng nz na 
> po nc
> cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000 
> efl=00010282
> nt!NtRequestWaitReplyPort+0x3:
> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1 
> ds:0023:76396d11=??
> Resetting default scope
>
> DEFAULT_BUCKET_ID:  DRIVER_FAULT
> BUGCHECK_STR:  0x8E
> PROCESS_NAME:  apcupsd.exe
>
> MISALIGNED_IP:
> nt!NtRequestWaitReplyPort+3
> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>
> LAST_CONTROL_TRANSFER:  from 804fe7e3 to 804f9f13
>
> STACK_TEXT:
> b50f78a4 804fe7e3 0000008e c0000005 805a1993 nt!KeBugCheckEx+0x1b
> b50f7c6c 80541415 b50f7c88 00000000 b50f7cdc nt!KiDispatchException+0x3b1
> b50f7cd4 805413c6 b50f7d64 805a1993 badb0d00 
> nt!CommonDispatchException+0x4d
> b50f7d50 805409ac 00000194 0150ecd0 0150ecd0 nt!Kei386EoiHelper+0x18a
> b50f7d50 7c90eb94 00000194 0150ecd0 0150ecd0 nt!KiFastCallEntry+0xfc
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 0150ee08 00000000 00000000 00000000 00000000 0x7c90eb94
>
> STACK_COMMAND:  kb
>
> FOLLOWUP_IP:
> nt!NtRequestWaitReplyPort+3
> 805a1993 d09a4d80e874    rcr     byte ptr [edx+74E8804Dh],1
>
> SYMBOL_STACK_INDEX:  0
> SYMBOL_NAME:  nt!NtRequestWaitReplyPort+3
> FOLLOWUP_NAME:  MachineOwner
> IMAGE_NAME:  hardware
> DEBUG_FLR_IMAGE_TIMESTAMP:  0
> MODULE_NAME: hardware
> FAILURE_BUCKET_ID:  IP_MISALIGNED
> BUCKET_ID:  IP_MISALIGNED
> Followup: MachineOwner

[Libusb-win32-devel] timeout error on control message

[Tom G. <tgr...@gm...>]

Hello.

I'm actually using the Java Libusb wrapper from
http://libusbjava.sourceforge.net/wp/ but was referred here from their
forum.

I'm having trouble sending  vendor specific control commands to a DS2490
USB to 1-Wire bridge.  Standard commands, like GET_STATUS, seem to work.
Likewise bulk and interrupt transfers.

The command is vendor specific, from host to device, and the recipient is
the device. bmRequestType should thus be 0x40, right?

This is the exception I get from my code:

ch.ntb.usb.USBTimeoutException: LibusbJava.controlMsg: usb_control_msg:
sending
control message failed, win error: The I/O operation has been aborted
because of
 either a thread exit or an application request.

        at ch.ntb.usb.Device.controlMsg(Device.java:552)
        at USBTest.readStatus(USBTest.java:79)
        at USBTest.main(USBTest.java:45)

Can the reason be that the Java wrapper demands some data and length but the
device's specs says none should be provided? If so I'm screwed...


My thread in the other forum:
http://sourceforge.net/forum/forum.php?thread_id=1858589&forum_id=660151

Thankful for any help/tip you can provide!
-- 
--
Tom

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

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

Is it possible that libusb-win32 1.0 to follow the API of OpenUSB?
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.

Regards,
Xiaofan

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

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

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

[Libusb-win32-devel] Do we like the same books?

[siramin056 <sir...@gm...>]

Just a friendly reminder that I invited you to Shelfari. Come see the books=
 I love and see if we have any in common. Then pick my next book so I can=
 keep on reading.=0A=0AClick below to join my group of friends on Shelfari!=
=0A=0Ahttp://www.shelfari.com/Register.aspx?ActivityId=3D24725878&InvitationCode=3Dda4c336d-e125-4697-8d51-519843cded8a=
=0A=0Asiramin056=0A=0AShelfari is a free site that lets you share book ratings=
 and reviews with friends and meet people who have similar tastes in books.=
  It also lets you build an online bookshelf, join book clubs, and get good=
 book recommendations from friends.  You should check it out.=0A=0A--------=
=0A=0AYou have received this email because siramin056 (sir...@gm...)=
 directly invited you to join his/her community on Shelfari.=0A=0AIt is=
 against Shelfari's policies to invite people who you don't know directly.=
 Follow this link (http://www.shelfari.com/actions/emailoptout.aspx?ema...@li...&activityid=3D24725878)=
 to prevent future invitations to this address. If you believe you do not=
 know this person, you may view (http://www.shelfari.com/siramin056) his/her=
 Shelfari page or report him/her in our feedback (http://www.shelfari.com/Feedback.aspx)=
 section.=0A=0AShelfari, 616 1st Ave #300, Seattle, WA 98104=0A

[Libusb-win32-devel] Do we like the same books?

[siramin056 <sir...@gm...>]

I just joined Shelfari to connect with other book lovers. Come see the books=
 I love and see if we have any in common. Then pick my next book so I can=
 keep on reading.=0A=0AClick below to join my group of friends on Shelfari!=
=0A=0Ahttp://www.shelfari.com/Register.aspx?ActivityId=3D23868877&InvitationCode=3Dda4c336d-e125-4697-8d51-519843cded8a=
=0A=0Asiramin056=0A=0AShelfari is a free site that lets you share book ratings=
 and reviews with friends and meet people who have similar tastes in books.=
  It also lets you build an online bookshelf, join book clubs, and get good=
 book recommendations from friends.  You should check it out.=0A=0A--------=
=0A=0AYou have received this email because siramin056 (sir...@gm...)=
 directly invited you to join his/her community on Shelfari.=0A=0AIt is=
 against Shelfari's policies to invite people who you don't know directly.=
 Follow this link (http://www.shelfari.com/actions/emailoptout.aspx?ema...@li...&activityid=3D23868877)=
 to prevent future invitations to this address. If you believe you do not=
 know this person, you may view (http://www.shelfari.com/siramin056) his/her=
 Shelfari page or report him/her in our feedback (http://www.shelfari.com/Feedback.aspx)=
 section.=0A=0AShelfari, 616 1st Ave #300, Seattle, WA 98104=0A

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

[Vu N. <vu...@gm...>]

Thank you very much

Vu

On 10/3/07, lib...@li... <
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: usb_set_configuration() hangs (Xiaofan Chen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 3 Oct 2007 07:17:20 +0800
> From: "Xiaofan Chen" <xia...@gm...>
> Subject: Re: [Libusb-win32-devel] usb_set_configuration() hangs
> To: lib...@li...
> Message-ID:
>         <a27...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 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
> *************************************************
>

Re: [Libusb-win32-devel] usb_set_configuration() hangs

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

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

[Libusb-win32-devel] usb_set_configuration() hangs

[Vu N. <vu...@gm...>]

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;  I traced it down to the
function _usb_io_sync() which points to the function DeviceIoControl();  I
found 2 instances in the forum for this problem, but the fix, for version
.10 actually, was to put memory or the out buffer;  I did that but the
DeviceIoControl() function still hangs;
///////////////
if ((*usb_dev = usb_open(dev)) != NULL) {
  retcode = usb_set_configuration (*usb_dev, 1);
  retcode = usb_claim_interface (*usb_dev, num_interface);
}
//////////////
Does anyone know how to get around this problem? I don't know how to dig
further after the DeviceIoControl() function;

Thank you in advance
Vu

Re: [Libusb-win32-devel] LibUsb-Win32 source changes?

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

On 10/1/07, trobinson <tr...@pi...> wrote:

> Why I think this is no longer feasable: (The one MAJOR negative side-effect)
> -------------------------------------------------------------------------
> After further research of the future libusb1 project,  I've discovered that
> there is no libusb kernel driver on a vista machine, it is using winusb!
> Talking to libusb via the DLL is mandatory to stay compatibe with future
> versions. In order for this to work, it would have to be implemented in the
> dll as well.  One of the first things the dll does is query device
> descriptor information in the "find_devices" function.  All of this would
> have to work differently.
>

However the libusb1 is not working yet (I tested the HID backend and
it is not working with interrupt read/write. I have not tested the WinUSB
backend under XP). And WinUSB is only for Vista/XP.
Under Win98SE/Win2k/WinXp, it is still better to use libusb-win32
device driver. So I think your patch is still useful.

Any examples of dealing with WM_DEVICECHANGE with your patched
version of libusb-win32 and your C# wrapper?

Xiaofan

Re: [Libusb-win32-devel] LibUsb-Win32 source changes?

[trobinson <tr...@pi...>]

Spiro Trikaliotis-8 wrote:
> I am asking myself if these do not open a security hole. I have not
> looked here into much detail, but which registry path do you open?

LIBUSB_IOCTL_GET_CUSTOM_REG_PROPERTY would open an retrieve values from the
"Device Parameters" key. (Example
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\$VID_PID$\$SERIAL$\Device
Parameters)


Spiro Trikaliotis-8 wrote:
> Travis, why do you need this patch? 

1) To identify and distingush between different device/device instances
(devices with equal PID and VIDs) attached to the PC without querying the
USB device for its descriptor/config information. 
2) Easily associate a "LibUsb" device with the WM_DEVICECHANGE notification
via the "SymbolicName" key value. 

Spiro Trikaliotis-8 wrote:
>  Perhaps, there are other, better
> solutions available than opening a (possibly negative) new API.?
I wasn't aware of anthing negative?  I'm trying to extend/increase/+
functionality.  The best way to get this type of information is through the
device driver, wouldn't you agree?

Spiro Trikaliotis-8 wrote:
> Even if this is not the case, one would have to *carefully* examine if
> there aren't other negative side-effects available..?
As I stated previously, LIBUSB_IOCTL_SET_CUSTOM_REG_PROPERTY is potentially
dangerous.  It can be omitted.  Without the ability to "set" there wouldn't
be any any danger of changing driver specific information.  Only key "value"
data would be returned.  None of the internal objects can be changed, the
new IOCTLs are completely independant from the others.

Why I think this is no longer feasable: (The one MAJOR negative side-effect)
-------------------------------------------------------------------------
After further research of the future libusb1 project,  I've discovered that
there is no libusb kernel driver on a vista machine, it is using winusb!
Talking to libusb via the DLL is mandatory to stay compatibe with future
versions. In order for this to work, it would have to be implemented in the
dll as well.  One of the first things the dll does is query device
descriptor information in the "find_devices" function.  All of this would
have to work differently.

Regards,
Travis

-- 
View this message in context: http://www.nabble.com/LibUsb-Win32-source-changes--tf4530174.html#a12971284
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

Re: [Libusb-win32-devel] LibUsb-Win32 source changes?

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

Hello,

* On Thu, Sep 27, 2007 at 12:22:19PM -0700 trobinson wrote:
 
> LIBUSB_IOCTL_GET_CUSTOM_REG_PROPERTY
> LIBUSB_IOCTL_SET_CUSTOM_REG_PROPERTY
> Get/Sets a custom property in the device objects registry key.

I am asking myself if these do not open a security hole. I have not
looked here into much detail, but which registry path do you open? Is it
the one where the name of the driver is located? In this case, any
user-mode program running on behalf of a user with almost arbitrary
rights could replace the driver with another one.

Even if this is not the case, one would have to *carefully* examine if
there aren't other negative side-effects available.

Travis, why do you need this patch? Perhaps, there are other, better
solutions available than opening a (possibly negative) new API.

Regards,
   Spiro.

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

[Libusb-win32-devel] Installing LibUsb-Win32 on Vista

[Alex G. <ab...@vi...>]

Installing LibUsb-Win32 on Vista


What I have done:-

   1.

      Download libusb-win32-filter-bin-0.1.12.1.exe (the version current
      @ 27/09/07)

   2.

      Right click on this file. Select Properties | Compatibility Click
      the “Run this program in compatibility mode” box and select
      “Windows XP (Service Pack2)” from the drop down list.

   3.

      Right click again and select “Run as “Administrator”. Follow the
      installation instructions. Running the test program list the usb
      devices plugged into my computer – but not my new device.

   4.

      Go to a downloaded and expanded folder
      libusb-win32-filter-bin-0.1.12.1
      Plug in new usb device and create a .inf file by going to the /bin
      folder and double-clicking inf-wizard.exe

   5.

      Follow the instructions. The program suggested I save the files in
      Alex/Documents so I left them there. It saved a .inf file and 2
      .cab files.

   6.

       From the Vista start button, go to Control Panel | Device
      Manager. This shows my device under “Other devices”. Clicking on
      the device gives me the properties and tells me that there is no
      driver installed. Click Reinstall Driver. Browse my computer for
      driver software. Browse to Alex/Documents then click Next. I then
      get the messages:-

      Windows found driver software for your device but encountered an
      error while attempting to install it.

      The system cannot find the file specified.


What am I doing wrong?


I have the system working OK under Win98 although it probably is an 
earlier version of Libusb-Win32.


How can I get a known working .inf file? The one generated by the wizard 
refers to _x64 files but there are no _x64 files installed. I copied the 
_x64 files from the folder with the wizard but this did not make any 
difference.


Alex



-- 
Internal Virus Database is out-of-date.
Checked by AVG Free Edition. 
Version: 7.5.484 / Virus Database: 269.13.1/981 - Release Date: 31/08/07 06:13

[Libusb-win32-devel] Kernel Driver not installing

[Ben C. <ben...@ho...>]

I am trying to install this on Windows XPSP2.  When I run the test app, I s=
ee this:
=20
DLL version: 0.1.12.1Driver version: -1.-1.-1.-1
bus/device  idVendor/idProduct
=20
I think this means the driver is not installed?
The first 2 times I ran the setup, it hung.  I disconnected all USB devices=
 and rebooted, uninstalled, and reinstalled, and now setup completes normal=
ly.  However it does not appear to have been successful.  The test app show=
s as above, and the app I downloaded and requires this driver (Lejos) is no=
t working either.
=20
How can I troubleshoot this?=

[Libusb-win32-devel] LibUsb-Win32 source changes?

[trobinson <tr...@pi...>]

First, a thanks to Stephen Myers and the rest of the LibUsb-Win32 crew for an
excellent universal USB driver.

My next (All CSharp) version of LibUsbDotNet uses 3 (three) new IOCTL codes
I'm hoping to get included in the LibUsb-Win32 project.

LIBUSB_IOCTL_GET_REG_PROPERTY
requests a device property by index using IoGetDeviceProperty.

LIBUSB_IOCTL_GET_CUSTOM_REG_PROPERTY
LIBUSB_IOCTL_SET_CUSTOM_REG_PROPERTY
Get/Sets a custom property in the device objects registry key.

I have allready modifed the libusb-win32 kernel driver source code to
include these IOCTL codes.  
Attached is an HTML diff report.
http://www.nabble.com/file/p12927507/LibUsbWin32Diff.html
LibUsbWin32Diff.html 
I made no changes to the dll because LibUsbDotNet talks directly to the
kernel driver.

Why I Need this:
1) These IOCTL codes allow me to query basic device information of the
attached USB devices without actually requesting descriptors.  Some cheap
USB devices don't deal well with control request if they are busy on other
endpoints.

2) GET_CUSTOM_REG_PROPERTY gets the custom registry properties by name,
mainly the "SymbolicName" of the device.  The SymbolicName  matches the name
returned by WM_DEVICECHANGE notifications.  This makes it easy to associate
a LibUsb device with the WM_DEVICECHANGE notifications.

3) SET_CUSTOM_REG_PROPERTY is obviously a bit dangerous,  LibUsbDotNet does
not make any "Set" request to the device registry key.  However, used with
caution this could be very useful.  It would enable someone to associate
custom information with a USB device that is persistent acrossed boots.


Regards,
Travis Robinson
tr...@pi...

-- 
View this message in context: http://www.nabble.com/LibUsb-Win32-source-changes--tf4530174.html#a12927507
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.