Ready-Event Registration
A version of this page is also available for
4/8/2010
If there is a service that some clients need to wait for, the service can register an event to be created by the OS. When the service is ready, it sets the event to announce its readiness. The clients can then open the event and wait for the service to set it.
The following registry key example shows how to register the event:
[HKEY_LOCAL_MACHINE\System\Events]
<Event Name>:REG_SZ"<Event Description>"
Event Name is the name of the event that is created when the system boots.
Event Description is the description of the event name. This can be a NULL string. The entry to add the event name value is controlled by the Sysgen process.
Predefined OS events names
The following table shows some predefined OS event names.
| Event name | Description |
|---|---|
SYSTEM/GweApiSetReady |
Owned by GWES.dll. This signals that the GDI and USER APIs are registered and ready to be used. |
SYSTEM/BootPhase2 |
Owned by Filesys.exe. This is triggered when the registry has switched from the boot registry to the real system registry. |
| Event name | Description |
|---|---|
SYSTEM/ShellAPIReady |
Owned by Shell32.exe and Telshell.exe on Windows Mobile Classic and Windows Mobile Standard, respectively. This signals that the Shell APIs are registered and ready to be used. |
SYSTEM/ShellInit |
Owned by Shell32.exe and Telshell.exe on Windows Mobile Classic and Windows Mobile Standard, respectively. This signals that the shell window is ready to process messages. |
Although you can define your own event names (for example, OEM/EventX), do not use event names starting with SYSTEM/ because these are reserved. This avoids collisions with event names in current and future versions of the OS.