config option to uncheck the autosave box in Customize dialog?

[lylebeidler]

My users keep overwriting the global config.win in the Customize dialog box,
because the

"Automatically save to" box is checked, and defaults to the network drive.



I would like to use a global config.pro option to either:

a) uncheck that blasted box

or

b) have it default to a local drive



I've looked through the list of config.pro options on Olaf Corten's site,
but I'm not finding anything. Did I miss anything, or is there a way to
thwart my users best attempts at messing up everyone else' window config?

Thanks.



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
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.

[lylebeidler]

I forgot to mention: setting the server config.win to read only just means
when my users do what they're not supposed to do, it writes config.win.2 or
.3 or.



Maybe I'll try putting it in it's own folder & making the whole folder read
only (thanks to Chris Rees for that suggestion)



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>

[dgschaefer]

Make 2 copies of your config.win on the server. One with a *.32767
extension and one with *.-32768 (the dash is important). This is the
largest number that a Pro|E file will increment to, but Pro|E creates
the special -32768 version as the 'last one'. I've found that you need
both. I don't think that Pro|E will recognize files with a larger
number either.

A user can still modify and save the config.win, but it overwrites one
(I can't recall which one at the moment) of those files rather than
creating a new one with a higher number. Then, when copying the files
from the server to the <loadpoint>/text directory at startup, the
company files will be copied over the user modified files, restoring the
company version. You just need to make sure that when you make changes
to the company file that you look to see which is newer and duplicate
that one so that they are both the same.

Then, when the user complains that their modifications aren't being
saved you can show them where they should be saving their personal
config.win files instead of overwriting the company file.

Doug Schaefer