Supporting Notifications in Your OS Design (Windows Embedded CE 6.0)
1/6/2010
The notification subsystem in Windows Embedded CE consists of two parts: a base notification engine and a notification UI. The base notification engine manages all of the notifications that are registered on the system and triggers notifications when an event occurs. The notification UI communicates notification events to a user and handles these notifications. To include the notification UI, choose either the Notifmin component for target devices with no UI, or the Notifpub component for target devices that can present a UI.
If you want application developers to be able to use notifications in the applications they create for your OS design, you must provide notification support in your OS design.
To support notifications in your OS design
Include the base notification engine in your OS design.
Include, and optionally modify, your notification UI.
Ensure that the interface between the base notification engine and your notification UI functions properly.
Executing the notification subsystem in your OS design
The notification subsystem may execute in device.exe or in services.exe.
If it is executed in device.exe, the notifications may be stopped and started programmatically by issuing IOCTL_SERVICE_START or IOCTL_SERVICE_STOP using the DeviceIoControl interface.
If it is executed in services.exe, the notifications can be stopped and started with standard services.exe interfaces, both programmatically and from the command line. In addition, services.exe enables loading and unloading the Notify module dynamically.