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: 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
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
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
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://cygwin.com/mirrors.lst getUrlToStream http://cygwin.com/mirrors.lst 2009/07/10 03:10:03 site: http://ftp.inf.tu-dresden.de/software/windows/cygwin32/ get_url_to_membuf http://ftp.inf.tu-dresden.de/software/windows/cygwin32//setup.bz2 getUrlToStream http://ftp.inf.tu-dresden.de/software/windows/cygwin32//setup.bz2 get_url_to_membuf http://ftp.inf.tu-dresden.de/software/windows/cygwin32//setup.bz2.sig getUrlToStream http://ftp.inf.tu-dresden.de/software/windows/cygwin32//setup.bz2.sig Checking MD5 for file://E:\download\Utilities\Shells\Cygwin\installInto/http%3a%2f%2fftp.inf.tu-dresden.de%2fsoftware%2fwindows%2fcygwin32%2f/release/libusb-win32/libusb-win32-0.1.12.2-1.tar.bz2 MD5 verified OK:
