Skip to main content
D
davehaigh13-Aquamarine
13-Aquamarine
April 19, 2012
Question

Creo 2.0-F001 & Another interesting thing

  • April 19, 2012
  • 11 replies
  • 6894 views
Creo Parametric 2.0-F001 is now available for download.

I was downloading Creo Direct 2.0, and when I went to install it even though I unchecked Parametric and Simulate, it proceeded to install them anyway. When I looked I noticed I had a new F001 folder inside the Common Files.

I looked at the version of Creo Parametric and it was now F001.

I didn't download F001 for Creo Parametric.

Turns out the download has all the software in one download. Even though you find a download under Creo Direct and another one under Creo Parametric. It's the same file.

David Haigh
Phone: 925-424-3931
Fax: 925-423-7496
Lawrence Livermore National Lab
7000 East Ave, L-362
Livermore, CA 94550


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.

11 replies

Show previous replies
T
TomU23-Emerald IV
23-Emerald IV
April 19, 2012
The common files location is being set in the PSF files. I've had no issue (so far) altering the common files location to one of my choosing. I typically install on a PC, copy the install folder to a server, re-organize the folder structure to my liking, then update all files accordingly. I use a text editor (Notepad++) that allows me to find and replace all occurrences of a text string in all files in a directory (or set of directories). This makes it very easy to replace install paths from something like "C:\PTC\Creo_2_F000\Creo 2.0" to "H:\Creo 2.0". For our users here, we only run Proe/Creo from the network. We never install locally (except on laptops). This makes administration MUCH simpler. I also use a homemade batch file to launch Proe/Creo. This allows me to setup the necessary environment variables at run time instead of hard configuring them on each computer. Across the board we use one version. When I decide to roll out a new version, I simply change one line in my batch file and the next time everyone starts up, they will automatically be running the new build. For maintenance releases, no one ever even knows they've changed builds. For major releases, it's a more obvious, but still requires no work from the end users (other than dynamic installations like thumbnail viewer, etc.).

Tom U.
Terms & ConditionsAccessibility statement