dave@westmark.UU.NET (Dave Levenson) (02/01/90)
I'm trying to run MS-DOS 3.2 under VP/ix under SysV/386 r3.2.
Most MS-DOS commands and applications work as I would expect.
Pipes don't work. If I try such MS-DOS commands as:
DIR | SORT
or
FC FOO BAR | MORE
The process hangs until I re-initialize the MS-DOS process.
The problem appears to be that the COMSPEC environment variable is
set to C:\COMMAND.COM. I think this causes COMMAND.COM to build its
termporary files (simulating pipes) in the C: device. This device
is not writeable (unless I log in as root) and so it hangs.
Does anybody know a work-around other than duplicating the simulated
C: drive for every user?
--
Dave Levenson Voice: (201 | 908) 647 0900
Westmark, Inc. Internet: dave@westmark.uu.net
Warren, NJ, USA UUCP: {uunet | rutgers | att}!westmark!dave
[The Man in the Mooney] AT&T Mail: !westmark!davefmcgee@cuuxb.ATT.COM (~XT6561110~Frank McGee~C23~L25~6326~) (02/13/90)
In article <388@westmark.UU.NET> dave@westmark.UU.NET (Dave Levenson) writes: >The process hangs until I re-initialize the MS-DOS process. >The problem appears to be that the COMSPEC environment variable is >set to C:\COMMAND.COM. I think this causes COMMAND.COM to build its >termporary files (simulating pipes) in the C: device. This device >is not writeable (unless I log in as root) and so it hangs. I'm not sure, but I believe you are correct in thinking that MSDOS builds it's pipes by simulating files. To get around the problem of creating temp files, you might want to try running your commands as batch files off of drive C:, but have your batch file cd to a directory you can always write on (such as u:\tmp). So your batch file might look like : echo off PATH=lots;of;paths; U: cd \tmp [ do your own thing here ] And now you should be able to create temp files, no matter who you are. -- Frank McGee, AT&T Entry Level Systems Support attmail!fmcgee (preferred) att!cuuxb!fmcgee (those that can't reach attmail)