Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Running Multi[ple IVF versions

Christ_F_
Beginner
3,499 Views
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
0 Kudos
23 Replies
Steven_L_Intel1
Employee
640 Views
Hmm - I just tried again on VS2010. When I click on View Array, I hear the sound IE makes when it has blocked a popup window but saw no message. Perhaps VS2010 is blocking it somehow.
0 Kudos
Christ_F_
Beginner
640 Views
Tim,

I think I indicated that both desktop and laptop machines were running Windows Virtual PC which requires Virtualization support so this is successfully enabled on both machines. Bios options are skimpy on laptop but this particular issue does not seem to be the problem.

cf
0 Kudos
TimP
Honored Contributor III
640 Views
Quoting cftac
Tim,

I think I indicated that both desktop and laptop machines were running Windows Virtual PC which requires Virtualization support so this is successfully enabled on both machines. Bios options are skimpy on laptop but this particular issue does not seem to be the problem.

cf

I was mentioning BIOS only for the case where BIOS limitations prevent running Virtual PC, which evidently isn't your problem.
0 Kudos
Reply