First build using VS 2008

[prstsc_coloncolon_dt]

Here I am again, (last time before I go read the WHOLE doc)
I successfully built the FXPLORER project within VS but, when I started it, I got

"The Dialog dynamic Link Library IFDNGnnn.DLL is missing or not registered."

Did I miss something during the install ?
I added in the source a few

type *,'creating window'

(as I used to do) to see the dynamic of the exec, but the output seems to be redirected to nl:

Any chance to get these outputs to a log?
I'd be pleased to do something like

C> def sys$output fxplorer.log

you see.

I would also like to find a piece of code which does the same as

if (.not. status) call lib$signal(%val(status))

instead of

"The program has crashed, do you want to send the dump to YouKnowWho"

Tx.
Bye for now.

D.

[Steven_L_Intel1]

Well, you happen to have chosen one of the perhaps two samples that fall afoul of an install bug. Here's how to fix it.

Open the folder C:Program FilesIntelCompilerFortran10.1.019IA32in. Copy the file ifdlg100.dll to C:Program FilesIntelCompilerFortran10.1.019IA32lib Then FXPLORER should run.

FXPLORER is a "Windows Application" that does not have a character-cell console window, so the TYPE goes nowhere. If you were working with a "Console Application" you'd get what you wanted. Indeed, I'd recommend sticking with Console Applications for now until you get a better feel for the environment. An easy one to start with is optimizeint_sin.f90. Just compile it and run.

Note that when you are running from inside Visual Studio, if you start debugging you must first set a breakpoint at an executable line in the program or else it will just run and exit. Also, when a debug session exits, the console window, if any, disappears. If you use the "Start without debugging" option, then the console window will remain.

It is possible to redirect the console output, if there IS a console, to a file. To do this, right click on the project, select Properties, Debugging. Set the "Command Arguments" field to:

> fxplorer.log

The > character is required. This will send all console output to that file which will be placed in the project directory. Of course, fxplorer is not a console application so this won't work. It is possible to open a console from any application type, but I think you should walk before you run.

There isn't anything like lib$signal. Windows does not have the nice exception handling that VMS makes available to all languages. There is a Fortran library routine TRACEBACKQQ that will display a traceback (this requires that the program be built with the traceback feature enabled), but it doesn't display a message.