> I found that installing VS2003 SP1 caused a few problems on my PC. My
> installation was VS2003 Professional (VC++) followed by VS2005 Standard
> (VC++ and VC#), on XP Pro SP2.
>
> First thing I noticed was that many of my file associations had been
> corrupted. .TXT of all things was now some type library extension, and
> Visual Studio solutions were pointing somewhere strange. Many others had
> become broken. Running "Restore File Associations" from VS2005's options
> seemed to fix them all, though it reported an error and said it couldn't
fix
> all associations for some reason.
>
> Secondly my VS2003 C++ directories were corrupted; my executables path had
> gained a "CC" before the compiler path, becoming "CC$(VCInstallDir)bin"
> which caused all compiles to fail with "Error spawning cl.exe". Standard
> library include and lib paths were also broken, this time gaining only a
> single C, causing compilation then linking to fail with unexpected errors.
>
> Just throwing this out there in case anyone else encounters these
issues...
> quite astonishing really given the length of time this has been in
> development. And I think the installation speed could have used some
> optimisation too...

>
> --
> Andy
>
>

>I found that installing VS2003 SP1 caused a few problems on my PC. My
>installation was VS2003 Professional (VC++) followed by VS2005 Standard
>(VC++ and VC#), on XP Pro SP2.
>
> First thing I noticed was that many of my file associations had been
> corrupted. .TXT of all things was now some type library extension, and
> Visual Studio solutions were pointing somewhere strange. Many others had
> become broken. Running "Restore File Associations" from VS2005's options
> seemed to fix them all, though it reported an error and said it couldn't
> fix all associations for some reason.
>
> Secondly my VS2003 C++ directories were corrupted; my executables path had
> gained a "CC" before the compiler path, becoming "CC$(VCInstallDir)bin"
> which caused all compiles to fail with "Error spawning cl.exe". Standard
> library include and lib paths were also broken, this time gaining only a
> single C, causing compilation then linking to fail with unexpected errors.
>
> Just throwing this out there in case anyone else encounters these
> issues... quite astonishing really given the length of time this has been
> in development. And I think the installation speed could have used some
> optimisation too...
>
> --
> Andy
>

>I found that installing VS2003 SP1 caused a few problems on my PC. My
>installation was VS2003 Professional (VC++) followed by VS2005 Standard
>(VC++ and VC#), on XP Pro SP2.
>
> First thing I noticed was that many of my file associations had been
> corrupted. .TXT of all things was now some type library extension, and
> Visual Studio solutions were pointing somewhere strange. Many others had
> become broken. Running "Restore File Associations" from VS2005's options
> seemed to fix them all, though it reported an error and said it couldn't
> fix all associations for some reason.
>
> Secondly my VS2003 C++ directories were corrupted; my executables path had
> gained a "CC" before the compiler path, becoming "CC$(VCInstallDir)bin"
> which caused all compiles to fail with "Error spawning cl.exe". Standard
> library include and lib paths were also broken, this time gaining only a
> single C, causing compilation then linking to fail with unexpected errors.
>
> Just throwing this out there in case anyone else encounters these
> issues... quite astonishing really given the length of time this has been
> in development. And I think the installation speed could have used some
> optimisation too...
>
> --
> Andy
>