* BASH.EXE: No more processes ?
@ 1998-10-15 0:44 Enoch Wu
0 siblings, 0 replies; only message in thread
From: Enoch Wu @ 1998-10-15 0:44 UTC (permalink / raw)
To: gnu-win32
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@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1998-10-15 0:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-10-15 0:44 BASH.EXE: No more processes ? Enoch Wu
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).