A Fortran test application making use of ClearWin64.dll has been successfully compiled using Intel's fortran build environment (64 bit), especially using ifort for compilation and xilink for linking.

We used the Intel Fortran Compiler ifort, version 11.1, for compilation.
The application (named test1.exe) creates a simple window using winio$ and generates some output logged into a file before and after the winio$ call. It works as expected when executed.

Now, we want to use a newer version of Intel's fortran build environment (64 bit), namely version 14.0.

We successfully created the test application from Fortran source file test1.for for Intel's build environment version 14.0, as well.

However, when starting test1.exe created with version 14.0, the following error occurred:

Unreasonable graphics dimensions - 1718157512 x 1718157512

Both applications make use of module files and object files (here for clrwin$) which have been created version specific, as well, for both compiler versions in question.

We checked that both apps call into the same dll ClearWin64.dll.

Is there any comment on that? Could I bypass the problem by means of an appropriate call using clearwin64.dll?

Dietmar,
When you declare inside your Intel Fortran program some array around 100MB, 200MB or even 1 GB are created EXE files have similar sizes up to 1 GB too? What are standard stack sizes for single array there? Can you allocate say few 20 GB arrays in 64bit Fortran with the RAM less then that amount?

If I use another gFortran so I rebuild the .mod-files.
This is o.K.
But then I want to build the .exe-file I get an error: clearwin64.dll file not recognizes: File format not recognized
If I want to build the .exe-file with the "Salford"-gfortran I get the following logical error (because the .mod-files were not compiled with the same gFortran): Wrong module version '10' (expected '8') for file 'mswin$.mod' opened at (1)
How can I solve this problem?

Thanks to all who helped, especially to Ian: the values 200 in the winio$ call weren't in the right size. The integer size depends on the compiler options which I choose making 200 a 2 byte constant. If I substitute all occurrences of 200 with 200_8 or 200_4 (8 byte constant or 4 byte constant), then the winio$ call works successfully and as expected.

However, I am a little confused about the following: if I introduce variables IW and IH like Ian suggested then the winio$ call works for all types of integer for IW and IH (8, 4 and 2 byte constants).

And I am wondering why the behaviour changed when changing the versions of the intel compile environment.

In 64 bit Fortran, winio$ passes 64 bit integer addresses even for the constant values. What ClearWin+ receives depends on the positioning of the 32 bit integer with respect to the address that is passed.