Multiple Levels of Configuration Files

Modified on Tue, 7 Mar, 2023 at 3:52 PM

config.pro


Creo Parametric has three layers of config.pro files that are used to set default configuration settings:


  1. Creo Installation Directory:
    • This is a subdirectory inside where Creo was originally installed. 
    • For example: C:\Program Files\PTC\Creo 3.0\M110\Comon Files\text\ (or a variation based on the version and date code installed)
  2. User Home directory:
    • This is the directory of the “HOME” environment variable for the current user. 
    • For example: C:\Users\<USERNAME>\
  3. Working directory: 
    • This is the directory that Creo is set to upon startup. 
    • Out of the box, this is set as C:\Users\Public\Documents, however, the default working directory may be changed depending on your configuration. 
    • A good way to check this directory is to click the “Select Working Directory” button while in Creo (File -> Session -> Select Working Directory)

Note: For Creo version 9.0.2.0 and later, there is now a fourth option as well. See more information here.


These files are loaded chronologically in this order, which can be important. 

  • Let’s say that the config.pro in the installation directory contains a setting for “pro_unit_length”, which has a value of “unit_inch”. 
  • Then the config.pro at the user’s home directory level also contains this setting, but with a value of “unit_mm”.
  • If there are duplicate configuration settings found in the above files, the latter one will be used (aka, if a duplicates option is found in the working directory, Creo will use that value). So therefore, in this case, Creo would use the “unit_mm” value.


config.sup

To help “force” configuration settings onto their users, PTC provides an additional file called a “config.sup” file. This file is contained in the installation directory, is read first, and establishes settings that cannot be changed regardless of values in later config.pro files. Because of this, it is often common for administrators to also lock this file using windows file permissions so that the settings cannot be modified without administrative privileges.


Related Documentation

For more information on the above, please see:


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article