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
From:	"Daniel Armbrust" <daniel DOT armbrust AT charter DOT net>
To:	"'Max Bowsher'" <maxb AT ukf DOT net>, <cygwin AT cygwin DOT com>
Subject:	RE: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN)
Date:	Sun, 24 Nov 2002 14:12:10 -0600
Message-ID:	<000201c293f5$c50365c0$0400a8c0@vortex2533>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
In-Reply-To:	<00bf01c293d6$c62800b0$78d96f83@pomello>

You guys sure are fast for a Sunday.  Open source is great : )

I am surprised that I am this unlucky.  Previously, I tried to track
this problem down, and I thought that I had come across an FAQ that
referenced cygwin causing Blue Screens, and the answer was basically you
have bad drivers.  This is why I assumed this was more frequently
reported.

Anyway, 
Clarifications:

This has happened to me on the initial install, (not all, but most
packages) and also today, when I downloaded rsync + dependencies and
other updates since the last time I downloaded (about a months worth) so
maybe it was around 10 packages.

If there is anything I can do to provide you with more debugging info
(or if theres any other suggestions you can give me for debugging this
if it is solely a hardware/driver issues) let me know, 

Thanks, 
Dan





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