forums.silverfrost.com

[GlenFlint]

I'm having trouble installing SilverFrost FTN95 Express on a computer that can't be attached to the internet. The computer is running Windows XP Service Pack 3 and the CD contains only Silverfrost FTN95 Express.msi. Is there something else that should be installed first that would resolve the problem?

Here is the error message:

[GlenFlint]

I have ftn95_express.exe on the CD, not the msi. Sorry for the confusion.

[PaulLaidler]

Did you intent to use Visual Studio?
If not then you may find that all of the relevant components have been installed anyway.
You would find things like ftn95.exe, slink.exe, plato.exe etc in the Silverfrost folder and you could start by opening up the IDE called Plato.

[GlenFlint]

We don't need Visual Studio, though the standalone PC has Visual Studio 2005, which is not detected during the Silverfrost installation. After installing the Personal Edition we were able to build a simple hello world FORTRAN program using PLATO, but unable to see its output.

On another machine, on which I have admin privileges, the output from the hello world program is preceded by a splash screen stating that "This program was built with a Personal Version of FTN95 etc." That splash screen does not appear on the standalone PC. We go immediately to the MS/DOS looking window that says "Press RETURN to close window . . ." When the program was modified to write to a file, no file was created.

During the installation, on the standalone machine, there was a warning that the PATH variable couldn't be updated because we were not the system administrator. The administrator could not be found and we pressed ahead. The readme.txt file did not shed any light on how to set the PATH variable. Could that be the reason the program does not appear to be running?

[PaulLaidler]

The PATH environment variable should include the Silverfrost FTN95 folder.

The default installation puts FTN95 into C:\Program Files\Silverfrost\FTN95 for a 32bit operating system. This is the folder to include in the PATH.

Under Windows 7, the current release of Plato may need to run with Administrator privileges unless you first copy Plato.exe to a different folder. Otherwise you may not have write access to the associated ini file.

[GlenFlint]

Good news: The system administrator re-installed FTN95 Personal Edition and the compile is working.

Bad news: We created a new project and used "add existing" to bring in around 120 FORTRAN files. The files are named *.f and *.FI (FORTRAN includes). Build reports that it can't find the *.FI files. There appears to be no way to move them into the "Include files" folder of Plato.

We removed the *.FI from the "Source files" folder and afterwards they magically appeared in the "Include files" folder, but are still reported as missing during a build.

Is there some naming convention or method of pointing to the include files that would resolve this problem?

[JohnCampbell]

If you look in the ftn95 include directory "C:\Program Files (x86)\Silverfrost\FTN95\include" there are a number of file name extensions.

My understanding is that:
.ins is typically used for an include file
.for is typically used for a fixed format fortran
.f90 is typically used for free format fortran
.f95 is typically used for free format fortran

I think this applies to most compilers, although .f95 extensions are not recognised by some other compilers.

FTN95 help states:
By default, files that have a .F95 or .F90 extension are assumed to be free format files whilst files that have a .FOR or .F extension are assumed to be fixed format files.

You may note that most of the supplied .ins files are formatted so that they can be interpreted as either fixed or free format. This is achieved by placing an & in column 73 (for free) and column 6 (for fixed) of the next extension line.

John

[PaulLaidler]

If the compiler is reporting an INCLUDE file as missing then either the INCLUDE statement has the wrong form or the file name is wrong in some way.

Here is an INCLUDE statement

INCLUDE 'filename.ins'

You can use single or double quotes and any extension. If the file is not in the same folder as the current file then you must give the full path or use something like ..\filename.ins to go up one folder etc.

For fixed format FORTRAN the statement must start at column 7 or after.

As you have noted, Plato does not treat INCLUDE files as source files but adds them automatically to the Include section of the Project Explorer window.

Also, if you want Plato to apply syntax colouring to .fi files then you will need to add .fi to the relevant "File filter". You will find this in the Options dialog that is opened from the Tools menu. Go to Text editor, then Language settings and select Free format Fortran or Fixed format Fortran. Now add ;.fi to the end of the list of filters.

[GlenFlint]

Thanks for the help, it's working much better now.

We're still dealing with a few differences between FORTRAN compilers.

This bit does an implied do loop:

[PaulLaidler]

It is possible that lists like

(ja, jr, rust(1, ja, jr, 1 ))

within an implied DO loop, are OK in Fortran 66 but are nolonger standard conforming.

In other words FTN95 does not support this extension to the standard.

[JohnCampbell]

I think there was more than that wrong with the write statement. The following adaptation may be closer to what is required.

[GlenFlint]

Thank you again! The extra pair of unneeded parenthesis appear to have generated error 571.

[JohnCampbell]

Other necessary changes were:
corrected the implied do loop "jr = maxlr" to "jr = 1, maxlr"
changed the fortran unit number from 7 to 17 ( 7 is not a portable number )
opened the required file on unit 17
initialised "rust" with FORALL
changed the format from E to ES ( looks a lot better )