Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!amdahl!drivax!cavender From: cavender@drivax.UUCP (Steve Cavender) Newsgroups: comp.sys.ibm.pc Subject: Re: Strange DOS behavior Message-ID: <1524@drivax.UUCP> Date: Sun, 10-May-87 00:35:28 EDT Article-I.D.: drivax.1524 Posted: Sun May 10 00:35:28 1987 Date-Received: Sun, 10-May-87 09:19:39 EDT References: <1293@ur-tut.UUCP> Reply-To: cavender@drivax.UUCP (Steve Cavender) Organization: Digital Research, Monterey Lines: 30 Keywords: DOS In article <1293@ur-tut.UUCP> akk2@ur-tut.UUCP (Atul Kacker) writes: >I just tried the following on my PC running DOS 3.2. ... >A> TYPE filename.ext | MORE > >and I got an error message > >Write protect error writing drive A: ... >I am only trying to read from the disk. Am I missing something here ? >Atul Kacker Yes. The something missing is concurrency of processes. Since 'TYPE' and 'MORE' run sequentially, pipes in PC- or MS- DOS are implemented via files on disk. The command interpreter redirects stdout of 'TYPE' to a temporary file on drive A, which gets you the write protect error. If drive A had not been write protected, 'TYPE' would have run to completion, then 'MORE' would have been run with stdin redirected to that same file. 'MORE' can still be used on a write protected drive (at least for what you were trying to accomplish above) with the following command: A>MORE