problem running Intel fortran

[ivf_ian]

Several months ago, after a problem downloading the Intel Fortran package, I was given advice to uninstall the code and reinstall VS, Base Toolkit, HPC Toolkit in that order.  I did so and I could then use the code for developing Fortran programs.

I have not used that particular computer for quite a while and when I tried running the Fortran package again, I received the following error messages: missing files. Libfcoremdd.dll, Libmmd.dll and MSVCR100D.dll.  How come there is now an issue re. running the Intel Fortran?

I tried downloading MSVCR100D.dll and putting it in directories C:\windows\System32 and C:\windows\SysWOW64 as instructed by https://www.youtube.com/watch?v=Iv4yibSY6zs , but it still didn’t recognize the file when attempting to run the Fortran package.

What is the best way to fix the problem?  Uninstall old code and reinstall latest version?

Appreciate help in this matter.  Cheers, ivf_ian

[andrew_4619]

Libfcoremdd.dll is I think (without checking) a Intel runtime library used with a debug build. Those libraries are only set up if you are running the application with VS.  If you are want to run outside VS I suggest making a release build.

Copying dlls around a system is a good way to end up in trouble unless you know exactly what you are doing!

[ivf_ian]

I am running the program on the visual studio platform. 

Strangely enough, checking on whether or not the downloaded file mentioned above actually ended up in either of those directories, this was not the case, but a couple of files with names close to it did.  How could that be?

[witwald]

Funnily enough, a day or so ago I have encountered a similar problem with my Visual Studio 2022 Version 17.14 installation and the Intel Fortran Compiler 2024.2.1 (IFX and IFORT) installation. It started generating the "missing DLL" message out of the blue.

This behaviour appears to have started after one of the recent Windows 11 updates. I uninstalled Intel Fortran and reinstalled it and was able to run programs in debug mode again, which is one of those quite handy features when writing code. I am not sure what went awry with the original installation.

Where previously I was able to easily execute a program compiled in debug mode, either inside the debugger or starting it without debgugging, I am now being prompted for administrator permissions each time the debug-compiled program is executed. The way around that is to start the VS 2022 IDE in administrator mode. Again, I am not sure what has changed to create these new requirements.

[andrew_4619]

C:\Program Files (x86)\Common Files\Intel\Shared Libraries\intel64 is where those dlls are on my system, are they still there? I suspect the will be and it is the locating them that is going wrong.

[ivf_ian]

I don't have that directory, only upto Intel\shared files.  

[ivf_ian]

Thanks witwald, I was hoping for something like that to solve the problem.  Will try it.

[ivf_ian]

Thanks for your feedback, witwald. 

I installed Visual Studio Community 2026 and Intel one API HPC Toolkit, although I’m not sure how successfully.  Then I tried to run one of my programs, and while it appeared to input the various subroutines etc, when attempting a compile, I received the following error message:

Configuration ‘Debug\Win32’ requires compiler support for the ‘Win32’ platform, but that support is not installed.  Please either install the compiler support for ‘Win32’ or select another configuration.

How do I go about doing this?  Also what is the name of the VS executable  (exe) code and where is it located?

[JohnNichols]

If you installed the current VS and oneapi, you are stuck with IFX which is 64 bit, you need to select the 64 bit builds. 

IFX is a little annoying, but it is slowly getting better. 

If you want IFORT you need a 2024 offline installer.  

[ivf_ian]

Apologies, I guess I replied to the wrong contributor - new at this game,  Anyway, I uninstalled Visual Studios community 2026, Intel OneAPI Base Toolkit and Intel oneAPI HPC Toolkit and reinstalled them in that order.  However, I am still getting the same message as mentioned above, i.e. Configuration ‘Debug\Win32’….. When looking up how to install the compiler support, it informs me to install desktop development with C++ workload via Visual Studio installer (MSVC).  Checked this out, but found that this code had already been installed during the installation of VS.  I looked into the IFX option but couldn’t find how to download it.  So what is the issue and where do I go from here?  Appreciate any help with this.

[JohnNichols]

This is your error I think.  If you look up on picture you will see the greyed out X32, select the X64.  

Then it looks like these two shots

I do not know if 2026 Fortran does not install the link to IFORT, or I have to update it.   But if you are using 2026 use IFX, the minor issues are not worth wasting time.  

[ivf_ian]

I don't appear to have a greyed out area like yours - how come?  To the right of the debug window is win32, which when pressed gives the user a choice of win32 or configuration manager.  Do we have different versions of the download codes?  I find it weird that setting up the capability to develop programs using the VS platform seems to be very hit and miss.  While I would like to continue with code I have downloaded, how does one install IFX? 

[andrew_4619]

Your project is a project to build a win32 application. That is not an option. You need to go into the project configuration manager and add a x64 project platform to it and enable and select that.

The "problem" is IFX is only X64 and you are asking for something it does not do.

[Steve_Lionel]

Intel has moved the location of the DLLs around several times. The Common Files folder is no longer used. The NEW, NEW, NEW location, until next week (probably), is C:\Program Files (x86)\Intel\oneAPI\compiler\latest\bin

If you have the Common Files folder in your PATH, remove it.

[ivf_ian]

How do I remove the common files folder in my path?

[andrew_4619]

Yes it appears that location also.... Having just looked at my default PATH  is seems crazy that Intel has sooooo many really long path entries for OneAPI.....