creo1 architecture

I found the answer to my own question.
The order is simply determined by sorting the .psf files in the bin-folder in ascending order. So I now start the names with 01, 02, etc. to get the order I want.

Bjarne
In Reply to Bjarne Frandsen:

Hi Dmitry

I have also started looking at Creo and its installation and agree on your
findings. It adds some info to the registry, but it do not seem to have
any influence on the application it self, so it can still be copied
around.

After I have installed and uninstalled Creo several times I have yet to
see one install, where the startup configuration dialog have the same
order of the various configured licenses.
In it latest incarnation I got two Creo (default) entries.


Do anybody know how to reorder these items. It do not seem to follow the
order set from within setup.exe.

Thank,
Bjarne



Dmitry Ushamirsky <->
19-10-2011 17:42
Please respond to
Dmitry Ushamirsky <->


To
<->
cc

Subject
[proesys] - creo1 architecture







Hi pros!
Two points
1. If you started to play with creo1/pro installation, you have noticed
that it installs into two main directories: Common Files and pro, plus PTC
Quality Agent. I guess the logic here is to separate files that are used
between modules of creo and files that are specific to these modules,
Ansys does it like that and it makes sence. In PTC's implementation
though, it does not! It does not look like they thought it through all the
way - most of the "pro" or "parametric" is installed under the Common
Files/M010. It includes executables and proe, sorry creo/pro, config
files, install and batch scripts, but psf files and help is under pro
directory. Now if you have Mechnica, sorry Simulate, module than you will
see another folder "Simulate" at the proe_loadpoint directory. In that
directory there are, again, psf, install and html files, but executables
are already in Common Files. BTW, all the module's executables are
installed in the Common Files directory no matter of the selections you
have made during installation - your selections are responcible only for
psf and some batch scripts configuration.
2. Good part is I still can copy the installation to the other machine and
it would run. I just copied Common Files and pro directories to another
machine and it works fine. If you do not want PTC Quality Agent to be
installed, just don't copy it along.

D

Site Links: View post online View mailing list online Send new post
via email Unsubscribe from this mailing list Manage your subscription
Use of this email content is governed by the terms of service at:
http://portal.ptcuser.org/index.php?module=sthtml&op=load&sid=s1_010_tos

I run Pro/E through a Network installation and determine which license is used by way of a script and the current user who executed it. This allows me to set specific licenses or extensions to the correct users and have it launch automatically based on their user name.

Many years ago, I copied the installation from computer to computer but that's too time consuming for me. One install is easy to upgrade and have everyone running the same version.

I did notice the different folder setup created by Creo 1.0 and I too find it odd.

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