This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: bluescreen during XF86/cygwin build
----- Original Message -----
From: "Dave Cook" <dcook@caveduck.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>;
<cygwin-xfree@cygwin.com>; <cygwin@cygwin.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