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 Message-ID: <01b801c294cd$7559c860$78d96f83@pomello> From: "Max Bowsher" To: "Robert Collins" Cc: 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> Subject: Re: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN) Date: Mon, 25 Nov 2002 21:56:07 -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 03:53, Daniel Armbrust wrote: >> Where can I get this? >> >>> >>> >>> If the NT 4 machine crashes every time, would you be willing to run >>> a special debug version of setup, that will write it's log entries >>> to the event log? They should be visible post install then, and you >>> can tell us what the last ones recorded are. > > > Well, I was going to roll it for you. However, having been reminded of > the McAfee problem - do you have McAfee installed? - I'd rather have > you try the current setup snapshot, which will give you the option for > disabling McAfee during the download and install process. > > 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. 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/