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:	<3BA6CC55.5070104@ece.gatech.edu>
Date:	Tue, 18 Sep 2001 00:23:49 -0400
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
CC:	cygwin AT cygwin DOT com
Subject:	Re: Bluescreen reboot with cygwin/W2K
References:	<3BA64F47 DOT 2010809 AT ece DOT gatech DOT edu> <3BA653A9 DOT 7000404 AT ece DOT gatech DOT edu>

Charles Wilson wrote:

> Never mind.  Although it is/was repeatable with the 
> run-mkgroup/CYGWIN=ntsec/no-existing-/etc/group scenario, I just had it 
> happen again while I was innocently running setup.
> 
> My hardware is probably damaged, not just my previous NT software 
> installation.  @#$!&#$.


The first time, I "reinstalled" cygwin on top of an existing tree. 
After completely deleting the entire tree, and *really* reinstalling 
cygwin, I have seen no more wacky bluescreens. (/me crosses fingers)

So, problem "solved".  I don't think this episode is worth tracking 
down; it's probably some weird interaction between my damaged drive, new 
W2K install, phase of moon, ...

--Chuck



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

- Raw text -