🚀 go-pugleaf

> If I remember correctly, I think 2K/XP has a timeout period for that
> message.  If you do not return control back to the OS in a timely fashion,
> the OS moves on anyway and assumes your application stopped responding.
Try
> utilizing the WM_QUERYENDSESSION message as well, do some of your cleanup
> work there as well, so that WM_ENDSESSION has less work to do and can
return
> back to the OS faster.

That seems not to be entirely correct.
If the timeout is reached Windows displays a messagescreen where you are
informed
that the app in question is not responding and you are asked to cancel it.
But this
message is not displayed in my app. If I put a Sleep(10000) as first
statement
in the WM_ENDSESSION eventhandler I get this messagescreen. If I remove this
line
I get nothing and the app is terminated quite fast but the last statements
in the
WM_ENDSESSION event handler are not reached. It also does not explain why
all works correct if the app is not hidden. It seems that one of the actions
I perform
directly or indirectly in the event handler makes Windows immediately
interrupt it.

It is getting even better. As shutdown is difficult to debug I put a fopen,
sprintf, fclose
sequence after every action I perform in the event handler to find out where
the
handler is getting interrupted. With these lines inside the message handler
it is no longer
interrupted by Windows. If I remove these lines the problem comes back.

IMHO the whole Windows shutdown process was allways full of quirks, badly
designed
or at least badly dokumented. Just my 2 cents.

Everybody who has comments or experiences with Windows shutdown is
kindly invited to this discussion.

Thank's.
Regards,
Frank.