X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10203041729.AA25371@clio.rice.edu> Subject: Re: New Win2K/XP bug report To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii) Date: Mon, 4 Mar 2002 11:29:47 -0600 (CST) Cc: djgpp-workers AT delorie DOT com (DJGPP developers) In-Reply-To: from "Eli Zaretskii" at Mar 04, 2002 07:15:13 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 > > Maybe I'm missing something on how running a shell will fix a pipe? > > If instead of "foo | less" you run "cmd.exe /c foo | less" from the Bash > command prompt, does it solve the problem? I thought you said it did, > so I suggested to run PE executables via the Windows shell. It runs just fine outside of bash, but if you do anything with cmd as above from bash it also doesn't work. for example, cmd /c dir | strings shows absolutely nothing under bash (cmd is also a win32 image). > The idea is that if cmd.exe starts with its stdout redirected, any Win32 > console application run from it will inherit the redirection. Since cmd.exe is also a win32 executable, sending its output to a djgpp image also doesn't seem to work.