Message-Id:	<3.0.1.16.19980709205958.27afae5e@shadow.net>
Date:	Thu, 09 Jul 1998 20:59:58
To:	"John M. Aldrich" <fighteer AT cs DOT com>
From:	Ralph Proctor <ralphgpr AT shadow DOT net>
Subject:	Re: Compile gives Abort! error
Cc:	djgpp AT delorie DOT com
In-Reply-To:	<35A442C3.B06EDBF2@cs.com>
References:	<6o005b$r$1 AT nnrp1 DOT dejanews DOT com>
Mime-Version:	1.0

At 12:10 AM 7/9/98 -0400, you wrote:

>I think I should add a test for TMPDIR to DJVERIFY, except that I still
>haven't figured out how to test a drive/directory for writeability...
>any ideas?

Ah, John, you don't need to do that. DJVERIFY is just fine. Rememeber a
year or so ago I wrote
you while I was testing it and thought maybe a temp directory test would be
needed? Well, I just
test it by undeleting the files left in the temp directory.

I have: SET TMPDIR=D:\   [That's a 4mb ram disk]

Then after a compile run I go to D:/>undelete [enter] and pow! the story
unfolds. The file are all
undeletable. How can you beat that for a test? Try it with a hello world
compile--you'll get three
files remaining on the ram disk and it tells quite a story.

Does this make sense?  Looks good to me, but if there is a fallacy here,
please let me know.

Ralph

- Raw text -