How to change the default creo config file location to our local drive custom config created by us.
There are two locations from where your config files get picked up during launching Creo.
1. <Creo Load Point>\CommonFiles\text
2. (Default Working Directory) (You can get this when you launch the Creo session and just check what is your default directory).
If you copy your custom config file into any of these two locations, you should be able to get them in effect.
There are actually 3 locations that config files are read from, in this order. See CS28227.
If you are using a config.sup, it must go in location #1. If multiple config.pro files are loaded, they are cumulative. Where multiple config.pro files contain the same option, the value in the last file read wins.
Regarding the 3rd option I have tried by giving a network location, but still Creo is reading the config file from The text folder in the loadpoint only.
1. Changed the start-in path "\\\\server\share\creo\common" but Creo is still reading the config.pro file from "C:\Program Files\PTC\Creo 2.0\Common Files\M200\text"
Thanks in advance.
ok. Then the question is why Creo is not able to read the config.pro file from network location "\\\\server\share\creo\common" ?
Map the server location to a drive letter and try that for your location.
x: drive mapped to \\server\share\creo
start-in folder uses x:\common
Thanks Ben. I tried it and it is working correctly.
but without mapping the server location, is it not possible to achieve the same thing using the full network path "\\\\server\share\creo\common" ?
I thought PTC has said not to use UNC pathing on Windows, but I could be wrong. I have always used mapped drives for simplicity.
Found these in other articles on PTC support web pages:
When sharing a directory, for example a server directory, mapped drives give better performances than UNC path for the server and shared resource in the following format: \\server name\share name.
A standard file location can be the local disk r a mapped drive on a remote computer. The Universal Naming Convention (UNC) path for network rives is also considered as a standard path if the value for DisableUNCCheck is set to True for he key HKEY_CURRENT_USER\ Software\Microsoft\Command Processor, in the registry file.