config.pro

[CharlieGraham]

To All,

We have a config.pro, config.win & config.sup that are all copied via a script file embedded in the start up command. If a local config.pro & config.win is preferred by any user, does it just have to be loaded into the start up dir? Or is there more to it to override the the script?

Any help would be greatly appreicated,

Charlie Graham

Stryker Spine Allendale, NJ

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.

[rrich]

From the Pro/e help pages

How Pro/ENGINEER Reads Configuration Files at Startup

Pro/ENGINEER reads configuration files automatically from several areas. If
a particular option is present in more than one configuration file,
Pro/ENGINEER applies the most recently loaded/read setting.

At startup, Pro/ENGINEER first reads in a protected system configuration
file called config.sup. It then searches for and reads in configuration
files (config.pro, config.win, menu_def.pro) from the following directories
in the following order:

1. loadpoint/text (loadpoint is the Pro/ENGINEER 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 Pro/ENGINEER from this loadpoint
uses the values in this file.

2. Login directory - This is the home directory for your login ID.
Placing your configuration files here lets you start Pro/ENGINEER from any
directory without having a copy of the files in each directory.

3. Startup directory - This is your current or working directory when you
start Pro/ENGINEER.

[davehaigh]

You should have your script copy the files to the ProE loadpoint text directory. Then the user can have their own config.pro in the startup directory.

xcopy "P:\configs\loadpoint\configs\*" "C:\ptc\proeWildfire 4.0\text" /y /r
attrib +R "C:\ptc\proeWildfire 4.0\text\config.pro"
attrib +R "C:\ptc\proeWildfire 4.0\text\config.sup"
attrib +R "C:\ptc\proeWildfire 4.0\text\config.win"
del "%USERPROFILE%\pro\wf4_home\*trail.*"
"C:\ptc\proeWildfire 4.0\bin\proe.exe"


1. Copy all the files from some location to the ProE loadpoint. Force it to overwrite existing files

2. Set the config files you just copied to the loadpoint to read only

3. Delete old trail files

4. Startup ProE

Create a shortcut of this script, and change the start in directory to a directory specific to that client. In the example above that would be %USERPROFILE%\pro\wf4_home

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550