windows vista + Intel visual Fortan 9.0 +visual studio?

[kelaynak]

Hello,

1) Do you think that I can use Intel visual 9.0 in Windows Vista?

If yes, a) is it possible with visual studio 2003? necessary adjustment?

b) is it possible with visual studio 2005? necessary adjustment?

If no, what about with Intel visual 9.1?

Thanks in advance

Rgds

[TimP]

I don't doubt the correctness of advice posted previously on this forum. It's difficult enough to use VS2005 with Vista (install with upgrades as administrator, set tab run as administrator...). I wouldn't recommend ifort 9.0, even if it may be possible. 9.1 should work, but 10.x normally would be preferable. A new version may be released before you get squared away with your attempts to combine discontinued software with Vista.

[Steven_L_Intel1]

9.1.037 or later can be made to work on Vista with VS2005. 10.0 supports this combination; earlier versions do not. I think we had to make some changes to support Vista so I would not expect 9.0 to work reliably.

[Paul_Curtis]

Steve,

Could you clarify the what the limits are for running VS plus the various IVF versions, on the several versions of Windows?

I have a development machine with Win2K running IVF9.1.037 or whatever the last version is in the 9.1 series, together with VS2003. I apparently cannot upgrade to IVF10 because IVF10 is said not to support W2K (?).

Our products are widely distributed on W2K and XP (and a few Vista) machines, and it all works perfectly. If I upgrade the development machine to XP or Vista, and then go to IVF10, will F90 executables created from IVF10/XP or IVF10/Vista still be runnable on W2K machines?

What exactly is the set of features which "require" XP or Vista and are not supported by W2K?

TIA
Paul Curtis

[Steven_L_Intel1]

Paul,

The supported versions are for installation and use of the compiler. Executables you build should run on Windows versions back to Windows 2000 at least, maybe earlier unless you use certain Win32 APIs not present in the earlier versions.

I will admit that we don't test this much, but we have no reason to believe that there is a problem running IVF-compiled executables on W2K.

The reason we dropped W2K support is that Microsoft doesn't support VS2005 on W2K and our resources for testing OS variants are limited, so when we added Vista we dropped W2K. Again, this is for development, not deployment.

[Paul_Curtis]

Thanks for the response, but a few more questions...

Does "dropped W2K support" mean that IVF10 does not work on W2K, ie an actual technical change such that fundamental aspects of compiler functionality are absent or broken?

How about upgrading my IVF9.1.x to IVF10 retaining VS2003 on W2K? Does that cross some sort of line, or is that possible, since VS2003 works perfectly on W2K (and, as near as I can infer from the chat here, much better in fact than VS2005 on Vista or XP); and if IVF10 is supported in VS2003, why would that support be broken by platform issues?

[Steven_L_Intel1]

IVF 10 will refuse to install on W2K. Sorry. There is no technical change; it's just a support issue. We have not tested IVF 10 on W2K and can't make any representations as to whether or not it works,

[g_f_thomas]

MADsblionel:

9.1.037 or later can be made to work on Vista with VS2005. 10.0 supports this combination; earlier versions do not. I think we had to make some changes to support Vista so I would not expect 9.0 to work reliably.

FWIW I have 9.1.033 (it looks like VNI did a rebuild of IMSL 5 beyond this release and good to 9.1.038) and 10.0.027 working fine in VS 2005 on Vista.

Gerry

[hansr]

Nice to hear, that "Executables you build should run on Windows versions back to Windows 2000 at least." Now we can upgrade to IF10. After reading the Release Notes, we have had decided not to upgrade to IF10, because half of our users use W2000. Release Notes Intel Visual Fortran Compiler 10.0 : "Requirements to Run Applications For applications built for IA-32 systems: an IA-32 system running Windows XP, Windows Vista or Windows Server 2003. Some applications may run on older versions of Windows - you are responsible for testing compatibility." Hans

[Steven_L_Intel1]

As far as I know, we have not made any changes that would break W2000 compatibility for executables, but we no longer test on W2000 so it is up to you to make sure that your application works.

[JohnR]

I can report that I have had no problems whatsoever compiling on W2K (SP4) with all v10 compilers up to and including 10.0.27. I have successfully compiled complex projects using VS2003 and the command line, and created both 32-bit and 64-bit versions.

The applications run well on W2K (SP4), XP (SP2), 2003 server 64.

Cheers

John