I am not going to let Cygwin BSOD my Windows 2000 Server

Michael A Chase mchase@ix.netcom.com
Sat Apr 20 09:36:00 GMT 2002

On Sat, 20 Apr 2002 02:51:45 -0400 George Hester <hesterloli@hotmail.com> wrote:

> I realize that at one time setup.exe might not have been all that it was
> thought to be.  And that now it may be better.  But once burned many
> people
> do not jump back in the flames.  Well I decided I would stick my little
> toe
> in again and see the results.  I really thought there would be manual
> install literature because of the way setup.exe let me download these
> files.
> I had to un bzip2 them; ungz them; untar them and they are now sitting
> here
> ready to be installed.  So I went looking for that Manual install.

I'm having trouble understanding how setup.exe became the source of all
evil in the universe.  You had one BSOD months ago which may or may not
have been caused by setup.exe and as a result you are unwilling to try
another version of it ever again.

A client level program like setup.exe shouldn't be able to cause a BSOD and
it doesn't have any of the proprietary hooks into the OS that Microsoft's
programs have, so I'm skeptical of your statement that it caused the BSOD.  
Was it the only non-OS process active on your machine at the time?
Considering the number of BSODs caused by MS Word, MSIE, and MSOE, does
that mean you've stopped using them as well?

Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.

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/

More information about the Cygwin mailing list