Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sun, 27 May 2001 00:37:57 -0400 From: Christopher Faylor To: cygwin-xfree@cygwin.com, cygwin@cygwin.com Subject: Re: bluescreen during XF86/cygwin build Message-ID: <20010527003757.A12171@redhat.com> Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com, cygwin@cygwin.com References: <002501c0e662$0ed24a60$6800a8c0@dbca950> <016b01c0e662$415f9320$0200a8c0@lifelesswks> <003d01c0e665$9e71aff0$6800a8c0@dbca950> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <003d01c0e665$9e71aff0$6800a8c0@dbca950>; from dcook@caveduck.com on Sat, May 26, 2001 at 09:29:28PM -0700 On Sat, May 26, 2001 at 09:29:28PM -0700, Dave Cook wrote: >>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 :) No, it doesn't actually. It just uses standard Win32 API calls. With an OS like W2K there is really no way that Cygwin should be able to cause a blue screen. If it does, it's an OS bug, not a Cygwin bug. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple