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
  • 4841 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

Show previous replies
D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 7, 2011
That makes sense, but is of no help for copying company config files
from the server into the install/text folder before Pro/E is launched
and therefore before the PRO_DIRECTORY variable is set. We do that now
to maintain consistency through our installations as a lot of companies
do, but with Creo 1.0 the path to the text folder changes with every
build update. So, if you aren't diligent about making sure every user is
on the same build, copying the config files to the client machines gets
harder.



Having that variable set beforehand would be nice, but would create its
own set of problems for us in that we have 2-3 versions (WF3, WF4, etc.)
installed at the same time. Frankly, I'm not certain what value there is
in having the build in the install path and would just as soon take it
out.



Doug Schaefer
D
davehaigh13-Aquamarine
13-Aquamarine
November 7, 2011
Those variables are in the parametric1.psf file. I can't imagine that the %CREO_COMMON_FILES% location would change between the different numbered .psf files in the bin directory. That's assuming you use multiple .psf files.

You might be able to grab it with findstr in a windows bat script.
Findstr "string to find" [file to look in]
You just need to figure out the correct argument to grab. Although it might be easier to use Perl to grab the value.

I agree, it's not the most admin friendly way to have configured Creo.

David Haigh
D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 7, 2011
Here's some batch code that I think will work. I need to test it more
and I'm not certain it's the most elegant way to do it, but it should be
able to capture the current build code of the local install
automatically.



First, I use the following to find the newest *.psf file (run it in the
parametric/bin folder):



for /f "delims=" %%A in ('dir /od /a-d /b *.psf') do set FILENAME=%%A



I think it's very unlikely that there would be an old *.psf file in
there pointing to an old build, but by checking for the newest file I
can be more sure that I'm getting the actual latest build installed.



Then, I parse that *.psf file for the SHIPCODE:



for /f "tokens=2 delims==" %%B in ('findstr "SHIPCODE" %FILENAME%') do
set BUILD=%%B



I can then use that BUILD variable in my paths for copying my config
files and be sure I'm copying into the right place based on the build
currently installed.



I'm not the best batch file programmer, I patched this together from
Google searches. If anyone has improvements on this, let me know.



Doug Schaefer
D
davehaigh13-Aquamarine
13-Aquamarine
November 8, 2011
The reason to have multiple .psf files in the parametric/bin folder is to allow the user to choose between licenses with different startup options. Since these are configured with ptcsetup by the admin, I think you would be safe to just pick the first one, parametric1.psf. The only way you would have an old out of date one is if you re-ran ptcsetup and created fewer license configurations. Even in that case parametric1.psf would still contain the latest information.

I have 11 .psf files.
Having multiple .psf files presents the user with this dialog when they start ProE.
[cid:image003.jpg@01CC9D60.CB37BA30]

This allows me to offer licenses for which I only have one or two copies to any user.

David Haigh
D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 8, 2011
We have two *.psf files and neither are named parametric1.psf. What I
want to avoid is the, admittedly very remote, chance that a build update
happens, new names are given to the *.psf files and the old ones do not
get removed. It would then be theoretically possible to have the last
*.psf file alphabetically (which is what the second line would fine if
you had it scan each one in turn) point to the wrong build.



Admittedly, if one copied a *.psf file into the folder manually it still
may have a newer date stamp, so even this isn't fool proof.



I'm open to suggestions as to making this more automated.



Doug Schaefer
D
dgschaefer21-Topaz IIAuthor
21-Topaz II
November 8, 2011
OK, at the risk of beating a dead horse, I think this batch code is a
more direct means of determining the build and poses less risk of
finding the wrong build. It should be run from the 'Common Files'
folder of your Pro/E install. It will find the folder name of the latest
build:



for /f "delims=" %%A in ('dir /a:d /b') do set BUILD=%%A



Even if multiple builds are present, this will find the latest because
conveniently, build numbers end up in alphabetic order (C000 -> F000 ->
M010 -> M020 -> etc.) The assumption there is that you want to run the
latest build present, which seems like a safe bet.



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

Gotcha - *now* I understand what you are trying to accomplish...


Another way to go about this would be to figure out what build(s) are loaded (by parsing the file named "instlog.txt", which located in the <loadpoint>\uninstall folder) I have a script that I wrote a few years ago that does this that I could share if you want...


Just thining out-loud here - you could step thru all top-level folders in your PTC installation folder; find all the <loadpoint>\uninstall\instlog.txt files & compile a list of builds. Then I guess that you would have to figure out which one is the latest build - yikes!


I think that it would be best to get rid of the "build-code-in-the-path" thing. What is the value-added here? :^)

D
DamianCastillo1-Visitor
1-Visitor
December 20, 2011

I quickly update all my scripts by using the Find and Replace function. This changes the path everywhere on my script and it takes only seconds to do.


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

Terms & ConditionsAccessibility statement