X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A567868.5040507@gmail.com> Date: Fri, 10 Jul 2009 00:08:24 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin Setup crashes Windows 2000 during preremove script libusb-win32 0.1.12.1-2 References: <20090709224630 DOT 1C18E57C03B AT castor DOT sshunet DOT nl> In-Reply-To: <20090709224630.1C18E57C03B@castor.sshunet.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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-win32 0.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