Intel® Software Network

I am not familiar with .FMK files.  Please post an excerpt.  Is this perhaps PowerStation 1.0, the 16-bit Windows version?

I don't know if they're still in business (or what price), but the web site is active:
http://www.emsps.com/oldtools/msfor.htm
I didn't check EBAY but there are likely other sources.

The Microsoft Fortan Powerstation 1 is a F77 with F90 like extensions compiler embedded in Visual Studio 97 but targeted for 32bit DOS application (Pharlap Dos extender) and QuickWin applications.

The compiler doesn't run  under Windows NT/2000/XP.

The FMK (project) file is a text file structured like a "make" file. You can find in it all the sources files, compiler and linker options.

I think it will be easier to upgrade to IVF.

 

Here is a small portion of the beginning of the .FMK file.  If anyone can tell me what version it belongs to, that'd be great.  The instructions I have for compiling the software are to open three different .FMK files and rebuild all, so without being able to open the .FMK files to compile I can not compile the software easily.  If you would like to see the full .FMK file or the entire software package to see if you can compile it without the .FMK file, please e-mail me.  My e-mail is in my profile information.

.FMK File.....

PROJ = TREETOPS
DEBUG = 1
PROGTYPE = 0
CALLER =
ARGS = joe-tc14
DLLS =
D_RCDEFINES = -d_DEBUG
R_RCDEFINES = -dNDEBUG
ORIGIN = F32VWB
ORIGIN_VER = 1.00
PROJPATH = C:TREE10BINTREETOPS
KNARF =
F32 = fl32
F32FLAGS_D_DEXE = /Zi
F32FLAGS_R_DEXE = /Ox /DNDEBUG
F32FLAGS_D_LIB = /Zi
F32FLAGS_R_LIB = /Ox /DNDEBUG
L32FLAGS_D_DEXE = -machine:i386 -base:0x00010000 -subsystem:console -entry:mainCRTStartup -debug:full -debugtype:cv4
L32FLAGS_R_DEXE = -machine:i386 -base:0x00010000 -subsystem:console -entry:mainCRTStartup
L32FLAGS_D_DEXEUB = -machine:i386 -base:0x00010000 -subsystem:console -entry:mainCRTStartup -debug:full -debugtype:cv4
L32FLAGS_R_DEXEUB = -machine:i386 -base:0x00010000 -subsystem:console -entry:mainCRTStartup
LIBS_D_DEXE = libf.lib libc.lib kernel32.lib ntdll.lib
LIBS_R_DEXE = libf.lib libc.lib kernel32.lib ntdll.lib
LIBS_D_BEXE = libf.lib libc.lib kernel32.lib ntdll.lib
LIBS_R_BEXE = libf.lib libc.lib kernel32.lib ntdll.lib
RUNFLAGS =
OBJS_EXT =
LIBS_EXT =
!if "$(DEBUG)" == "1"
F32FLAGS = $(F32FLAGS_D_DEXE)
L32FLAGS = $(L32FLAGS_D_DEXE)
LIBS = $(LIBS_D_DEXE)
!else
F32FLAGS = $(F32FLAGS_R_DEXE)
L32FLAGS = $(L32FLAGS_R_DEXE)
LIBS = $(LIBS_R_DEXE)
!endif

If that's representative of the .FMK files, then I'd suggest you don't need them.  Just create a Fortran Console Application in Visual Studio, add the source files and build.  That does look like PowerStation 1.0 and is a kind of project file.  These are not supported now.

It is a FMK file from Powerstation 1.0 for a DOS 32bit application with no additional libraries and obj files and no specific compilation options.

I think it will be relatively easy to compile with IVF if graphical functions are not used (search for inclusion of fgraph.fd and fgraph.fi in source files)

In IVF use :
/fpscomp:general   general powersation compatibility
/assume:byterecl    for record length in the Open statement of direct access files

If there is interface statements, they must be changed because the syntax in fortran Powersation is different :
Powerstation :

interface to subroutine ...

end

positionned at the beginning of each source file.

IVF

interface

subroutine ...

end

end interface

positionned in each subroutine or function.

IVF supports INTERFACE TO, but not when placed at the beginning of the file.  IVF also supports a lot of the graphics routines from fgraph.fd (and supports that include file.)