From: glenn AT gs DOT fay DOT nc DOT us (Glenn Spell)
Subject: Re: configure of cygwin package on win95 oddity
12 Jan 1999 00:58:23 -0800
Message-ID: <199901111318.FAA04384.cygnus.gnu-win32@shell4.ba.best.com>
References: <19990110145720 DOT 28191 DOT rocketmail AT send106 DOT yahoomail DOT com>
Reply-To: glenn AT gs DOT fay DOT nc DOT us (Glenn Spell)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
To: gnu-win32 AT cygnus DOT com

Earnie Boyd writes>
> I have found that the bug that causes the popup window informing that
> SH.EXE has caused a page fault in cygwin1.dll on Win95 DOESN'T happen
> if I am connected via DUN to my ISP. 8-O)

I've found many, many things that seem to change this behavior,
but nothing that is realiably effective as a work-around to this
*bug* in Cygwin. Cygwin *will not* run multiple sub-processes
on Windows 95 without crashing. There's something buggy about
the spawn/fork/sub-proc code. This all started with the Sept 98
changes to winsup. B19.4 (or maybe .5) was the last stable rel.

The frustrating thing is that Cygnus seems to have abandoned all
support of Windows 95 and probably text mounts too!

Until Cygwin can once again be make to run reliably on Windows 95,
it is nothing but a time-wasting pile of *crap*.

-glenn

-- 
            Glenn Spell <glenn AT gs DOT fay DOT nc DOT us>
         Fayetteville, North Carolina, U. S. A.
  ____________________________________________________
  ... blue skies ... happy trails ... sweet dreams ...
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".