new instal

just upgraded to 2006 from 2003.
went to open a part I'd made, which had been fully resolved and looking
fine, and it asked to rebuild. I said sure. and suddenly theer were
errors everywhere. to the point that not one solid resolved.
so I took the file lent it to a friend who has been using 2006 for a
while to see what he got. opened beautifully. he even saved as 2006
for me. I tried to open *that* file... same result.
my machine runs W2k, and is a celeron 1.7GHz.
anyone hit anything like this?
thanks
Reply to
smith
Loading thread data ...
Just to be "correct", I do NOT think there is an "upgrade" from 2003 to 2006 and it must be a virgin install of 2006 off CDs and then the SP upgrade you need.
I am currently unaware as to whether SWks 2006 is supported on W2k, but I know they have announced an end time for that W2K support.
Each time I do a really major upgrade as you have done, I load up my OS on a new hard drive and load the new SolidWorks, so I do not keep crap and corruption in my OS, because SolidWorks is too important to me to have the OS cause me problems.
I would seriously, seriously consider buying a copy of WinXP and getting the SP2 CD from Microsoft (cheap considering the SolidWorks cost).
Bo
Reply to
Bo
SW2006 is the last version that will support win2k, so I think you're ok on that. The one setting that can cause rebuild differences is Tools > Options > Performance > Verification on Rebuild. If you turn this off, it might improve your results. You also might have the other fellow hit a CtrlQ to make sure the parts really did rebuild.
I'd also try opening the parts individually to see if you can isolate the problem somewhat.
You said it was a part and that no solids resolved, so this was a multibody solid? Have you gone through to see just what the problems were?
smith wrote:
Reply to
matt
sorry, I uninstalled 2003, and installed 2006. just meant it's an upgrade for me. a new windows was on my list.
umm, I'll have him try again with the CTRL-Q and see if I get a beter result, although.. I have tried many different files, some I'd made in my old 2003, some my friend had done wholly on his 2006.
come to think of it, I'm not sure if I've tried one that was a simple extrude. I'll do that next.
but as for the part that started this annoyance, it's multibody, not simple but not super complex. the first error was right in the first sketch: zero length line. which of course would destroy the whole thing.
Reply to
smith
Didn't think SWx would even run on a Celeron, no matter what speed...Besides the operating system, you might want to consider a new box. (Unless you like me and have no choice but what they give you to work on) Actually, I run 2003 plus at home on a 3gig Pentium 4 with 1 gig of RAM...sucker flies and has NEVER crashed once. I'll model stuff at home and send it to my work PC running SWx 2005 just to eliminate frustration.... It'll be hard to upgrade from that version....
Reply to
IYM
Good you noted the Celeron issue, as I missed it.
In addition, the need to have an up to date Video Card is mandatory to avoid "issues".
formatting link
Bo
Reply to
Bo
SW runs on a celeron
Not that I'd recommend it for everyday use, but my home machine is a 1.8 GHz celeron w/ a hacked Geforce PCI video card, 1G memory and win2k. I've had '04 and '06 on it, and both run fine.
The performance is surprisingly good-- I've had some pretty big assemblies (200+ components )open in it, and while it won't win any prizes, it's good enough to get real work done.
Reply to
Michael
We are in the process of rolling out the same upgrade from 2003SP3.1 to 2006. We have a test box set up with 2006SP2 on it and have tested a number of 2003 models. We have not seen any rebuild errors yet. Brad
Reply to
Brad
Check to see if "Verify on Rebuild" is turned "on" on one computer and "off" on the other.
Roland
Reply to
Roland

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.