Share via


OSCapture.exe

Other versions of this page are also available for the following:

Windows Mobile Not SupportedWindows Embedded CE Supported

8/27/2008

When enabled, both CeLogFlush.exe and OSCapture.exe execute constantly. However, these two flushing applications differ significantly in the way they handle flushed data.

When CeLogFlush.exe runs, it flushes data to a file automatically.

In contrast, when OSCapture.exe runs, it keeps the data buffered in RAM. OSCapture writes data to a file only on command. OSCapture buffers a specifically limited amount of CeLog data on a device.

OSCapture does not write buffered data to a log file until you issue a command for that to happen. When you trigger OSCapture with a command, it copies the buffered data to a file. OSCapture stores a specified amount of the most recent data that was collected by the event tracking subsystem. When you trigger OSCapture with a command, it copies the buffered data to a file.

For example, if you specify a flush timeout of 2 seconds, and specify 10 saved flushes, then OSCapture maintains the most recent 20 seconds of activity in the CeLog RAM buffer. When you trigger OSCapture, it stores that 20 seconds of activity in a log file.

In This Section