www.coridium.us/forum

where are error.log files kept? [c:\program files (x86)\Coridium -- per the "save as popup"
Are they 'admin' only permissions
AS win10 file search doesn't show them
BUT when I save it - I can see the other two *.log files !!

Somewhere along the line Windows started prohibiting writes into Program Files directories. With that change there is an environment variable %temp% for temporary directories.

Our tools write into %temp%\Coridium any log files, temporary files, intermediate files and error logs.

In %temp%\..\..\Roaming\Coridium is where settings for the tools are kept in .ini files

For some reason (ask Bill sometime) the %temp% directory is not easily accessed from File Explorer and is not normally searched for files. You can access it by typing %temp% into the address window of File Explorer.

I checked [User]\App Data\Local\Temp\Coridium\ no logs - I have the results of compiling....
I checked [User]\App Data\Roaming\Coridium\ no logss - just the Basic & MiC ini files
I check the c:\Windows\temp file - no Coridium folder (needed Admin to look at it)
*
%temp% in File Exxplorer url window shows " [User]\App Data\Local\Temp"

What files are you looking for, that is where BASICtools and MakeItC write anything, except in MiC (MakeItC) which writes a log file of compiler steps into the source directory?

There are not any others.

I don't know what "save as a popup" means.

I got an error file while doeing a 'refresh' of the debug/Variables display --
lost commmunitcations **
I created this log file by coping the window data into Notepad

"save as popup" is the (TCL?) windoww that 'popsup' when you want to save the< log file> button
from the Error message window of ?Tcl?.

I created the same issue by interrupting the variable refresh process which became automatic at one point.

That interruption gets Stamp and PC out of sync, and you need to reset ComXX selection. So auto refresh of these windows is being disabled.

Save to log puts it wherever you tell it to (I assume).

Basicchip wrote:

Save to log puts it wherever you tell it to (I assume).

'
This is true - BUT thedefault is the c:\Program files (x86)\Coridium

Well that is the working directory of the tools, so your point?

My Point ; folks need to be aware of the 'default' location for log files is inaccessable,

Basicchip wrote:

Somewhere along the line Windows started prohibiting writes into Program Files directories. With that change there is an environment variable %temp% for temporary directories.

Our tools write into %temp%\Coridium any log files, temporary files, intermediate files and error logs.

'
I wrote:

*
%temp% in File Exxplorer url window shows " [User]\App Data\Local\Temp"

I see a conflict "Our tools write into %temp%\Coridium any log files......" --maybe two different APPS are writing the log file.