Posted by Mike Saunders on May 14, 2007 at 12:26:51:
During the development of our Comet Scripting application I have observed that the WAKEUP command works in a way I was not expecting.
During testing of the application, I was adjusting the PC time.
(I realize that adjusting this time would not normally be done.)
It appears that COMET has a internal clock that WAKEUP uses and is "initialzed" only when the comet session is started.
Changing the PC time after the Comet session starts causes the TIME$ value to be different from the WAKEUP time. TIME$ will reflect the current PC time, but WAKEUP will still be ticking on the original PC time.
The Comet session has to be restarted for WAKEUP to adjust to the new PC time.
(yes I am doing a DSTAT(CL1) before getting TIME$)