|
forums.silverfrost.com Welcome to the Silverfrost forums
|
View previous topic :: View next topic |
Author |
Message |
MasterD
Joined: 14 Mar 2007 Posts: 1
|
Posted: Wed Mar 14, 2007 7:37 pm Post subject: *** Unable to create executable file: testprog.EXE |
|
|
Hi,
I wrote a program, testprog.f90, contents:
PROGRAM testprog
IMPLICIT NONE
END PROGRAM testprog
and trying to compile by: 'ftn95 testprog.f90 /link'
I get the following error message:
[FTN95/Win32 Ver. 5.01.0 Copyright (c) Silverfrost Ltd 1993-2006]
NO ERRORS [<TESTPROG> FTN95/Win32 Ver.5.0.1.0]
Creating executable: testprog.EXE
*** Unable to create executable file: testprog.EXE ***
*** Compilation abandoned
What's going on, most simplest program there is, tried reboot, but doesn't work, any ideas? |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7926 Location: Salford, UK
|
Posted: Mon Mar 19, 2007 9:42 am Post subject: |
|
|
This code runs OK for me.
The only possible reason for failure that I can think of is that you do not have write access to the relevant folder. |
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2388 Location: Yateley, Hants, UK
|
Posted: Sat Apr 28, 2007 11:46 am Post subject: Unable to create the .EXE |
|
|
I get this all the time, for various completely valid reasons.
Firstly, as Paul says, if you can't write to the folder / subdirectory where you want to when creating the .EXE, then this message comes up. Common reasons are because it is on a CD (!) or because you don't have write permission there ... something that happens increasingly with computers that are "managed" by an IT department.
Secondly, you can't overwrite a previous version of the EXE. Again, there are several reasons for this, including that the previous version is set to read-only, but more commonly, because it is actually in use. During a phase of writing and testing (particularly with ClearWin), it is possible for a window to be created and left running and you can't see it. Then you don't seem to be able to create a new .EXE with the same name. Simply not closing the running version has the same effect. (This is my usual problem).
I discovered last year that when attempting to write a datafile you need to have write permission in the target folder as well as to select that folder with the Windows dialog. Hence, after an OPEN statement, you need an INQUIRE (or the combination in the OPEN) to check if it was successful - just going ahead with writing causes a lock up. In my case, this was something created by my IT department ... I'm used to full access to everything about my PC.
Eddie |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|