X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B3CF3BD.6040708@gmail.com> Date: Thu, 31 Dec 2009 18:55:57 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: BSOD after major release References: <846d84d90912310540o5aea16abtd2438373bfa9b7f4 AT mail DOT gmail DOT com> <4B3CDE9A DOT 5090304 AT gmail DOT com> <4B3CECC7 DOT 1090303 AT cygwin DOT com> In-Reply-To: <4B3CECC7.1090303@cygwin.com> Content-Type: text/plain; charset=UTF-8 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 Larry Hall (Cygwin) wrote: > On 12/31/2009 12:25 PM, Dave Korn wrote: >> It's conceivable you might get more BSoD trouble when you try that; if >> so, the best bet is to [ ... ] > I could be wrong but I don't believe this is necessary unless the OP has > actually manually configured each of these to be enabled after they are > installed with 'setup.exe'. Ah, quite possibly so. There definitely was a report a while back of the libusb driver crashing when it was stopped as part of the preremove, but I didn't check if the new driver gets automatically started, I was just trying to cover all the bases. 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