Message-ID: <4B3CECC7.1090303@cygwin.com>
Date: Thu, 31 Dec 2009 13:26:15 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0
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>
In-Reply-To: <4B3CDE9A.5090304@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 12/31/2009 12:25 PM, Dave Korn wrote:
> Sergey Ivanov wrote:
>> After installing new major release of cygwin i obtained bsod
>> Bad_pool_Header on the stage post-installing. As usual i installed
>> everything (full installation).
>> Is it possible to check which package wrong?
>>
>> P.S. I've tried to delete everything before installing exclude home
>> directory - still not work
>
>    There are only two possible packages in Cygwin that could be responsible for
> a BSoD: ioperm and libusb-win32, as they install device drivers (*.sys files),
> which are the only things that could cause a BSoD aside from some bug in the
> OS kernel itself.
>
>    If you don't have either of those installed, then it's some unrelated thing
> on your system as Larry suggests.  If you do, and you're not using them, just
> uninstall them.
>
>    It's conceivable you might get more BSoD trouble when you try that; if so,
> the best bet is to boot into safe mode, and delete either/both of "ioperm.sys"
> and/or "libusb0.sys" from your C:\WINDOWS\system32\drivers directory; then
> reboot in normal mode and use setup.exe to uninstall any remaining leftovers.

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'.  Although both have a "preremove" script to
remove the enabled drivers on uninstall via 'setup.exe', neither has a
postinstall script which would introduce the drivers to Windows.  So AFAICT,
Windows doesn't know about these drivers unless the user manually tells
WIndows about them after they are installed with 'setup.exe'.  If the OP
didn't do that, then there's no need to undo it.  Of course, if the OP
doesn't care about using these packages, there's no harm in uninstalling
them via 'setup.exe'.  If the OP did actually run '/usr/sbin/libusb-install'
and/or 'ioperm -i', then uninstalling them, as you suggest, is a worthwhile
exercise in tracking this issue.

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