If you were one of the lucky ones who got a new machine for the holidays and it came with a shiny new copy of Windows 8, not to fear. PTC has you covered. The latest maintenance release of Creo 2.0 is M030 and it is fully supported on Windows 8. Stop by http://www.ptc.com/company/community/first/teams.htm to download new software.
If you're not sure which maintenance version you have, it is easy to check. Just start Creo 2.0 and pick File, Help, About Creo Parametric.
All FIRST teams should be on Creo 2.0 at this point. You can continue to use the Creo Elements/Pro software if you have an older machine, but you should be able to run Creo 2.0 on the same hardware. The big benefit of updating to Creo 2.0 is the new UI and command layout making the application so much easier to use.
Hopefully you've all had a chance to download the updated KOP and Arena for Ultimate Ascent at http://www.catalogds.com/db/service?d=first&c=browse
New to Creo? Check out the Primer from the software download page. There's a lot of pages in the document, but you should be able to complete it in a few sessions and it will give you a great foundation in how to use Creo Parametric 3D CAD.
M030 is the first build code to be officially certified to be supported on Windows 8. Earlier versions (M010 and M020) will proabably work without issue but the are not officially supported.
Note that in general, I have found M030 to be more stable that M010.
I've updated to M030 and have to say that it is being much better mannered now. Dragging and droping parts from a browser directly into an assembly is working well
Just curious. Did you do the update over the web or via full media download? I have done a couple over the web w/o problem but have full CD image on a DVD and a USB and update from M010 completes in 10 seconds with no actual update being done.
I extracted the files to a USB.
I'm upgrading to from M010, so I made it install in the original directory.
After all these years, the installer still tries to create a directory name with a space in it, which is annoying because windows doesn't like it. The first go-around, I ended up with a ...Creo2/Creo 2.0/Creo 2.0 directory structure which means I had Creo 2 M010 and Creo 2 M030. I just copied everything up to the Creo 2 directory and ran the installer again...much cleaner
Just becomes a real pain in the neck to upgrade multiple machines!
I LOVE COMPUTERS!
In the past, I would do an install on a machine and get it set up. Then I would copy that directory to all the other machines I wanted it on and then ran setup. I could also create a trail file that runs through all the installer inputs so it can all be done in a batch file.
I notice that there is now a reconfigure.exe file, so I'm guessing it can probably done in a similar way.
Any comments from PTC wizards?
Wish it could be as easy as:
PTC would know ID and Team, etc. and could auto-generate and put in place Product Code and/or license file......
ARRRGHHH!!! I wish I was in Needham at the TC's right now. I'd love to find to have a nice, friendly chat with whoever hard-coded the Creo 2.0 directory name into the installer!
I have not. In fact, in over 20 years or using Pro/E-Creo (yes, I'm that old!) I have never seen a problem opening models from earlier versions or build codes.
What is the problem?
Also agrivated that I have a 0% success stat for M010 to M030 upgrade via web or media.
Only solution is to do full uninstall of M010 first. Left 3 machines doing reinstall successfully overnight at school. With issues of opening models between builds, will also have to help kids reload on their personal machines.UGH!!!!
Been there Stuart
When you do the upgrade, make sure you don't enter "Creo2" as the install folder. I believe that on my install when I had it M010 already, I had to select the next level up.
If I have c:\ptc\Creo 2.0\
I enter c:\ptc as the install location
What a pain. Team meets for 3 hours each nite and I am lucky to load 1 or 2 machines!
Are there any know issues with the "Install over the Web" process for Windows 8 (64bit). One of our students wanted CREO on his W8 machine and I initiated the Web install for him. Installer downloaded and installed. I ran it and got to the products to install screen and then hit install. Nothing except Quality agent seemed to install
I've had issues with the "Install over the Web" for the professional and educational version of Creo.
I REALLY have a problem with anything over the network at schools, thus my preference for using a DVD or thumbdrive for installing on other machines.
Holy cow Adam! I had no idea you were that much of an old geezer! (I only have about 15 years with Pro/E).
Anyway, started off with drag-and-drop into assembly crashing, then into a new window, and then plain old file, open.
I'd had quite a few other crashes with M010, so I figured it was time to go to M030 anyway.
This has become quite the complicated thread, I will try to summarize responses to all here:
1) Crashes opening M030 files in M010: In my 20+ years using Pro/E-Creo I have seen this happen maybe one time. If anyone has files from M030 that will not open in M010, please contact me, I would like to send them to development.
2) Installation via Web or Full Media: If you follow this forum even a little you will already know that may users (not all) have troubles with the web install. For this reason, I always suggest that you download the full media, place it on a thumb drive or DVD and install from that media. Most teams I know place it on a thumb drive or two and pass that around to the team for installation.
3) Update from M010 to M030: If you have the M030 media available, the update should be fairly painless. No new license file or Internet access is required. I would only update if you are experiencing problems with M010.
** Note: Josh had a problem with the installation folder because he was not using the default. I plan to look into this and will report what I find. Fortunately most Academic customers use the default installation folder.
5) Getting a PTC ID for joining the team's WC project: This isn't possible as the WC server points to the LDAP server containing each PTC ID. PTC ID must come first.
That's all I have for now. Sorry that some of you are having some problems with this, I hope this helps.
So, just wait I recently updated my Windows 8 laptop to Creo 2 build 40 and guess what I now get a popup window called CFGERROR listing a lot of config options that I have never used and don't need. I can't go from one part to another in an assembly without getting this error. Even when I am in a drawing as I go from sheet to sheeet (part to part) I get the same error. Beware build 40 at this time! I hope there is a way to stop this stuff (&^%$) My productivity using build 40 is about 20% less than using Build 20. Perhaps I should not even bother updating any more. I don't know.
Let me know if you have ever experienced this.
Donald, first of all, I think your post is in the wrong location. This is for High School students and mentors of FIRST robotics.
In regards to the "CFGERROR", you might check your "as loaded" config.pro and see if there are any incompatibilities with settings. If I recall, there is a red dot in the "Status" column.
Sorry I stuck my nose where it did not belong. I am still having problems with the configerr even though my config file shows only green spots ( don't understand these but I try to avoid the red ones all the time). I guess they are akin to traffic lights (which I do my best to avoid) at all cost. My point is the it's still an issue that when I open a file created in build 10, or 20 on build 40 I can't open any part without getting cfgterror for things that I don't even want set in my config.pro file. PTC I appreciate you trying to be the saviour of us all of cretans but leave my files alone! I have been using Pro for over 15 years (yeah I'm over 50) but I still don't like someone or something making decisions for me. I would not have survived to my age withouut being able to make very good decisions for myself. PLEASE HELP ME FIND A WAY TO FIX THIS!!!
I is most likly not related to the new build code of Creo that you are using. This error is typically generated when the config.pro option "mdl_tree_cfg_file" is pointed to an incorrect location or currupted .cfg file.