Thanks for the replies.
Still have not resolved the problems yet. I received advices to check/change the access
privilege setting on Pro/E start-in and /bin directory. I do have write access when
logged in as a normal user but still can't run Pro/E successfully other than logged in
as a administrator.
However, I do notice that under the start-in directory, a new trail.txt file
will be created every time I execute Pro/E even through the screen doesn't response.
This means Pro/E do run but can't continue till the Pro/E screen is shown.
Below are summaries of replies I received, which I believed will be useful for your reference:
I believe Pro/E writes a temp file in the install\bin directory.
Open up the file permissions there & it should work. [David R Gallup]
Pro/E does not write anything to the system areas or registry to affect it running due to privileges.
Check the "start in" part of the shortcut on the desktop. Set it to a directory the current user has read\write access to.
I also add the ProE bin directory to the path in the bat file that launches ProE.
This way no matter where you launch from, ProE can find what it needs. [Earl Beattie]
Check the start-in directory of your shortcut. Sounds like you don't have write access to it.
Pro/E is trying to create the trail file. [Robert Green]
I have encountered this issue in the past. Though, don't seem to recall the exact solution.
Try to clear out the start directory that you have defined during installation. remove the whole dir.
then create the dir when logged in as normal user (non-administrator).
My thought is as a normal user, proe is not able to write to the folder or
append some file created by admin user. [Devendra Verma]
Sounds like your start in folder has admin security associated with it.
Verify the start up folder can be written to by non admin users. [Jeff Smith]
