topic Problems installing Composer XE Fortran in Software Archive

Problems installing Composer XE Fortran

Hermann_Zeyen — Fri, 17 Dec 2010 10:20:09 GMT

Hi, It seems that there is a small bug in the installation procedure of the last Composer XE Fortran installer (w_fcompxe_novsshell_2011.1.127). While the C-installation allows to overwrite the older version, the Fortran installation does not allow me to do that, it creates without choice a new subdirectory and a second copy of the Fortran. Sure, I could intall C also in the same new subdirectory and everything works fine, however it would be good to allow coherent behaviour of both installations. All the best, HZ

Problems installing Composer XE Fortran

Hubert_H_Intel — Fri, 17 Dec 2010 10:29:55 GMT

I'll have a look at this and give you an answer soon.
Regards, Hubert.

Problems installing Composer XE Fortran

Hubert_H_Intel — Thu, 23 Dec 2010 15:29:05 GMT

Sorry for the delay. I did a couple of investigations with the Intel Visual Fortran Composer XE for Windows*, but couldn't detect any problem. Both the alternative Installation as well as an update installation (where the Compoxer XE Update 1 replaced the initial release) worked fine.
Could you please provide more info about the OS and evnrionment. Maybe this is an issue with a special system configuration only.
Regards,
Hubert.

Problems installing Composer XE Fortran

Hermann_Zeyen — Thu, 23 Dec 2010 16:07:12 GMT

Hi Hubert,

I am using Windows 7 professional 64 bits and I don't use the standard emplacement but want to install it on the D: disk. As I said, no problem installing the C compiler, but the Fortran simply didn't give me an option, even when I told it to do a user controlled installation (which in the former version was not necessary if the C compiler was installed first).

Cheers, Hermann

Problems installing Composer XE Fortran

Hubert_H_Intel — Fri, 07 Jan 2011 07:44:26 GMT

Hermann,
Which is the version of Visual Studio you have installed on your machine? Do you have more Visual Studio versions installed (2005, 2008 and/or 2010)?
Hubert.

Problems installing Composer XE Fortran

Hermann_Z_ — Fri, 07 Jan 2011 13:39:32 GMT

I am using Visual Studio 2010. Since I just reinstalled the whole system, there shouldn't be any trace of 2008 (the one integrated with Intel Fortran) left.

However, I don't think it has to do with Visual Syudio. The question where I wanted to install the new version simply didn't appear and this should be before the installer even asks about the VS version.
Hermann

Problems installing Composer XE Fortran

Hubert_H_Intel — Fri, 07 Jan 2011 14:09:49 GMT

Hermann,
I just finished a test installation on a fresh machine. I installed the C++ Composer XE and replaced this by the Comoser XE Update 1. The installation gave me the choice to either keep the initial version or overwrite it. I did an overwrite. Then I installed the Fortran Composer XE and then the Fortran Comoser XE Update 1, but here the installater didn't give me the choice to overwrite the initial Fortran installation; it installed the Update 1 side-by-side with the initial version. So it's true what you encountered. Thanks for submitting this finding. I'm going to file a defect for the installer.
Until this will be fixed by a newer update I think there is no real problem. Just make sure that the Fortran Update 1 is active (in Visual Studio go to Tools > Options > Intel Visual Fortran > Compilers and select the right version (here: Intel Compsoer XE 2011 Update 1 build 127).
Does this help?
Hubert.

Problems installing Composer XE Fortran

Hermann_Z_ — Fri, 07 Jan 2011 14:22:58 GMT

Hi Hubert,

What I did, I installed both C and Fortran in a new directory. Yes, it is no real problem (except for disk space and having to remove manually the old version). I only wanted to mention this problem so you are aware for the next update. Thanks for your attention.

H.

Problems installing Composer XE Fortran

Hubert_H_Intel — Tue, 11 Jan 2011 10:52:11 GMT

Hermann,
A defect was filed against the Fortran install problem and will be fixed in one of the next updates. Thanks for bringing this up!
Hubert.