Article ID: 106385 - View products that this article applies to.
This article was previously published under Q106385
The entry point of both 16-bit (Win16) and 32-bit (Win32) Windows applications is documented as follows:
However, under Win32, hPrevInstance is documented to always be NULL. The reason is that each application runs in its own address space and may have the same ID as another application.
To determine whether another instance of the application is running, use a named mutex. If opening the mutex fails, then there are no other instances of the application running. FindWindow() can be used with the class and window name. However, note that a second instance of the application could be started, and could execute the FindWindow() call before the first instance has created its window. Use a named object to ensure that this does not happen.
The fact that hPrevInstance is set to NULL simplifies porting Win16 applications. Most 16-bit Windows-based applications contain the following logic:
Under Win16, window classes only are registered by the first instance of an application. Consequently, if hPrevInstance is not NULL, then the window classes have already been registered and InitApplication() is not called.
Under Win32, because hPrevInstance is always NULL, InitApplication() is always called, and each instance of an application will correctly register its window classes.