factory default session of Creo2

[nrollins]

Hello everyone,



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?



Thanks!



-Nate


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[ptc-1932745]

In CREO2, go to File | Help | System Information.

A text dialog will open showing the current licence config and options.

Scroll down to "Configuration Files Read" to look for additional configs you may have missed.


Christopher F. Gosnell

FPD Company
124 Hidden Valley Road
McMurray, PA 15317

[AndyHermanson]

You also have a creo_parametric_customization.ui file hanging around somewhere. Look in your Start/Working directory, BIN location and the cache location.

[dgschaefer]

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.

Google to the rescue. According to

[MikeBrattoli]

C:\Program Files\PTC\Creo 2.0\Common Files\M100\text - "creo_parametric_admin_customization.ui"
"creo_parametric_customization.ui"

If you've saved a personal ribbon UI it would be in your Start In directory

Mike Brattoli
Moen Incorporated
Global Product Development Process Management
Administrator - PLM

[Description: Description: New Moen Logo.tif]
[Description: Description: Description: Description: Description: Description: Description: Description: fb]<">http://www.facebook.com/moen> [Description: Description: Description: Description: Description: Description: Description: Description: Description: t_logo-a.png] <">http://www.twitter.com/moen> [Description: Description: Description: Description: Description: Description: Description: Description: YouTube] <">http://www.youtube.com/moenfaucets> [Description: Description: Description: Description: Description: Description:

[dgschaefer]

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.

--

[MikeBrattoli]

Didn't know about that config option - interesting

Mike Brattoli
Moen Incorporated
Global Product Development Process Management
Administrator - PLM

[Description: Description: New Moen Logo.tif]
[Description: Description: Description: Description: Description: Description: Description: Description: fb]<">http://www.facebook.com/moen> [Description: Description: Description: Description: Description: Description: Description: Description: Description: t_logo-a.png] <">http://www.twitter.com/moen> [Description: Description: Description: Description: Description: Description: Description: Description: YouTube] <">http://www.youtube.com/moenfaucets> [Description: Description: Description: Description: Description: Description:

[davehaigh]

Suggest you take a look at my presentation a couple years ago. Creo Admin 101. Look at slides 11, 14, 15, 25, 30, 32

[mlocascio]

Nate,



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.



Michael P. Locascio

[nrollins]

Hi all,



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.



Thanks again to you all.



-Nate

[davehaigh]

Nate,
As you have discovered, Creo ain't ProE.

From an admin's point of view, the number and level of things you need to understand grew considerably.

David Haigh