X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: mjD.OBqswBAPbVUxYJaYPvc61jLEnpq8VnBwJGdbEJOPA9xw Message-ID: <4B4342D0.6010007@sbcglobal.net> Date: Tue, 05 Jan 2010 13:46:56 +0000 From: Greg Chicares User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [Fwd: Blue screen when running installation *.sh] References: <90b5ea8bf2f16241df4a81ce3c98331c DOT squirrel AT lorien DOT myftp DOT org> In-Reply-To: <90b5ea8bf2f16241df4a81ce3c98331c.squirrel@lorien.myftp.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 On 2010-01-05 13:03Z, tim AT XXXXXX DOT demon DOT co DOT uk wrote: > I have previously used Cygwin 1.5 successfully, but thought I should > report a possible issue with the newer 1.7.1 version. > > My XP workstation blue screens reliably when doing the final steps of the > Cygwin 1.7.1 installation somewhere in the /etc/postinstall/*.sh scripts. > The blue screen indicates the problem is with ibmfilter.sys and upon > rebooting, Microsoft suggests that the fault lies with the Lenovo Rescue > and Recovery application and that page leads to an update. However, whilst > the ibmfilter.sys driver may be somewhat fragile there is a chance that > Cygwin is triggering the fault by doing something odd. Your cygcheck output contains: | Warning: There are multiple cygwin1.dlls on your path | | Potential app conflicts: | | ZoneAlarm Personal Firewall | Detected: HKLM Registry Key. so you probably ought to resolve those issues first. Google shows that 'ibmfilter.sys' causes BSODs with many applications. As a workaround, you might try rebooting into "safe mode" (to prevent that driver from loading), then running the postinstall scripts in that environment. -- 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