Ready-Event Registration (Windows CE 5.0)
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 will be created when the system boots.
<Event Description> is the description of the event-based name. This can be a NULL string. The entry to add the <Event Name> value is controlled by the Sysgen process.
The following table shows some predefined OS events names.
| Event name | Description |
|---|---|
| SYSTEM/GweApiSetReady | Owned by GWES.exe. 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. |
| SYSTEM/ShellAPIReady | Owned by Explorer.exe. This signals that the Shell APIs are registered and ready to be used. |
Although you can define your own event names, for example, OEM/EventX, do not use event names starting with SYSTEM/ because they are reserved. This will avoid collisions with event names in current and future versions of the OS.
See Also
Determining if an API is Ready | Ready-Event Process
Send Feedback on this topic to the authors