Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!im4u!rutgers!sri-unix!sri-spam!ames!amdahl!dlb!plx!zaphod!dick
From: dick@zaphod.UUCP (Dick Flanagan)
Newsgroups: comp.sys.ibm.pc
Subject: DOS Pipes (was: Strange DOS behavior)
Message-ID: <631@zaphod.UUCP>
Date: Mon, 18-May-87 17:16:06 EDT
Article-I.D.: zaphod.631
Posted: Mon May 18 17:16:06 1987
Date-Received: Wed, 20-May-87 02:18:24 EDT
References: <1293@ur-tut.UUCP> <746@edge.UUCP>
Reply-To: dick@plx.UUCP (Dick Flanagan)
Distribution: world
Organization: From a cave in the Santa Cruz Mountains
Lines: 19
Keywords: pipes patches

Summary:

Expires:

Sender:

Followup-To:


In article <746@edge.UUCP> doug@edge.UUCP (Doug Pardee) writes:
>In PC-DOS, pipes are implemented by writing the output of the first
>program into a temporary file on the current drive, and then giving
>that file to the next program as input.

A _long_ time ago I ran across a patch to PC-DOS 2.1 that allowed
you to change the default device that pipes were written to.  In
other words, I was able to change command.com so it wrote (and looked
for) its pipes on my ramdisk.  Needless to say, this really speeded
things up.

Ever since I have been keeping my eyes open for the equivalent patch
for PC-DOS 3.1, with 3.3 soon to be the object of my attention as
well.  Can anyone help me with locate these patches?  If so, I'll
post the good news for all!
-- 
Dick Flanagan, W6OLD
UUCP:  ...!ucbvax!sun!plx!dick
GEnie: FLANAGAN