- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, my program was written in CVF 6.6 and was compiling/executing OK in WindowsXP. After porting to the latestIntel Visual Fortran/Evaluation Version in Windows 7 32-bit, I can compile the program succesfully, but the executable is not working, the console shows:
The program '[2696] Console1.exe: Native' has exited with code -1073741800 (0xc0000018).
Is it because of the executable is not compatible with Windows 7 32-bit or I have done anything else wrong?
Note: To compile the program, I have to disable /checkbound
The program '[2696] Console1.exe: Native' has exited with code -1073741800 (0xc0000018).
Is it because of the executable is not compatible with Windows 7 32-bit or I have done anything else wrong?
Note: To compile the program, I have to disable /checkbound
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> To compile the program, I have to disable /checkbound
By doing so, you probably tried to put the dirt under the carpet. In other words, instead of fixing a bug that a compile-time check revealed, you converted that bug to a run-time error.
You say that you ported your code from CVF to IFort. What did you do, specifically, and did you take account of the differences in behavior between the two compilers, as described in the article Migrating from CVF ?
By doing so, you probably tried to put the dirt under the carpet. In other words, instead of fixing a bug that a compile-time check revealed, you converted that bug to a run-time error.
You say that you ported your code from CVF to IFort. What did you do, specifically, and did you take account of the differences in behavior between the two compilers, as described in the article Migrating from CVF ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
0xc0000018 == {Conflicting Address Range} The specified address range conflicts with the address space.
This means that the load image is attempting to load (something) outside the bounds available to the application. On 32-bit Widows this is outside a 2GB address range. Note, with a boot option you can extend this to 3GB.
Is your static data + code larger than 2GB?
Jim Dempsey
This means that the load image is attempting to load (something) outside the bounds available to the application. On 32-bit Widows this is outside a 2GB address range. Note, with a boot option you can extend this to 3GB.
Is your static data + code larger than 2GB?
Jim Dempsey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jim
Really appreciate your comments. While compiling in CVF/WinXP theprogram imagewas exceeding the image size but the program executable still runs properly. I have two questions
How to check the image size?
How to extend this to 3GB?
Thanks,
LV
Really appreciate your comments. While compiling in CVF/WinXP theprogram imagewas exceeding the image size but the program executable still runs properly. I have two questions
How to check the image size?
How to extend this to 3GB?
Thanks,
LV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Google: Windows boot 3GB
One link:
http://dwf.blogs.com/beyond_the_paper/2009/04/enabling-3gb-switch-on-windows-vista.html
Note, you may also need to set a compiler/linker option for large address aware.
What this does is give you an extra 1GB.
If you are pushing over 2GB, I would suggest you consider migrating to a 64-bit installation.
Jim Dempsey

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