Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily.
X
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.
>The best way I know how is to have them in two different locations: Have the forst in the load point, the second in your start directory. > >-----End Original Message-----
1. Start Pro/e with no config.win file. 2. Load config.win #1 from one directory 3. Load config.win #2 from another directory 4. Save the results to config.win #3 in a third directory
Be aware, merging config.win files can produce unpredictable results. They are supposed to be cumulative, and are, but not always in the way you'd expect them to be.
Or rename both to one.win and two.win. Then both can be in the working dir and they can still be loaded one after the other.
One caution:
If config.win files are amended by overloading one file after another, they are subject to corruption, . Especially if any were born in an earlier rev of WF. This can make things unstable.
If you are moving to a new version of WF, it's best to create a new one from scratch.
--Glenn
On Tue, Aug 17, 2010 at 5:39 AM, Doug Schaefer < > wrote:
> > 1. Start Pro/e with no config.win file. > 2. Load config.win #1 from one directory > 3. Load config.win #2 from another directory > 4. Save the results to config.win #3 in a third directory > > Be aware, merging config.win files can produce unpredictable results. They > are supposed to be cumulative, and are, but not always in the way you'd > expect them to be. > > *Doug Schaefer* > > >
