INSIGHT checks for the existence of this file at startup and
looks for token words lacking a preceding # character (remove
the it to activate any of them). Many of the tokens have become
unnecessary with the advent of the recipe database.

#blockversioncheck: do not check for new version once-a-month
#blocknews: do not show news items at startup once-a-month
#keeplog: do not erase the log file at the beginning of every session (it is in the INSIGHT data folder)
#blockdatabase: Do not use the recipe database
#skippreferences: Do not read the startup preferences file to restore settings from last session
There is a section in the manual on troubleshooting also.

Please click the Contact link at the top of the page at
digitalfire.com to contact us.


TROUBLESHOOTING
====================================
If INSIGHT crashes during startup or shutdown, erase the INSIGHT 2008
Preferences.XML Dictionary file. It saves session-to-session information and
INSIGHT will behave as if you are starting it the first time. INSIGHT
also logs start-up and shut-down in a file named insightlog.txt (also
in the documents folder).

INSIGHT defines the following file paths (maping to non-obvious operating system paths indicated):

Documents Folder
MDT Folder - documents/insight
Recipe Folder - documents/insight
Temporary Folder
Preferences Folder
INSIGHT Application Folder - Program Files or Applications

In Linux they are all mapped to the INSIGHT folder in the users home folder.
When INSIGHT starts it writes lines into the insightlog.txt file showing where it is maintaining each.

INSIGHT reads and optionally writes the following file types in the above locations:

Recipe files: Recipe folder
Materials files: MDT folder
Recipe database: MDT folder
Temporary files: Temporary folder
Language files: Application folder
Reports files: Documents folder
Report template files: Documents folder
Preferences files: Preferences folder
Log file: Preferences folder
Overrides file: MDT folder