Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<003d01c0e665$9e71aff0$6800a8c0@dbca950>
From:	"Dave Cook" <dcook AT caveduck DOT com>
To:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>,
	<cygwin-xfree AT cygwin DOT com>, <cygwin AT cygwin DOT com>
References:	<002501c0e662$0ed24a60$6800a8c0 AT dbca950> <016b01c0e662$415f9320$0200a8c0 AT lifelesswks>
Subject:	Re: bluescreen during XF86/cygwin build
Date:	Sat, 26 May 2001 21:29:28 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

>Robert Collins wrote:
> It shouldn't be either. Cygwin doesn't install any drivers at this point
> in time.

I realize that cygwin doesn't install any actual drivers, but it pushes the filesystem in
ways that W2K may not expect :)

>I suspect your system.

Unlikely.  This system is maintained *very* carefully with proper drivers - BIOS - OS
updates with stability as the object.  I found this scenario interesting precisely because
I have not experienced a similar bluescreen in months, though I use Cygwin pretty much as
my primary working environment, and I do tons of gcc compiles.

I'll see if I can recreate it and capture the stack info...

Regards,

Dave


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -