Message-Id: <200110051113.f95BDOj26371@postino3.int.prima.com.ar>
From: "Orlando P. Hevia" <heviaop AT ciudad DOT com DOT ar>
To: djgpp AT delorie DOT com
Date: Fri, 5 Oct 2001 08:12:04 -0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: fortran scratch files
In-reply-to: <3BBD743A.B89039B6@is.elta.co.il>
X-mailer: Pegasus Mail for Windows (v3.12b)
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Eli Zaretskii wrote:

> 
> Look in the directory where the TMPDIR environment variable
> points, normally %DJDIR%/tmp, where %DJDIR% is the root of
> your DJGPP installation.  In my testing, the file name looks
> like forta52a.

Thanks you.

> 
> Why is this important, anyway?  These are scratch files, so
> their location should not be important, I think.

We (Alternative Transients Program developers) found a 
problem when the Ming32 version aborted without known 
reason.

The problem was in the scratch files, that were not 
deleted.

The cause was found that a lot of previous executions of 
the program aborted before the CLOSE sentence, of before 
the normal STOP. 

This is not frequent, few users reported the problem.

For Mingw32 files are fort.52 the first time, fort.52n 
(n=1,9) for following times.

Deleting fort.52 in %TMP% is the cure.

For DJGPP, the same problem may appear (not frequently, of 
course), but with your answer, we have the cure for DJGPP 
now.

Regards,

OPH. 2001-10-5 8:12


Ing. Orlando P. Hevia   
heviaop AT ciudad DOT com DOT ar
Santa Fe-Argentina