Reading of Configuration Files at Startup
A PTC application automatically reads configuration files from several locations. If an option is in more than one configuration file, the most recently loaded or the most recently read setting is applied.
At startup, a Creo application first reads in a protected system configuration file called config.sup. It then searches for and reads in the configuration files (config.pro, config.win, and menu_def.pro) from various directories in the following order:
1. <creo_loadpoint>\<datacode>\Common Files\text (creo_loadpoint is the Creo application installation directory)—Your system administrator may have put configuration files in this location to support company standards for windows configuration settings, formats, and libraries. Any user starting a application from this loadpoint uses the values in this file.
2. HOME environment variable—You can set this environment variable to pint to a directory created for you login ID. You can place your configuration files here to start the Creo application from any folder without having to copy the files in each folder.
3. Startup directory—This is your current or the working directory when you start a Creo application. Since the local configuration files (config.pro, config.win, and menu_def.pro) in this directory are the last to be read, they override any conflicting configuration file option entries. The config.pro file does not, however, override any config.sup entries.