Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: How to diagnose Cygwin / Windows shutdown problem Date: Thu, 24 Jul 2003 12:32:11 -0700 Lines: 14 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en, zh In-Reply-To: Igor Pechtchanski wrote: > There is such a mechanism on Win2k. I don't think there is one on > Win9x. This thread seems to indicate that there isn't one on WinXP, > either, at least not for shutdown messages. Are you saying that when you click close on a shell window and Windows sends an event (WM_CLOSE I think) Cygwin does catch this but when you do shutdown of Windows then Windows does not send some event to all processes informing them to shutdown? Or are you saying that when you do shutdown of Windows then Windows does send some event to all processes informing them to shutdown but Cygwin for some reason cannot catch this one? Why would Cygwin be able to catch the WM_CLOSE but not the WM_SHUTDOWN? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/