Where else could I place my config.pro?

[fiebigc]

Is there anywhere else I could place my config.pro and config.win files other than the working directory? I'm just being anal but I would like to have a directory were all of my configuration files are neatly stored. The working directory gets so full of junk that I hate having such an important file there. Any suggest on how to make ProE look for the config.pro and config.win in another file while still using the working directory. Thanks.

 

[jeff4136]

Help
. Pro/ENGINEER Fundamentals
.. Pro/ENGINEER Menus
... The Tools Menu
.... Using Configuration Files
..... About Configuration Files


gives you what you want.


Three locations are read ...
<loadpoint>\text\
Login directory (e.g. the active directory on boot)
Startup directory (working directory)

 

[fiebigc]

Thanks I'll give it a try.

 

[looslib]

You can also create a mapkey that reads your config.pro file either after startup or as part of the startup.

 

[jelston]

You can also create a mapkey that reads your config.pro file either after startup or as part of the startup.

Yeah, what he said. I, too, am very anal about this type of stuff. I have any file somewhat related to pro/e all under two folders (used to be one but i changed for security reasons). This is convienent since i VPN from home, i just copy my files to a briefcase on my IPOD and update the files between home and work.

 

[tommypurple2]

I use windows.... Not sure if that is a good thing or not, but you can hide files with it. That is what I do....

 

[csusie]

in your proe.bat file create some command lines that copy your configs from a safe location to your loadpoint or working directory everytime your launch and then launch the bat file instead of proe.exe. You will always have the latest and greatest config file. Works well if you have multiple users.

 

[dgs]

<loadpoint>\text\
Login directory (e.g. the active directory on boot)
Startup directory (working directory)

Just to clarify/expand on this.
<UL>
<LI>The login directory is your 'home' directory as defined by Windows environment variable.
<LI>The 'Start up directory' can also be defined by setting the 'start in' field in the properties for the icon used to launch Pro|E. This doesn't work if you're calling a batch file instead of the Pro|E executable. Then what ever the last directory the batch file browses to (via the 'cd' command) will be your start up directory.</LI>[/list]


The batch file idea is a good one, but rather than editing the Pro|E batch file,I create my own and call the Pro|E file from it. That way my changes aren't wiped out when we upgrade Pro|E. I use the batch file to copy the company configs to the <loadpoint>\text folder. Ithen place the user configs in individual server folders named with their usernames. Then I set the icon's 'start in' fieldto Z:\config\%username%\ or whatever.
Edited by: dgs

 

[jdurston]

You can also put your config.pro and config.win in any directory you define by "%HOMEDRIVE%:\%HOMEPATH%"


For our local installations "%HOMEDRIVE%" is our "H:" drive (home drive) and "%HOMEPATH%" is nil "". So, we can put our config.pro / config.win in our H: drive top level folder.


If you have the permissions on your machine, you might be able to define where this is.


The advantage (although we don't use it this way) of putting your config's on a network drive would be that you access them if you login on another computer.


Keep in mind there is an order in which Pro will read the configs. First, loadpoint text, then homepath/homedrive, then local working directory in that order. Unless you have config.sup options, the config options read LATER will override the ones defined earlier (if they are different.)

 

[kevinjbrault]

Just a quick comment .... If you change your %homedrive% or %homepath% you can mess up other windows functionality.


Instead ProE will look for an environment variable called %home% and read config files in it.You can create this on the local computer or in a batch file that calls ProE (set home=h:\proe_configs for example).


If ProE finds the "home" variable it will not look in "homedrive/homepath".


Kevin

 

[fiebigc]

Thanks kevinjbrault, that was the clean and simple answer I was hoping for.


I created a new windows environment variable call "home" and set it's value to "C:\ProE_Configuration_Files\". I placed my config.pro, config.win, config_tree.cfg, appearance.dmt, and ecad_hint.map in that same directory. After I restarted my computer ProE loaded just like it should.

Thanks.