Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <028a01c294d2$5e09d1a0$78d96f83@pomello> From: "Max Bowsher" To: "Robert Collins" Cc: References: <000101c293d4$d4d19510$0400a8c0@vortex2533><1038169036.23988.82.camel@lifelesswks> <3DE25584.4000906@charter.net><1038256859.23476.328.camel@lifelesswks> <01b801c294cd$7559c860$78d96f83@pomello> <1038258059.23988.338.camel@lifelesswks> Subject: Re: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN) Date: Mon, 25 Nov 2002 22:31:08 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Robert Collins wrote: > On Tue, 2002-11-26 at 08:56, Max Bowsher wrote: >> Robert Collins 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/