Updates and new releases

[HelloMOTO]

New wildfire 2.0 user, datecode M120: Can anyone explain to me why PTCs support page is so complicated? o.k., nevermind. back to the point of this post, the PTC website lists lots of newer datecodes for wildfire 2.0. In fact, i think there is an error in the page that indicates there is now a wildfire 4.0. Please clarify whether it is beneficial to consider the newer datecodes. If newer datecodes are worth getting, then how do you keep your software up to date? Is it as simple as clicking an update button someone where hidden deep in the PTC website or do you have to reinstall the package? oh man... Solidworks was never this difficult to manage

 

[looslib]

You have to reinstall te software, but it knows the old location and overwrites the old files. In my experience, it is faster to remove and reinstall then overwrite.

There is a tool on the PTC site that will tell you what the bugs, how many new bugs and how many got fixed in each release.

Also look at

http://www.cadmin.co.uk/

for a 'review' of the different builds.

M160 seems to be very stable and has fixed some performance issues when used with PDMLink. This is the build that we used at my last company and the one I am rolling out now.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[Heckler]

Trust me SWx has its own set of problems but Pro/E is somewhat convaluted to upgrade date codes. I was told by a PTC engineer to remove the old date code then do a fresh install.

Best Regards,

Heckler
Sr. Mechanical Engineer
SW2005 SP 5.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

"Coming together is a beginning, staying together is progress, and working together is success." - Henry Ford

 

[HelloMOTO]

Thanks guys, i'll uninstall then reinstall. One more question: If my coworkers machine is running the M120 datecode and i update mine to the latest, will that cause a conflict? (we're using a server license which is running on my machine, and i can't login to his machine)

I know the best solution is to just upgrade everyone... I'm just curious about the compatibility because updating ProE isn't so automatic.

 

[Heckler]

What version of Flexlm are you using? Does that new date code call for an upgrade to Flexlm? .... If not then you should be safe but I would call PTC to make sure.

Best Regards,

Heckler
Sr. Mechanical Engineer
SW2005 SP 5.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

"Coming together is a beginning, staying together is progress, and working together is success." - Henry Ford

 

[dgallup]

I never uninstall Pro/E, I just install another version beside the old one & try it out for a while before switching. I only install to a server, users just have a shortcut on their desktop to the current production version. Very easy to administer that way. I don't think you can do that with SW.

 

[Heckler]

But performance takes a hit running software over the network. I wouldn't suggest loading MCAD software that way. The server just administers the user licenses. I do agree with loading a new version along side the original but only at major upgrades not updates. First you will need to check if the new date code requires an updated Flexlm.

Best Regards,

Heckler
Sr. Mechanical Engineer
SW2005 SP 5.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

"Coming together is a beginning, staying together is progress, and working together is success." - Henry Ford

 

[dgallup]

If you have a slow network Pro/E can be a little slower to launch over a network. There is no difference once it is up. Most networks are fast enough (even ours!) that you won't see any difference.

 

[looslib]

All files created in a version of Pro/E, like Wildfire 2, or comptable with each other across all builds.

Network installs are the easiest to administer but you do have the start-up lag. In my testing it is about 30 seconds to start a local install and 90 to start a network install the first time after logging on. The network time can be affected by network performance, but generally on a 100 mbit connection it is okay.

The network install really pays off when you have to upgrade 50+ workstations to a new build. Just upgrade the server and everyone has the latest build. It is fully supportted by PTC as an installation method.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[dgallup]

I just timed my workstation, Pro/E took 34 seconds to come up across the network. We do not have fast servers or new workstations but it is a 100 mb connection.

 

[looslib]

Is that after a new login or had you been running Pro/E, exit and then start it again? That time would agree with my timing on a restart of Pro/E, which is 6 seconds from a local install.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[Tofflemire]

Hi DGallup,

Your video driver might be the problem. You can go to your config.pro and change the following setting to set if it makes it faster to start up. You have to restart proE to have this changed take affect. Save the config.pro first.

"graphics" to "opengl" or from to the different options for graphics.

IF changing this makes a difference than you may look into finding a better driver for opengl.

Tofflemire