Config.win Files

[feisthammela]

We currently have 6 seats of Pro/E and everyone would like to have their own config.win settings. The problem we are having is that everyone uses the same startup directory and different loadpoint directories. Since the startup directory config.win overrides any loadpoint directory config.win we don't have a good way for everyone's config.win to be custom. Is there any way to force Pro/E to look at the startup directory config.win first and then the loadpoint directory config.win?

 

[dr_gallup]

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. <li ="kadov-p-CTopic-Text-Numbered">
   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.
   <li ="kadov-p-CTopic-Text-Numbered">
   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.
   <li ="kadov-p-CTopic-Text-Numbered">
   Startup directory - This is your current or working directory when you start
   Pro/ENGINEER.

So have every user create their own config.win in their login directory and don't put any config.win in the startup directory.

 

[dgs]

dr_Gallup has the order right, but the config.sup & config.pro aren't related to the config.win. I don't think you can change that order.


However, it seems that by assigning each user's login directory and keeping personal config.win files there AND making sure there are no config.win files in the startup directory you can accomplish what you want.


The other question is, why is everyone using the same startup directory? There may be an alternative way to accomplish that goal that will allow users to have their own startup folder. For example, if the point is that everyone is on the same project and that way they don't have to set their working directory, then record a trail file that sets the working directory and set Pro|E to run it at start up. You just need to set the trail file as a parameter in the start up icon:


<proe_launch_command> <path_to_trail_file>

 

[feisthammela]

That all sounds like it would work, but my goal is to be able to have one location where the default config.win is stored and separate locations, depending on the user, where the custom config.win is stored. This way it makes mass updating of this file more straight forward. If the user chooses not to use the new feature, theyshould be able toget rid of it and then savethe config.winto their own location.


We use the same startup directory because we all use the same config.pro file. Which, likewith the config.win, makes it easier to mass update the file.

 

[dgs]

What we do here is store the file on the server in a remote location and then run a simple batch file at Pro|E start up to copy the files into the Pro|E startup folder. That way the company files are loaded first and the user files are loaded second. The batch file can be very simple (in our case it has evolved into something complex). Al you need is all your config files (and only config files) in a network folder and a single line batch file:
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">


xcopy /q /y ,path_to_server_folder>\*.* "<path_to_proe_load_point>\text\"</BLOCKQUOTE>
That will copy everything in the server folder to the loadpoint and will not ask for overwriting if the files exist.
An alternative would be to reverse my earlier instructions. Set everyone's login directory to a common folder and put the company filers there and then set each person's startup folder to their own config folders. Then the company files get loaded first and the user files second.

 

[feisthammela]

Either of those options sound like they might work...I'll have to givethem a try. Thanks!