As part of our custom Pro/E launch batch file, it creates a config.pro in the user's profile folder with certain settings.
(C:\Documents and Settings\<user id=">\config.pro)
This is one of the places that Pro/E (Wildfire 3) looks for config.pro when launched.
However, for one user, this config.pro file is being ignored as if it did not exist.
This is confirmed through: Help > Technical Support Info, which lists all config.pro files that are read.
This only known difference between this one user and others is that he uses a laptop.
He is on Windows XP SP3 like all other 32-bit users here.
Has anyone ever seen this behavior?
2280 E. West Maple Road
Walled Lake, MI 48390-3828
Some things to check:
Are You using Active Directory ? - so maybe the actual home directory is a server folder.
Check the environment variables in ProE's system window. Where does ProE see the home directory?
What about user privileges?
Gerry....perhaps you've already found the solution but if not perhaps this might be helpful? Run the 'set home' from a command window and check to make sure that HOMEDRIVE and HOMEPATH points to the location where the HOMESHARE from theAD account is mapped.
Thanks to all that replied, and special thanks to Jim for the clue we needed.
When executing "set home" we noticed that the user had HOMESHARE defined, which should not have been there.
And on top of that, it was pointing to a nonexistent share on a server.
We looked up the user's account (active directory) and found that this nonexistent path was set as his remote home folder.
We have no idea as to why it was set up this way.
Because the share did not exist, Windows XP was smart enough to default back to the normal home folder on the local drive, but Pro/E did not.
After we disabled the remote home folder option, all was well.
If You want global settings for all users, put it in the <proe-install>/text folder.
User-specific settings are best in the working directory. That file should only contain changes wrto the global settings.
If You have different user settings, copy the file to the working directory before starting ProE. (Remember, ProE will add an index when local changes are made.)