OAL Elements for Error Reporting (Windows CE 5.0)

Windows CE 5.0
Send Feedback

OEMs can use programming elements in the OEM Adaptation Layer (OAL) to enable Error Reporting, and to customize Error Reporting functionality.

By default, Error Reporting will create a dump file using reserved memory. The amount of reserved memory to be used is set by dwNKDrWatsonSize.

There are also a number of APIs that are used to access the reserved memory. The reserved memory is in RAM, and will not persist if the device is turned off.

To implement the Error Reporting dump in real persistent storage, which can persist the Error Reporting dump file even after a complete power loss, OEMs can override certain function pointers to OEM-specific Error Reporting support functions.

The following table shows function pointers and OS APIs that can be used by OEMs. These function pointers call the default implementation each associated API.

The function pointers can be overridden to point to new OEM functions that implement OEM-specific persistent storage for dump files. In this case, the OEM functions must not make use of any system APIs, because using these APIs in this way may make the system hang.

If the OEM chooses to override these functions, they should not set dwNKDrWatsonSize; dwNKDrWatsonSize reserves RAM only for the default implementation of these functions.

Function pointerOS APIDescription
pfnNKDrWatsonFlush DrWatsonFlushFlushes the Error Reporting dump data to the underlining storage.
pfnNKDrWatsonClear DrWatsonClearClears the Error Reporting dump storage by zeroing the whole Windows CE Error Reporting dump area.
pfnNKDrWatsonRead DrWatsonReadDataReads data from the Error Reporting dump area.
pfnNKDrWatsonWrite DrWatsonWriteDataWrites data to the Error Reporting dump area.
noneDrWatsonGetSizeRetrieves the size of the dump area.

See Also

Developing an OEM Adaptation Layer

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.