cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

Default Install Folder in Creo 2?

dgschaefer
21-Topaz II

Default Install Folder in Creo 2?

Creo 2, M010



I noticed that in Creo 2, M010 the default install folder is now simply
C:\Program Files, not C:\Program Files\PTC\. I re-checked F001 and it
defaulted to C:\Program Files\PTC. Now I end up with a Creo 2.0 folder
in Program files, not in PTC for new installs. Is this an official
change or a bug?



It's hard to make a startup script when the install folder changes from
build to build.



Doug Schaefer

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
4 REPLIES 4

Hi, that's interesting, I've found the same datecode installed to c:\Program Files\PTC\Creo 2.0\Creo 2.0!!


In the past, we've always installed Pro/E @ C:\ptc\proe-wf4 - but with Creo I'm thinking of going with default settings unless there's a way to force the install folder via environment variable or setup argument.


Edwin

In Reply to Doug Schaefer:


Creo 2, M010



I noticed that in Creo 2, M010 the default install folder is now simply
C:\Program Files, not C:\Program Files\PTC\. I re-checked F001 and it
defaulted to C:\Program Files\PTC. Now I end up with a Creo 2.0 folder
in Program files, not in PTC for new installs. Is this an official
change or a bug?



It's hard to make a startup script when the install folder changes from
build to build.



Doug Schaefer
Senior Project Engineer, Mechanical
- <



Design Central
Columbus, Ohio

www.design-central.com http://www.design-central.com

614.890.0202



Confidentiality Notice
This is a transmission from Design Central Inc, Columbus, Ohio which may
be privileged and confidential, and thus is protected from disclosure.
This message is NOT intended for transmission to, or receipt by, anyone
other than the named addressee (or a person authorized to receive and
deliver it to the named addressee). If the reader of this message is not
the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this e-mail
message in error, kindly accept our apology and please delete it from
your system without copying or forwarding it, and notify the sender of
the error by reply e-mail or by calling 614.890.0202 (collect).



I am also running Creo 2.0 M010 and it defaulted to C:\Program Files\PTC


Not sure why your install did not.


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

Odd, I've installed M010 on two PCs (both Win7 64) and both went simply
to C:\Program Files. F000 and F001 went to C:\Program Files\PTC.



Doug Schaefer
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn

Doug,
My install also still include to PTC folder in the path.
If you launch you startup script from the .psf you can make use of the PRO_DIRECTORY environment variable that points to the ../CommonFiles/<datecode> folder and make your script work with any installation path.
Using this approach I have reused my startup script from Creo 1.0 F000 through all updates to Creo 2.0 M010 without any changes.

/Bjarne
Announcements


Top Tags