forrtl: severe (38): error during write, unit 6, file CONOUT$

[ronghewang]

When I updated to "Intel Visual Fortran Compiler Integration for Microsoft Visual Studio* 2005, V11.0.074", I always get "forrtl: severe (38): error during write, unit 6, file CONOUT..." when call STOP. How can I hide this error message?

[Steven_L_Intel1]

What project type is this? (Console, DLL, Windowing, etc.)?

Why did you pick that specific version? I suggest 11.1.038 or 11.0.075.

[ronghewang]

Quoting - Steve Lionel (Intel)

What project type is this? (Console, DLL, Windowing, etc.)?

Why did you pick that specific version? I suggest 11.1.038 or 11.0.075.

Console.

I will try 11.0.075, and let you know the result.

Thanks Steve.

[ronghewang]

It still happens in V11.1.038.

After I checked the configure settings, the problem is on:
AdditionalOptions="/fpscomp " FPS4IOFormat="true" FPS4LDIOSpacing="true" FPS4Logicals="true" FPS4General="true"

If I removed the compatibility settings, the RTE is gone, but the results are not expected. How can I do now?

If you want to test, I created a simple windows application, the winmain.f90 is like:

integer(4) function WinMain( hInstance, hPrevInstance, lpCmdLine, nCmdShow )
!MS$ ATTRIBUTES STDCALL, ALIAS : '_WinMain@16' :: WinMain
stop 0
WinMain = 0
return
end

When run to "stop 0", you will get the problem.

[Steven_L_Intel1]

I can reproduce this - it was the 0 argument to STOP that was the key. I didn't need any of the /fpscomp options to see this. Our issue ID is DPD200139029.

I suggest you remove the "0" from the STOP - and really, in a windowing application, STOP is rather "rude", though I suppose it works.

[ronghewang]

You are right. If I removed the 0, it works for the normal condition. But it does not work for other abnormal conditions, such as stop the program by data validations.

After I did further test, if use (/fpscomp:general), then it works. If does not ues (/fpscomp:general), it does not work. If I still need "STOP errorcode", any further suggestions?

Thanks,

[ronghewang]

Quoting - Steve Lionel (Intel)

I can reproduce this - it was the 0 argument to STOP that was the key. I didn't need any of the /fpscomp options to see this. Our issue ID is DPD200139029.

I suggest you remove the "0" from the STOP - and really, in a windowing application, STOP is rather "rude", though I suppose it works.

How can I get DPD200139029?
Thanks.

[Steven_L_Intel1]

It's not something you get - this is the tracking identification of the problem report I filed with development. When a fix is available, I'll post a reply here.

[Steven_L_Intel1]

This problem is corrected by 11.1 Update 3, available now.

[qing_chen63a]

Hi Steve,

By using 11.1 update 3, I still got this problem. Attached please find two VS projects. The first (named pscreen) creates a DLL containing a write-to-screen function, and copies the DLL to the relevant directory in the second project (multiwin), where the function is called. If you build the DLL first, and then the simple
windows application program and run it, you will get the error as shown in the attached snapshot.

Any good suggestions?

Thank you in advance!

Qing

[Steven_L_Intel1]

I tried this with Update 3 and did not see an error.