Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

config.pro gets saved automatically to login dir.

Status
Not open for further replies.

gesigner

Mechanical
Apr 29, 2002
28
0
0
US
I’m having a problem with Pro/E 2001 (2004290) and config.pro files. I’m running both Wildfire 3.0 and 2001 so I want to have separate config files for both. However Pro/E 2001 keeps saving a config.pro file back to the login (home) directory where it gets read by both Wildfire and 2001. Is there a way to stop Pro/E from creating this config.pro in the login directory? Thanks.

 
Replies continue below

Recommended for you

I'm only running Pro/E 2001 but here is some information from the help files.

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 current 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 and config.win) 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.

Notes: The local config.pro and config.win files (in your startup directory) are the last to be read; therefore, they override any conflicting configuration file option entries. The config.pro file does not, however, override any config.sup entries. You can create and store custom configuration files in your current working directory. These custom configuration files usually apply to specific projects.


Heckler
Sr. Mechanical Engineer
SWx 2007 SP 3.0 & Pro/E 2001
XP Pro SP2.0 P4 3.6 GHz, 1GB RAM
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

(In reference to David Beckham) "He can't kick with his left foot, he can't tackle, he can't head the ball and he doesn't score many goals. Apart from that, he's all right." -- George Best
 
Thanks. Wow, I thought we were the only ones left running 2001. Nice to know there are others. Some of the people around us that we work with haven't moved to Wildfire yet, so I work 90% on 2001 & 10% on Wildfire. I get more Wildfire files all the time, though. Thanks again.
 
Yeah, PTC really dropped the ball when they gutted Pro/E and made it Wildfire. For the longest time the PTC marketeers tried to separate the new Wildfire from what was known as Pro/E. But now they're calling it Pro/E again. We are still paying for upgrades but I just don't want to deal with the data conversion. I know some day I will be forced to do it but until then....2001 is the real Pro/E

Heckler
Sr. Mechanical Engineer
SWx 2007 SP 3.0 & Pro/E 2001
XP Pro SP2.0 P4 3.6 GHz, 1GB RAM
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

(In reference to David Beckham) "He can't kick with his left foot, he can't tackle, he can't head the ball and he doesn't score many goals. Apart from that, he's all right." -- George Best
 
Status
Not open for further replies.
Back
Top