On one system I use, the installation of SP0 and incremental upgrading to SP1, SP2 and then SP2.1 (at the various times the packs became available) were reasonably easy; however, each of the upgrades took far longer than the initial installation.
On another system, the story is quite different and was extremely problematic.
In retrospect, I think the presence of Windows Registry and/or Windows Installer information for the Pre-Release of SolidWorks 2004 was the culprit.
Here's what transpired:
- I attempted to upgrade from SP0 (installed from the production release CDs) to SP2.1, but repeatedly the process dialog boxes informed me that SP0 was being configured. SP0?! - When the supposed upgrade completed, SolidWorks 2004 was STILL version SP0.
- To work around this, I decided to use the Control Panel applet to remove SolidWorks 2004 Pre-Release1 and SolidWorks 2004 SP0. (They were both listed, but only one actually existed, since SP0 had been installed over the Pre-Release.)
- After the program removal, I of course had to reinstall 2004 SP0 - then I was able to apply the "patch" to SP2.1 with the following difficulties:
A. The installation routine wasn't prompting me for the original CD(s), so it was necessary to perform the upgrade via the command line, as suggested by a SolidWorks support bulletin "workaround".
B. As the configuration phase was in progress, it seemed to hang when nearly complete. I was about to kill the process, but then noticed an underlying window's message box telling me that a particular .dll file couldn't be found. When I chose to ignore and then close it, the configuration finished. Why that message couldn't have popped up on TOP is the question.
C. During the installation of the upgrade files, it was often necessary to steer the program to the proper location of source files. It was even necessary to copy two of the .cab files from the SP0 CD (to the directory on my hard drive where the SP2.1 files had been unzipped) in order to continue.
So while it took only about 15 minutes to install a fresh copy of
2004, the upgrade to SP2.1 required roughly 1 1/2 HOURS. What's wrong with this picture?As the upgrade was "cleaning up" after itself, I noticed a dialog box message saying that previous versions of the program were being removed. Little did I know that my Traditionally installed SolidWorks
2003, SP5.1 was included in the "wiping" process.I realized 2003 had gone missing when attempting to launch it - only to see the waving flashlight icon searching for the target executable...
O.K., I can see where there might occur a stripping of the common Registry entries that could affect the running of my installation of
2003, but when looking through Windows Explorer, I found to my horror and amazement that the 2003 program files had been completely removed!So now I have to reinstall SolidWorks 2003. I'll do a traditional install, but will need to "hack" the Registry to temporarily keep the Windows Installer from dominating the process.
SolidWorks Corporation (if you're listening) - What were you thinking when you forced all users to employ the Windows Installer method? Is my experience creating a misconception or is the SP0 to SP2.1 service pack literally programmed to ferret out and destroy all earlier versions - even if they were traditionally installed?
Per O. Hoel
one unhappy camper