Re: libUSB-Win32
On 13/06/2017 01:18, Chris Johnson wrote: Hi. Never run into this before. Running Win7 and installing cygwin via setup-x86_64 v2.879. I kept running into categories I couldn't install due to a missing libUSB-W32 driver. Some of the categories are Devel Math Net Publishing Python I get an error about libusb0, says I need to install this driver. Does anybody know; What this is? What it does? What uses it? Why it isn't part of the cygwin packages apparently? Because it need an external software driver. Are you trying to install all of devel category and more ? Very bad choice, there are more than 7000 packages and I doubt anyone need more than 2000 Limit your installation to what you really need. You can always add missing packages later. Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
libUSB-Win32
Hi. Never run into this before. Running Win7 and installing cygwin via setup-x86_64 v2.879. I kept running into categories I couldn't install due to a missing libUSB-W32 driver. Some of the categories are Devel Math Net Publishing Python I get an error about libusb0, says I need to install this driver. Does anybody know; What this is? What it does? What uses it? Why it isn't part of the cygwin packages apparently? Tnx. -- Chris, (from the laptop) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libusb-win32-1.2.6.0-1, libusb1.0-1.0.17-1
The following packages have been updated for both arches: * libusb0-1.2.6.0-1 * libusb-devel-1.2.6.0-1 * libusb1.0-1.0.17-1 * libusb1.0-devel-1.0.17-1 LibUSB is a library that provides generic access to USB devices. As a library, it is meant to be used by developers, to facilitate the production of applications that communicate with USB hardware. Please note that in order to use libusb0, you must download and install the driver from upstream (a warning to this effect will be displayed by Cygwin setup), as it now only builds with MSVC. This release is the first for x86_64. The libusb-win32 package has been split into separate runtime and devel packages. libusb1.0 has been switched to the libusbx fork, following the lead of several Linux distros, as development of the original upstream has seemingly ceased. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libusb-win32 1.2.5.0-1
Version 1.2.5.0-1 of "libusb-win32" has been uploaded. This is a new upstream release, the filter installer is not shipped any more as it does not build on cygwin any more. It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin AT cygwin DOT com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin Setup crashes Windows 2000 during preremove script libusb-win32 0.1.12.1-2
At 02:37 2009-07-10 +0200, you wrote: >At 00:08 2009-07-10 +0100, you wrote: >>> During Cygwin Setup noticed system crash, while setup screen displayed >>> something like: >>> Running preremove script libusb-win32 >>> Attempting to isolate the problem I told setup to keep the current version >>> of libusb-win32 and setup installed everything else apparently fine. >>> After this I tried running setup again with only this attempted update: >>> libusb-win320.1.12.1-2 ->0.1.12.2-1 >>> this again leads to a sudden system reset. >>> >>> Questions: >>> 1. Am I correct in understanding this is not the intended behaviour? >> >> Nah, it's not some kind of reset-to-complete-install thing, if that's what >> you're wondering. There must be a bug in the libusb driver when it's >told to >> unload. >> >> >> 2. What is the best way to work around (or solve) this problem? >> >>Start->Run->"devmgmt.msc". Select "View" menu -> "Show hidden devices." >>Expand the "Non-Plug and Play Drivers". Find libusb. Dunno exactly >what it's >>called, but it should be fairly obvious; to check, when you find it, >>double-click it to bring up the properties. Switch to the "Driver" >tab and >>click "Driver Details"; if the driver is called "libusb0.sys", that's the >>right one. Switch back to the "General" tab, click the "Device usage" >>drop-down, select "Do not use this device (disable)". Click OK, exit >>everything, reboot. >> >> You should now be able to run setup having booted without libusb >running, so >> it won't have to unload to be replaced and won't crash doing so. >> >> >> 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor back.) >> >>The hippos sent a ransom note... but we can't read it, as it's >covered with >> a brown substance that sounds like a bell. >> >> cheers, >>DaveK > >Hi Dave, > >Thanks for your quick reply. >Couldn't find libusb among "Non-Plug and Play Drivers". >Also libusb0.sys can only be found at: E:\cygwin\lib\libusb\ >not at: C:\WINNT\system32\drivers\ >This suggests that E:\cygwin\usr\sbin\libusb-uninstall either completed >anyway before the crash, or >libusb0.sys was never properly installed to begin with? >By the way: > >testlibusb >returns: > Dev #0: - > >And testlibusb-win shows: > DLL version: 0.1.12.1 > Driver version: -1.-1.-1.-1 > > bus/device idVendor/idProduct > >Having a closer look at libusb-install and libusb-uninstall reveals that >running /usr/lib/libusb/install-filter crashes Windows. (Also when I try to >redo libusb-install from a bash prompt.) So this means something in Windows >(or another part of Cygwin?) changed to cause the install-filter.exe >program to now crash the OS? Assuming the new version would work correct >would a workaround be to replace the old install-filter.exe program with >something more innocent like the E:\cygwin\bin\echo.exe program? (Assuming >that after that Cygwin Setup would install the new libusb version with a >new, corrected install-filter.exe?) > Tried it (replacing install-filter.exe with echo.exe). (See attached log file.) This works in the sense that there is no crash and install-filter.exe is replaced by a new version on install. However there is still no libusb to be found among "Non-Plug and Play Drivers", nor is there a libusb0.sys to be found underneath the WINNT directory. Also except for the DLL version number (which is now: 0.1.12.2), the output of testlibusb and testlibusb-win is the same as before. This makes me wonder if the installation process isn't flawed to begin with? If any one is interested I could check if the new install-filter.exe also crashes Windows 2000? I always wonder why people take the trouble to put flaws in their programs?2009/07/10 03:09:16 Starting cygwin install, version 2.573.2.3 2009/07/10 03:09:16 Current Directory: E:\download\Utilities\Shells\Cygwin\installInto 2009/07/10 03:09:16 Changing gid to Users 2009/07/10 03:09:16 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access. 2009/07/10 03:09:49 source: network install 2009/07/10 03:09:51 root: E:\cygwin binary system 2009/07/10 03:09:53 Selected local directory: E:\download\Utilities\Shells\Cygwin\installInto 2009/07/10 03:09:55 net: Direct Loaded cached mirror list get_url_to_membuf http
Re: Cygwin Setup crashes Windows 2000 during preremove script libusb-win32 0.1.12.1-2
At 00:08 2009-07-10 +0100, you wrote: >> During Cygwin Setup noticed system crash, while setup screen displayed >> something like: >> Running preremove script libusb-win32 >> Attempting to isolate the problem I told setup to keep the current version >> of libusb-win32 and setup installed everything else apparently fine. >> After this I tried running setup again with only this attempted update: >> libusb-win320.1.12.1-2 ->0.1.12.2-1 >> this again leads to a sudden system reset. >> >> Questions: >> 1. Am I correct in understanding this is not the intended behaviour? > > Nah, it's not some kind of reset-to-complete-install thing, if that's what > you're wondering. There must be a bug in the libusb driver when it's told to > unload. > > > 2. What is the best way to work around (or solve) this problem? > >Start->Run->"devmgmt.msc". Select "View" menu -> "Show hidden devices." >Expand the "Non-Plug and Play Drivers". Find libusb. Dunno exactly what it's >called, but it should be fairly obvious; to check, when you find it, >double-click it to bring up the properties. Switch to the "Driver" tab and >click "Driver Details"; if the driver is called "libusb0.sys", that's the >right one. Switch back to the "General" tab, click the "Device usage" >drop-down, select "Do not use this device (disable)". Click OK, exit >everything, reboot. > > You should now be able to run setup having booted without libusb running, so > it won't have to unload to be replaced and won't crash doing so. > > > 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor back.) > >The hippos sent a ransom note... but we can't read it, as it's covered with > a brown substance that sounds like a bell. > > cheers, > DaveK Hi Dave, Thanks for your quick reply. Couldn't find libusb among "Non-Plug and Play Drivers". Also libusb0.sys can only be found at: E:\cygwin\lib\libusb\ not at: C:\WINNT\system32\drivers\ This suggests that E:\cygwin\usr\sbin\libusb-uninstall either completed anyway before the crash, or libusb0.sys was never properly installed to begin with? By the way: testlibusb returns: Dev #0: - And testlibusb-win shows: DLL version: 0.1.12.1 Driver version: -1.-1.-1.-1 bus/device idVendor/idProduct Having a closer look at libusb-install and libusb-uninstall reveals that running /usr/lib/libusb/install-filter crashes Windows. (Also when I try to redo libusb-install from a bash prompt.) So this means something in Windows (or another part of Cygwin?) changed to cause the install-filter.exe program to now crash the OS? Assuming the new version would work correct would a workaround be to replace the old install-filter.exe program with something more innocent like the E:\cygwin\bin\echo.exe program? (Assuming that after that Cygwin Setup would install the new libusb version with a new, corrected install-filter.exe?) cheers, Arend-Jan. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin Setup crashes Windows 2000 during preremove script libusb-win32 0.1.12.1-2
Larry Hall (Cygwin) wrote: > On 07/09/2009, Arend-Jan Westhoff wrote: >> 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor >> back.) > > That would be me but I won't tell you my name or where to find me... > > Oh rats! Looks like I'm going to have to go hide with Igor. > But wait, where's Igor?... Now I'm really screwed. Dammit, I specifically *told* you to make sure the gimp suit was done up tight... what are we gonna do now you've let him escape? cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin Setup crashes Windows 2000 during preremove script libusb-win32 0.1.12.1-2
On 07/09/2009, Arend-Jan Westhoff wrote: 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor back.) That would be me but I won't tell you my name or where to find me... Oh rats! Looks like I'm going to have to go hide with Igor. But wait, where's Igor?... Now I'm really screwed. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin Setup crashes Windows 2000 during preremove script libusb-win32 0.1.12.1-2
Arend-Jan Westhoff wrote: > During Cygwin Setup noticed system crash, while setup screen displayed > something like: > Running preremove script libusb-win32 > Attempting to isolate the problem I told setup to keep the current version > of libusb-win32 and setup installed everything else apparently fine. > After this I tried running setup again with only this attempted update: > libusb-win320.1.12.1-2 ->0.1.12.2-1 > this again leads to a sudden system reset. > > Questions: > 1. Am I correct in understanding this is not the intended behaviour? Nah, it's not some kind of reset-to-complete-install thing, if that's what you're wondering. There must be a bug in the libusb driver when it's told to unload. > 2. What is the best way to work around (or solve) this problem? Start->Run->"devmgmt.msc". Select "View" menu -> "Show hidden devices." Expand the "Non-Plug and Play Drivers". Find libusb. Dunno exactly what it's called, but it should be fairly obvious; to check, when you find it, double-click it to bring up the properties. Switch to the "Driver" tab and click "Driver Details"; if the driver is called "libusb0.sys", that's the right one. Switch back to the "General" tab, click the "Device usage" drop-down, select "Do not use this device (disable)". Click OK, exit everything, reboot. You should now be able to run setup having booted without libusb running, so it won't have to unload to be replaced and won't crash doing so. > 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor back.) The hippos sent a ransom note... but we can't read it, as it's covered with a brown substance that sounds like a bell. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: libusb-win32 0.1.12.2-1
On 08/07/2009 04:20, Samuel Thibault wrote: It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). What about 64-bit Windows? Is a 64-bit driver available somewhere? It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. Well, almost: 1) has a #include . While that's certainly necessary inside of libusb, it's not required for the public interface and actually messes up some things which #include . Could you please move that #include into an internal header, or into the sources, so as not to expose it in the public interface? 2) Nowadays libusb provides a pkg-config file: http://cygwin.com/ml/cygwin/2008-05/msg00151.html Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: libusb-win32 0.1.12.2-1
Version 0.1.12.2-1 of "libusb-win32" has been uploaded. This is a new upstream release, handles composite device interfaces. It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin AT cygwin DOT com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
libusb-win32: libusb.pc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Apparently the linux version of libusb ships with a libusb.pc pkg-config
file. Packages use it to determine if libusb is installed, but
libusb-win32 package is missing it.
Could something like the attached be added to libusb-win32?
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkgkkK4ACgkQpiWmPGlmQSOK9gCgzkrqDXXcVM4IIyqUCD8rp7dW
S4EAn3d5EdBnuS3p65SGyOl9+cH8yvsg
=gPTX
-END PGP SIGNATURE-
prefix=/usr
exec_prefix=/usr
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: libusb
Description: USB library
Version: 0.1.12
Libs: -L${libdir} -lusb
Cflags: -I${includedir}
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
On 4/22/07, Samuel Thibault wrote: Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit : > Or you could follow the model of the ioperm package, which requires you to > manually run "ioperm -i" to install the .sys file. > Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit : > I think it would be very bad to install a (kernel-mode) driver by > default without any action of the user just because they selected a > package to install. > > > Maybe I could ship two separate packages: one for the library and one > > for the driver, and automatically install the driver at postinstall of > > the second package. > > That sounds ugly, why can't the user just run foo-config like every > other package that requires configuration? Currently, I'm indeed requiring the user to run /usr/sbin/libusb-install by hand (and uninstall is automatically called on package removal). So we should stay this way, ok. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ (just adding another idea to the pool) why not just include a REALLY simple application that asks "install libusb driver (Y/n)?" wouldnt that be another simple route? just put it in the postinstall or at the first bash run. btw, daveK, your welcome. -- Morgan gangwere "Space does not reflect society, it expresses it." -- Castells, M., Space of Flows, Space of Places: Materials for a Theory of Urbanism in the Information Age, in The Cybercities Reader, S. Graham, Editor. 2004, Routledge: London. p. 82-93.
Re: libusb-win32 auto-install?
Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit : > Or you could follow the model of the ioperm package, which requires you to > manually run "ioperm -i" to install the .sys file. > Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit : > I think it would be very bad to install a (kernel-mode) driver by > default without any action of the user just because they selected a > package to install. > > > Maybe I could ship two separate packages: one for the library and one > > for the driver, and automatically install the driver at postinstall of > > the second package. > > That sounds ugly, why can't the user just run foo-config like every > other package that requires configuration? Currently, I'm indeed requiring the user to run /usr/sbin/libusb-install by hand (and uninstall is automatically called on package removal). So we should stay this way, ok. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
Samuel Thibault wrote: > Yes of course (I actually call the uninstallation script at preremove). > But the question is "do we dare installing a driver just because the > user asked for package installation?". > > The problem is that libusb-win32 might be pulled as a dependency of > another package (the upcoming brltty package for instance), in which > case the use may be really be aware that some driver will get installed. I think it would be very bad to install a (kernel-mode) driver by default without any action of the user just because they selected a package to install. > Maybe I could ship two separate packages: one for the library and one > for the driver, and automatically install the driver at postinstall of > the second package. That sounds ugly, why can't the user just run foo-config like every other package that requires configuration? Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: libusb-win32 auto-install?
On 23 April 2007 02:33, Samuel Thibault wrote: > Yes of course (I actually call the uninstallation script at preremove). > But the question is "do we dare installing a driver just because the > user asked for package installation?". > > The problem is that libusb-win32 might be pulled as a dependency of > another package (the upcoming brltty package for instance), in which > case the use may be really be aware that some driver will get installed. > > Maybe I could ship two separate packages: one for the library and one > for the driver, and automatically install the driver at postinstall of > the second package. Or you could follow the model of the ioperm package, which requires you to manually run "ioperm -i" to install the .sys file. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
Hi, Larry Hall (Cygwin), le Sun 22 Apr 2007 21:25:50 -0400, a écrit : > The final decision is, of course, yours but I would say that if it's > really just an installation step, there's nothing technically stopping > you from performing the step automatically through a postinstall script, > for example. Yes of course (I actually call the uninstallation script at preremove). But the question is "do we dare installing a driver just because the user asked for package installation?". The problem is that libusb-win32 might be pulled as a dependency of another package (the upcoming brltty package for instance), in which case the use may be really be aware that some driver will get installed. Maybe I could ship two separate packages: one for the library and one for the driver, and automatically install the driver at postinstall of the second package. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
Samuel Thibault wrote: > Hi, > > Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit : >> A good reason for this division is to allow for user input during the >> configuration step, which "setup.exe" doesn't have support for. > > It doesn't need user input. > >> If running your libusb-install is more like a configuration step, > > It's not really configuration, it's really installation: the driver is > copied into C:\WINDOWS\... and a service is registered. > >> I might also encourage leaving things as is if the running of the >> script requires a reboot to take affect. > > Fortunately it doesn't. > >> Depending on your what your safety concerns are, that might be another >> good reason to leave things as is. > > Well, since we touch drivers, I'd prefer to leave as is. But since > at least one user asked for installation to be done automatically, I > preferred to ask for advice. > The final decision is, of course, yours but I would say that if it's really just an installation step, there's nothing technically stopping you from performing the step automatically through a postinstall script, for example. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: libusb-win32 auto-install?
On 23 April 2007 00:16, Morgan Gangwere wrote: > On 4/22/07, Samuel Thibault wrote: On 22 April 2007 14:49, Morgan Gangwere wrote: > On 4/22/07, Brian Dessent wrote: On 22 April 2007 15:45, Morgan Gangwere wrote: > On 4/22/07, Samuel Thibault ens-lyon.org> wrote: :-) Thank you Morgan! cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
On 4/22/07, Samuel Thibault wrote: Hi, Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit : > A good reason for this division is to allow for user input during the > configuration step, which "setup.exe" doesn't have support for. It doesn't need user input. > If running your libusb-install is more like a configuration step, It's not really configuration, it's really installation: the driver is copied into C:\WINDOWS\... and a service is registered. > I might also encourage leaving things as is if the running of the > script requires a reboot to take affect. Fortunately it doesn't. > Depending on your what your safety concerns are, that might be another > good reason to leave things as is. Well, since we touch drivers, I'd prefer to leave as is. But since at least one user asked for installation to be done automatically, I preferred to ask for advice. Thanks for the answer, Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ well, heres a bright idea. why not simply have a second package like "libusb-win32-autoinstall" that was just a postinstall script that ran the install? just a thought :D -- Morgan gangwere "Space does not reflect society, it expresses it." -- Castells, M., Space of Flows, Space of Places: Materials for a Theory of Urbanism in the Information Age, in The Cybercities Reader, S. Graham, Editor. 2004, Routledge: London. p. 82-93.
Re: libusb-win32 auto-install?
Samuel Thibault wrote: > Hi, > > Installing my libusb-win32 package doesn't automatically install the USB > driver, the user has to run /usr/sbin/libusb-install. I preferred to go > this way for safety. > > However, some user reported that it would be better that the > installation is automatically performed (since if one installs > libusb-win32, that's most probably for using it). What do people think > about it? I think there's a precedence for separating an install from the configuration. This is done for other packages, like openssh, cron, etc. A good reason for this division is to allow for user input during the configuration step, which "setup.exe" doesn't have support for. If running your libusb-install is more like a configuration step, I'd say leave it as is (though maybe change the name to indicate it's a configuration script instead). I might also encourage leaving things as is if the running of the script requires a reboot to take affect. Depending on your what your safety concerns are, that might be another good reason to leave things as is. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
libusb-win32 auto-install?
Hi, Installing my libusb-win32 package doesn't automatically install the USB driver, the user has to run /usr/sbin/libusb-install. I preferred to go this way for safety. However, some user reported that it would be better that the installation is automatically performed (since if one installs libusb-win32, that's most probably for using it). What do people think about it? Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
Hi, Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit : > A good reason for this division is to allow for user input during the > configuration step, which "setup.exe" doesn't have support for. It doesn't need user input. > If running your libusb-install is more like a configuration step, It's not really configuration, it's really installation: the driver is copied into C:\WINDOWS\... and a service is registered. > I might also encourage leaving things as is if the running of the > script requires a reboot to take affect. Fortunately it doesn't. > Depending on your what your safety concerns are, that might be another > good reason to leave things as is. Well, since we touch drivers, I'd prefer to leave as is. But since at least one user asked for installation to be done automatically, I preferred to ask for advice. Thanks for the answer, Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
Hi, Morgan Gangwere, le Sun 22 Apr 2007 08:44:55 -0600, a écrit : > On 4/22/07, Samuel Thibault ens-lyon.org> wrote: > >Installing my libusb-win32 package doesn't automatically install the USB > >driver, the user has to run /usr/sbin/libusb-install. I preferred to go > >this way for safety. > > > >However, some user reported that it would be better that the > >installation is automatically performed (since if one installs > >libusb-win32, that's most probably for using it). What do people think > >about it? > > > are you using Windows XP? 98? 2000? Vista? > it would be _really_ helpful to know what you're running. ?! I'm the maintainer of the libusb-win32 package, and would like the opinion of people whether the libusb-win32 package should auto-install the USB driver or not. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libusb-win32 auto-install?
On 4/22/07, Samuel Thibault ens-lyon.org> wrote: Hi, Installing my libusb-win32 package doesn't automatically install the USB driver, the user has to run /usr/sbin/libusb-install. I preferred to go this way for safety. However, some user reported that it would be better that the installation is automatically performed (since if one installs libusb-win32, that's most probably for using it). What do people think about it? Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ are you using Windows XP? 98? 2000? Vista? it would be _really_ helpful to know what you're running. all you have to to is run cygcheck -s -v- r attach that and we can help you alot. another note: check the postinstall script for libusb-win32 - it might not run (bleh)/libusb-install. if it doesn't, PGA ( http://www.cygwin.com/acronyms/#PGA ) -- Morgan gangwere "Space does not reflect society, it expresses it." -- Castells, M., Space of Flows, Space of Places: Materials for a Theory of Urbanism in the Information Age, in The Cybercities Reader, S. Graham, Editor. 2004, Routledge: London. p. 82-93. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.24-2: libusb-win32
Maurits Kooiman wrote: > I used your libusb-win32 (the testlibusb worked). > mine linker couldnt find the usb functions. > > Do you have any idea where to look? > > Regards > Maurits Kooiman > > Result of the make-file: > > make -k all > Building file: ../main.cpp > Invoking: GCC C++ Compiler > g++ -O3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" > -o"main.o" "../main.cpp" > Finished building: ../main.cpp > > Building target: NXTinterface.exe > Invoking: GCC C++ Linker > g++ -o"NXTinterface.exe" ./main.o > ./main.o:main.cpp:(.text+0xe1): undefined reference to `_usb_init' > ./main.o:main.cpp:(.text+0xe6): undefined reference to `_usb_find_busses' > ./main.o:main.cpp:(.text+0xeb): undefined reference to `_usb_find_devices' > ./main.o:main.cpp:(.text+0xf0): undefined reference to `_usb_get_busses' > ./main.o:main.cpp:(.text+0xf5): undefined reference to `_usb_get_busses' > collect2: ld returned 1 exit status How do you expect this to ever work? You're not telling to link against the library. It's not a mind reader, you need to give it -lusb. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
1.5.24-2: libusb-win32
Dear Reader, I used your libusb-win32 (the testlibusb worked). mine linker couldnt find the usb functions. Do you have any idea where to look? Regards Maurits Kooiman Result of the make-file: make -k all Building file: ../main.cpp Invoking: GCC C++ Compiler g++ -O3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -o"main.o" "../main.cpp" Finished building: ../main.cpp Building target: NXTinterface.exe Invoking: GCC C++ Linker g++ -o"NXTinterface.exe" ./main.o ./main.o:main.cpp:(.text+0xe1): undefined reference to `_usb_init' ./main.o:main.cpp:(.text+0xe6): undefined reference to `_usb_find_busses' ./main.o:main.cpp:(.text+0xeb): undefined reference to `_usb_find_devices' ./main.o:main.cpp:(.text+0xf0): undefined reference to `_usb_get_busses' ./main.o:main.cpp:(.text+0xf5): undefined reference to `_usb_get_busses' collect2: ld returned 1 exit status make: *** [NXTinterface.exe] Error 1 make: Target `all' not remade because of errors. Build complete for project NXTinterface -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
1.5.24-2: libusb-win32
Dear Reader, I used your libusb-win32 (the testlibusb worked). mine linker couldnt find the usb functions. Do you have any idea where to look? Regards Maurits Kooiman Result of the make-file: make -k all Building file: ../main.cpp Invoking: GCC C++ Compiler g++ -O3 -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -o"main.o" "../main.cpp" Finished building: ../main.cpp Building target: NXTinterface.exe Invoking: GCC C++ Linker g++ -o"NXTinterface.exe" ./main.o ./main.o:main.cpp:(.text+0xe1): undefined reference to `_usb_init' ./main.o:main.cpp:(.text+0xe6): undefined reference to `_usb_find_busses' ./main.o:main.cpp:(.text+0xeb): undefined reference to `_usb_find_devices' ./main.o:main.cpp:(.text+0xf0): undefined reference to `_usb_get_busses' ./main.o:main.cpp:(.text+0xf5): undefined reference to `_usb_get_busses' collect2: ld returned 1 exit status make: *** [NXTinterface.exe] Error 1 make: Target `all' not remade because of errors. Build complete for project NXTinterface -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Updated: libusb-win32 0.1.12.1-2
Samuel, Just confirming that this release solves my problem reported in http://cygwin.com/ml/cygwin/2007-03/msg00718.html . Many thanks for fixing this. Ton van Overbeek -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libusb-win32 0.1.12.1-2
Version 0.1.12.1-2 of "libusb-win32" has been uploaded. It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin@cygwin.com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
Hi, Corinna Vinschen, le Mon 26 Mar 2007 10:42:51 +0200, a écrit : > On Mar 24 20:21, Samuel Thibault wrote: > > > > Actually, I'm wondering: instead of trying to make libusb0.sys work > > > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in > > > > libusb-install, to just copy it into c:\windows\system32\drivers\ and > > > > then use the usual libusb-win32 filter setup? That works fine and > > > > actually makes the patch simpler... > > > > > > I am pretty sure that would solve the problem. > > > > Yes it does, but the question to cygwin developers is: is it ok > > packaging-wise? > > If it helps to work better, it should be ok in this case. It will help a lot yes. What is the best way to get the C:\windows\system32\drivers directory ? %systemroot%\system32\drivers, %windir%\system32\drivers or something else ? Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
On Mar 24 20:21, Samuel Thibault wrote: > > > Actually, I'm wondering: instead of trying to make libusb0.sys work > > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in > > > libusb-install, to just copy it into c:\windows\system32\drivers\ and > > > then use the usual libusb-win32 filter setup? That works fine and > > > actually makes the patch simpler... > > > > I am pretty sure that would solve the problem. > > Yes it does, but the question to cygwin developers is: is it ok > packaging-wise? If it helps to work better, it should be ok in this case. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
Ton van Overbeek, le Sat 24 Mar 2007 20:13:21 +0100, a écrit : > > Err, no, usbd.sys is always installed in > > c:\windows\system32\drivers\usbd.sys, and that's precisely because > > libusb0.sys is not installed there too that the usual discovery fails. > > > > Yes, I know. But copying usbd.sys to /usr/lib/libusb makes the problem > go away. Well, yes, but usbd.sys definitely belongs to windows/system32/drivers. Remember that this is a windows-shipped file, we shouldn't make a copy like this. > > Actually, I'm wondering: instead of trying to make libusb0.sys work > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in > > libusb-install, to just copy it into c:\windows\system32\drivers\ and > > then use the usual libusb-win32 filter setup? That works fine and > > actually makes the patch simpler... > > > > I am pretty sure that would solve the problem. Yes it does, but the question to cygwin developers is: is it ok packaging-wise? Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
On Sat, 24 Mar 2007, Samuel Thibault wrote: > Hi, > > Ton van Overbeek, le Sat 24 Mar 2007 04:06:09 +0100, a écrit : > > I believe I found the cause of the problem. > > When running cygcheck on /usr/lib/libusb/libusb0.sys I get this: > > > > $ cygcheck /usr/lib/libusb/libusb0.sys > > c:/Cygwin/lib/libusb/libusb0.sys > > Error: could not find usbd.sys < > > Well, this happens with the old version too. But in the new version, > libusb0.sys is started differently from the old version, that possibly > makes the windows-provided usbd.sys discovery fail. > You are right. I get the same cygcheck output with the old version. > > Somehow the Cygwin libusb0.sys must link to usbd.sys with the full path > > i.e. c:\windows\system32\drivers\usbd.sys instead of assuming that > > usbd.sys is located in the same directory as libusb0.sys. > > Err, no, usbd.sys is always installed in > c:\windows\system32\drivers\usbd.sys, and that's precisely because > libusb0.sys is not installed there too that the usual discovery fails. > Yes, I know. But copying usbd.sys to /usr/lib/libusb makes the problem go away. At the next boot loading of libusb0.sys succeeds. See excerpt from ntbtlog.txt below: Loaded driver btkrnl.sys Loaded driver agp440.sys Loaded driver \SystemRoot\System32\DRIVERS\intelppm.sys Loaded driver \SystemRoot\System32\DRIVERS\CmBatt.sys Loaded driver \SystemRoot\System32\DRIVERS\nv4_mini.sys Loaded driver \SystemRoot\System32\DRIVERS\usbuhci.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \SystemRoot\System32\DRIVERS\usbehci.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \SystemRoot\System32\DRIVERS\b57xp32.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \SystemRoot\System32\DRIVERS\gticard.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \SystemRoot\system32\drivers\tiumfwl.sys Loaded driver \SystemRoot\System32\DRIVERS\bcmwl5.sys Loaded driver \??\c:\Cygwin\lib\libusb\libusb0.sys Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys Loaded driver \SystemRoot\System32\DRIVERS\Apfiltr.sys Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys > Actually, I'm wondering: instead of trying to make libusb0.sys work > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in > libusb-install, to just copy it into c:\windows\system32\drivers\ and > then use the usual libusb-win32 filter setup? That works fine and > actually makes the patch simpler... > I am pretty sure that would solve the problem. Ton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
Hi, Ton van Overbeek, le Sat 24 Mar 2007 04:06:09 +0100, a écrit : > I believe I found the cause of the problem. > When running cygcheck on /usr/lib/libusb/libusb0.sys I get this: > > $ cygcheck /usr/lib/libusb/libusb0.sys > c:/Cygwin/lib/libusb/libusb0.sys > Error: could not find usbd.sys < Well, this happens with the old version too. But in the new version, libusb0.sys is started differently from the old version, that possibly makes the windows-provided usbd.sys discovery fail. > Somehow the Cygwin libusb0.sys must link to usbd.sys with the full path > i.e. c:\windows\system32\drivers\usbd.sys instead of assuming that > usbd.sys is located in the same directory as libusb0.sys. Err, no, usbd.sys is always installed in c:\windows\system32\drivers\usbd.sys, and that's precisely because libusb0.sys is not installed there too that the usual discovery fails. Actually, I'm wondering: instead of trying to make libusb0.sys work from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in libusb-install, to just copy it into c:\windows\system32\drivers\ and then use the usual libusb-win32 filter setup? That works fine and actually makes the patch simpler... Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
I believe I found the cause of the problem. When running cygcheck on /usr/lib/libusb/libusb0.sys I get this: $ cygcheck /usr/lib/libusb/libusb0.sys c:/Cygwin/lib/libusb/libusb0.sys Error: could not find usbd.sys < C:\WINDOWS\system32\ntoskrnl.exe C:\WINDOWS\system32\BOOTVID.dll C:\WINDOWS\system32\HAL.dll C:\WINDOWS\system32\KDCOM.dll Copying usbd.sys from c:\windows\system32\drivers to /usr/lib/libusb makes the problem disappear. After a reboot everything works. Somehow the Cygwin libusb0.sys must link to usbd.sys with the full path i.e. c:\windows\system32\drivers\usbd.sys instead of assuming that usbd.sys is located in the same directory as libusb0.sys. HTH Ton van Overbeek -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
Ton van Overbeek, le Fri 23 Mar 2007 16:56:48 +0100, a écrit : > Yes, Installed 0.1.10.1-3 after removing 0.1.12.1-1 and it works fine. Ok, so people can use that one instead for the few coming days until I fix the issue. > Also there is now an /usr/lib/libusb/install-filter.exe which did not > exist in 0.1.10.1-3. Yes, but it assumes that the filter is in the windows directory, which I wouldn't want to do in a cygwin package. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
On Fri, 23 Mar 2007, Samuel Thibault wrote: > Hi, > > Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit : > > I have problems with the libusb-win32-0.1.12.1-1 Cygwin package. > > Just to make sure, does the old 0.1.10.1-3 work fine? > Yes, Installed 0.1.10.1-3 after removing 0.1.12.1-1 and it works fine. See below. > > My guess is that /usr/sbin/libusb-install omits some crucial step > > (registry? kernel service?) which makes device driver loading at boot > > fail. > > Mmm, libusb-install just uses a very lightly modified version of > original libusb-win32 setup function, so it should be fine. There may be > some other subtle problem with not running the filter from > C:\windows\system32\drivers, I'll see that. > One difference I notes is that 0.1.10.1 uses legacy usb support with libusbd-nt.exe or libusbd-9x.exe in addition to libusb0.sys. This was removed in April 2005 in the libusb-win32 svn repository at SourceForge. Also there is now an /usr/lib/libusb/install-filter.exe which did not exist in 0.1.10.1-3. Ton van Overbeek -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
Hi, Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit : > I have problems with the libusb-win32-0.1.12.1-1 Cygwin package. Just to make sure, does the old 0.1.10.1-3 work fine? > My guess is that /usr/sbin/libusb-install omits some crucial step > (registry? kernel service?) which makes device driver loading at boot > fail. Mmm, libusb-install just uses a very lightly modified version of original libusb-win32 setup function, so it should be fine. There may be some other subtle problem with not running the filter from C:\windows\system32\drivers, I'll see that. Thanks for the report ! Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
I have problems with the libusb-win32-0.1.12.1-1 Cygwin package. Installation went fine. After running /usr/sbin/libusb-install the test program worked OK and also my own libusb based program worked fine. The real problem started after the following reboot. The /usr/sbin/libusb-install installs the usb filter driver. This filter is inserted in the drivers for all possible device classes. At the following reboot the loading of all device drivers in these classes failed, with as a consequence that none of these devices were working. On my XP/SP2 system these classes were: - Universal Serial Bus Controllers - Sound, video and game controllers - Modems - Network adapters - Smart card readers - Imaging devices - Human Interface Devices - Palm OS Handheld Devices - Bluetooth Devices - Portable Devices This is pretty disastrous: no network, no sound, no ... The original non-Cygwin package from SourceForge does not have the problem. It installs the filter driver in c:\windows\system32\drivers\libusb0.sys and the dll in c:\windows\system32\libusb0.dll. The Cygwin package installs the dll in /usr/bin/cygusb0.dll and the filter driver in /usr/lib/libusb/libusb0.sys. Installing the SourceForge package after the Cygwin package also solves the problem, i.e. combining cygusb0.dll and c:\windows\system32\drivers\libusb0.sys works OK. My guess is that /usr/sbin/libusb-install omits some crucial step (registry? kernel service?) which makes device driver loading at boot fail. I checked the failures by enabling boot logging and inspecting c:\windows\ntbtlog.txt. All the devices show up with yellow exclamation marks in the device manager. I am not a windows driver expert, so for now I cannot use the Cygwin package. Ton van Overbeek -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libusb-win32 0.1.12.0-1
Version 0.1.12.0-1 of "libusb-win32" has been uploaded. It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin@cygwin.com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] New package: libusb-win32 0.1.10.1-3
Version 0.1.10.1-3 of "libusb-win32" has been uploaded. It is a library that allows userspace application to access USB devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP). It is derived from and fully API compatible to libusb available at http://libusb.sourceforge.net. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin@cygwin.com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
