View previous topic :: View next topic |
Author |
Message |
PaulMather
Joined: 19 Sep 2017 Posts: 10 Location: Nottingham
|
Posted: Tue Oct 17, 2017 5:27 pm Post subject: Error Message when ftn95 is started |
|
|
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 |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7931 Location: Salford, UK
|
Posted: Tue Oct 17, 2017 9:26 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
PaulMather
Joined: 19 Sep 2017 Posts: 10 Location: Nottingham
|
Posted: Fri Oct 20, 2017 4:34 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
kaliuzhkin
Joined: 17 Sep 2012 Posts: 33
|
Posted: Sat Oct 21, 2017 8:15 pm Post subject: Me too |
|
|
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
|
|
Back to top |
|
|
kaliuzhkin
Joined: 17 Sep 2012 Posts: 33
|
Posted: Sat Oct 21, 2017 8:16 pm Post subject: Me too |
|
|
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
|
|
Back to top |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
Posted: Thu Oct 26, 2017 2:24 am Post subject: |
|
|
Quote: | ... windows25 machines ... |
Mr Gates has been prolific .... 10 straight to 25 eh ... I want one !!! :O) lol |
|
Back to top |
|
|
KennyT
Joined: 02 Aug 2005 Posts: 317
|
Posted: Mon Nov 27, 2017 6:14 pm Post subject: |
|
|
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 |
|
Back to top |
|
|
KennyT
Joined: 02 Aug 2005 Posts: 317
|
Posted: Wed Dec 20, 2017 12:48 pm Post subject: |
|
|
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 |
|
Back to top |
|
|
PaulMather
Joined: 19 Sep 2017 Posts: 10 Location: Nottingham
|
Posted: Wed Dec 20, 2017 4:09 pm Post subject: |
|
|
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 |
|
Back to top |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
Posted: Wed Dec 20, 2017 6:58 pm Post subject: |
|
|
it must have been a beta-max version of the msVCR80.dll causing the problem |
|
Back to top |
|
|
KennyT
Joined: 02 Aug 2005 Posts: 317
|
Posted: Wed Dec 20, 2017 8:56 pm Post subject: Re: |
|
|
PaulMather wrote: | 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 |
|
Back to top |
|
|
|