My clock is set to Central Standard Time if I run the game 6:59:59 PM or before it runs fine, running the game at 7:00:00 PM will reproduce the Error 41, this will occur all the way to 11:59:59 PM.
Odd thing is if I go to tomorrows date it starts failing at 12:00:00PM
Edit: I take this back, I cant seem to get the game to work on any future date.
Very interesting, I’m in the US EST so set my date back one day to 8/30/09 same time and it worked. And it did crash right around 8PM local. If 8PM EST is midnight in the UK where cliffski is located then for some reason GSB really doesn’t like September for some reason. lol
I’ve been messing about with a few different times and dates settings and it seems to only work for me during August 2009, any other date and you get either Error 41 or Error 36. Seems to adjust for the time zone you have your system set to so that whatever time you have your system clock and time zone set to it works out if that is in August 2009 according to UTC/GMT and crashes or not accordingly.
I am on Central Standard Time, I set my clock to 6:59:45
I loaded GSB, let the game sit on the main menu for 30 seconds. Click a menu item and it crashed. The error code was different from before but the error log shows something interesting. It jumped ahead several hours when it reported the error message, was expecting to see a time stamp around 7 o’clock PM not midnight. The game seems to have its own internal clock system or something cause the times don’t match at all and this might be causing the game to crash when its trying to write data past that that particular moment in time.
Yup, it’s definitely time related. Ran the game fine this afternoon (or rather, it didn’t crash in this specific way then), but when I got home tonight at 10:49 it began doing the crash on startup. I changed the clock to 12:49, and now it booted up fine.
Guys, I apologise massively. This is all my fault. I’m patching the game now and it (and a whole bunch of other things) will be fixed automatically in a minute. The game should autopatch.
Unfortunately, it can only auto-patch if it can start up to past the initial title screen … where it pointedly does not for me, sadly. Sigh. But, good on ya for trying, mate.
Actually, cunningly it should if it all works manage to autopatch before then. You will find out in about half an hour.
If not, you will be able to redownload the whole (ready-patched) game anyway. This was is just quicker.
Checked just now; it updates properly for me, before the error has even a chance to strike.
Game works, however there was a minor issue with the installer wanting to install it to C:\Program Files, while I got it on D:. Nothing major, but still.