Xref: utzoo comp.unix.i386:2901 comp.sys.att:8766
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!ucsdhub!cuuxun!cuuxb!fmcgee
From: fmcgee@cuuxb.ATT.COM (~XT6561110~Frank McGee~C23~L25~6326~)
Newsgroups: comp.unix.i386,comp.sys.att
Subject: Re: VP/ix Question
Summary: how dos does temp files
Message-ID: <4478@cuuxb.ATT.COM>
Date: 12 Feb 90 17:48:15 GMT
Expires: 12 Mar 90 00:00:00 GMT
References: <388@westmark.UU.NET>
Reply-To: fmcgee@cuuxb.UUCP (Frank W. McGee)
Followup-To: comp.sys.att
Distribution: na
Organization: AT&T Computer Systems, Lisle, IL
Lines: 29

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)