finding fortcom on Windows 7

[phil]

I know Windows 7 isn't officially supported,but I saw Steve's May 1 post so I know some of you have tried it and it works. Though maybe it works because you were using VS2008. I installed VS2005 and IVF 11 (build 75) on Windows 7 build 7100 and when I go to compile a program I get a "fortcom: no such file or directory" message. I tried to repairing the integration between IVF and VS andreinstalling IVF. I checked the path and other environment variables and they look the same as they do on my Windows 2003 setup. Anybody else run into this?

-phil

[Steven_L_Intel1]

How are you starting the command prompt environment? Are you using the "Build Environment for IA-32 Applications" shortcut? I have had no issues on build 7100. I doubt the VS version matters.

[phil]

Quoting - Steve Lionel (Intel)

How are you starting the command prompt environment? Are you using the "Build Environment for IA-32 Applications" shortcut? I have had no issues on build 7100. I doubt the VS version matters.

I'm using the IDE. Do you have to configure the command prompt when you use the IDE? Also forgot to say it's 64-bit Windows 7 and it happens whether I use the IA-32 or Intel-64 IVF compiler.

[Steven_L_Intel1]

No, you don't have to configure the command prompt.

In Visual Studio, select Tools > Options > Intel Visual Fortran > Compilers. Check that Platform says Win32 (for now) and that Selected version says or 11.0.075. Click on the ... button to the right of Executables. It should show a list like this:

$(IFortInstallDir)binia32
$(CommonProgramFiles)IntelShared FilesIa32Bin
$(VSInstallDir)Common7IDE
$(VCInstallDir)BIN
$(VSInstallDir)Common7Tools
$(VSInstallDir)Common7Toolsbin
$(FrameworkDir)$(FrameworkVersion)
$(WindowsSdkDir)bin
$(PATH)

if you change Platform to "x64" it should look like this:

$(IFortInstallDir)binIntel64
$(CommonProgramFiles)IntelShared FilesIa32Bin
$(VSInstallDir)Common7ide
$(VCInstallDir)binamd64
$(VCInstallDir)bin
$(VSInstallDir)Common7Tools
$(VSInstallDir)Common7Toolsbin
$(FrameworkDir)$(FrameworkVersion)
$(WindowsSdkDir)bin
$(PATH)

Make sure that the folder C:Program FilesIntelCompiler11.0�75fortranBin exists and has IA32 and Intel64 folders exist and have files in them, including fortcom.exe.

[phil]

Thanks for your help Steve. The entries you listed in the Toos->Options etc. are all the same, however the path

C:Program FilesIntelCompiler11.0�75fortranBin

is actually

C:Program Files (x86)IntelCompiler11.0�75fortranBin

And it has fortcom in it. That's where it was installed by default. There is another Program Files folder without the (x86)... maybe I should've installed it there? Though the IFORT_COMPILER11 environment variable points to the right place. I'm having the same problem on two computers with the same setup. Maybe it's a permissions problem? I'm using an administrator account but I've heard that sometimes things aren't run as administrator. Though I wouldn't think that would lead to a "file not found" problem.

[Steven_L_Intel1]

No, that's all ok. I forgot some of the details for x64.

But you did remind me of something. You MUST run VS2005 as an administrator on W7 and Vista. I think that may indeed be your problem.

[TimP]

You must be running the 64-bit version of Windows 7, in which case that is the correct default path.
If you installed MSVC X64 component, and set /X64 in your project, the 64-bit ifort for Intel64 would be required, otherwise the 32-bit compiler for ia32.
Inside the ifort installation, in the bin folder, you will have either intel64 or ia32 directories, or both.
If you download the ifort installer, there are separate 32- and 64-bit versions, and also the big one which gives the option of either or both.
You would need to install or repair ifort as administrator, but should be able to run as administrator or not, as long as you work in a folder where you have write permission.

[phil]

Hold the presses! So when I create a new project and compile/run it, everything is fine. But I've been trying to get a pre-existing project to work... one that was created with the same VS2005 and IVF11 setup but on 32-bit Windows 2003. Sorry to keep adding new bits of information. Sometimes it's hard to know what's important.

Since the new project works I guess it's not the permissions issue. I can't find a reference to the Program Files path in the .vfproj or .sln files and /X86 is set in the project I'm trying to get running, so I'm not sure how to "port" this project from the 32-bit computer. I'll keep digging...

[DavidWhite]

Steve,

You say that VS2005 must be run as administrator. Does this also apply for VS2010?

I am still running VS2005 on XP. I am about to upgrade to VS2010 prior to the deployment of our new computers which will have Win7. However, no users will have Local Administrator access, so I am wondering what issues are going to arise.

Thanks,

David

[Steven_L_Intel1]

As far as I know, neither VS2008 nor VS2010 require administrative privileges to run.