Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Content-Type: text/plain; charset="iso-8859-1" From: Tim Prince Reply-To: tprince AT computer DOT org To: Charles Wilson , cygwin AT cygwin DOT com Subject: Re: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN) Date: Mon, 25 Nov 2002 00:08:38 -0800 References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021124131806 DOT 03241008 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021124134357 DOT 02ad0608 AT pop3 DOT cris DOT com> <3DE1542E DOT 7050508 AT ece DOT gatech DOT edu> In-Reply-To: <3DE1542E.7050508@ece.gatech.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20021125080838.2868B2CB1E@mailout.ywave.com> On Sunday 24 November 2002 14:35, Charles Wilson wrote: > Guys, I'm really surprised nobody has mentioned the obvious culprit (or > asked the obvious question): > > Anti virus software? Was McAfee or Norton (but esp. McAfee) running > while setup.exe was executed? > > I *always* disable McAfee before running setup. Every time I forget, I > get a bluescreen. Minidump analysis shows that the fault is in fact > McAfee -- which runs in kernel mode -- and not setup. > > (I also turn off McAfee when compiling; it really slows down disk IO) > Every time my admins force a new version of McAfee, I modify the installation to remove the feature which checks every script every time it is executed, instead setting it up to perform a full weekly scan. I have had no problems this way with setup or running builds. With that McAfee feature enabled, scripts will stall so long that standby is invoked. -- Tim Prince -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/