

Check that the file exists in the specified location and that is compiled for 32-bit systems". \ServoData\DISCON_win32.dll could not be loaded. My major problem is that FAST aborts when I am trying to incorporate the blade controls by using ServoDyn. I have though encounter some problems with the DISCON.dll, similar to those mentioned in previous posts by other users. I am actually focused on the 5 MW NREL wind turbine and using the sample files for this turbine that are contained in the FAST v8 archive.
INTEL VISUAL FORTRAN VERSION 11.1.048 DOWNLOAD WINDOWS
I am analyzing offshore wind turbines for my dissertation using FAST v8 in a 64-bit machine with windows 7. My name is Dimitrios Bilionis and I am a PhD student at the National Technical University of Athens, Greece. These additional settings increased the discon.dll size to over 1000 kb, indicating it has "integrated" something into it With these IVF settings, the recompiled discon.dll worked on my collegues computer that did not have IVF installed. So changing the compiler settings solved the problem If you are using MVS2008: Tools -> Options -> Intel(R) Visual Fortran -> Compilers -> Default options: /Qvc9 /Qlocation,link,"$(VCInstallDir)bin" / libs:dll OR /Qvc9 /Qlocation,link,"$(VCInstallDir)bin" / libs:static (underlining the added options). And if they are missing, discon.dll cannot be loaded. It seems that when IVF compiles the discon.f90 (using default compiler settings) it needs some library files from the IVF installation folder when a FAST simulation is started. This is a systematic pattern, I tested it with 10 collegue computers (XP32 and Win7_64-bit all with no IVF preinstalled). This triggers the popular error message "DISCON.DLL could not be loaded". Running FAST with the recompiled discon.dll works with many different compiler options so I personally don't have any problems with the controller.īUT funny things start happening (or actually nothing happens) when copying the entire simulation folder (contain all FAST model files, FAST.exe and discon.dll) to a new computer WITHOUT IVF preinstalled. On my computer (WinXp32bit) I have installed MVS (Microsoft Visual Studio 2008) and IVF( Intel Visual Fortran) 11.1.054. I have come accross similar "challenges" while compiling the discon.f90 to discon.dll. Here I post a screen shot of my compiling window. If setting up the enviornment variable does not work, why not copy this file to your current directory?

LIBC.lib is in C:\Programme\Intel\Compiler\Fortran\9.1\IA32\Lib.

Path=C:\Programme\Intel\Compiler\Fortran\9.1\Ia32\Bin C:\Programme\Gemeinsame Dateien\Intel\Shared Files\Ia32\Bin C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Bin C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Bin\WinNT C:\Programme\Microsoft Visual Studio 8\Common7\IDE C:\Programme\Microsoft Visual Studio 8\VC\BIN C:\Programme\Microsoft Visual Studio 8\Common7\Tools C:\Programme\Microsoft Visual Studio 8\SDK\v2.0\bin C:\WINDOWS\Microsoft.NET\Framework\v7 C:\Programme\Microsoft Visual Studio 8\VC\VCPackages C:\PROGRA~1\MKSTOO~1\bin C:\PROGRA~1\MKSTOO~1\bin\X11 C:\PROGRA~1\MKSTOO~1\mksnt C:\Programme\Intel\MKL\9.1.027\ia32\bin C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\Programme\Intel\Compiler\Fortran\9.1\IA32\Bin C:\Programme\Intel\Compiler\Fortran\9.1\EM64T\Bin C:\Programme\Intel\IDB\9.1\IA32\Script C:\Programme\Microsoft Visual Studio 8\Common7\IDE It looks strange for your question, I doubt about the system enviornment settings for your intel fotran compiler, here is my PATH variable value: I am the person who compiled FAST, A2AD and DISCON.f90. With 64bit settings on the Win7 machine, I get another error (ifort: error #10037: could not find 'link') but that is not of interest for me, because I want a 32bit dll file. I got these results on both machines, with the 64bit machine set to 32bit build environment variables.

LINK : error LNK2001: unresolved external symbol _load_config_usedĭISCON.dll : fatal error LNK1120: 118 unresolved externals so I guess, that this library is indeed required. LINK : error LNK2001: unresolved external symbol : error LNK2019: unresolved external symbol _memmove ref Libifcore.lib(cvtas_t_to_a.obj) : error LNK2001: unresolved external symbol _fltused Libifcore.lib(cvt_cvtas_s.obj) : error LNK2001: unresolved external symbol _fltused Libifcore.lib(cvt_cvtas_t.obj) : error LNK2001: unresolved external symbol _fltused Libifcore.lib(cvtas_nan_t.obj) : error LNK2001: unresolved external symbol _fltusedĭISCON.obj : error LNK2001: unresolved external symbol _fltused Libifcore.lib(cvtas_a_to_s.obj) : error LNK2001: unresolved external symbol _fltused
