Date:	Tue, 21 Aug 2001 20:40:00 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	sandmann AT clio DOT rice DOT edu
Message-Id:	<1438-Tue21Aug2001204000+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com
In-reply-to:	<10108211653.AA15145@clio.rice.edu> (sandmann@clio.rice.edu)
Subject:	Re: Fseek on STDIN problem on Win 2K
References:	<10108211653 DOT AA15145 AT clio DOT rice DOT edu>
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

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Tue, 21 Aug 2001 11:53:15 -0500 (CDT)
> 
> Guess what?  _get_dev_info(0) == 0 on *ANY* redirected input on Windows NT 4.0
> unless it is from CON.  So these weird handles appear on NT 4.0 also.

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

> This is also true for a real pipe on NT - it does not need to go to a 
> temporary file.  You can't seek on pipes - but it appears these strange
> handles support some limitied seeking in a strange way.

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?

> 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?

- Raw text -