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: <018301c0e669$e3a09380$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Dave Cook" <dcook AT caveduck DOT com>, <cygwin AT cygwin DOT com>
References: <002501c0e662$0ed24a60$6800a8c0 AT dbca950> <016b01c0e662$415f9320$0200a8c0 AT lifelesswks> <003d01c0e665$9e71aff0$6800a8c0 AT dbca950>
Subject: Re: bluescreen during XF86/cygwin build
Date: Sun, 27 May 2001 15:00:02 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 27 May 2001 04:51:46.0163 (UTC) FILETIME=[BB69BC30:01C0E668]

----- Original Message -----
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>
Sent: Sunday, May 27, 2001 2:29 PM
Subject: Re: bluescreen during XF86/cygwin build


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

Uhmm, like open? close? delete?. Cygwin pushes the fs less than things
like MS proxy server 2.0, which had thousands of files with _long_
filenames in it's uri cache.

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

Well, win2k SP2 hasn't been out for months :]. I've already heard a
couple of horror stories about SP2 on focus-ms. The thing to remember,
with any configuration, is that stability == don't change unless you are
affected by a problem. And sometimes not even then.

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

Please do. If you'r interested in figuring this out, you probably
alreasdy have some info in memory.dmp from the last bluescreen.

Rob

> Regards,
>
> Dave
>
>


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