From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10108211758.AA12162@clio.rice.edu>
Subject:	Re: Fseek on STDIN problem on Win 2K
To:	eliz AT is DOT elta DOT co DOT il
Date:	Tue, 21 Aug 2001 12:58:19 -0500 (CDT)
Cc:	acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com
In-Reply-To:	<1438-Tue21Aug2001204000+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Aug 21, 2001 08:40:00 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> Does this depend on the shell in use?  E.g., what happens if you use
> command.com instead of cmd.exe?

I *ALWAYS* use cmd.exe, but it doesn't make any difference.

> I can understand why seeking on pipes doesn't work--it doesn't wiork
> on Unix either.  But redirected files? whatever gave the NT folks the
> idea they can stop supporting it?

Actually it does work on pipes on NT (with the observed bugs).

> > For example, I can do dir | test and see the same strange behavior, but
> > no file is created on disk.
> 
> Hmm?  Are you saying that "dir | test" doesn't go through a disk file?
> Is that cmd.exe or command.com?

Correct, no disk file.  For both cmd.exe and command.com as far as I can
tell.

For example dir /s \ | more on DOS takes a while, then more starts 
displaying; this is instantaneous on NT.

- Raw text -