Date: Mon, 31 Aug 1998 16:50:02 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: RJ vd Boon <rjvdboon AT cs DOT vu DOT nl>
cc: djgpp-workers AT delorie DOT com
Subject: Re: How to locate djgpp.env?
In-Reply-To: <m0zDRXE-000XeuC@sloep06.cs.vu.nl>
Message-ID: <Pine.SUN.3.91.980831164323.24142C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 31 Aug 1998, RJ vd Boon wrote:

> hmm, I don't think this will help very much, if the user (as I do)
> points his %TMP% and/or %TEMP% to the ramdrive, or maybe doesn't even
> set his %TEMP% at all (dos < v7 doesn't set %TEMP% to something, if
> you don't specify it, right?)

I didn't think this alternative would solve all the cases: that's 
impossible.  The questions is: does it solve more cases than the current 
setup?

People who change the setting of their TEMP and TMP generally know what 
they are doing, and they also read the docs.  For example, README.dos 
from tar112b.zip says this:

  5. WARNING!!!  Working with large compressed archives needs a lot of
     temporary free disk space, since `tar' invokes `gzip' via a pipe,
     which on MS-DOS is simulated with a disk file.  If you set the
     TMPDIR environment variable to a RAM disk, make sure you have
     enough space there for the uncompressed archive.  (For unpacking
     .tar.gz files, the size of uncompressed archive can be estimated
     by multiplying the compressed size by 4.)  When in doubt, point
     TMPDIR to your hard drive before invoking `tar'.  If there's not
     enough space on the drive where TMPDIR points, `tar' will
     complain about unexpected end-of-file (depending on whether you
     are creating or extracting files, the message might actually come
     from `gzip').