Welcome to our forums
I get runtime error R6034: Incorrectly loading c++ runtime library whenever I start ftn95. The coompiler still runs, usually, and I have reinstalled the ftn95 package. Any suggestions?
Paul Mather
This is a strange one because FTN95 does not directly call a Microsoft C++ runtime library. It uses its own runtime library which is in salflibc.dll.
If you Google the error number then you get all kinds of advice which may or may not be relevant.
I don't see how it can have anything to do with FTN95 itself but presumably is some kind of systems fault on your machine.
It is odd to find that not all windows25 machines do not output this error and as the compiler still works I think I will leave it and hope that it is fixed in a system update.
Thanks for your time.
I get the same error message occasionally. I don't know why and I ignore it.
BTW, I'm using Windows 10 on an HP Envy Laptop.
Dan 😄
I get the same error message occasionally. I don't know why and I ignore it.
BTW, I'm using Windows 10 on an HP Envy Laptop.
Dan 😄
I get the same problem, if i compile with /debug and that generates some warnings/errors, then the compilation batch file stops until I click the OK button on the R6034 error window, at which point the compilation completes successfully (if there were only warnings) and the batch script continues .
interestingly, if i compile from within my editor (PsPad) and capture the errors in the log window, it doesn't generate the R6034 error.
K
an update on this:
I found that, if i started the compiler from a certain directory, the error didn't occur. Further investigation showed up that, in the other offending folder, there was an old copy of MSVCR80.DLL - removing it solved the issue for me.
k
I found several versions of msvcr.dll, the latest apparently related to the installation of a new Epson printer. DOS Dir gave 6 versions, but File explorer only found 2, so I added 'old' to the name of the older file but I still got the error message.
How did you discover a relationship between msvcr80.dll and Ftn95? not purely fortuitously, I bet!!
Paul
Quoted from PaulMather I found several versions of msvcr.dll, the latest apparently related to the installation of a new Epson printer. DOS Dir gave 6 versions, but File explorer only found 2, so I added 'old' to the name of the older file but I still got the error message.
How did you discover a relationship between msvcr80.dll and Ftn95? not purely fortuitously, I bet!!
Paul
i noticed that when i invoked ftn95 from within one particular folder, i didn't get the error. I passed this on to Silverfrost and they suggested that there might be a DLL in the folder that was having the issue. then it was just a a case of binary chopping the DLLs, renaming them to .LLD, until i isolated the one causing the problem.
K