I am trying to get a session of Creo 2 to start in a completely default - out of the box - configuration. I thought I could do that easily by simply pointing my launch shortcut icon to "start in" an empty folder (that has no config.pro, sys.col, tree.cfg,.etc.)
That sort of works, but there are still remnants of my custom config showing up - most notably some homemade icons in my quick launch toolbar that are pointing to Mapkeys that do not exist.
Does anyone know where Creo is finding my custom stuff remnants - and more importantly how to get it to stop looking there? It sounds like there's a config.sup hiding in my load point or something, but I am only smart enough to know some of the terminology - not where to look nor how to finagle the files. Any helpers out there can guide me?
On a similar note - I am running M090 and currently downloading M110. I don't mind installing M110 as a default UI install and keeping M090 as my customized UI install. I only need to have a default install for a couple of weeks until the PTC Live event is past. Would that make things easier - to install a different build to its own folder and keep it default?
The UI customization file goes into the cache folder. That's buried deep in the Windows user directory. You can set it by environment variable, which we do here so that we can have control over those files instead of Windows. Since our setup is custom, I don't recall where the default location is.
That's no longer the case by default; it goes to that folder I mentioned in my last email.
You can set the config option load_ui_customization_run_dir to yes, then it is read from and saved to your start up directory. However, if you are working outside of a PDM system, however, this will potentially result in *.ui files in all your project folders as Creo saves it to your working directory without prompting whenever you move an icon or add a Quick Launch button.
You will need to make sure that any of your config.pro and/or config.sup files are "put on ice." I would recommend finding them and renaming them with some kind of label like config-old.pro just so that Creo doesn't read it.
Summary (and rant...) factory default session of Creo2
Thanks to all of you who replied. The valuable pieces of info I got was access to the File>Help>System Info file that lists the configs loaded - and the path to my Windows user folder that has a "creo_parametric_customization.ui" file in it.
Removing (renaming) that file does strip Creo of all custom Ribbon Tabs and Quick Launch customizations. It does not remove the folder favorites list - that is kept in a cache file somewhere - David Haigh presented on that and I wish I had attended. I don't need this enough to spend the time learning it now, though.
Good tip to install virtual box and put a fresh Creo install on it. Again, I don't want to open a can of worms when I have minimal needs.
I tried setting "load_ui_customization_run_dir" to yes - but it does not seem to read ALL of the customization settings from the ui file that is created. The custom ribbon tab and the icons I added to QL toolbar are not kept there. They remain in the Windows user folder. How to change that location.?
Rant - why would they split the .ui file into two ? I am sure there is a good coding reason for it. But it sure is a PITA as well as pretty confusing.
There also exists a "creo_parametric_admin_customization.ui" that lives in the loadpoint. I am not sure what that controls and if it can help me or not. But I think I am well off enough to do what I need to with a little effort.