Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3DE28D8B.7050105@ece.gatech.edu>
Date: Mon, 25 Nov 2002 15:52:27 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Peter A. Castro" <doctor AT fruitbat DOT org>
CC: cygwin AT cygwin DOT com
Subject: Re: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN)
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021124152104 DOT 02744e18 AT pop3 DOT cris DOT com> <Pine DOT LNX DOT 4 DOT 21 DOT 0211251003500 DOT 7231-100000 AT gremlin DOT fruitbat DOT org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Peter A. Castro wrote:


> And, just to provide a counter example: I always run Norton AntiVirus
> with automatic / background scanning enabled.  I generally have to,
> because of infected machines at work which probe the network whenever we
> get hit with the latest rash of viruses :(.  I've done all my Cygwin
> installs/updates with AntiVirus enabled and never had a BSOD (I'm running
> NT4 on fairly stable hardware and up to date drivers).  So, it is
> possible and if something does fail, it more like a driver fault than an
> application fault.


Yes, it HAS to be a "driver" fault (more accurately, it CANNOT be an
application fault).  Applications run in ring 3 (call it "user mode" --
but it's a protected execution mode enforced by the x86 processor
hardware).  drivers and such (like virus scanners) run in ring 0 (call
it kernel mode) along with the ntos kernel.  If you get a BSOD, it is by
definition a ring 0 fault == kernel mode == drivers/virus-scanner/kernel 
problem.  [AFAIK, ring 1 and ring 2 are not used by MSWin]

Now, as far as Norton vs. McAfee, the setup.exe BSODs have most often 
been reported wrt McAfee.  I only recall one report from a year back or 
more where Norton was the culprit.

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