>George:
>
>Thanks for your comments.
>
>>
>>Carlos,
>>
>>System Modal is a leftover from Win16. It doesn't exist in Win32.
>
>You mean in the sense that it will not let you interact with any window of any application running? (I think that was the behavior in Win16)
>
>Because it shure still exists in Win32, maybe with a different behavior, as it says on MSDN of the MessageBox API Function uType parameter:
>
>MB_SYSTEMMODAL
>Same as MB_APPLMODAL except that the message box has the WS_EX_TOPMOST style. Use system-modal message boxes to notify the user of serious, potentially damaging errors that require immediate attention (for example, running out of memory). This flag has no effect on the user's ability to interact with windows other than those associated with hWnd.
>
>And its not documented in the help for Messagebox in VFP9, but try typing in the command window:
>
>

>?messagebox("text",
>

>
>and see Intellisense kicking in and showing you the 4096 parameter: "4096 - System modal (use with timeout parameter)"
>
>So you are right, System Modal Win16 behavior is gone, but its still there in Win32 with a different meaning: It just shows the MessageBox on Top of all the app windows in the system.
>
>And by the way, that blank icon shows up also when using the MessageBox API Function, so its not a FOX problem.
>
Carlos,

Nope, it isn't a Fox problem. The reason that this comes into being is that Win16 and Win32 are totally different multi-tasking operating systems.

Win16 is co-operative. Basically, the means that whatever window has the focus gets the bulk of the processor time.

Win32 is pre-emptive. Each open application gets just so much of the CPU's cycles. This is about 50 milliseconds.