Implementing an Event Tracking Library
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
You can create a new event-tracking library by making a DLL that loads into the kernel. The kernel calls your functions to log events, change zone settings, and query DLL zone settings.
To load your library into the kernel, create an application that calls LoadKernelLibrary with the name of your DLL.
For an example, see the sample program in %_WINCEROOT%\public\common\sdk\samples\CeLog\load. Note that LoadKernelLibrary requires both your event tracking DLL and your load application to be privileged applications. After your application loads your library into the kernel, the application can exit. The event-tracking library remains loaded into the kernel.
In This Section
- CeLog Table Interfaces
Describes the primary interface between the kernel and an event tracking library implementation.
- CeLog IOCTL Interface
Describes the IOCTL interface that your library can use call to communicate with the kernel.
- Registering an Event Tracking Library.
Provides a detailed example of registering an event-tracking library DLL.
- Logging Event Data
Describes how to use CeLog viewing and flushing tools from a custom library.