R6034 an Application has made an attempt to load the C runti

I was compiling a test.f90 fortran program using

ftn95 test.f90 /link

Then, I got a pop up box with the title of 'Microsoft Visual C++ Runtime Library' saying 'Program: c:\Program files (x86)\Silverfrost\FTN95\ftn95.exe

R6034 An application has ade an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information'

test.exe did seem to be produced.

But, test.f90 is a simple 'Hello word' program.
I wonder if a more complicated program is compiled, will the compilation fail? This error message is unsettling to me. How can this be fixed?

I installed FTN95 a few weeks ago. The problem only show up a few days ago. The version of FTN95 is 8.05 ACADEMIC version. The install file itself was from Dec 2016. The machine itself is a Windows 10 machine.

Dan Chan (dc7669)

This is strange. I assume that you are working from a 'Command Prompt' window but in any case I can't think how this error might arise.

Since you are using an academic license you could check that you are using it correctly.

Alternatively you could download and use the personal edition of FTN95 which can be obtained via the Silverfrost website...

https://www.silverfrost.com/32/ftn95/ftn95_personal_edition.aspx

A few people have seen this error before:

https://forums.silverfrost.com/Forum/Topic/3219 https://forums.silverfrost.com/Forum/Topic/1767

It seems to be related to old DLLs being loaded ..by something. FTN95 doesn't use these DLLs itself. However it could do indirectly. Do you know if you are compiling for .NET?

Yes, I am running 'FTN95 test.f90 /link' in a dos prompt.

I did try resinstall FTN95, but did not result in any different result.

It seems that the R6034 error showed up on as a pop-up windows when ftn95 is run, even before the test.f90 is loaded.

From the links provided, it looked like it may not be a big problem. And the exe file can still be generated.

I cannot rename the *.dll file in the install directory of Fortran to test if any of the dll is the culprit.

The easiest solution may be just let it be?!

Dan Chan