potter
Member
Registered: Feb 2000
Location: SW Virginia
Posts: 290 |
I'm not having this problem, nor am I using Backupbuddy or TimeSync, but I have a theory.
Starting with PalmOS v3.3 several of the time syncing programs crashed during the Hotsync. I appeared that PalmOS v3.3 didn't like a program on the Palm changing the time during the Hotsync. The solution some of the author took was to set an alarm during the Hotsync for a few minutes. When the alarm goes off, the program does not play a sound or puts up a dialog box, it only resets the time appropriately. TimeSync might be doing this, but when it does it is inadvertently turning the device back on.
To test this, can you temporally disable the TimeSync conduit, or remove the TimeSync program from your Visor, and then test again.
Hmm, I said that I did not have this problem. Well while I was writing this message I did the test on my Visor. Well it just did it. I said that I don't use TimeSync, but I do use TimePALm. So maybe TimePALm has the same problem.
Testing ... Hmm, TimePALm's conduit cannot be disabled. Deleting the program. ... Well after waiting a bit, it has not turned itself back on. I think this may be the cause.
Now, why does MarkEagle not see this. Either he is running a different version of TimeSync, or the time drift between his Visor and his Desktop is so small that the TimeSync program does not have to set the time on his Visor. To test this he could change the time on his Visor by a few minutes and then Hotsync.
|