The solution ended up that there were remnants of three .NET programs
still resident on the computer. By using a registry cleaner (registry
mechanic) I was able to fix the tech support changes to the registry,
then use a uninstall program (not the Microsoft ones which didn't work,
but Smarty
Conclusions - bet wary of tech support J If I had thought to use non
Microsoft registry fix and uninstaller before hand, I probably could
have avoid days of frustration and hours of work, yet on all the message
boards I read of people with the same .NET errors, this never came up.
Is there any
We use the premium for work groups (5+ people) and 2008 has some nice
features, but 2006 works fine and I didn't see enough of a benefit to
warrant a $1500 expense at the moment.
I did try reinstalling 2008. I get part way through to where it asks to
install SQL and then crashes
From:
Well, back to grasping at straws, have you tried a Registry Cleaner?
Just anecdotally, as a certified non-expert, I found Registry First Aid
to be helpful without doing too much, and System Mechanic to be both
helpful and dangerous because it did do too much.
Another thought - have you tried
