Installing the IMSL Fortran Windows
win7-32位系统下abaqus6.9安装intel visual fortran11历程和setenv调用故障的解决
win7-32位系统下abaqus6.9安装intel visual fortran11历程和setenv调用故障的解决2013-04-04 21:52:44| 分类：默认分类| 标签：|字号大中小订阅本人菜鸟一枚。
由于要学习abaqus的子程序使用方法，所以要在电脑上安装ivf（intel visual fortran）才行。
根据网上的教程，我鼓捣了三四天才顺利装上。
其间遇到了一些问题，网上很难找到答案。
为了避免大家再受到相同的折磨，现将安装日志记录如下。
1. 需要的软件。
abaqus的子程序是用fortran语言编写的，要调用必须安装ivf。
但是ivf只有程序编译功能（胡乱解释），需要依靠microsoft visual studio软件进行连接。
所以要首先安装vs（visual studio）。
2.软件版本。
win7-32位系统，abaqus6.9（版本较老，懒得换）。
vs2008中文版（有的网友说中文版的不行，但是我的经历证明是可以的）需要在ivf之前安装，abaqus安装次序无所谓。
ivf11.1.038版本，必须在vs2008之后安装。
3.设置。
网上有两种方法，一种需要改环境变量，另一种不需要，本人较驽钝，选第二种。
打开abaqus安装文件夹C:\SIMULIA\Abaqus\Commands（看自己的安装路径了），找到abq691.bat 文件，右键选择“编辑”。
在原有文字之前加上@call "C:\Program Files\Intel\Compiler\11.1\038\bin\ia32\ifortvars_ia32.bat"，包括引号在内哦。
4.开始菜单——〉所有程序——〉abaqus6.9——〉abaqus verification，进行安装验证，完成后会自动生成并打开验证结果文件，各项都是“PASS”，表示安装成功。
5.经验教训。
软件版本不对是不行的。
Fortran软件安装大全
为大家介绍fortran编译软件，和imsl库的使用，有些地址已失效，有些软件在群共享里VS破解用百度的序列号，ivf用crack文件里的许可文件（.lic）。
一．跟上时代的脚步：Visual studio2012+intel visual fortran2013, （兼容win7 64位32 位）目前是最新的组合，配合强大的vs2012编译器，全新的VS界面感触以及操作。
仅这个可以跑在win8系统上。
/d/iMuvAwLMJAC8l1tR9cd二．推荐使用IVF2011+MVS2008（兼容win7 64位32 位）下载方案地址：/p/1536274172mvs2008：/topics/2743184/ivf2011：/topics/2901142/安装看页面评论，IVF版本自带MKL（Intel数学核心库）三．通用版本：MVS2008+ivf11.0.061（兼容win7 64位32 位）mvs2008：/topics/2743184/ivf11.0.061 ：/topics/2746349/安装看页面评论，IVF版本自带MKL（Intel数学核心库）四．IMSL6.0下载地址：/post-310268.html（下载32位的IMSL库）安装方法：/s/blog_6c7caddf0100n8up.html（仔细认真看）安装参考：/html/kaifa/281/2011/09/024*********.htm这个imsl6.0只支持第三个fortran版本组合。
五．大名鼎鼎的CVF了，自带IMSL库，在群共享里，跑在xp上，win7可能不兼容。
六．免费软件ftn95编译器，fortran95的格式，语法严格，结构精简。
Xp以及win7 32位，也在群共享此文由计算数学_小傲同学总结，欢迎转载。
Windows下VSCode搭建Fortran环境
Windows下VSCode搭建Fortran环境Windows下VSCode搭建Fortran环境1. 下载VSCode下载然后⼀路安装即可安装下⾯3个插件2. 下载MinGW-W下载之后解压记住路径.例如我放在: C:\environment\mingw643. 搭建环境变量1. 打开环境变量即在系统变量中加⼊: C:\environment\mingw64\bin注意: 结合⾃⼰的路径.2. 测试是否成功打开cmd, 输⼊gcc , 显⽰如下, 则配置成功4. 编写Fortran代码1. 打开VSCode, 并新建⽂件program projectNameimplicit noneprint *, "Hello world"!fortran语⾔注释 pause写上, 运⾏窗⼝不闪退pauseend program projectName2. 写代码环境才能运⾏在当前项⽬下新建⽂件夹:.vscode在该⽂件夹下,新建⽂件: launch.json复制以下代码在该⽂件{"version": "0.0.1","configurations": [{"name": "Fortran Launch (GDB)","type": "cppdbg","request": "launch","targetArchitecture": "x86","program": "${workspaceRoot}\\${fileBasenameNoExtension}.exe","MIMode": "gdb","miDebuggerPath": "C:/environment/mingw64/bin/gdb.exe",//结合⾃⼰的路径!"args": [],"stopAtEntry": false,"cwd": "${workspaceRoot}","externalConsole": true,"preLaunchTask": "gfortran"},{"name": "Intel Debug Attach","type": "cppvsdbg","request": "attach","processId": "${command:pickProcess}"}] }注意: "miDebuggerPath": "C:/environment/mingw64/bin/gdb.exe" 这是我的mingw64路径在该⽂件夹下,新建⽂件: tasks.json复制以下代码在该⽂件{"version": "2.0.0","command": "gfortran","args": ["-g","${file}","-o","${workspaceRoot}\\${fileBasenameNoExtension}.exe"],"presentation": {"echo": true,"reveal": "always","focus": false,"panel": "new", //这⾥shared表⽰共享，改成new之后每个进程创建新的端⼝"showReuseMessage": true,"clear": false}}3. 运⾏代码成功!或者通过控制台输⼊gfortran main.f90 -o main就会⽣成⼀个main.exe以后新建新的Fortran项⽬, 将.vscode⽂件夹复制到别的项⽬下即可。
intel_fortran安装图文教程
安装说明： 1.安装 MS visual studio 建议安装正版MS visual studio 2008、 2010。（也可使用破解版来体验） 学生正版序列号免费申请：说明见后 https:// https:///Product/P roduct.aspx?productid=4 / 下载地址： Liser上 fortran语言 的课件 校内的ftp（Grid搜索，bbs的 mswindows版资源下载） 六维空间 其它地址
没有装visual studio的电脑，或没有正确整合 的：安装后，没有可启动程序 右图为正确安装后的开始菜单栏目
启动visual studio 或者启动intel parallel fortran compile XE 2011都intel visual fortran ConsoleApplication main program code 取好文件名字，选择存储位置
/
https:///Pr oduct/Product.aspx?productid=4
无法正常验证时候，使用教育网ip上网，
若没有安装MS visual studio 编译器，则会出 现如图情况，反之没有叹号
windowsins的的tall正在准备安装解决办法百度文库
windows install正在准备安装解决办法方法一：卸载，重新安装windows installer服务一、先用msiexec /unregserver 停掉windows installer服务。
二、下载InstMsiW.exe，用winrar解压开。
进入目录。
三、右击msi.inf ，点击安装，右击mspatcha.inf ，点击安装。
四、再用msiexec.exe /regserver 启用服务。
方法二：1.如果曾安装过ACDSee5.0（包括迷你中文版），卸载它。
如果还不行就重装Windows Installer 或者ACDSee 4.02.运行cmd，然后运行sfc/scannow检查系统文件3.运行Services.msc，把Windows Installer 服务设置为手动运行，然后重新运行4.打开任务管理器，找到并结束ikernel.exe进程，重新安装5.禁用杀毒软件的实时防护6.删除 C:\Program Files\Common Files\InstallShield\Engine\6\Intel 32这个文件夹中的所有文件，然后重启动电脑，重新运行安装程序或者查看下面的网页：安装程序安装出错解决方法之葵花宝典 moonet（翻译）/develop/article/18/18184.shtm方法三：这是由于一些软件制作的问题导致windows installer不能正常工作恢复步骤如下:1.再次安装windows installer2.0,运行instmsiw.exe如果说"服务已经安装"然后直接退出安装就再跟着做,否则你重装就OK了!2.删除注册表中的[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer]然后运行instmsiw.exe3.绝招:(1) 删除msiserver 服务运行regedit，删除下面的MSIServer 服务[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer]把下面的内容存为unmsiserver.reg 文件，然后双击左键，把它合并进注册表中;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;unmsiserver.regWindows Registry Editor Version 5.00[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;(2) 删除msi 的文件用下面的脚本存为一个unmsi.inf文件，然后在inf文件上右键单击install，就会删除一些msi的dll，这时windows 的 sfc机制可能警告一些系统文件被修改要求插入win2k的光盘，不理睬它。
IMSL在IVF下的安装和配置
安装的时候输入License时输入201111，安装后把源文件中的Crack目录下的License.dat 复制到IMSL的安装目录（默认是C:\\Program Files\VNI)下的License目录下。
然后用记事本打开License,另存为License.lic,保存在同样的目录下。
配置环境：Windows 7 ProfessionalMicrosoft Visual Studio 2008 Professional EnglishIntel。
piler.Professional.v11.1。
060IMSL Fortran Numerical Library Version 6。
0IMSL在IVF中的安装和应用（Windows系统)——------————-—-—————-——-—--———--—-———-—--—--——--——--—1. IMSL在IVF中的安装2。
IMSL在IVF中的调用3. 其它程序库的调用--—-—————--—-—-———-——-———————----——--————————--—--———1. IMSL在IVF中的安装1）如果是IVF pro版本自带的IMSL，直接安装就OK。
可以直接阅读第2部分。
2) 如果是手动安装，IVF与IMSL版本不同,要注意以下问题a) 首先，安装IMSL到缺省目录（不同的版本，目录可能不同）例如，IMSL6.0的安装路径是C:\Program Files\VNI\imsl\fnl600b）如果是在IDE环境下调用IMSL，那么需要首先设置IMSL在IVF中的搜索路径，其设置方法为:设置步骤:（1）打开Microsoft Visual Studio 2008 ;(2) 打开菜单Tools｜options.。
.（3）选择左侧的”Intel（R) Fortran“，再选”Gerneral“或是”compiler“, 然后在右侧找到”Project Directories"或是“compiler Selection".然后在下面你可以看到"Libraries”和"Includes”.点击右侧的”.。
Fortran入门：Windows平台的Fortran编译器安装和使用
Fortran⼊门：Windows平台的Fortran编译器安装和使⽤因为课程需要，今年开始学习FORTRAN语⾔。
之前学校的计算概论⽤的是C，后来⼜学了C++和Python作为⾯向对象的⼯具，数值计算⽅⾯主要通过学校的许可证⽤的MATLAB。
因为专业侧重数值模拟和反演问题，对于FORTRAN这⼀门上古的数值计算语⾔早有⽿闻，在学习Scientific Computing的时候也经常讲到⼀些原本是基于FORTRAN优化的⼦程序和底层设计模块。
上⽹查了⼀下，FORTRAN的社区⾮常少，⽽且可能是因为使⽤者都已经是富有经验的程序设计者，⾃学⼊门的新⼿不多，很多地⽅还是需要⾃⼰摸索，就决定索性在博客上记录⼀下摸索的过程。
FORTRAN，原意为Formula Translation（公式翻译器），是出现很早的⼀门⾼级语⾔。
FORTRAN的主要⾯向科学计算、数值计算，虽然在FORTRAN-2003版本中逐渐引⼊了更加丰富的⾯向对象(Object Oriented)设计思维，但是其主要的功能仍然是数值计算领域；某种意义上，使⽤FORTRAN的⼈⼀般不需要过于复杂的⾯向对象策略，需要使⽤复杂完整的⾯向对象策略的⼈也并不会选择FORTRAN。
最近还发现⾮常⾟酸的⼀点，CNBlogs上的代码插⼊不⽀持Fortran的语法⾼亮，也没有找到⽀持的插件。
⼀. FORTRAN 编译器的安装查了⼀下，⽬前相对常见的Fortran编译器版本是Fortran77或者Fortran90/95，进⼊新世纪的修正版本Fortran2003反⽽⽤的⽐较少。
流⾏的免费FORTRAN编译器实现⽅案包括GCC的GFortran，Intel的Intel Fortran Compiler等。
我这⾥使⽤的是G95，是GFortran对应Fortran95的⼀款编译器。
Windows系统上如果已经安装了MinGW体系（如果你使⽤过gcc的C语⾔或者C++编译器，⼀般都已经装了），那么⼀个.exe ⽂件就可以帮忙搞定安装G95的全部操作！⾮常⽅便！g95 --version然后cmd会返回⼀个G95的版本信息，如下所⽰。
windows f2py 调用fortran 代码
在Windows系统中，你可以使用f2py工具调用Fortran代码。
f2py 是一个Python的Fortran编译工具，可以将Fortran源代码编译为Python可调用的共享库。
以下是在Windows系统中使用f2py调用Fortran代码的基本步骤：
1. 安装Python和NumPy
在使用f2py之前，你需要先安装Python和NumPy。
你可以从Python官网下载并安装Python，然后使用pip安装NumPy。
2. 安装f2py
你可以使用pip安装f2py。
打开命令提示符，输入以下命令：
```shell
pip install numpy-f2py
```
3. 编写Fortran源代码
创建一个Fortran源代码文件（例如：hello.f90），其中包含你想
要调用的Fortran函数或子程序。
4. 使用f2py编译Fortran源代码
打开命令提示符，进入Fortran源代码所在的目录，输入以下命令来编译源代码：
```python
f2py -c -m hello hello.f90
```
这将生成一个名为“hello”的共享库文件（.dll文件）。
5. 在Python中调用Fortran函数
现在你可以在Python中导入生成的共享库文件并调用Fortran函数。
例如：
```python
import hello
hello.say_hello()
```
这将调用Fortran源代码中定义的say_hello函数。
Fortran运行中给出的系统错误及解决方法
. Fortran 运行中给出的系统错误及解决方法以下均为linker tools errors and warningsLinker Tools Error LNK1000unknown error; consult documentation for technical support options Note the circumstances of the error, try to isolate the problem and create a reproducible test case, then contact technical support.Linker Tools Error LNK1101incorrect MSPDBxx.DLL version; recheck installation of this product The version of MSPDBxx.DLL available on your system does not match the version required by this tool.Linker Tools Error LNK1102out of memoryThere was not enough memory for the tool to run. Probably the paging file exceeded available disk space. If a shortage of disk space is not the cause, note the circumstances of the error, try to isolate the problem and create a reproducible test case, then request technical support.Linker Tools Error LNK1103debugging information corrupt; recompile moduleProbably the compilation was terminated before a valid object file was created.Recompile the given object file. If recompiling does not correct the problem,note the circumstances of the error, try to isolate the problem and create a reproducible test case, then consult technical support.Linker Tools Error LNK1104cannot open file "filename"The tool could not open the given file. One of the following may be a cause:l There was not enough disk space.l The file does not exist.l The filename or its path was incorrectly specified.l The specified drive is invalid.l The file does not have the appropriate permissions.l The path for filename expands to more than 260 characters.l If the given file is named LNKn, which is a filename generated by the linker for a temporary file, then the directory specified in the TMP environment variable may not exist, or more than one directory is specified for the TMP environment variable. (Only one directory path should be specified for the TMP environment variable.)l If the error occurs on the executable filename, an earlier version of the executable may still be running. You will need to terminate the executable before linking it. In Windows NT (including Windows 2000) or Windows 95,you can use the utility PVIEW to look for and kill instances of the application.l If the error message occurs for a library name, and you recently ported the .MAK file from a previous Microsoft Visual C++ developmentLinker Tools Messages Page 3 of 37environment, the library may no longer be valid. Ensure that the library still exists in this circumstance.l If the error message occurs for a library name such as CONSOLE.LIB, and you included object modules from an older Fortran developmentenvironment such as Microsoft Fortran PowerStation, recompile all source files with Visual Fortran to create new object files and libraries.Linker Tools Error LNK1105cannot close file "filename"The tool could not close the given file. Possibly there was insufficient disk space available.Linker Tools Error LNK1106invalid file or disk full: cannot seek to locationThe tool could not read or write to location in a memory-mapped file:l Your disk may be too full to complete the link. Free up some space and try the link again.l The error may be a result of trying to link over a network. Some networks do not fully support the memory-mapped files used by the linker. Try linking on your local disk to see if that fixes the problem.l There may be a bad block on your disk. Although the operating system and disk hardware should have detected such an error, you may want to run a disk checking program.Linker Tools Error LNK1107invalid or corrupt file: cannot read at locationThe tool could not read the file. Recreate the file.Linker Tools Error LNK1108cannot write file at locationThe tool could not write to the file. One of the following may be a cause:l There was not enough disk space to create the file.l The drive being written to was not available, possibly due to a network problem.Linker Tools Error LNK1109cannot remove file "filename"LIB could not delete the given file. Before LIB writes the new version of a library, it removes the existing library file. One of the following may be a cause:l The given file does not have the appropriate permissions.l The drive containing the file was not available, possibly due to a network problem.Linker Tools Error LNK1110Linker Tools Messages Page 4 of 37cannot rename file "filename"LIB could not rename the given file. When LIB builds a new version of a library, it creates atemporary file, then renames the file. One of the following may be a cause:l The given file does not have the appropriate permissions.l The drive containing the file was not available, possibly due to a network problem.Linker Tools Error LNK1111invalid /BASE argument "argument"The /BASE option was incorrectly specified. Either no argument was specified or argument is not a number.Linker Tools Error LNK1112module machine type "type1" conflicts with target machine type "type2"The object files specified as input were compiled for different machine types.Linker Tools Error LNK1113invalid machine typeThe machine type specified in the object header is not valid. Probably the file is corrupt. Rebuild the object. See Corrupt Object File for more information.Linker Tools Error LNK1115/MACHINE option requiredLINK or LIB cannot determine the machine type for objects that are provided entirely from libraries. Either specify the /MACHINE option with the appropriate machine type or specify at least one object file in the input.Linker Tools Error LNK1117syntax error in option "option"The given option was not correctly specified.Linker Tools Error LNK1118syntax error in keyword statementThe given module-definition statement was not correctly specified.Linker Tools Error LNK1119invalid ordinal number "argument"The argument following the at sign (@) in an ordinal specification was not avalid number. An ordinal number is an optional argument in either an /EXPORToption in a LINK or LIB command or an EXPORTS statement in a moduledefinitionfile. It is an index into the exports table. The number must be aninteger in the range 1-65535.Linker Tools Error LNK1120number unresolved externalsLinker Tools Messages Page 5 of 37Error LNK1120 gives you a count (number) of unresolved externals for this link.The conditions that cause unresolved externals are described with errorLNK2001 (see Linker Errors LNK2001 to LNK2014), which precedes this error message (once for each unresolved external).Linker Tools Error LNK1121duplicate ordinal number "number"The given ordinal number was specified more than once in either an /EXPORT option in a LINK or LIB command or an EXPORTS statement in a moduledefinition file. Ordinal numbers must be unique integers in the range 1-65535.Linker Tools Error LNK1123failure during conversion to COFF: file invalid or corruptThe object or resource could not be converted to COFF. This tool requires the format of all input files to be COFF. If an input file is not COFF, the tool runs a conversion tool, either CVTOMF (to convert 32-bit OMF objects) or CVTRES (to convert resource files). This error is preceded by errors or warnings from the conversion tool. One of the following may be a cause:l The file is corrupt.l The file is not a valid file type. An example of an invalid type is a 16-bit OMF object.Linker Tools Error LNK1127library is corruptThe library file is corrupt. Rebuild the library.Linker Tools Error LNK1129cannot find resolution for weak extern symbolThe given weak external symbol does not have a default resolution. Probablythe symbol table is corrupt. Rebuild the object file. See Corrupt Object File for more information.Linker Tools Error LNK1130Linker miscalc (base relocations off by number)There was not enough space in the image to write base relocations.Linker Tools Error LNK1131no library file specifiedThe LIB /EXTRACT command required a library as input, but a library filenamewas not specified.Linker Tools Error LNK1132invalid format for MS-DOS stub file "filename"The filename specified with the /STUB option was not a valid real-mode MS-DOS executable (.EXE) file.Linker Tools Messages Page 6 of 37Linker Tools Error LNK1136invalid or corrupt fileThe input file either has a corrupt header or is zero size or abnormally small.See Corrupt Object File for more information.Linker Tools Error LNK1137invalid argument specified with /SECTIONEither the name or the attributes argument to the /SECTION option is specified incorrectly.Linker Tools Error LNK1140too many modules for program database; relink with /PDB:NONEThe project contains more than 4096 modules. One of the following is asolution:l Relink using /PDB:NONE.l Compile some modules without debugging information.l Reduce the number of modules.Linker Tools Error LNK1141failure during build of exports fileLINK could not build the exports (.EXP) file. Causes of this error include system problems such as insufficient memory and syntax errors in options or moduledefinition statements. This error is preceded by another error that givesadditional information.Linker Tools Error LNK1143invalid or corrupt file: no symbol for COMDAT section numberThe object file is corrupt. Rebuild the file. See Corrupt Object File for more information.Linker Tools Error LNK1144error with LINK_REPRO var; cannot open "filename"The linker could not create filename. One of the following may be a cause:l Check that you've set your LINK_REPRO environment variable to anexisting directory and not the current directory.l Make sure there are no read-only files in the directory.l Make sure none of the files in the LINK_REPRO directory are open byanother process, because the linker needs to write to them.Linker Tools Error LNK1145/MERGE created circular link for section "section"You attempted to merge a section into itself. Check the /MERGE options.Linker Tools Error LNK1146Linker Tools Messages Page 7 of 37no argument specified with option "option"The given option requires an argument.Linker Tools Error LNK1147invalid number specified with option "option"The argument to the given option was specified incorrectly.Linker Tools Error LNK1148failure during conversion to COFF: cannot copy temp file filenameEDITBIN could not convert the input file to COFF. When EDITBIN converts a file,it creates a temporary file, then copies the file. One of the following may be a cause: l The given file does not have the appropriate permissions.l There was not enough disk space to create the file.l The drive being written to was not available, possibly due to a network problem.Linker Tools Error LNK1149output filename matches input filename "filename"The output filename specified with the /OUT or /IMPLIB option was the same asan input file.Return to Main Linker Error PageLinker Errors LNK1152 to LNK1189Linker Tools Error LNK1152cannot resolve one or more undecorated symbolsThis error is preceded by one warning LNK4022 for each undecorated symbolthat could not be resolved and by at least two warnings LNK4006 for theduplicate symbols found for the undecorated symbol.Linker Tools Error LNK1153/VXD command-line option requiredYou attempted to build a virtual device driver without the /VXD option. Relinkwith the /VXD option.Linker Tools Error LNK1154specified import library filename matches exports file "filename"The filename specified with LINK /IMPORT or with LIB /DEF /OUT conflicted with the filename given by LINK or LIB to the exports file, which is formed from thebase name of the main output file and the extension .EXP.Linker Tools Error LNK1155special symbol "symbol" already definedLinker Tools Messages Page 8 of 37The given symbol is reserved for use by LINK.Linker Tools Error LNK1156.sbss section not supportedAn object file contained an .sbss section.Linker Tools Error LNK1157fixup overflow; offset of target symbol "symbol" greater than +-8MBThe VXD is too large, or the sections are not arranged properly.Linker Tools Error LNK1158cannot run "filename"The given executable file called by LINK is not in the directory that contains LINK and is not in a directory specified in the PATH environment variable. Linker Tools Error LNK1159no output file specifiedNo name was specified for the main output file (executable file or DLL). LINK derives the default name of the output file from the base name of the first object file. If no object files are specified, and if the /OUT option is not used, this error occurs.Linker Tools Error LNK1160library with zero objects not allowedAn attempt was made to remove an object from a library that contained only that object. The object was not removed.Linker Tools Error LNK1161invalid export specificationEither the /EXPORT option or the EXPORTS module-definition statement incorrectly specified an export. A possible cause is a typing error.Linker Tools Error LNK1162expected aux symbol for comdat section numberThe linker expected to find an auxiliary symbol table for the indicated COMDAT but could not. The object file is probably corrupt. See Corrupt Object File for more information.Linker Tools Error LNK1163invalid selection for comdat section numberThe byte in the object file indicating the type of COMDAT section is invalid. The object file is probably corrupt. See Corrupt Object File for more information. Linker Tools Error LNK1164section section alignment (number) greater than /ALIGN valueThe alignment size for the given section in the object file exceeds the value specified with the /ALIGN option. The /ALIGN value must be a power of 2 and Linker Tools Messages Page 9 of 37must equal or exceed the section alignment given in the object file. Either recompile with a smaller section alignment or increase the /ALIGN value. Linker Tools Error LNK1165link failed because of fixup errorsThe build failed due to fixup errors. The /FORCE or /FORCE:UNRESOLVED option overrides this error.Linker Tools Error LNK1166cannot adjust code at offset=offset, va=valueLINK was unable to pad the code as required. Certain instructions are not allowed to cross page boundaries on some processors. LINK attempts to add pads to correct this situation. In this case, LINK could not work around the problem.Linker Tools Error LNK1167file contains relocs but header has no machine typeA converted COFF object did not have a machine type specified in its header. One cause of this error is omitting a machine type when converting a .RES file in a separate step before linking.Linker Tools Error LNK1168cannot open filename for writingThe given file does not have write permission.Linker Tools Error LNK1169one or more multiply defined symbols foundThe build failed due to multiple definitions of one or more symbols. This error is preceded by error LNK2005. The /FORCE or /FORCE:MULTIPLE option overrides this error.Linker Tools Error LNK1170line in command file contains limit or more charactersThe length of a line in a command file must be less than the given limit.Linker Tools Error LNK1171unable to load filenameThe given DLL was unavailable. The possible locations for the DLL are the current directory, the system directory, the Windows directory, and the directories specified in the PATH environment variable.Linker Tools Error LNK1172more than one object with the name "object" found; rename object(s) orrelink /PDB:NONEA library contained two or more objects with the same name. Do one of the following:Linker Tools Messages Page 10 of 37l Rename the objects using unique names and rebuild the library.l Link using the /PDB:NONE option.Linker Tools Error LNK1173unable to find entrypoint function in filenameThe given function does not exist in the given DLL.Linker Tools Error LNK1174unable to /REBASE filename; not a valid Win32 imageThe format of the given file was invalid.Linker Tools Error LNK1175failed to /REBASE filenameThe rebase operation failed on the given file.Linker Tools Error LNK1177TOC size limit exceededThe linker was unable to create a TOC (Table of Contents) in your image file. The limit is 2048 entries in the TOC.Linker Tools Error LNK1178missing MODEND record; file is invalid or corruptThe linker tool tried to convert an OMF object module to COFF format but could not find an expected MODEND (module end) record in the OMF object. The OMF object module is corrupt and needs to be recreated or recopied. See Corrupt Object File for more information.Linker Tools Error LNK1179invalid or corrupt file: duplicate comdat comdatAn object module contained two or more COMDATs with the same name. One possible cause is if you use the Visual C++ /H option with the Visual C++ /Gy option. The /H option limits the length of external names, and the /Gy option packages functions in COMDATs.Linker Tools Error LNK1180insufficient disk space to complete linkThe linker tool was unable to complete a file operation since the operating system reported that the disk is full. Free up space on your local and network drives (if you are writing files there).Linker Tools Error LNK1181cannot open input file "filename"The linker tool could not find "filename" because it does not exist or the path was not found.Linker Tools Error LNK1182Linker Tools Messages Page 11 of 37cannot have more than 64K exportsYou have reached the linker's limit of 65,536 exports.Linker Tools Error LNK1183invalid or corrupt file: extended relocation count number less than 65535The COFF object file is corrupt since it contains an extended relocation count that is less than 0xFFFF. See Corrupt Object File for more information.Linker Tools Error LNK1184invalid section name "section" specified in option or directive "option"You gave the linker an invalid section name in option. Invalid section names contain "$" or blanks.Linker Tools Error LNK1185invalid section name "section" specifiedYou gave the linker an invalid section name in a .DEF file. Invalid section names contain "$" or blanks.Linker Tools Error LNK1186invalid or corrupt COFF object; reloc to undefined static symbol "symbol"Your COFF object module is corrupt since it contains a relocation entry for an undefined static symbol. See Corrupt Object File for more information.Linker Tools Error LNK1187Corrupt object - unmatched name relocation; ignoredYour object file contains bad relocation information. Recopy or recreate the object file. See Corrupt Object File for more information.Linker Tools Error LNK1188BADFIXUPSECTION:: invalid fixup target "symbol"; possible zero length section This message is issued only for VxD links when the target of a relocation does not have a section. With LINK386 (an older version), an OMF GROUP record (generated by a MASM GROUP directive) may have been used to combine the zero length section with another non-zero length section. COFF format does not support the GROUP directive and zero-length sections. When LINK automatically converts this type of OMF objects to COFF, this error may occur.Linker Tools Error LNK1189LIBTOOMANYMEMBERS:: library limit of number objects exceededThe limit of 65535 objects or members in a library has been exceeded.Return to Main Linker Error PageLinker Errors LNK1190 to LNK1581Linker Tools Error LNK1190Linker Tools Messages Page 12 of 37invalid fixup found, type typeThe object file has become corrupted. Recompile.Linker Tools Error LNK1194cannot delay-load dll name due to import of data symbol symbol name; relink without /DELAYLOAD:dll nameYou cannot delay load a DLL if data is imported from it.Linker Tools Error LNK1195target machine "machine" requires "option"Add the required option.Linker Tools Error LNK1196invalid or corrupt import object: unknown versionThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1197invalid or corrupt import object: unknown typeThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1198invalid or corrupt import object: unknown name typeThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1199invalid or corrupt import object: non-zero reserved fieldsThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1200error reading program database "filename"The given program database (PDB) could not be read, probably because it is corrupted. If filename is the PDB for an object file, recompile the object file; use the /debug:full and /pdbfile options. If filename is the PDB for the main outputfile and this error occurred during an incremental link, delete the PDB and relink.Linker Tools Error LNK1201error writing to program database "filename"; check for insufficient disk space LINK could not write to the program database (PDB) for the output file. One of the following may be a cause:l The file is corrupted. Delete filename and relink.l There was not enough disk space to write to the file.l The drive being written to was not available, possibly due to a network problem.Linker Tools Error LNK1202Linker Tools Messages Page 13 of 37"filename" missing debugging information for referencing moduleThe given program database (PDB) for an object file was invalid. Recompile the object file; use CL's /Zi option.Linker Tools Error LNK1203"filename" missing current debugging information for referencing moduleThe given program database (PDB) for an object file was invalid. Recompile the object file; use CL's /Zi option.Linker Tools Error LNK1204"filename" compiled /Yc /Yu /Z7; cannot create PDB; recompile with /Zi Multilayered program databases (PDBs) are not supported in combination with old-style debugging information. Recompile using CL's /Zi option.Linker Tools Error LNK1206cannot overwrite Visual C++ 1.0 PDB "filename"; delete and rebuildThis version of LINK cannot write to an existing program database (PDB) created using older versions of the visual development environment. Delete filename and rebuild.Linker Tools Error LNK1207incompatible PDB format in "filename"; delete and rebuildThis version of LINK cannot write to the existing program database (PDB). Delete filename and rebuild.Linker Tools Error LNK1209program database "filename" differs from previous link; relink or rebuildThe given program database (PDB) is invalid and possibly corrupt. Relink. If filename is also the PDB for an object file, recompile to recreate the PDB. Linker Tools Error LNK1210insufficient memory for incremental link; relink with /INCREMENTAL:NO There was not enough virtual memory available for LINK to create the incremental status (.ILK) file.Linker Tools Error LNK1211precompiled type information not found; "filename" not linked or overwritten The given object file, compiled with /Yc, either was not specified in the LINK command or was overwritten.Linker Tools Error LNK1212error opening program database; file is in useThe PDB is already in use by another application.Linker Tools Error LNK1213unexpected import object encounteredThe import library has become corrupted. Rebuild the library.Linker Tools Messages Page 14 of 37Linker Tools Error LNK1221a subsystem can't be inferred and must be definedThe linker does not have enough information to infer which subsystem you will target your application. To fix this error, use the /SUBSYSTEM option.Linker Tools Error LNK1561entry point must be definedThe symbol specified by the /ENTRY option is not defined.Linker Tools Error LNK1581corrupted object or old compiler (bad Pcode entry point)Your object file contained a bad entry point. The object file is probably corrupt.。
FORTRAN环境下MPI的安装与运行
注：因为我给的压缩包约400kb，不能作为附件上传，所以在请总版主将其放到此贴中或合适的地方。
请大家等待附件上传到这。
谢谢！或从以下地址下载：ftp://202.115.134.210//incoming/majiaWindows环境下简便的配置MPICH2并行环境很多Windows用户在应用并行环境时，发现对工程的设置非常麻烦，其实这一问题可以容易的解决。
本文将就Compaq Visual Fortran 6.5环境中如何实现MPICH2并行计算做一简单的介绍。
首先，介绍一下MPICH2的安装，MPICH2可以在以下网站免费下载/mpi/mpich2/，我下载的是Win32 IA32平台的安装程序/mpi/mpich2/downloads/mpich2-0.971-2-win32-ia32.msi 。
在Windows下安装此程序即可，其默认安装目录为c:\program files\mpich2。
在此目录下有四个子目录，分别为bin，example，include和lib。
其中bin目录下有两个执行文件，smpd.exe和mpiexec.exe。
在后面将介绍其应用。
在“我的电脑”环境变量设置中将bin目录写入路径path变量，这样就可以在任何地方执行此目录下的文件了（或者，你可以将其copy到工作目录，如果你不闲烦的话）。
其次，设置CVF6.5环境，这一步需要将MPICH2的include和lib目录写进CVF6.5的搜索目录。
其做法请参考设置过程图解cvfdemo.html ,其中需要注意的是将图解中的对应目录换成MPICH2目录下的include和lib。
设置完成后，将本压缩包中mpich2.mod文件拷贝到MPICH2目录下的include子目录下。
Mpich2.mod是我自己编写的一个接口程序，用于简化CVF6.5与MPICH2之间的环境设置，此程序必需放在正确的地方。
最后，介绍如何运行并行程序。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
IMSL Fortran 程序库Windows 版安装与使用说明安装IMSL Fortran数值程序库1. 执行安装程序放入光盘片后，安装程序将会自动执行。
如果您插入光盘片后无法自动启动安装程序，您可于光盘片中直接执行setup.exe 安装程序。
如果您使用Intel Visual Fortran Compiler 8.0 专业版请在光盘IMSL目录下执行setup.exe。
2. 欢迎窗口第一个窗口显示IMSL Fortran数值程序库安装精灵程序。
请点选Next按键以启动安装程序。
3. 授权合约此窗口显示使用者授权合约。
当您阅读完内容并且同意此合约请按Yes继续下一步。
4. 安装系统此窗口允许您选择所需安装的IMSL Frotran 数值程序库于IA-32或Itanium（可复选）后按Next 继续下一步。
5. 安装目录设定IMSL Fortran数值程序库安装目录，预设为C:\Program Files\VNI\CTT5.0。
您可使用Browse按键修改，若该目录不存在，您将被建议建立该目录，同意后按Next继续下一步。
6. 安装进度在安装过程中将会实时更新目前安装进度。
7. 环境变量设定通常设定自动更新IMSL Fortran数值程序库所需环境变量，我们建议您按Yes。
8. 安装完成当安装完成后，您将会被通知，按Finish 结束安装精灵程序。
IMSL Fortran数值程序库授权码设定以下将依照您所选择安装的目的进行，并非所有的步骤都是必须的。
∙Intel Visual Fortran Compiler, 专业版已设定好授权码请直接跳至步骤7。
∙试用版本：请输入试用授权码，依照步骤1 与3 设定。
∙无限使用版：无限制使用者个数授权码，请依照步骤1 至3 设定。
∙个人使用：单机版或网络版授权码，请依照步骤1 至6 设定。
1. 设定环境变量设定LM_LICENSE_FILE 环境变量安装授权档案。
于控制台点选系统开启系统内容在进阶窗口中点点选环境变量按键，在您（您登入系统的名称）的使用者变量点选新增键入LM_LICENSE_FILE 为变量名称，变数值为c:\program files\vni\license\license.dat，（视您安装目录而定）设定完后关闭窗口。
2. 永久授权码的License Key information为取得永久授权码，您必须提供相关的系统信息。
为获得系统信息请开启命令提示字符更改目录至c:\Program Files\VNI\license\bin directory，执行get_hostid_intel.bat。
后会建立一个名为hostinfo.<hostname>的档案，<hostname>即为此计算机名称。
请将hostinfo.<hostname>档案内容email至lmgr@以建立该系统永久授权码。
3. 授权码输入一旦您取得永久授权码或是试用码，其相关信息必须被复制至license.dat 档案。
此档案预设的路径为c:\Program Files\VNI\license\license.dat。
以下为此两种授权码的范例。
一人使用的永久授权码SERVER imslserver 1111abcd 27000DAEMON VNI c: \VNI\license\bin\bin.i386nt\VNI.EXEFEATURE IMSLFPC VNI 5.000 01-jan-00 1 2DF10701D310DD6D039A3 "" 1111abcd试用版本的授权码FEATURE IMSLFPC VNI 5.000 30-jun-2004 0 FCAA4309EE7BFF6EC846 "" DEMO4. 设定授权服务器请按以下步骤设定授权服务器：a) 执行位于c:\Program Files\VNI\license\bin\bin.i386nt\lmtools.exe的程序b) 使用Config Services窗口设定服务名称和lmgrd.exe档案和license.dat与log檔。
c) 您也可以于Server diagnostics窗口的perform diagnostics确认server是否运作正常。
以下图片显示各步骤窗口：5. 启动授权服务器选择Start Server去启动授权服务器。
您也可由此停止服务器或重新读取log檔。
服务器启动后log 档可藉由4b)查看是否运作正常，若伺服有问题请先检查log檔。
6. 检视授权服务器状态为running点选Perform Status Enquiry查询服务器状态。
其它有用的信息：∙如果您在授权码确认时发生错误，您可先使用LMTOOLS的Stop停止、Start启动或Reread 检视log檔。
∙授权管理程序Macrovision FLEXlm 相关信息：∙授权技术支持服务信箱lmgr@使用IMSL Fortran 数值函式库1. 建立范例程序此范例程序将解决以下的线性方程式问题：33x + 16y + 72z = 129-24x - 10y - 57z = -9618x - 11y + 7z = 8.52. 建立新项目启动Visual Studio 并新增Visual Fortran 主控台应用程序项目，命名为fnl。
3. 加入程序代码复制以下程序至fnl.f90原始码档案并储存。
! ================ Program start ==============program fnl! Include the necessary header file:! For the dynamic library:INCLUDE …link_f90_dll.h‟! For the static library:! INCLUDE …link_f90_static.h‟! Declare which IMSL functions will be usedUSE LSARG_INTUSE WRRRN_INT! Declare variablesPARAMETER (LDA=3, N=3)REAL A(LDA,LDA), B(N), X(N)!! Set values for A and B! A = (33.0 16.0 72.0)! (-24.0 -10.0 -57.0)! (18.0 -11.0 7.0)! B = (129.0 -96.0 8.5)!DATA A/33.0, -24.0, 18.0, 16.0, -10.0, -11.0, 72.0, -57.0, 7.0/DATA B/129.0, -96.0, 8.5/!! The main IMSL function call to solve for x in Ax=B.! This is the floating point version, to use double-precision, call DLSARG.!CALL LSARG(A,B,X)!! Now print the solution x using WRRRN, a printing utility!CALL WRRRN('X',X,1,N,1)END PROGRAM fnl ! ================ Program End ==============编译与执行IMSL Fortran数值程序库1. 设定环境变量如果您之前未设定自动设定环境变量，您必需于IMSL Fortran Library安装位置执行cttsetup.bat批次檔。
2a. 自【命令提示字符】中编译为使用【命令提示字符】编译，请开启「开始」-> 「所有程序」-> Intel(R) Software Development Tools -> Intel(R) Fortran Compiler 8.0 -> Build Environment for Fortran applications。
Shared Library> %F90% %F90FLAGS% fnl.f90 %LINK_F90%Dynamic Library> %F90% %F90FLAGS% fnl.f90 %LINK_F90_STATIC%2b. 使用Visual Studio .NET 环境编译在输入以上所程序后，您必须设定项目的属性以便此项目能够发现IMSL Fortran 程序库。
首先于选单Project -> fnl Properties开启Fortran -> General加入以下路径C:\ProgramFiles\VNI\CTT5.0\include\Intel32 至“Additional Include Directories”。
接着于Project -> fnl Properites开启Linker -> General 输入C:\Program Files\VNI\CTT5.0\lib\intel32 至“Additional Library Directories”。
最后编译此项目从窗体Build -> Build Solution。
3a. 自【命令提示字符】中执行> fnl.exeX1 2 31.000 1.500 1.0003b. 自Visual Studio .NET 环境中执行从窗体选择Debug -> Start.X1 2 31.000 1.500 1.000Press any key to continue.您可以从C:\Program Files\VNI\CTT5.0\notes\f90里的txt文件获得更多信息IMSL Fortran 程序库技术支持服务信箱imsl@。