Would like to have "start in" directory separate from config.pro location

[pimm]

I have done a Google search as well as reviewing PTC's documentation online but haven't discovered exactly how to do that which likely isn't that difficult.

I want to have my "Start In" location to be easily accessible and my config.pro burrowed in deeper but in a location that would not change after new Creo installs.

Below shows where I would like the respective directory locations to be:

Start In: C:/CurrentWork

Config.pro: C:/CurrentWork/Creo/Settings

There is one PTC help file that seems to suggest how this might be done, but I don't know where the suggested line would get applied.

Alternate Path—You can set the environment variable PTC_CREO_ALT_SETTINGS_PATH to point to an alternative path where you store your configuration files. This path could be set to any mapped network drive or a shared OneDrive folder.

The following files are read automatically from the directory that PTC_CREO_ALT_SETTINGS_PATH points to:

◦config.pro

◦config.sup

◦creo_parametric_admin_customization.ui

◦creotk.dat/protk.dat/prodev.dat

[tbraxton · Accepted solution]

The environment variables are a Windows OS construct, not Creo Parametric.

Set environment variables in your system environment variables or within a startup script.

Use a dedicated batch file to launch Creo with all variables pre-set.

Keep your config.pro  file in a stable location and use PTC_CREO_ALT_SETTINGS_PATH to point to them—this helps when upgrading Creo versions.

[pimm]

Thank you!

I was able to replicate the independent config.pro re-location.  As for myself it saves the step of having to back out of the initial startup work directory so it will save time and help compact my settings folder for all of the pertinent templates held in it.

I hope that I can convince the rest of the group to adopt the same practice.

[tbraxton]

Using System Properties in Windows 11