- Tue Jun 24, 2008 5:05 am
#273652
OMFG - *that* was the most frustrating computer-related experience I have had in years...
OK, so after trying everything I can think of I finally broke down and installed Windows XP SP3. No luck. I then started removing everything I could think of trying the installation after each item - including .NET 3.0 as well as .NET 2.0. After removing .NET 2.0 the installer looked like it might actually succeed because it started downloading and installing .NET 2.0 again. Well, after awhile it bailed with the same failure, except now the message indicated .NET 2.0 succeeded but the vcredist_x86.exe install failed in exactly the same way. I even tried running msiexec in verbose logging mode on both the unpacked vcredist MSI file as well as the Maxwell plugin MSI file and absolutely nothing was logged except for one line indicatiing msiexec started.
So next I tried various debugging methods - DebugView, FileMon, ProcMon, etc. etc. with absolutely no light at the end of the tunnel. Then, for kicks I ran the vcredist_x86.exe as Administrator (I am a local administrator BTW, and I have always installed it as me before) and all of a sudden it installed. WTF?
OK, so now I run the maxwel Solidworks plugin as Administrator and it proceeds to install vcredist_x86.exe yet again, but this time it succeeds and the plugin installer runs and completes with no issues.
So now I am completely baffled. This makes absolutely no sense whatsoever. *But* I think I may have a pretty good idea of what it is about my particular system that tweaks this bug. When I originally installed XP, I added my username (as an administrator) with no password associated with it and used it for quite some time that way (I installed a couple versions of Maxwell in this configuration as well). At some point a looong time ago I wanted to either share a drive or perhaps it was that I wanted to use remote desktop - I can't remember. Anyway, one of these requires that your username have a password, so I changed my user profile to have a password associated with it, and probably changed the permissions on all the files when prompted (I am running an NTFS filesystem by the way).
At any rate - being a software developer myself as my day job - I have a warm fuzzy feeling that this is totally the root cause of this issue. I'll bet if you test installing an older version with a user that is a local admin with no password on their account, then change that account profile to use a password (thus changing permissions on a whole pile of stuff), I think an installation of a newer version of the plugin as that same user will then fail. I'm not sure if this is a feature of the maxwell plugin installer, or the vcredist_x86.exe installer, or windows installer itself.
Anyway, thank <insert diety here> I am done fighting with this bug! Hopefully this helps someone in the future... Thanks again to those who responded.
Mark.