Date: Sun, 15 Mar 1998 15:05:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Mitchell Spector <spector AT EnchantedLearning DOT com>
cc: HANRIGOU Philippe <HANRIGOU AT cgste DOT mq>, djgpp AT delorie DOT com
Subject: Re: Problem with bash
In-Reply-To: <3507B50E.6355@EnchantedLearning.com>
Message-ID: <Pine.SUN.3.91.980315150435.9708J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 12 Mar 1998, Mitchell Spector wrote:

> I just downloaded bash, and I'm having exactly the same problem.
> (I've had no difficulties at all with djgpp.)  I'm running
> Windows 95 version 4.00.950a, with "Microsoft Plus! for Windows 95".
> bash hangs for me in the same way as has been described here.  If I
> start up in DOS, though, bash seems to work fine.

Please post the same system information that Philippe posted.  I would
like to look for common peculiarities in your two configurations.

> What I noticed was that if I type 16 characters
> (getting no apparent response at all), the system then starts to beep
> at each character typed, as if I had exceeded the length of an
> input buffer.

That would mean that Bash is busy-waiting, stuck in some endless loop
waiting for something.  But the BIOS keyboard handler still works,
which is why you get the beeps when the keyboard typeahead buffer
fills.

> The other thing that might be related is that I'm quite low on
> hard drive space.  go32-v2 executed within bash reports:
> DPMI memory available: 9335 Kb
> DPMI swap space available: 13065 Kb

This is not low enough to expect problems in Bash.