Running Multi[ple IVF versions

[Christ_F_]

1. I had a licenced version of IVF 11.1 running with the VS2008 shell. I tried VS2010 with IVF2011.1 and now have licenses for both products. When I checked my VS2008 installation I found it was now running IVF2011.1. The reason I did not notice this for a long time is that it was runing my applications with IMSL just fine. Should installing IVF2011.1 overwrite the 11.1 installation? Did I miss something in the installation?

2. The document:
http://software.intel.com/en-us/articles/intel-math-kernel-library-intel-mkl-for-windows-using-intel-mkl-with-imsl-fortran-numerical-library?wapkw=(imsl)
describes a method for calls to IMSL to be routed automatically to MKL. Is this still and will this continue to be an active feature of IMSL integration and what changes to the procedure describerd need to be made for use with VS2008 and IVF11.1? Trying to get this to work is what alerted me to the version issue above.

Thanks

cf

[Wendy_Doerner__Intel]

When you install a never version of the compiler as you did with Intel Visual Fortran 2011 (which is really just 12.0) over an older version, the newer version's IDE will install into allMicrosoft Visual Studio products on your system. If the major versions are not different (i.e. both 11.1.xxx) then the newerIDE will probably work with both versions and you can select which compiler is called under Tools => Options. In your case, you can not install 11.1 on vs2008 shell and 12.0 on VS 2010.

------

Wendy

Attaching or including files in a post

[Martyn_C_Intel]

For2.:
Yes, with the 11.1 compiler, you can continue to use MKL underneath IMSL to supply versions of the BLAS that are more highly optimized for Intel processors. There is more than one way to do this, see the 11.1 Fortran Compiler User and Reference Guide, under Building Applications/Using Libraries/Using the IMSL mathematical and statistical libraries/Using the IMSL libraries from the Integrated Development Environment. The simplest way is to use an include file to link the needed IMSL, MKL and OpenMPlibraries, e.g

INCLUDE link_fnl_shared_hpc.h

You need to ensure that the paths to the include and library directories are set up as described in the user guide. You should not use this version of IMSL with Intel Fortran Composer XE 2011 (contains the 12.0 compiler).

[Christ_F_]

Hi,

Thanks for the reply. When I choose the 11.1 compiler in my options window and run with the line "include 'link_fnl_shared.h' " in my source, the program runs to completion. When I include the line "include 'link_fnl_shared_hpc.h' " the program crashes (halts execution and exits even in debug mode) at the first call to an IMSL subroutine.

cf

[Steven_L_Intel1]

You don't say what the error is. For each compiler version shown in the Tools > Options > Intel Visual Fortran > Compiler dialog, you must add the IMSL include and library paths.

If you are using link_fnl_shared.h, the IMSL DLLs must also be on PATH - this should have been set up when IMSL installed.

What is the error message?

[Christ_F_]

Steve,

There is no error when I use: link_fnl_shared.h. All my programs link and execute correctly so I believe the IMSL libraries are installed correctly.

When I replace this statement with: link_fnl_shared_hpc.h as suggested to use MKL backup to IMSL that the problem arises. The program simply exits at the first call to any imsl routine. This occurs even in debug mode and there is no other window, statement or warning. The command window program simply closes and I am returned to the IDE. If I started the program in debug mode then debug mode has been shut down when I am returned to the IDE. The problem seems to be in the link to the MKL libraries.

cf

[Steven_L_Intel1]

Ah, that I can understand. The MKL libraries changed in an incompatible way between 11.0 (when the IMSL libraries were built) and 11.1, creating this problem. Solution: don't use the "shared_hpc" variant for now. The static version should work.

[Christ_F_]

Steve,

Using the static libraries worked.

I hate to keep going over old ground: I am running Win 7 Pro on my office machine. Array Visualizer installed and worked with VS2008 and IVF11.1 as advertised when I simply added the appropariate LIB and INCLUDE directories to the compiler options and ran your VS repair tool. It also continued to work without any additional effort on my part when I ugraded to VS10 and IVF12. On my laptop however the same install (VS2008 and IVF11.1) and the same installer (me) crashes VS (VS Needs to Close etc) when I try to look at an array while debugging. I have removed and reinstalled several times to make sure it was not some thoughtless choice I made but this does not appear to be the case. What is going on here?

cf

[Steven_L_Intel1]

Is your laptop running 64-bit Windows? If so, Array Visualizer simply does not work there.

[Christ_F_]

Steve,

I don't know what you mean by "work". Both my mchines run 64 bit windows. I installed the 32 bit Array visuaizer on both. On both machines the "View Array" option is available on the Debug Menu and when I right click on an array during a debug session. This has been the case since I first installed VS2008 and IVF11.1. On my office machine, however, the view array option works and continued to work on VS10 and IVF12. On my home machine choosing "View Array" crashes VS.

Both machines are running Intel processors (I7 in the office and I5 on the laptop) and both have a lot of memory (12GB in the office and 8GB on the laptop). Virtually identical software is installed on both of them and both are up to date.

Both have Virtual Windows XP installed where I run CVF (I thought I saw someones post say CVF did not work under Virtual XP - not true)

Anyway, there is a clear difference in the behavior of the two machines. I have not ever tried programming with the AV - it was not of interest.

cf

[Steven_L_Intel1]

I've never been able to get AV, either 32-bit or 64-bit, to work under 64-bit Windows. I can get the View Array menu item to appear, but selecting it causes VS to crash.

[TimP]

I expect AV will work if you can bring up XP 32-bit under Win7-x64. This depends on BIOS support, as well as on a CPU with virtualization support. The laptop I bought my wife has this blocked in the BIOS. I did find that CVF worked OK inside the XP32 box.

[Christ_F_]

Since this is really important to me and perhaps to a small group of users, is there something we can do on my office machine to find out why it runs there?

I am dumping environment variables and IVF compiler options for include and lib for both machines and will have a look.

cf

[Steven_L_Intel1]

You have both versions installed. Use Tools > Options > Intel Visual Fortran > Compiler to select which version you want to use from within Visual Studio. The default is "Latest".

Regarding using IMSL with MKL, the instructions in that article are for command line use only and are more complicated than required. If you follow the instructions in the Intel Visual Fortran documentation for using IMSL (under Using Libraries > Using IMSL), you'll read that you need only add the following lines to one of your sources:

include 'link_fnl_static_hpc.h'
!DEC$ OBJCOMMENT LIB:'libiomp5md.lib'

Do not use IMSL with the version 12 compiler at this time.

[Samba_Ba1]

Steve,

It is a bit offline but does AV work with VS2010 and the new version 12 compiler?
I could not get it to work, it is grayed out on my machine.
I am using a 32 bit windows dual core intel processor.

Thanks,
Samba.

[Steven_L_Intel1]

I can get it to wok on a 32-bit system, but it may require a registry edit.

[Samba_Ba1]

Can you explain me the procedure to get it to work then or do you prefer to send me the details offline?

THanks

[Steven_L_Intel1]

Try the attached .reg file.

[Samba_Ba1]

Hi Steve,

I tried it but it did not work.
I am using the VS 2010 version 10.0.30319.1 RTMREL with .NET framework version 4.0.30319
I tried to edit the file with version 10.0 instead of 9.0 but it did not work.
I forgot to mention that I have the av_dev_ia32 installed.

Any suggestion?

Thanks and regards,
Samba.

[Steven_L_Intel1]

I am confused by "I tried to edit the file". You should only need to double-click on the .reg file to update the registry.

[Samba_Ba1]

Hi Steve,

First, I double-click on it and it updated the registry. Then I tried av on VS2010 but it did not work.
Then I open up the file and saw that it has VisualStudio/9.0 and I am using 10.0 so I changed the 9.0 to 10.0 and re-double-clik on it and it did not work again.
Was it what I supposed to do?

THanks,
Samba.