Date:	Thu, 17 Feb 2000 10:37:58 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Sherlock Campbell <scampbell AT mail DOT utexas DOT edu>
cc:	djgpp AT delorie DOT com
Subject:	Re: pipes in bash
In-Reply-To:	<4.2.0.58.20000216110515.00961be0@mail.utexas.edu>
Message-ID:	<Pine.SUN.3.91.1000217103715.20415O-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 16 Feb 2000, Sherlock Campbell wrote:

> CONFIG.SYS
> 
> REM [Header]
> Rem TShoot:
> FILES=32

Try enlarging this number (to 60 or something) and see if that helps.
You will need to reboot in order for the change to take its effect.

> DEVICE=c:\windows\setver.exe

Try without this line.  SETVER is evil.

Btw, what is this DMI thing you have installed?  For example, the
following lines show it:

> SET WIN32DMIPATH=C:\DMI\
> Rem TShoot: SET PATH=C:\DMI\BIN;D:\PROGRA~1\BORLAND\CBUILDER\BIN
> SET PATH=D:\PROGRA~1\HLM;C:\DMI\BIN;C:\LSA\bin;

[DJGPP.ENV:]
> +PATH_SEPARATOR=:
> +PATH_EXPAND=y

Why did you need these two lines?  I think they can be dangerous,
although I cannot find any immediate link to your problem with pipes.
I suggest trying without them, just in case.

In any case, you shouldn't edit DJGPP.ENV to add such lines.  You
could set them in the environment, e.g., from AUTOEXEC.BAT.  Editing
DJGPP.ENV is a Bad Idea (tm).

- Raw text -