Has anyone run into the problem where the start times for scripts that repeat do not reset correctly after a reboot? I am running on W2000 using ver 7.2.043 ( I thought upgrading to latest version may resolve the problem, but it didn't). I did find a work-around. If you right-click on the MacroSched Icon and take 'Quit' option prior to rebooting, the times are set correctly.
I'd like to find a solution so quitting MS is not necessary. I did verify before rebooting on Saturday that the script times had already reset to the proper time of 00:15 for Monday. The script in question runs M-F 00:15 to 23:30 repeating every 8 min. After reboot the time is 14:00 or something odd.
Has anyone else seen this or know what may be causing this?
Script Start times after reboot
Moderators: Dorian (MJT support), JRL
Script Start times after reboot
Bill Ault
Cargill Investor Services, Inc.
Chicago, IL
312-460-4000
Cargill Investor Services, Inc.
Chicago, IL
312-460-4000
-
Guest
Hi Armstrong,
The reboot was not affected. More so it was how macro-scheduler was affected by the reboot. Script times do not reset the the correrct start times. I've mentioned this to mjtnet but have not received a reply. However, if you 'quit' macro-scheduler first before you reboot, then the script start times are ok.
Bill
The reboot was not affected. More so it was how macro-scheduler was affected by the reboot. Script times do not reset the the correrct start times. I've mentioned this to mjtnet but have not received a reply. However, if you 'quit' macro-scheduler first before you reboot, then the script start times are ok.
Bill
Bill,
You didn't reveal much detail about your setup. On a notebook used primarily for software (beta) testing, Macro Scheduler invokes reboot every 60 minutes, 24 hours a day, 7 days a week, without a single glitch. Bear in mind, the said notebook running the Macro Scheduler script is located in a hot and humid environment (no air conditioning). The script almost almost acts like a clock. Whenever the notebook reboots, I know it's exactly one, two, three,... o'clock. Given such actual observation, Macro Scheduler does not seem to be affected by reboot.
No, I didn't quit Macro Scheduler either manually or automatically. Macro Scheduler always reboots at exactly the next hour.
My sys config:
Macro Scheduler version: 7.2.043
Win 98 se
You didn't reveal much detail about your setup. On a notebook used primarily for software (beta) testing, Macro Scheduler invokes reboot every 60 minutes, 24 hours a day, 7 days a week, without a single glitch. Bear in mind, the said notebook running the Macro Scheduler script is located in a hot and humid environment (no air conditioning). The script almost almost acts like a clock. Whenever the notebook reboots, I know it's exactly one, two, three,... o'clock. Given such actual observation, Macro Scheduler does not seem to be affected by reboot.
No, I didn't quit Macro Scheduler either manually or automatically. Macro Scheduler always reboots at exactly the next hour.
My sys config:
Macro Scheduler version: 7.2.043
Win 98 se
