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:	<028a01c294d2$5e09d1a0$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Robert Collins" <rbcollins AT cygwin DOT com>
Cc:	<cygwin AT cygwin DOT com>
References:	<000101c293d4$d4d19510$0400a8c0 AT vortex2533><1038169036 DOT 23988 DOT 82 DOT camel AT lifelesswks> <3DE25584 DOT 4000906 AT charter DOT net><1038256859 DOT 23476 DOT 328 DOT camel AT lifelesswks> <01b801c294cd$7559c860$78d96f83 AT pomello> <1038258059 DOT 23988 DOT 338 DOT camel AT lifelesswks>
Subject:	Re: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN)
Date:	Mon, 25 Nov 2002 22:31:08 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Robert Collins <rbcollins AT cygwin DOT com> wrote:

> On Tue, 2002-11-26 at 08:56, Max Bowsher wrote:
>> Robert Collins <rbcollins AT cygwin DOT com> wrote:
> 
> 
>>> If you don't have McAfee installed, then I'll roll an Event Log
>>> based setup for you.
>> 
>> Why not just flush the logs to disc after each line? I've got a
>> patch lying around here somewhere to do that. I'll update it to the
>> latest version. 
> 
> As long as:
> A) It's on NTFS
> B) The must-not-cache flag is set in CreateFile.
> 
> Otherwise, the last entries will be lost when the crash occurs.

Oh. I think I was just closing the file all the time.

Max.


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

- Raw text -