From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10110112130.AA13896@clio.rice.edu>
Subject: 4NT pipe problems [was Re: First round of XP tests]
To: tim DOT van DOT holder AT pandora DOT be (Tim Van Holder)
Date: Thu, 11 Oct 2001 16:30:53 -0500 (CDT)
Cc: djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au ('Andrew Cottrell')
In-Reply-To: <000801c15291$e1157560$6ff8e0d5@pandora.be> from "Tim Van Holder" at Oct 11, 2001 10:18:17 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > Was this launched from cmd or command? (I use cmd).  
> 
> From 4NT.  Haven't tried under cmd yet, I think.

I can reproduce this problem under 4NT, but it isn't XP 
specific.  Under my NT 4 system, any pipe with djgpp images
seems to hang 4NT.

For example: grep if groups | grep if

This will hang 4NT.  If you kill 4NT from the task manager the NTVDM
it uses is hosed (it must be killed before the command box is useful).
If you kill NTVDM the "hung" process will return (and 4NT continues
to work).

If I pipe a non-djgpp image between them it seems to work just fine:

For example: grep if groups | more | less

This looks very much like a 4NT bug, and doesn't look XP specific.