installing sw2005

It came the other day, like many others so I've read. Last couple releases we were in the middle of major projects and didn't want to risk any major headaches so we waited a while to install the upgrade. This time I'm ready to jump right in, I'm using XP Pro sp1, and have SW2004sp3 running, I'll likely up to the latest 2004 SP before I switch to 2005.

Can I still have both 2004 & 2005 loaded side-by-side? Is SW2005 ready for Prime Time or should I wait for SP1?

Comments appreciated.

Thanks Whit

Reply to
wc
Loading thread data ...

I find it to be quite ready, at least for what I do (in the broad machine design category). You really should check it out on your data before you jump though.

I have 03, 04, and 05 installed, but I've honestly not been back into 04 since. Precautions to separate 04 and 05 data are of course in order.

Reply to
Dale Dunn

I agree here. I'm the only one using it yet, but I'm on my own project right now. Seems to be pretty stable, I like a lot of the new features (power trim) and I wanted to get more experience with it before the masses here started in. I have been consistent in my installations in that SW2003 goes into SolidWorks2003, etc. That way everything stays clean enough to be able to run them all, if necessary.

WT

Reply to
Wayne Tiffany

You should fully Test SW before jumping into the fire. If you happen upon a bug that keeps you form doing your work. Your pretty well screwed! Because once your converted your files, you're there to stay. I also recommend that all companies fully test each major version with their products. Because we all only do what we do. Some use surfaces, some don't... some use Sheet metal only.... some do molds. So people will never do some of the things you do. So if you don't fully test SW, then it's no ones fault but your own if you find a bug and there is no workaround. On top of that your fully converted over and there is nothing no one can do for you.

I'm not saying SW05 isn't trust worthy, but I would rather be safe, then sorry.

Regards, Scott

Reply to
Scott

Very sound advice! There cannot be anything so revolutionary or beneficial in 2005 that is worth the risk. Next releases are always more hype and curiosity than productivity gain. I'm still crashing and burning on 2004/SP4.1

Spent almost two hours last night cleaning up an assembly that decided without user approval to change configurations and loose the location of a part. It had something to do with opening a new drawing, creating a configuration with a section, then creating another configuration from that configuration and suppressing some of the parts in the final configuration. And even before creating the configurations, opened the assembly drawing to discover mate errors that were not there previously. I have seen something like this way back in 2000 and Plus. 2004 crashes, slow drawings and other problems have wiped out any productivity gains that I may have gleaned from the release.

Geez, almost talked myself into upgrading

Kman

Reply to
Kman

I also suggest now turning on the performance email. That is one of the reasons that SW 2005 is as stable as it is. This year for Alpha and Beta it was "locked" to the on position. They now read the email that goes out religously and get very valuable information from it. Even more when you crash. If you have the performance email on SolidWorks will now what time down to the minute of when you crashed and have an idea why.

Ken Maren

Reply to
Ken Maren

I have 2003, 2004 and 2005 running side by side.

Reply to
P

I have 2003, 2004 and 2005 running side by side.

Reply to
P

I have 2003, 2004 and 2005 running side by side.

Reply to
P

Of course you have daily tape or hard drive archives, to protect against worst case scenarios, right?

Frankly, even though I have SWks 2004/4.1 and it is stable for me, I very often do a Save As with a suffix, just so I can revert if some part &/or assembly screws up badly (which ocassionally happens: last about 3 weeks ago). Yeah, I wind up with PartH.sldprt and so forth, but it is a heck of a lot easier than doing hours of work over to retreat to a former design position.

Bo

Reply to
Bo Clawson

Thanks for the input guys, lots of good, solid advise. I'll likely load it at home this weekend and see how it goes.

Thanks

wc wrote:

Reply to
wc

Must also your have newsgroup repeat button ON along with the three version of SolidWorks running concurrently! (grin)

Kman

Reply to
Kman

Daily tape back up! Nope Save, all the time till my save finger goes numb. Murphy's law SP4.1: When you forget to back up is precisely when your system will crash and cause hours of grief.

Kman

Reply to
Kman

One thing I've always had problems with in 2005. Opening drawings. I have been having major problems with drawings becoming corrupt and not being able to open them. This goes for old existing drawings that I've never used in 2005 to ones that were done complete in 2005. The one issue dealt with area hatching. I removed the area hatching in 2004 and the drawings then would open fine in 2005. You can run both side by side but install in separate directories and like everyone else said BACK UP your data before using 2005. And open your drawings first before doing anything with the models. If you open the models and save and then try to open the drawings you may just be SOL.

Reply to
J

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.