Granted this is not an every day occurance, but I was trying out a utility's boot CD (not an Acronis product), which has the gall to change the BIOS time and date without warning. When I rebooted back into Windows, the time and date were actually 9 hours in advance (so 5pm 31/10/2008 here, and the BIOS was now 2am 1/11/2008 ), this confused the TI scheduler, which tried to run a task with the following results. It failed with an error message that the path and disks could not be found, and updated the logs and tasks to tomorrows date. Now the interesting thing is, I do not have the run if missed option enabled on any of my tasks, as it causes a major problem in my view if an image is restored and one forgets to detach the external image drive on reboot - bung go all your nice images. So why would the scheduler think it ought to run because at boot time the date was out of wack? It's taken me a little while to eradicate the all the TI files that seem to track the date, so it'll be interesting to see if it runs the schedule at 7:13pm tonight as it is supposed to. Colin OH Yes and Acronis, I still have had no acknowledgement of my two ticket requests.