Date: Mon, 16 Mar 1998 13:38:19 +0200 (IST) From: Eli Zaretskii To: Mitchell Spector cc: HANRIGOU Philippe , djgpp AT delorie DOT com Subject: Re: Problem with bash In-Reply-To: <350C33D5.6298@EnchantedLearning.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Sun, 15 Mar 1998, Mitchell Spector wrote: > > Please post the same system information that Philippe posted. I would > > like to look for common peculiarities in your two configurations. > > See below. I appreciate your looking at this. Thanks, but I meant mainly the CONFIG.SYS, AUTOEXEC.BAT and the output of the command "set" when typed in a DOS box configured exactly as you do to run Bash. Please post these. > Yes, but what I found slightly strange was that the buffer filled > up after only 16 characters. That's the (ridiculously small) size of the BIOS keyboard buffer. > One thing is different from what Philippe described. After I terminate > bash via ctrl-break, I find that my DOS box (within which I entered > bash) has also hung. On his machine, DOS hung for a few seconds > and then was back to normal, but on my machine it's just dead; it's > not busy-waiting since the processor usage goes back down to a low > level. I think these differences (which are minor) are due to a different Windows version you are using. > Within bash, I can run both built-in commands and regular DOS > executables (like XCOPY) without difficulty. It seems to be > just djgpp executables that cause bash to hang. Bash pulls out some very complicated tricks when it runs DJGPP programs, to make up for several blatant bugs in some commercial DPMI servers (resource leaks and such likes) which raise their ugly head when running nested DPMI programs, like when Bash invokes another DJGPP program. Something in your setup triggers some obscure bug in that part.