From: Christopher Faylor <cgf-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: I am not going to let cygwin BSOD my Windows 2000 Server
Date: Sat, 20 Apr 2002 09:36:00 -0000 [thread overview]
Message-ID: <20020420163557.GB3256@redhat.com> (raw)
In-Reply-To: <a9r4qg$nrt$1@main.gmane.org>
On Sat, Apr 20, 2002 at 03:19:40AM -0400, George Hester wrote:
>Do you have all your toes?
Sure. My toes are not so sensitive that they become burned off if
I encounter a problem with my system.
I'm also the kind of guy who thinks that if something is working for 99%
of the people out there and *I* have a problem that it is probably *my*
problem. So, often, I like to figure out what that problem is.
Sometimes, if I don't have enough time or interest, I might wait to see
if a new version of a program solves my problem but I never grow so
averse to trying something new that I steadfastly avoid running a
program because it once gave me problems.
Does that answer your question?
cgf
>_________________________________
>"Christopher Faylor" <cgf-cygwin@cygwin.com> wrote in message
>news:20020420070212.GA3256@redhat.com...
>> On Sat, Apr 20, 2002 at 02:51:45AM -0400, George Hester wrote:
>> >Suggestion. Let's consider a Manual Install Direction for us weenies
>> >that lost a few toes trying to install this software in the past.
>>
>> You're making things way too hard for yourself. Just run setup.exe
>> and select "Install" rather than "Download". Then everything will
>> be installed automatically. You don't have to unzip/bunzip anything
>> by hand. setup.exe has *never* required a manual step like this.
--
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/
next prev parent reply other threads:[~2002-04-20 16:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 0:02 I am not going to let Cygwin " George Hester
2002-04-20 0:02 ` I am not going to let cygwin " Christopher Faylor
2002-04-20 0:21 ` George Hester
2002-04-20 9:36 ` Christopher Faylor [this message]
2002-04-20 10:04 ` David Means
2002-04-20 11:02 ` George Hester
2002-04-20 11:21 ` Larry Hall (RFK Partners, Inc)
2002-04-20 14:28 ` Charles Wilson
2002-04-20 14:38 ` Charles Wilson
2002-04-20 14:49 ` Charles Wilson
2002-04-21 0:54 ` George Hester
2002-04-20 15:30 ` Michael A Chase
2002-04-20 22:05 ` Compiling cygwin Dave Trollope
2002-04-20 15:40 ` I am not going to let cygwin BSOD my Windows 2000 Server Christopher Faylor
2002-04-20 16:46 ` Cliff Hones
2002-04-21 1:20 ` George Hester
2002-04-21 6:55 ` Cliff Hones
2002-04-21 11:32 ` Christopher Faylor
2002-04-21 14:25 ` Cliff Hones
2002-04-21 16:20 ` OT: Cygwin at Fault? (Was Re: I am not going to let cygwin BSOD my Windows 2000 Server) Paul G.
2002-04-21 20:18 ` I am not going to let cygwin BSOD my Windows 2000 Server George Hester
2002-04-20 9:36 ` I am not going to let Cygwin " Michael A Chase
2002-04-20 11:17 ` Charles Wilson
2002-04-21 20:29 ` George Hester
2002-04-22 14:28 ` Paul G.
2002-04-20 0:19 Robert Collins
2002-04-20 15:44 Robert Collins
2002-04-20 15:56 ` I am not going to let cygwin " Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020420163557.GB3256@redhat.com \
--to=cgf-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).