Latest update - w_fc_p_10.1.024

[davidspurr]

[Vista64 Business / QX9650 / IVF 10.1.021 / VSPPE] EDIT: that should have been 10.1.019

Updating to the new version (10.1.024) requires a full uninstall of VSPPE in order to retain ability to develop x64 code. Ouch!

Does that mean:

1. Will lose customisations in VS?
2. When reinstall VSPPE, is it then necessary to reinstall VS2005 SP1? Then w_fc_p_10.1.024?
3. Do I need to uninstall VS2005 SP1 explicitly, or does that happen when VSPPE is uninstalled? I have no separate entry for SP1 under the "Programs & Features".
4. How do I tell if I installed VSPPE with IVF 10.0 or 10.1? Sadly I suspect the former [:-(]. but I'm not certain (see below).
5. If I update to w_fc_p_10.1.024 without re-installing VSPPE, can I do it later if I decide to produce further x64 exe's? ie. later uninstall VSPPE, then re-install VSPPE & w_fc_p_10.1.024?

Unfortunately, I do need to install this update as it seems one of the bugs in 10.1.021 is stopping me from compiling a critical program ("Internal error with IPO and MKL library").

David



Details from "About Microsoft Visual Studio":

Microsoft Visual Studio 2005
Version 8.0.50727.867 (vsvista.050727-8600)
Microsoft .NET Framework
Version 2.0.50727 SP1

Installed Edition: IDE Standard

Intel Fortran Compiler Integration
Intel Fortran Compiler Integration for Microsoft Visual Studio 2005, 10.1.4156.2005, Copyright (C) 2002-2008 Intel Corporation

Microsoft Visual Studio 2005 Premier Partner Edition - ENU Service Pack 1 (KB926601)
This service pack is for Microsoft Visual Studio 2005 Premier Partner Edition - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/926601

Update for Microsoft Visual Studio 2005 Premier Partner Edition - ENU (KB932232)
This Update is for Microsoft Visual Studio 2005 Premier Partner Edition - ENU.
If you later install a more recent service pack, this Update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/932232

[davidspurr]

Turns out the IPO/MKL problem was due to a compiler bug.

As noted in a separate post in the MKL forum, I took the plunge & installed the update sans VSPPE un-install & that fixed the Linker error I had hit into.

Still interested in answers to most of the above questions (though I now suspect I might be lucky - looks like my VSPPE may have been installed with 10.1)?

[Steven_L_Intel1]

I think you are referring to words that have been in the Installation Guide since the initial 10.1 release and this is only relevant if your VSPPE was installed by 10.0. You do not have to uninstall and reinstall VSPPE moving from one 10.1 version to another.

VS2005 SP1 would have to be reinstalled if you reinstall VSPPE. It does not have a separate uninstall.

There's a simple way to know if you have to reinstall VSPPE or not. Simply build an x64 "Hello World" application specifying that you are linking against the single-threaded, non-debug DLL libraries. (/libs:dll without /threads or /dbglibs). If it links, you're ok.

[davidspurr]

Thanks Steve