![]() ![]() Since he's a new user, he doesn't have any configuration files here. So the next logical place for personal options is %HOMEDRIVE%%HOMEPATH%\config.pro. In our installation, load point and start-in locations are controlled by the sysadmin. Creating a new configuration file is fuzzy. Where Creo reads configuration files has been asked an answered. I'm trying to coach a new user in CP4 configuration settings and the CP4 configuration editor has me befuddled. I'd open that file and ADD in your customizations (rather than replacing the entire file). Creo1.0/Common Files/Text directory, you'll see the main config.pro file. ![]() As I said, this could be in one of several places depending upon whether you're running a 32 bit or 64 bit operating system and whether or not you've loaded Creo in a non-default location.ĭown inside that. but you should see a folder called " Creo 1.0/Common Files/Text". With Creo, the file structure is different than previous versions of Wildfire(Pro/E). This is usually inside your Program Files or Program Files (x86) or elsewhere on your C: drive. The only other alternative I can suggest is putting your config.pro options in the Creo loadpoint location. Let me know if that's the same directory you're using as your home directory or not. See if you can locate the value of the variable called USERPROFILE. Try opening a command/DOS window in Windows 7. What you call your Home directory is not the same directory Creo is using as your Home directory.Although, hey, it's PTC so who knows what may have happened! which would be a change from 25 years of Pro/ENGINEER and Creo functionality. Creo no longer reads the config.pro from the "Home" directory.# this, if it's already enabled in /etc/bash.Thre are only two possibilities as I see it: # enable programmable completion features (you don't need to enable # See /usr/share/doc/bash-doc/examples in the bash-doc package. # ~/.bash_aliases, instead of adding them here directly. # You may want to put all your additions into a separate file like # Add an "alert" alias for long running commands. Test -r ~/.dircolors
0 Comments
Leave a Reply. |