Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <4.3.1.2.20020420140204.02a6eb48@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Sat, 20 Apr 2002 14:15:54 -0400
To: "George Hester" <hesterloli AT hotmail DOT com>, cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: I am not going to let cygwin BSOD my Windows 2000 Server
In-Reply-To: <a9s9ri$ppm$1@main.gmane.org>
References: <a9r365$mj3$1 AT main DOT gmane DOT org>
 <20020420070212 DOT GA3256 AT redhat DOT com>
 <a9r4qg$nrt$1 AT main DOT gmane DOT org>
 <20020420163557 DOT GB3256 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:51 PM 4/20/2002, George Hester wrote:
>Sort of.  Maybe it does work for 99% of the people out there.  I know
>nothing of that.  And yes, my toes are sensitive to things such as this.  If
>I lose my op sys it takes me months to get it back to the condition I had
>before its destruction.  You may not believe me but I assure you that is the
>case.
>
>The information I have garnered here has helped to maybe stick my toes in
>the fire again.  I will wait a while and see if there is any good soul that
>can explain the procedures for a manual setup. And if that is pie in the sky
>then at that point I will decide if walking around with a few less toes is
>worth it.



Clearly, you're suffering from phobias which this list is ill-equipped to 
help you resolve.  Your best bet in that regard is to seek help from the 
appropriate forum.

In terms of setup and BSOD issues, Rob is quite right in pointing out that
setup may have once or may now tickle an O/S bug on your system that causes
a BSOD for you but this is an O/S issue, not a setup or Cygwin one.  You want
to talk to M$ about that.  If setup is or was tickling this bug for you, 
there is no permanent damage as a result.  It just means that you have to 
reboot after it runs.  But I fear I'm stepping into the area of your phobia
so I'll abandon this argument.

With respect to the idea of waiting for someone to document installation
steps so that you can follow them, I fear again that you've missed the 
point of this project.  If you're interested in finding this information 
out and really want the answer, it's best to pursue it yourself.  Chris 
Faylor has posted one possible script to do this.  Setup source is another
avenue.  Wait for whatever and whomever you want if that suits you but I
implore you to not bug the list about it in the meantime.  As near as I can 
tell, your phobias have backed you into a corner and you prefer to complain 
to the list about your resulting helplessness rather than taking some action 
that will resolve your problems. 





Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


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