Skip to main content
B
BertilRogmark12-Amethyst
12-Amethyst
March 31, 2020
Solved

Wildfire 3 set up does not accept the desired Start-up directory.

  • March 31, 2020
  • 2 replies
  • 3816 views

I am trying to move my WF3 installation to a new computer running Windows 10 Pro 64-bit.

I have got it up and running but the setup ignores my specified start-up directory and insists on launching Proe under C:\Users\<user name>\documents\.

I have found a way to run the ptcsetup.bat file in the bin directory by forcing the file to set the machine type to

i486_nt but I have not found out how to force the start-up directory to what I want.

Can anybody advice me a way to solve this?

I have a similar problem lurking - installing Intralink 3.4.

The same issue here, up and running but will not accept my chosen start-up directory and launching again in the C:\Users ... etc as above.

HELP!

Best answer by KenFarley

I always create a shortcut on my desktop, then edit the properties to explicitly specify the "Start in:" field. (for me it's C:\ptc). Works like a charm.

I then pin the shortcut to the taskbar so it's always available every morning.

2 replies

K
KenFarley21-Topaz IIAnswer
21-Topaz II
March 31, 2020

I always create a shortcut on my desktop, then edit the properties to explicitly specify the "Start in:" field. (for me it's C:\ptc). Works like a charm.

I then pin the shortcut to the taskbar so it's always available every morning.

B
BertilRogmark12-AmethystAuthor
12-Amethyst
April 1, 2020

I tried creating a shortcut for <installation_directory>\bin\proe.exe with the desired startup directory set.

Unfortunately, I still end up in the same place, i.e. C:\Users\<user name>\documents\.

I get the same result with a shortcut for proe1.bat

The trail.txt files created by ProE however, are correctly written to the desired startup directory.

It appears that the intended startup directory name reaches some settings but not all. I believe that when

proe.exe launches ad finds no address it resorts to C:\Users\etc. as a default.

I don't know how to proceed, maybe I have to manually set "working directory" each time I have started ProE.

Ideas anybody?

 

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
April 1, 2020

Create the shortcut to parametric.bat, not proe.exe!!!!

 

M
MartinHanak24-Ruby III
24-Ruby III
April 2, 2020

Hi,

in Creo Parametric following option must be set in config.pro file

file_open_default_folder working_directory

Note: I do not know whether this option exists in ProE WF3.

B
BertilRogmark12-AmethystAuthor
12-Amethyst
April 2, 2020

The config.pro option exists in WF3, I have tried but it did not solve my problem.

On second thought, config.pro normally is loaded in your startup directory and therefore I believe that a setting in config.pro cannot influence what the startup directory should be - can it?

 

I am going to look in the registry to see if there is anything that points to the directory in which ProE opens.

 

Any other idea anybody???

G
GabrielZaha14-Alexandrite
14-Alexandrite
April 6, 2020

Wf3 is reading the configuration option from multiple locations.

Put the "file_open_default_folder working_directory" line in the <loadpoint>\text\config.pro

This config file is always read at start-up regardless of the starting directory.

I'd recommend to do this from a text editor and not from Widlfire interface.

Terms & ConditionsCookie settingsAccessibility statement