Won't take me to error line

After compiling my code, and clicking on the error message, Plato won't take me to the error line. The message is 'File System Error' and 'Access denied.' (This worked on older versions on another computer). Any suggestions? Plato 4.61, FTN95 6.3.5.0, Windows 7 Pro, checkmate win32.

I looks like a runtime error so try running the program using the debugger.

This is a compile time issue. When a compiler error is detected, Plato reports the error at the bottom. It used to be when you clicked on the compiler error message, Plato would take you to the offending line of code. In my current installation, it won't take me to the offending line. Once the offending line of code is fixed, the program runs fine.

Is this always the case for every kind of error? Just add an extra false character somewhere and see what happens when you compile.

The latest version of Plato allows you to use 64 bit gFortran and you may get this kind of problem because Plato does not always recognise the layout of the gFortran error messages. Otherwise it should work OK for FTN95 and SCC.

I get this for any compiler error message. None can be clicked to take me to the offending line in the code. Also, the same happens with warnings as well. I know my Windows 7 Pro is installed as 64 bit, but FTN95 installed itself under 'Program Files (x86)' if that makes any difference. This did work on an older version of FTN95 on a Windows XP machine. Thank you for your help!

Using a 64 bit operating system should make no difference.

What happens if you right click on the error line and select 'Goto error/tag'?

The same thing: an error box pops up. The menu bar says 'File System Error,' and the message is 'Access is Denied.' If it means anything, it took Plato several seconds to respond the first time, after which subsequent responses were instantaneous.

This look like a run time error and not a compiler error.

This looks to me that you have access rights problems to some of the directories being used, probably for creating or writing a file.

If you get an error then the file sdbg.ini might be created in c:\Windows\sdbg.ini or c:\users\your_name\AppData\Local\VirtualStore\Windows\sdbg.ini

Alternatively you may not have create or write access in the directory where you are trying to compile.

Are you compiling a file in C:\ ?

If you can start the compiler and get some sort of message, then presumably you have installed the compiler and have read access to C:\Program Files (x86)\Silverfrost\ftn95

John

Just wanted to summarize. I can compile, link, and run error-free code without any trouble. Plato is listing compile errors (and warnings) at the bottom window in the usual way. All errors (and warnings) are completely normal and as expected, and disappear as the code is fixed. What is not happening in Windows 7 Pro (and worked fine in XP) is the ability for me to double click the error message in the bottom window, and then have the upper window adjust itself automatically to display the offending line of code.

Plato is trying to access a file called ErrorLog in the current working directory. Do you have read access to that file?

When looking under properties of the ErrorLog file, it is owned by administrators. System and administrators had full control access, users did not. I gave users full control access, but this did not solve the problem. I looked into the file, the contents look reasonable. The file has no associations; I had to select notepad to read it.

Plato will delete the file and create it again so giving access rights afterwards will not help. What happens if you run Plato as an Administrator?

Neither logging in as administrator, nor right-clicking Plato in my user to run under administrator, helped. I still cannot double-click to the offending code line.

As I understand it, your ErrorLog file does not have read access because of its location. Have you tried putting your files in a folder the has general access rights?

Thanks Paul and sorry for the delay. Moving my project folder to the root directory (c:\) solved the problem. Does this suggest an easy configuration change fix for me, or should we just leave it at that?

I am not sure what configuration changes you have in mind but I suggest that if you have a working solution then you leave it at that.