Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3DE1542E.7050508@ece.gatech.edu>
Date: Sun, 24 Nov 2002 17:35:26 -0500
From: Charles Wilson <cwilson@ece.gatech.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN)
References: <5.1.0.14.2.20021124131806.03241008@pop3.cris.com> <00bf01c293d6$c62800b0$78d96f83@pomello> <5.1.0.14.2.20021124131806.03241008@pop3.cris.com> <5.1.0.14.2.20021124134357.02ad0608@pop3.cris.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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)

Now, I realize that it would cause some raised eyebrows if we put, in 
big friendly letters on the main cygwin page, "Turn off all antivirus 
software before running this (unverified) binary setup.exe, and using it 
to install 300MB of other (unsigned) software on your system".

But is there really any other option?  Heck, even if we did sign all of 
the packages and provide verification, we'd still be asking people to 
trust us enough to turn off their virus scanner...and because McAfee 
sucks eggs, we kinda HAVE to make that request, or we get blamed for BSODs.

--Chuck


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