Greetings All,
I have been having problems with the notification queue since about two weeks after I purchased my XV6700. There have been several posts from folks that appear to have the exact same issue that I have. Generally the problem occurs when my first notification of the day does not wake up the PPC, it just waits until I hit the power button and then starts blaring.
It is not limited to the system alarm, it also causes any and all notifications to suspend. If multiples are received before you hit the power button then it generally locks up and requires a soft reset and sometimes causes multiple ringings that are tough to clear.
I have tried many things to fix this such as the wakeup tweak, new ROMs, new alarm programs, cleaning the queue, deleting suspect items from the queue, etc... Nothing seemed to work.
I believe that I may have found the culprit though. There are several windows procs that run occasionally, they are clocknot.exe, calnot.exe, repllog.exe, and calupd.exe, and they do various house cleaning chores. I believe that the cause of all of my woes falls on calupd.exe, it somehow corrupts the notification queue and causes my PPC to stay asleep when the next notification is due.
I have proven this by systematically disabling each of the .exe's and causing them not to run at night, which is easier said than done as they are each set by the ROM and cannot actually be removed. BUT they can be changed.
You can effect how often they run by creating a new entry for each and setting the date far into the future, in my case I set them to run on January 1st 2010, the old entry disappears when you enter the new one and keeps it from running. Each entry even survives a soft reset, except for calupd.exe which must be re-created after each reset.
All of my notifications are now ROCK SOLID, I have not had an error for the past two weeks, which is a marathon for my PPC!! The only thing that I am concerned with is the toll for effectively disabling the cleanup procedures. I have not found any ill effect yet, but I have not had them disabled for a great length of time.
My question is: As long as I run my own maintenance now and then to clean up the crap, is there any problem with doing this???
Any insights would be appreciated...
-J