Win32s and Windows NT Timer Differences

Last reviewed: January 3, 1997
Article ID: Q105758

The information in this article applies to:

Microsoft Win32s versions 1.30, 1.30a, and 1.30c

Under Windows NT, timers are system objects; as such, they are not owned by an application. SetTimer() can be called from within one application with a handle to a window that was created by a different application. This application would process the WM_TIMER messages in the window procedure. The timer event will continue to occur even after the application that created the timer has terminated. Note that it is fairly uncommon for a Win32-based application to create a timer for another application, but this method does work.

Because Win32s runs on top of Windows 3.1 and shares many of its characteristics, timers are owned by the application that calls SetTimer(). The timer event terminates when the application that owns the timer terminates.

KBCategory: kbprg kbhowto
KBSubcategory: W32s
Additional reference words: 1.30 1.30a 1.30c

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.