Ms Fortran Powerstation 4.0
RE: Fortran Power Station 4.0RE: Fortran Power Station 4.0. Date: Tue, 2 Mar 1999 12:56:31 -0600. From: 'Nathan Blair'. Subject: RE: Fortran Power Station 4.0Yan,My advice is to stop what you are doing and start working within the MSPowerstation 4.0 environment to create and debug FORTRAN code. Thedevelopment environment is the best thing about the Powerstation 4 compilerand I wish we had had it years ago. To get started with the Powerstationdevelopment environment, please read the document called 'Using CommonFortran Compilers with TRNSYS' from the following webpage:I would also suggest that you read the general FORTRAN information page at:This should get you started with using the development environment. Thereare also books available (probably from www.amazon.com) on using thePowerstation compiler.Nate Blair.Nathan BlairUW Solar Energy Laboratory PHONE: 608-20 Engineering Drive FAX: 608-262-8464Madison WI 53706 USA'You can teach a better sermon withyour life than with your lips.'
- Oliver Goldsmith.-Original Message-From: owner-trnsys@relay.doit.wisc.edu Behalf Of Yianno KadisSent: Tuesday, March 02, 1999 12:08 PMTo: TRNSYS Emial GroupSubject: Fortran Power Station 4.0Hello everyoneI am trying to run a simulation with a solid desiccant model which I havedownloaded from the TRNSYS web site (the file is called 1302NEW.for)The compiler I am using is Microsoft FORTRAN Power Station 4.0 butunfortunately I do not have any manuals for it. I have tried to follow thesimple tips on how to get started using the Microsoft Fortran PowerStation4.0 compiler to create, compile, debug, and link subroutines for use withTRNSYS 14.2.Unfortunately I am having trouble understanding the steps required to dothis. For example the first step states 'from the command line (DOS prompt)enter the following: fl32.exe/c/Ox/G5. Which Dos prompt is this?How do I do this?
The next step refers to a file called link.fp4 and thestatement link @link.fp4 to form the Dynamic Link Library. Where do I writethis statement?Also some statements need to be written into the TRNSHELL program under thefilesetupcompiler menu.
The instructions say to insert the line:MSDEV BIN FL32.EXE/c/Ox/G5 on the compile line but what do you enter in therebuild and user command lines?Can someone please just run me through the steps in easy to understandlanguage so as I can use FORTRAN written source code programs into a TRNSYSsimulation.Many thanks for your helpYan Kadis. References:. From: Yianno Kadis. Prev by Date:. Next by Date:. Previous by thread:. Next by thread:.
Index(es):.
Well the last time I used Powerstation was in a previous century so my memory might not be that good.If I recall well Powestation never made windows applications only ms-dos applications, I recall using microsoft graphics primatives to create a user interface. I think you will need to do some work but maybe not much work.Your phrase 'visual components / dialogs' worries me. What graphics does this program use (if any)? Do you have and third party libraries that are used? How many fortran source files do you have?
Is it a mixed language program?I think maybe you need to give us some more information.You could just create a new project (of the correct type) in Visual studio, add your source files to the project and then look at what errors result as a starting point. Thanks for answers!It is a FORTRAN program. MSFLIB is used. No graphics is used, only simple dialogs with input field controls and command button controls.I have created a new project solution (QuickWin), included all code modules.Also included the (resource.fd) as well as the script (script.rc) defining the different dialogs in the project.also off course USE IFLOGM.'
Schabort, Victor wrote:How do I make the dialog identifiers visible in the code - its declared in the.fd file and defined in the script, but the program somehow does not see it at run time?I also struggle to view the script.rc in the resource editor viewer.it gives identifier errors.The resource editor saves an.rc file, script.rc in your case and resource.h (header include for C language). Intel have a utility deftofd.exe that takes the.h file and makes a fortran include.fd file.
Microsoft Fortran Powerstation 4.0
You normally set a pre-build step to do this automatically. If you do a forum search you will find instructions on this.I presume this is an old.rc file? Fixing it is possible with a text editor but a bit hard to know what the problem is. If it is one or two simple dialogs creating a new resource file might be easier.
You could post the broken.rc and.h so we can look at them. You do not need to create a QuickWin application in order to use dialog boxes. INTERFACEinteger(4) FUNCTION ControlPanel(arg)! Or integer(DWORD)!DEC$ ATTRIBUTES STDCALL, ALIAS:'controlpanel':: ControlPanelinteger(4),POINTER:: arg!
Or integer(DWORD)END FUNCTIONEND INTERFACE.integer(INTPTRKIND):: ControlPanelHandle = 0integer(INTPTRKIND):: ControlPanelStack = 0! Inheritinteger(INTPTRKIND):: ControlPanelArg = 0integer(4):: ControlPanelFlags = 0! Or integer(DWORD)integer(INTPTRKIND):: ControlPanelThreadID = 0.! Create seperate thread to run the Modal Dialog control pannelControlPanelHandle = CreateThread(&& NULL, ControlPanelStack, loc(ControlPanel), loc(ControlPanelArg), && ControlPanelFlags, loc(ControlPanelThreadID)).integer(4) FUNCTION ControlPanel(arg)!DEC$ ATTRIBUTES STDCALL, ALIAS:'controlpanel':: ControlPanelUSE IFLOGMuse GlobalDataimplicit noneINCLUDE 'RESOURCE.FD'integer(4),POINTER:: arginteger(4) returnVal, nsCHARACTER(256) textLOGICAL retlogexternal ControlPanelCallBackretlog = DLGINIT( IDDDIALOG1, ControlPanelDlg )if(.not. Retlog) write(.,.) 'Dialog error for IDDDIALOG1'call DlgSetTitle( ControlPanelDlg, ControlPanelTitle )! Set your callback functions hereretlog = DlgSetSub( ControlPanelDlg, IDCRADIO1, ControlPanelCallBack ).ControlPannelRunning =.true.! Used by main program to know modal dialog is runningreturnVal = DlgModal( ControlPanelDlg )!
Doesn't return unless cancled (or IDCevent not specified)ControlPanelExit =.TRUE.! Used by main program to know modal dialog has completedControlPanelPause =.FALSE.! Used by main programControlPanel = returnValend FUNCTION ControlPanel.SUBROUTINE ControlPanelCallBack( dlg, id, callbacktype )!DEC$ ATTRIBUTES DEFAULT:: ControlPanelCallBackUSE IFLOGMuse GlobalDataimplicit noneINCLUDE 'RESOURCE.FD'TYPE (dialog) dlgINTEGER id, callbacktype, iStatCHARACTER(256), automatic:: textLOGICAL retlogINTEGER cel, far, retintreal(8), automatic:: xyz(3)text = 'undefined'ControlPanelPauseRefresh =.true.NextDisplayTime = 0! Update nowSELECT CASE (id)CASE (IDCRADIO1)! Radio button 1 selected by user so! Change display accordinglyvIavDisplayFrame = 0!
VIavDisplayFrame = 0 Inertial Frame! VIavDisplayFrame = 1 Orbital FrameCASE (IDCRADIO2).END SELECTEND SUBROUTINE ControlPanelCallBackJim Dempsey.
We paid a lot of money - I don't think this is the community edition - here is the system info:Microsoft Visual Studio 2015 Shell (Integrated)Version 14.0.23107.0 D14RELMicrosoft.NET FrameworkVersion 4.7.03056Installed Version: IDE StandardMicrosoft Visual Studio Tools for Applications 2015 0-00000-AA661Microsoft Visual Studio Tools for Applications 2015Visual Basic 2015 0-00000-AA661Microsoft Visual Basic 2015Visual C# 2015 0-00000-AA661Microsoft Visual C# 2015Intel® Advisor 2018 Update 2Intel® Advisor 2018 Update 2, (build 550069), Copyright © 2009-2018 Intel Corporation. All rights reserved.Intel® Inspector 2018 Update 2Intel® Inspector 2018 Update 2, (build 550070), Copyright © 2009-2018 Intel Corporation. All rights reserved.Intel® Parallel Studio XE 2018 Update 2 Composer Edition for Fortran Windows. Package ID: wcomplib2018.2.185Intel® Parallel Studio XE 2018 Update 2 Composer Edition for Fortran Windows.
Ms Fortran Powerstation 4.0 Program
Integration for Microsoft Visual Studio. 2015, Version 18.0.0038.14, Copyright © 2002-2018 Intel Corporation. All rights reserved. Other names and brands may be claimed as the property of others.Intel® VTune™ Amplifier 2018 Update 2Intel® VTune™ Amplifier 2018 Update 2, (build 550381), Copyright © 2009-2018 Intel Corporation. All rights reserved. Sorry, but I still find myself in a confused place.I used the Dialog sample code example supplied with the Fortran Parallel Station XE 2018 installation(.Parallel Studio XE - Fortranipsxe2018sampleswin20171109compilerfDialogTEMP) - see attach zipIt compiles 100% and runs, but the dialog identifiers are undefined at run-time, so the program cannot execute further.This code example should run as it is in my view??I have no idea why the Dialog Identifiers are still undefined.I am not sure about the C option at installation - I will try an re-install and see what the options are.Attachments.
OK I loaded that sample from the intel zip and loaded the provided vfprog into VS2017It runs fine but maybe you are finding in debug the resource constants are undefined in debug? This is because you need to compile with the option /debug-parameters:all for the debugger to display the values. This does not effect program operation.As a side note I had to 'Fix' the TEMP.rc as #include 'afxres.h' gave a file not found error which stopped compilation.I replaced this line with:#include 'winres.h'#include 'winver.h'To get it to work. I do not know if that is and sdk install issue on my machine or a problem with the sample. Thanks, here is the build html in a zip. (of the TEMP demo)Would it be possible to TeamView to check my installation?I suspect some problem with the installation or the custom build step setting.I did do a command line compilation of the rc file successfully, but the.res file is not linked to the.exe.-As a backup, I compiled the Fortran Application on MVS 1997 with Digital Fortan on an old WinXP machine. Everything worked perfectly.But it would not run on Windows 10 on my new machine.- Attachments. I used the intel sample and Vfprog file 'straight out of the box'.
The Buildlog is as follows Victors does not show the first step (create.fd) and failed on Rc command:Generating resource.fddeftofd.srcresource.h.srcresource.fdCompiling resources.Rc /fo 'Debug/TEMP.res' 'C:UserscadfiDesktopTEMPsrcTEMP.RC'Microsoft (R) Windows (R) Resource Compiler Version 10.0.4 Copyright (C) Microsoft Corporation. All rights reserved.Compiling with Intel(R) Visual Fortran Compiler 18.0.2.185 IA-32. Ifort /nologo /debug:full /Od /module:'Debug/' /object:'Debug/' /Fd'Debugvc150.pdb' /traceback /check:bounds /libs:static /threads /dbglibs /c /Qlocation,link,'C:Program Files (x86)Microsoft Visual Studio2017CommunityCommon7IDEVCbin' /Qm32 'C:UserscadfiDesktopTEMPsrcTEMP.F90' Linking. Link /OUT:'Debug/TEMP.exe' /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:'DebugTEMP.exe.intermediate.manifest' /MANIFESTUAC:'level='asInvoker' uiAccess='false' /DEBUG /PDB:'Debug/TEMP.pdb' /SUBSYSTEM:CONSOLE /IMPLIB:'C:UserscadfiDesktopTEMPMsvsDebugTEMP.lib' -qm32 'Debug/TEMP.obj' 'Debug/TEMP.res' Embedding manifest. Mt.exe /nologo /outputresource:'C:UserscadfiDesktopTEMPMsvsDebugTEMP.exe;#1' /manifest 'DebugTEMP.exe.intermediate.manifest' TEMP - 0 error(s), 0 warning(s).
Jim, I am not sure what you mean, or how to answer you.