Creo 2.0-F001 & Another interesting thing

[davehaigh]

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.

[dgschaefer]

I wondered how Creo would handle an installation of say M050 of Direct
when M030 of Parametric was installed. Would it install both in the
'Common Files' folder or silently upgrade the older build? I'm not sure
this answers it since F001 is an odd build, I've never seen an 'F' build
that wasn't F000.



I'd assume this was a fix of some critical issue and might therefore
mean all would be updated where an older maintenance build would not.



BTW - Anyone know what the story is about Creo 2.0 F001? I have F000
downloaded but not installed.



Doug Schaefer

[davehaigh]

I asked PTC.

F001 fixed the uninstall bug.

Also it's intended functionality that when you update one you update all. So if you have Direct, Parametric, & Simulate they will all update at the same time.

David Haigh

[bgruman]

Maybe I'm jumping the gun here, but this sounds like a bad deal to me...
I currently have a couple of clients that are running WF4-M160, other
clients that are running WF4-M060, and another that is still on WF3-M200.
To avoid possible regen errors, I have always considered it necessary to
build parts using the exact build code that my clients are using... so,
I end up with several different Pro/E installs on my systems.
Now, fast forward to the Creo2 world... If I have two clients on two
different builds of Creo2, and PTC has an "update one, update
all" philosophy, How do I manage the separate build installs on my end?

Am I missing something here???

Bernie

Bernie Gruman
Owner / Designer / Builder
www.GrumanCreations.com

[davehaigh]

This doesn't preclude you from having multiple installs on your system. I think you just need to change the loadpoint to a path with the maintenance release in it. At this point I have no intention of updating the software in place.

C:\ptc\Creo 2.0-F001\.......
C:\ptc\Creo 1.0-M030\......
C:\ptc\Creo 1.0-M020\......
C:\ptc\WF4-M210\.......
Etc.

You better have a large hard drive or install these on a network resource.

David Haigh

[AndyHermanson]

Also, the install does not overwrite the Common Files folders. It installs a new "date code" folder next to it for date code specific files.

[cid:image001.png@01CD1E32.6B957F10]

[cid:image002.png@01CD1E32.6B957F10]

[AndyHermanson]

Sorry didn't finish my thought... So all you need is a different launcher. You can have your build specific config.pro options in the common folder\text and just launch the build that you want without having them all installed correctly. This is moving forward of coarse so it doesn't solve the issue with the Wildfire installs.

[bgruman]

Thanks All for the info.
I've just re-upped my maintenance and have yet to install Creo1, or Creo2.

Thanks for the heads up on this issue. Looks like I have a lot to learn
with Creo.
Bernie

Bernie Gruman
Owner / Designer / Builder
www.GrumanCreations.com


On Thu, Apr 19, 2012 at 1:43 PM, Andy Hermanson <
andy.hermanson@daktronics.com> wrote:

> Also, the install does not overwrite the Common Files folders. It installs
> a new "date code" folder next to it for date code specific files.****
>
> ** **
>
> [image: Description:
> C:\Users\aherman\AppData\Local\Temp\SNAGHTML15beac2.PNG]****
>
> ** **
>
> [image: Description:
> C:\Users\aherman\AppData\Local\Temp\SNAGHTML15cb206.PNG]****
>
> ** **
>
> *From:* Haigh, David A. [
> all" philosophy, How do I manage the separate build installs on my end?**
> **
>
> ** **
>
> Am I missi...

[davehaigh]

Just another shameless advertisement.

I'm going to be presenting a talk at PlanetPTC in Orlando, June.
Creo Admin 101.

Yes there's a lot of stuff to know.

Your job as an admin just got a lot more complex.

David Haigh

[davehaigh]

Well, actually, you can't do that.

Even though there is an F000 and F001 folder in the Common files folder.
The executable in the Parametric folder got updated to F001.
That F000 folder is dead wood, there is no executable left that is F000

The only way to have different maintenance releases is to install them in different load points.

David Haigh

[TrainStopper]

All this administration business has me distressed 😉 I truly have no need for build-versioned paths and prefer not to have to diddle around with the paths in config.pro every time I install a new build.
Easy enough to try at my end, but I'm wondering if anyone confirmed whether the installation of Creo can still be forced into non-changing directory paths of my choosing?

Regards,
Walt Weiss

[TomU]

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.