CheckNotifications updated

[bkbroil]

Update (15 Jan 2004): Version 1.9 of CheckNotifications has the following improvements:
Re-wrote portions of the code to help avoid the continous spinning hourglass issue. This was caused by possible out-of-memory conditions, which is hopefully corrected now. Also added more memory error checking messages.
Added a progress window that will be displayed when the program reads events from the system, clears them, or writes them to a log file. This will give a better indication if the program is actually working or if it is hung up.
Corrected some issues with removing duplicate events from the system.
Added a "Refresh" button to the menu bar to refresh the events on the screen.
Overview:
The Pocket PC 2003 OS appears to have a bug that can slow down the performance of a Pocket PC device, and can potentially cause ActiveSync delays. It has been identified that after every soft-reset of your device, a few extra "Notification Events" are added to the Notification Event Database on your system (This database holds system notifications such as alarms, timed events, etc.). After several soft-resets, a device can have several hundreds of extra notification events that can reduce the performance of a device.
The offending notifications are labeled "SSTimeChange" and "conmgr.exe". Since we do a lot of soft-resetting when we develop our software, we discovered one of our 2003 devices to have over 600 notification events (when it typically has less than 50!).
CheckNotifications will remove these notification events, as well as the "IA_Caller_ID.exe" events from the Notification Event Database that seem to be duplicated on the Pocket PC phone-based devices. Only those events associated with the "RunAppAfterRestore" event status will be removed.

[Addic]

Is that only applicable to Windows mobile 2003 or does it also involve PocketPC 2002/2000?
Just thought I'd better check. :?

[Brad Isaac]

Just WM 2003 is affected by the notification bug.

[Addic]

Hokey! Ta for the super rapid response......... shame most developers aren't that quick