help : how to load 2 different config.pro?

[Ghery]

Hi, by default my pro-e wf4 settings are these:

1) upload the config.pro "general" from the folder c:\programs\proewildfire4\text
2) upload the config.pro "personal" from the folder d:\work_area (the latter is set in the field "by" of the link on the dekstop of pro-e

what I would like to do is to move the config.pro "general" into a shared network folder on the server, so if/when I modify it will automatically be loaded by my colleagues, instead of being forced to pass it via email and then remind everyone to replace the file manually.

Is it possible to do what?

Thank you.

 

[dema]

config.pro can be anywhere we keep it on the server.

you just have to go to the icon that launches pro and properties where to "change the path with what you put the file

 

[Ghery]

Yes, but I have already set the path "from" putting, as mentioned above, the path of the personal macro (d:\work_area), and that's fine.

what I would like to do is to move the path of the general config from "c:\programs\proewildfire4\text" to "z:\proe_config"

 

[dema]

we have the config.pro on the server and in the icon is specified that path
on the machine in the folder ...test there is a config.sul

Try and let me know.. .

 

[StudioSoluzioni]

Hello, do you play cad manager?
I suggest what I did to regularize the use of config.pro at a customer.
1. I cleaned all computers from the various iso.pro files, pippo.pro, test.pro, nonfordimental.pro that users had created independently. clearly before erasing remember to make a backup.
2. I created on the server a single config.pro and a single dtl. I also established a single search_path.pro that loads the paths of libraries and commercials.
3. at the opening of proes a batch file ensures that everyone has the updated version of the config.pro overwriting that in the text folder of the program.
4. locally all users have a boot folder with the same name wf_start
5. each user has a vload.pro file where their macros and options are loaded. I have banned customization of all options that affect normalization.
6. in the config.pro is loaded only one macro that to the need charge vload.pro
7. in the wf_start boot folder I allowed customization of config.win.
8. Trails go to separate folder otherwise at first cleaning users delete their customizations with tranquility
9. when you need to update the config.pro update it on the server and everyone finds it on the first restart.

 

[maxopus]

hi study solutions, thank you for the precise and punctual intervention.
I remind you that for new users the cad3d regulation provides for a brief presentation to the community and the reading of the regulation.

 

[Ghery]

Hello, do you play cad manager?
I suggest what I did to regularize the use of config.pro at a customer.
......... .
3. at the opening of proes a batch file ensures that everyone has the updated version of the config.pro overwriting that in the text folder of the program.

hi study solutions, although not official in practice are the cad manager in the office so I thank you for the directions.
Would you tell me how you wrote this batch?

Thank you.


@dema : for how we configured your system does not work; in the pro-e connection on the desktop the "da" field must point to the individual user's work directory, otherwise it would not charge the personal macro file. Thank you.

 

[dema]

otherwise would not charge the personal file of the macros. Thank you.

personal things, we don't really like them, because. can happen to have to change pcs for any reason or have to explain a command and personal experience if configurations are different you just lose time looking for commands, then if a macro is useful to me can be for others too....

so we use the
config.sup on single pc with configurations in alphabetical order
config.pro on network disk with macros

if you need personal macros add them to .sup

 

[Ghery]

In fact, 99% of the macros are "company" but it does not take that if a colleague wants to make the macro to measure the distance between two axes (I'm inventing...) it can do. .

but better explain the .sup or .sul file function as you wrote above?
I've never used them, and I miss how it's loaded.

if the config.pro is on the network I imagine that its loading is set in the "from" field of the pro-e connection used to start the program; but how is the .on loaded?

Thank you.

 

[dema]

the sup automatically loads without telling him anything but must be in the text folder

 

[Ghery]

I add.... how to specify the "current work directory" within the config.pro ? the only 2 options are "search_path" and "search_path_file" but do not work. The company's config.pro starts at the start of the project:

a possible personal file I need to get it started from the path d:\work_area....I cannot use the text folder (in c:\)

 

[Ghery]

the sup automatically loads without telling him anything but must be in the text folder

I understand that: but I have another need:

the "work directory" must be "d:\work_area" because for 10 years at this part there is on each pc a local "d" partition for the cad...all macros tied to the workarea point to that path there.

from here my question upstairs

how to specify, in the config.pro, a "work directory" (other than text) ?

Thanks :finger:

 

[StudioSoluzioni]

... would you tell me how you wrote this batch?...

is a simple xcopy of dos. if there is a systemist in the company will surely know how to do, otherwise you will look on the internet

personal things, we don't really like them, because. can happen to have to change pcs for any reason or have to explain a command and personal experience if configurations are different you just lose time looking for commands, then if a macro is useful to me can be for others too....

in principle it is true. but in practice I have found problems:
1. key combinations made by a right-handed to launch macros force the left-handed to leave the mouse continuously. so I prefer that users decide on their own how to make macros and especially if farsele.
2. it is not right to impose on all macro icons, there are those who prefer to have the minimal layout and throw everything from keyboard, there are those who prefer icons and do not even know to have shortkeys available
3. Many macros only serve for individual work sessions.

I add.... how to specify the "current work directory" within the config.pro ? the only 2 options are "search_path" and "search_path_file" but do not work. The company's config.pro starts at the start of the project:

a possible personal file I need to get it started from the path d:\work_area....I cannot use the text folder (in c:\)

the "work directory" must be "d:\work_area" because for 10 years at this part there is on each pc a local "d" partition for the cad...all macros tied to the workarea point to that path there.
...
how to specify, in the config.pro, a "work directory" (other than text) ?

I have clear what you have to do, so I think you should read, or read, carefully the two embossed topics of ozzy in this forum and make a minimum of reasoning on how to apply them to your case. there are the answers you are looking for clearly described.

 

[Ghery]

study solutions, I read and read the 2 threads in relief but I can't see the solution to load 2 config.pro from paths to my liking :frown:

I realized that a config.pro can be uploaded via boot directory (field "from" in connection to pro-e) but the 2nd config do not find how to upload it to my liking. ..the only option would be that of the "text" folder but as I have already written it does not do to my case

If you can enlighten me, thank you:

 

[dema]

2. it is not right to impose on all macro icons, there are those who prefer to have the minimal layout and throw everything from keyboard, there are those who prefer icons and do not even know to have shortkeys available

All office stations must be the same, since when they call me because they can't do something, I don't have to go crazy looking where they put the commands.

 

[Parametric_Ozzy]

sometimes even looking in the proe guide would not do so bad, since it is found everything.
I will copy an extract that explains the priorities of loading the files mentioned.

note

config.sup is a protected system configuration file. the system administrator uses this file to set the configuration options to be used throughout the company. the values set in this file cannot be replaced by other config.pro (local) files.

at startup, create elements/pro reads first a protected system configuration file called config.sup. Next, search and read configuration files (config.pro, config.win, menu_def.pro) from the following directories in the order indicated.

1-loadpoint/text (loadpoint is the creo elements/pro installation directory) - the system administrator may have inserted configuration files in this location to support company standards related to window configuration settings, formats and libraries. users who start creating elements/pro from this loadpoint use the values present in this file.

2-access directory - home directory for access id. If you place the configuration files in this directory, you can start creating elements/pro from any directory without the need to have a copy in each directory.

3-start directory - current or working directory when starting creo elements/pro.

Note:

the local configuration files (config.pro, config.win and menu_def.pro) in the boot directory are the last files to read; therefore, replace all entries of configuration file options in conflict the config.pro file, however, does not replace any config.sup voice.

you can create and store custom configuration files in your current work directory. These custom configuration files typically apply to specific projects.

then there are ten other systems to configure, including the xcopy as it used to study solution, or use to set the environment variables in windows.
I am also of the opinion that it is good to set up some icons, but all the rest must be taken from a single file that manages the key user, otherwise every time it is a slaughter to configure and to one goes one thing to another no..
greetings