Ready-Event Process (Windows CE 5.0)
The ready-event process consists of modules that expose a ready-event and threads that wait for a ready-event.
Modules that expose a ready-event
When Filesys.exe starts, events are created as soon as the registry is initialized. If the RAM-based registry is in use, the events are created before any applications or drivers are started. If the hive-based registry is in use, the events from the boot hive are created before any applications or drivers are started. Then, when the system hive is loaded, the events from the system hive are created. For more information, see RAM-Based Registry Initialization and Hive-Based Registry Initialization.
When the module that added the event data is run, it calls OpenEvent to open and set the event. Any waiting thread is released. The event remains active for the life of the OS.
Threads that wait for a ready-event
When modules start, they will first try to call OpenEvent for the API sets to which they are related. If OpenEvent fails, the API set was never, and will never be, registered. If OpenEvent succeeds, the module can call the WaitForSingleObject function to wait for the API set to be registered. This eliminates polling and lets a module know whether an API set will be registered.
See Also
Determining if an API is Ready | Ready-Event Registration
Send Feedback on this topic to the authors