Hi,
I just switched from V8i to Connect and would have a few questions, also among to a comment in the following text (hope I can link this here?):https://envisioncad.com/microstation-connect-ucf-and-pcf-files/- In the Connect Edition, the UPF and the UCF are now bound to the Microstation user and are called personal.upf and personal.ucf by default.I read in the linked text above, that there is still a configuration variable for the UPF file, but it wouldn't work and you shouldn't use it either ..... !?
Is that correct?
I would like, as in the past, to rename all of my personalized configuration files with my initials.E.g .: XY_UserPref.UPF and XY_UserConf.UCFI also found the variable for the UPF and was able to test it successfully. It seems to work for the UPF.
- What about user-related UCF?How would I have to proceed to rename it? Is that even possible?
In msconfig.cfg (which we shouldn't touch) I found:# ------------------------------------------------- ---------------------# The names of the user preference (.upf) and user configuration (.ucf) files,# which are stored in the $ (_ USTN_HOMEPREFS) directory, are determined by _USTN_USERNAME.# ------------------------------------------------- --------------------_USTN_USERNAME: Personal_USTN_PREFNAMEBASE: $ (_ USTN_HOMEPREFS) $ (_ USTN_USERNAME)# ------------------------------------------------- --------------------
That means that the UPF and UCF always get this fixed name "Personal" via this variable ....But I still haven´t understood, how Microstation controll which UCF file has to be loaded, in order to refer to a renamed file.Please, can someone explain this?
I would be happy if you could explain what the statement in the text linked above is based on and whether my plan for renaming this files is possible.
Thanks a lotRegardsRaphael
I see I need to update that post.
You can rename, and change the location of the .UPF file through configuration variables, as well as the locations of the Personal.dgnlib, and other preference related files.
The .UCF file cannot be renamed, nor relocated.
Rod WingSenior Systems Analyst