schedule firing at wrong time PM not AM

[dianeoforegon]

I have SuperDuper and some iCal events scheduled for 3AM, but they are
firing at 3PM. I've checked System Preferences date & time and everything
shows as correct. Is there some cron file that could be corrupt?

[dnanian]

Not if both are going wrong: iCal doesn't use cron.

[tsebsietxis]

I have exactly the same problem - seems to be a limitation of iCal - it only does it when the system is set to 12hour time - if it is set to 24hour time all seems to work fine. I find the 24hour time so hard to understand!

[shg]

I have my Leopard box set to 24-hr time, and SD is still running my evening backups in the morning, 12 hours from when it should.

[dnanian]

Make sure your locale is also somewhere that uses 24-hour time...

[dianeoforegon]

My problem involved two sources.

My iCal events times had been reset. Reset them and they work.

Then had to figure out why SuperDuper was misfiring. Finally tracked it down to my Schedule for Sleep. The schedule reverted to an old schedule where it put the computer to sleep not giving SuperDuper time to complete. I unchecked it and now SuperDuper puts the computer to sleep as directed.

All of this happened after applying the Combo updater.