linking Fortran 9.1 compiler with Visual Studio C++ Express 2005 in Vista

[cusilicon]

I have installed in this order: Visual Studio C++ express, the service pack for VS C++ express, the update for VS C++ express for Vista. Next I installed Microsoft SDK for Windows Vista Update (6000.16384.10). I then installed Intel Fortran 9.1 IA32 compiler, debugger, and integrations.

I am trying to run this with Simulia's Abaqus v. 6.7-1 and during Abaqus' verification it was unable to find Fortran 9.1 or C++. So this was my first clue that something was wrong.

I next tried running the ifortvars.bat file in the command window (DOS environment) and it gives me the following: "setting environment for Microsoft Visual Studio 2005 x86 tools. The system cannot find the path specified."

It certainly seems Intel fortran and VS 2005 are having some sort of problem linking together.

I am running the VS and Fortran with administrator privelages and have already tried unistalling everything and re-installing.

Any ideas? Is it something with the 'express' edition. Do I just have to point Fortran to visual studio somehow?

Thanks

[TimP]

VS express doesn't support GUI integration of non-Microsoft compilers such as ifort, so you couldn't have installed that. For command line operation, ifortvars.bat must CALL the vcvars32.bat of the VS, the same one which is used by the start menu command prompt window of VS. Assuming that CL is working in the VS command prompt window, it should also work in the ifort command prompt window, if you have the correct reference to vcvars32 in ifortvars.bat.
I wouldn't be surprised if the Abaqus user function facility required more than the VS express installation with ifort, unless Abaqus specifically instructs you on how to use Express. There are 90 day trial and academic versions of VS, and anyway the price of VS is small compared with Abaqus.

[Steven_L_Intel1]

This should work from the command line. Edit ifortvars.bat and correct the Call line so that it calls the correct .bat from VC++ Express, either vcvars32 or vsvars32. You'll also want to edit ifort.cfg and correct the path to the linker, if necessary.

I can't help you regarding Abaqus not finding ifort - I have no idea what it is looking for.

[cusilicon]

Quoting - Steve Lionel (Intel)

This should work from the command line. Edit ifortvars.bat and correct the Call line so that it calls the correct .bat from VC++ Express, either vcvars32 or vsvars32. You'll also want to edit ifort.cfg and correct the path to the linker, if necessary.

I can't help you regarding Abaqus not finding ifort - I have no idea what it is looking for.

Steve,
Thanks for the quick response. After looking at the ifortvars.bat file, the call line to the windows sdk was wrong. After I changed the call line to the proper SDK, I could run ifortvars.bat and have it recognize C++ express. I did check the ifort.cfg file, but it did not need editing.

As it turns out Abaqus was still not able to recognize fortran or c++. So, I uninstalled Abaqus, the SDK for Vista, and all the intel fortran stuff.

After uninstalling, I decided I should go back to the 2003 SDK. So here is what I am now using: The same c++ express I mentioned in the original post, microsoft platform sdk for windows server 2003 R2, and intel fortran 9.1. Vista seems to get along fine with this older SDK (which is the SDK I used in XP). I should also note, I had a copy of this SDK on a cd and I tried to use it the first time I installed Abaqus on my Vista machine. The install would not work so that is why I went to the newer Vista specific SDK. This time however, I downloaded the 2003 SDK from the microsoft site and did the windows verification as recommended on the download site. I did not have any trouble with the SDK install this time. After uninstalling and reinstalling this stuff I didn't have to change anything in the .bat files of Fortran. I did have to add: @call "C:program filesmicorsoft visual studio 8vcbinvcvars32.bat" to my abq671.bat file (for abaqus). I did not have to do this in XP to get abaqus to work.

So in the end, the old SDK seems to work best with Abaqus in Vista, although there is a chance in all of my tweaking trying to get stuff to work, I simply messed something up and the new SDK would actually work fine. (I'm certainly not going to uninstall stuff just to find out though!) Sorry for the length, but in case someone with a similar problem with Abaqus came across them I wanted them to have the full story. Thanks again!