From:	wue AT eskimo DOT com (Enoch Wu)
Subject:	BASH.EXE: No more processes ?
15 Oct 1998 13:48:06 -0700 :
Message-ID:	<Pine.SUN.3.96.981014135411.23081A-100000.cygnus.gnu-win32@eskimo.com>
Mime-Version:	1.0
To:	gnu-win32 AT cygnus DOT com

Hi,

Installation of B19.1 was successful on 1 computer.  On another computer
running Windows 95, which had successful B18 installation a while ago,
B19 did not run well.  Well, I'm not quite sure if this installation bears
any relation to the beta versions.  

I've a strange work around.  If I run Procomm Plus for DOS on Windows 95
just to cause an error exit, I can then run BASH as smoothly as ever.
Here is a description of BASH.EXE error (if I don't run Procomm to "init"
my computer):

$ps          (   ps or mount, ls, and many more ... same effect)

fork_helper:  ResumeThread failed, rc=2
BASH.EXE:  No more processes

-----------------
I uninstalled McAfee Virus checker since the FAQ clued me to it.  Rebooted
and uninstalled and rebooted and reinstalled usertools.exe with the
new cygwinb19.dll update 1.  I still get the "fork" problem.

I need your help on this.


Enoch

-
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".

- Raw text -