@spud11 Oh! We just replied at the same time. :)
The problem can be easily fixed in reicast (I think), when you start reicast, it has to update the date in the emu.cfg before doing anything else, it has to be the first task it does. Because currently, it just reads the date in the emu.cfg and starts from it while you're playing, then when you exit the game, it saves the date into emu.cfg. But the clock in reicast is never updated with your system and is only "alive" when you play a game. So for instance, if it was 1:30 pm on January 10th the last time you exit a game, and if you don't play for 3 months, the next time you will launch a game, the date will be 3 months late. And if you play for 30 minutes, when you will exit the game, the clock will be 2 pm on January 10th (3 months late). And it seems that when the offset is bigger than about a month, it asks you to update the date.
It's why I wrote this little script to do this task automatically. Some people maybe tried the script that I provided months ago in this thread, but this one wasn't working anymore because of a technical issue with every 32 bit system (too complicated to explain here), but this new script is smaller and doesn't have this issue.
Edit: I want to add that if you don't have an RTC battery or an internet connection, it doesn't matter, the time won't be right with the real time of course, but at least the time between your system and reicast will be perfectly in-sync and so it shouldn't ask to update the date and time anymore.
