Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: I am not going to let Cygwin BSOD my Windows 2000 Server MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 20 Apr 2002 17:18:58 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "George Hester" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3K7JMw25414 > -----Original Message----- > From: George Hester [mailto:hesterloli AT hotmail DOT com] > Sent: Saturday, April 20, 2002 4:52 PM > To: cygwin AT cygwin DOT com > Subject: I am not going to let Cygwin BSOD my Windows 2000 Server Consider this: A BSOD is equivalent to a unix kernel panic - usermode software should be unable to produce that result. If setup.exe EVER BSOD'd your server, it is the problem, not setup.exe. Rob -- 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/