Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X
I've been researching these forums for hours to help a friend.
Last week, his Creo application lost the ability to see any of his mapped network drives.
We've been able to manually go into the network and save certain folders to his "Favorites"
However, we are unable to set a working directory.
Every single time we open the program, it starts in C:\Windows
It should be starting in S:\Engineering
I've tried adding this line to the config.pro file:
file_open_default_folder working_directory
I've tried changing the shortcut path in Windows.
Nothing works. Help.
-Rob
Solved! Go to Solution.
I apologize for my "snippity" comment. I was frustrated after working on (what turned out to be) a simple problem for 3+ hours.
The creo.exe file in the program directory had "always run as administrator" checked off. Therefore it was not using the users mapped drives.
Quick and easy fix I found on another site.
Robert,
Try setting Start in location to S:\Engineering in Creo shortcut.
> Select Creo shortcut > Right Click > Properties > Change Start in to S:\....
What part of "I've already tried changing the shortcut" did you miss?
Because the moderators took forever to post my question in the first place...
And because people can't read and keep suggesting things we've already tried...
I've already solved the problem by finding the solution on another forum.
Thanks.
As you have already got it working, you may add some information and mark that as correct answer. Your information may help others.
If you could not see your network drives, that would be your issue, not the fact that you cannot set the working directory.
You cannot pull the working directory from Favorites.
We all 'volunteer' our time to answer questions on here, don't get so snippity when someone missed reading something and replies with an answer that you may have already tried, We are only humans.
We have found that laptops don't always connect to mapped drives and to ensure the proper firing of an application that is drive dependent, we wrote a visual basic program to "shake awake" the mapped drive before continuing with starting the of the actual desired program.
I apologize for my "snippity" comment. I was frustrated after working on (what turned out to be) a simple problem for 3+ hours.
The creo.exe file in the program directory had "always run as administrator" checked off. Therefore it was not using the users mapped drives.
Quick and easy fix I found on another site.