- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I have a code writen in F77. It was compiled and exicute successfully on my computer. However, I tried to rebuild it and run the exe file (e.g., yin.exe) yesterday. I got an error saying ' yin.exe is not a valid win32 application. This is the build information.
------ Rebuild All started: Project: CheckOriginalSAWS, Configuration: Debug Win32 ------
Deleting intermediate files and output files for project 'CheckOriginalSAWS', configuration 'Debug|Win32'.
Compiling with Intel Fortran Compiler 10.1.019 [IA-32]...
SAWS.FOR
Linking...
Embedding manifest...
Build log written to "file://C:\CheckOriginalSAWS\CheckOriginalSAWS\CheckOriginalSAWS\Debug\BuildLog.htm"
CheckOriginalSAWS - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
I tried a hello wolrd project with for suffix to check my compiler. It works well. I was wondering what happend. I installed g95 in my computer. Can this be the reason? It seems not to me.
I have a code writen in F77. It was compiled and exicute successfully on my computer. However, I tried to rebuild it and run the exe file (e.g., yin.exe) yesterday. I got an error saying ' yin.exe is not a valid win32 application. This is the build information.
------ Rebuild All started: Project: CheckOriginalSAWS, Configuration: Debug Win32 ------
Deleting intermediate files and output files for project 'CheckOriginalSAWS', configuration 'Debug|Win32'.
Compiling with Intel Fortran Compiler 10.1.019 [IA-32]...
SAWS.FOR
Linking...
Embedding manifest...
Build log written to "file://C:\CheckOriginalSAWS\CheckOriginalSAWS\CheckOriginalSAWS\Debug\BuildLog.htm"
CheckOriginalSAWS - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
I tried a hello wolrd project with for suffix to check my compiler. It works well. I was wondering what happend. I installed g95 in my computer. Can this be the reason? It seems not to me.
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Very helpful, thanks.
You have common B07 which contains five arrays that are dimensioned (50000000) and are of type REAL*8 (DOUBLE PRECISION.) Right there you have almost 2GB. There are also other image sections that are large.
What is happening is that the data size of the executable is just too big for 32-bit Windows. You'll have to reduce the constant MDAT to reduce the array size or switch to the Intel 64 architectiure for your system and OS (and compiler.)
You have common B07 which contains five arrays that are dimensioned (50000000) and are of type REAL*8 (DOUBLE PRECISION.) Right there you have almost 2GB. There are also other image sections that are large.
What is happening is that the data size of the executable is just too big for 32-bit Windows. You'll have to reduce the constant MDAT to reduce the array size or switch to the Intel 64 architectiure for your system and OS (and compiler.)
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which version of Windows are you running?
Try this experiment. In Visual Studio, right click on the project and select Properties. Select Linker > Manifest File and change Generate Manifest to No. Also in the Linker properties, change General > Suppress Startup Banner to No. Then do a Rebuild of your solution and see if the problem persists. If it does, please attach the buildog.htm in the Debug or Release folder to a reply (see my signature below for instructions on attaching files).
Try this experiment. In Visual Studio, right click on the project and select Properties. Select Linker > Manifest File and change Generate Manifest to No. Also in the Linker properties, change General > Suppress Startup Banner to No. Then do a Rebuild of your solution and see if the problem persists. If it does, please attach the buildog.htm in the Debug or Release folder to a reply (see my signature below for instructions on attaching files).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
Which version of Windows are you running?
Try this experiment. In Visual Studio, right click on the project and select Properties. Select Linker > Manifest File and change Generate Manifest to No. Also in the Linker properties, change General > Suppress Startup Banner to No. Then do a Rebuild of your solution and see if the problem persists. If it does, please attach the buildog.htm in the Debug or Release folder to a reply (see my signature below for instructions on attaching files).
Try this experiment. In Visual Studio, right click on the project and select Properties. Select Linker > Manifest File and change Generate Manifest to No. Also in the Linker properties, change General > Suppress Startup Banner to No. Then do a Rebuild of your solution and see if the problem persists. If it does, please attach the buildog.htm in the Debug or Release folder to a reply (see my signature below for instructions on attaching files).
XP professional,version 2002,service pack 3.
The build log is attached. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, nothing obvious there. Would you please attach a ZIP of this project, including the EXE that was built?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
Ok, nothing obvious there. Would you please attach a ZIP of this project, including the EXE that was built?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Very helpful, thanks.
You have common B07 which contains five arrays that are dimensioned (50000000) and are of type REAL*8 (DOUBLE PRECISION.) Right there you have almost 2GB. There are also other image sections that are large.
What is happening is that the data size of the executable is just too big for 32-bit Windows. You'll have to reduce the constant MDAT to reduce the array size or switch to the Intel 64 architectiure for your system and OS (and compiler.)
You have common B07 which contains five arrays that are dimensioned (50000000) and are of type REAL*8 (DOUBLE PRECISION.) Right there you have almost 2GB. There are also other image sections that are large.
What is happening is that the data size of the executable is just too big for 32-bit Windows. You'll have to reduce the constant MDAT to reduce the array size or switch to the Intel 64 architectiure for your system and OS (and compiler.)

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page