yang686526

solidworks 2006 crashing after installing service pack 3
microsoft has come out with their service pack ( security upgrade 3). since then my copy of solid-works 2006 which has been running fine up until now, occasionally gives me a signal that it has encountered a problem and needs to close. about twice a week usually right when i am in the middle of something.
running solid-works rx indicates, that other than being a bit low on memory ( yellow x) there are no problems with the program. of course every time this does this, the computer is sending an error report to microsoft.
is any body else having this problem?
b.e.
hie berkshire, i can really understand your headache with this one. my experience of xp sp3 has been a bad experience also.................however slightly different.
one monday of last week, i unpacked a brand new dell workstation (tested on the sw website), powered up, connected to the company network and installed ms office 2003. shortly afterwards, the usual, "updates are ready to install" so i proceeded with the updates (a mixture of security patches). out of the box the os was xp sp2, so while i was in "updating" mood, i decided to use "microsoft update", and basically i installed everything that was recommended, including sp3, obviously thinking that it was the right thing to do by keeping eveything up-to-date.
however, i started to install sw2008sp4 from a full download, all was fine until 65%, then error 1603 and the installation fails. possibly the download i thought, so i used the dvd at sp0.0, same error message at 65%. so i gave up and contacted my var. they said, that it must some preconfigured dell setting in the windows registry so wipe the hdd and re-install everything. i planned to do that on wednesday however my own dell workstation had issues so i ended up reformatting its hdd and installing everything from scratch instead. i done the same installation procedure as the other workstation and the same damn error 1603 message again.
after alot of messing about, i ended up installing sw2007sp5 onto both machines. no error messages, perfect install. as a test i then gambled to upgraded that working installation to sw2008sp4, the error message 1603 came up only when installing sw explorer, but i just uninstalled the previous 2007 version of sw explorer and ran the sw explorer installation again. no errors this time. now i have a working machine again.
i have never had so much hassle in all my years trying get some bloody software installed. the funny things is, i actually had 3 version of sw running my own workstation prior to wiping it (2007sp5, 2008sp4, 2009beta3) all worked perfectly. the os was on sp3 of xp.
so from my experience i have deduced the following:
1) for a brand new workstation, do not install xp sp3 until you have solidworks 2008 up and running first.
2) sw2007 appears to install fine xp sp3. i can't speak for any other version.
according my var, sp3 is changing, in some way, registry permissions which is causing the installation to fail. they recommend holding off on installing sp3 for another few weeks until ms have made some tweaks, and if already installed to roll-back the installation to sp2.
anyhow, thats my two cents worth.
cheers,
declan.
that kinda confirms my suspicions, everything was working fine until i put sp3 into the computer.
b.e.
i recently received a new computer, equipped w/ xp pro sp 3, also a dell. using sw 2008 sp 0.1 (if it ain't broke don't fix it.) installed sw after the upgrade of the os, everything is ok. no crashes, rock solid. been using this setup for 2 months now. dell precision 5400 intel xeon e5420, 2.5ghz, 4 gb ram, nvidia quadro fx1700
regards.
c
thanks for this posting. it answers my questions about xp sp3. not going to do it.
matt lorono
cad engineer/ecn analyst
silicon valley, ca
i've installed xp-sp3 on eight computers (one with sw08-sp4, one with sw2006sp4, the rest without any cad) ... no problems with installing ... no problems seen on any pc.

its a pretty mixed response on this issue......either everything has gone perfect or its been a complete disaster story. unfortunately its been the latter for me.
i will have to adopt the approach of "if its not broken don't try to fix it".