Skip to main content
D
dgschaefer21-Topaz II
21-Topaz II
November 1, 2011
Question

Creo 1.0 Default Install Path

  • November 1, 2011
  • 18 replies
  • 4836 views
Anyone have trouble with the default path that Creo uses for
installation that includes the build code?







It seems that would cause potential headaches when doing build updates.
Do updates get installed alongside the old builds? Will I have icons
still pointing to the old install?



I realize that M010 is only been out for a few weeks, but I figure
someone must have been down this road by now.



Doug Schaefer

18 replies

C
ChrisCollinson12-Amethyst
12-Amethyst
November 1, 2011
We always change the install path and have done with the install to creo
1.0 parametric


Best Regards

Chris Collinson
CAD Administrator
D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 1, 2011
We always use the default path just to keep things simple.



I'm curious if setting your own path eliminates the build code folder.
The build number is a sub folder of the 'Creo 1.0' folder, actually 2
levels down within the 'Common Files' folder. I would assume that even
if you choose your own folder, the 'Common Files' folder would still
contain a folder with the build number. Is that true?



Doug Schaefer
D
dgallup1-Visitor
1-Visitor
November 2, 2011

I never use the default path but I always install each update in parallel with the build code in the path. That way I can run as many different builds as I care to install. Currently we have 5 builds of WF 2, 3 & 4. I like to stay away from the bleeding edge.


PTC quality philosophy: We've upped our quality standards. Up yours.

B
BryanBruder1-Visitor
1-Visitor
November 2, 2011

I just installed Creo 1.0 F00 and then installed Creo1.0 F010. The install asked me if I wanted to delete the old C:\Program Files\PTC\Creo 1.0\Common Files\F000folder or not. I chose to delete the C:\Program Files\PTC\Creo 1.0\Common Files\F000 folder and the install created a new folder C:\Program Files\PTC\Creo 1.0\Common Files\M010.



Bryan

D
DamianCastillo1-Visitor
1-Visitor
November 2, 2011

I am with David on this. I always choose a simpler install path and add the _build to the install folder. This allows me to go back to an old build quickly if the new build had a bug that was going to hurt us.


I also install only once on the network so I can install new builds while everyone is still running the current build. Next time they close and relaunch Creo, they are running the latest build and have no clue. I like it this way.

In Reply to David Gallup:



I never use the default path but I always install each update in parallel with the build code in the path. That way I can run as many different builds as I care to install. Currently we have 5 builds of WF 2, 3 & 4. I like to stay away from the bleeding edge.


PTC quality philosophy: We've upped our quality standards. Up yours.







"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 2, 2011
That's good info, at least it prompts you to delete the old install.



The problem for us, and I think many folks, is that we use a script to
copy config files into the text folder install directory. With every
upgrade, we'll need to change our script. If some users get the new
version and some do not, the script won't work properly.



However, looking at the config file that ships with Creo 1.0, it uses
the variable '$PRO_DIRECTORY' to point to the install folder like this:



drawing_setup_file $PRO_DIRECTORY\text\prodetail.dtl



I'd like to make use of that in my script, but I can't figure out where
it is defined. Unfortunately, it looks like it's defined during Pro/E
launch which would be too late. Entering 'set PRO_DIRECTORY' at a
command prompt gets 'Environment variable PRO_DIRECTORY not defined'.



Anyone know when this gets set?



Doug Schaefer
M
mkelley1-Visitor
1-Visitor
November 3, 2011

Open a system window from withing Pro/E; type set, and presto you will have a listing of all variables currently set...! Based upon my experience, the PRO_DIRECTORY variable is not available; however there is usually something similar that will get you there. Simply refer to the desired varible via $<name> in your ProE config files, or %<name>% in your scripts. Good Luck!

D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 3, 2011
I checked that. There is no system variable that points to any PTC
product directory.



Doug Schaefer
D
DonSenchuk12-Amethyst
12-Amethyst
November 4, 2011

I got the impression that $PRO_DIRECTORY is simply a placeholder for you to fill in with the directory path specific to your facility.

M
mkelley1-Visitor
1-Visitor
November 7, 2011

That doesn't sound right to me - I've always seen a number of variables that are set by PTC; in my particular case now "PRO_DIRECTORY" is avialable.


Make sure that you try the "set" command from a *Pro/E* command prompt. To do this, you must choose: "Window / Open System Window" from within a live Pro/E session...


All of the variables displayed in this manner may be invoked from within a Pro/E session; via $<name> in the config files, or by %<name>% in a batch script triggered by Pro/E.

Show more replies
Terms & ConditionsCookie settingsAccessibility statement