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.

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.

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!!

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.