From the manual:
Don’t know how this squares with the actual controls on your car.
So? He’s said that he has corrected it before; it’s just damn funny (especially when it rolled right past 31).
Sounds like a bounds error of some kind. The leap year code must erroneously bypass the constraints entirely rather than just allowing an extra day.
The code probably tells it to rollover on midnight 2/28 but not on leap year, but then doesn’t have any constraint beyond that.
I’ll put my money on it running up to Feb 99 and then rolling over to Feb 00.
I’m subscribing to this thread. I know I don’t have to post to do that, but I wanted to announce it. I hardly ever subscribe to any threads, but this one is interesting and likely won’t be finished for a while.
FEB 40 and counting…
Wow, and I thought my Dodge Durango that would go from 3:59 to 3:60, then about 3 seconds later to 4:00 was cool.
I reckon it’s got some mis-ordered or mis-nested conditional checks in the code - which probably means it has no way to get out of February in a leap year. That means one of a few things could happen:
It might count up to 99, then click back to Feb 01 (maybe 00) - and continue doing this until the end of the year.
If the date number is a single byte value, it might continue incrementing it until it gets to Feb 255, then back to Feb 00 or Feb 01 - except that it probably can’t express anything beyond Feb 99 on the display, so it might display nonsense, or nothing, or some kind of truncation (i.e. displaying 01 to 09 instead of 101 to 109, or displaying 10 for the whole of that range)
I’d be really interested to hear from someone with experience of programming devices like this - would I be right in assuming it’s got a microcontroller in there? Is it possible to actually write a program with unhandled exceptions that crashes one of these devices, or will it keep on churning through instructions no matter what?
Has it been going through to 31 on months that have only 30 days?
At that point it will tear a hole in the time/space continuum and nobody can say what happens then.
Just keep it below 88 MPH!
You car is just trying to give Black History Month the support it deserves.
“Shortest month of the year? Fuck that!”
It’s still February…for extremely large values of February. 
If they were being really efficient with their bits it might roll over at Feb 64 (63 even?). Though given it didn’t roll over at 32 means it probably won’t at 64.
Reminds me of one of my lazy habits. I put stuff in the microwave and almost allways put in something for like 66 seconds, 99 seconds, 2:22, 3:33, 9:99 minutes and so on. So my microwave allows seconds that should not be allowed to exist under human laws.
Update: It’s FEB 61, and that’s no joke.
So May 8th is when it’s gonna presumably read “Feb 99”, yeah? That means May 9th is the day to really watch for on this thread… (Sets Google Calendar reminder)
I wonder — is there any apocalyptic sect/myth/legend that sets 5/10/2012 as the date for The End™? If so, the clock in the Shoelessmobile may be trying to tell us something.
I think Feb 99 is when this happens, except to the OP’s car instead (link safe for work but kinda loud).
Hint to OP. Pack some extra food and water.
By my back of the napkin calculations, today is Feb 99, 2012:
29 days in Feb
31 days in Mar (to Feb 60, as it were)
30 days in April (to Feb 90, as it were)
so May 9th = Feb 99.
So how’s it looking on that 2003 Hyundai Santa Fe today, Shoeless? And needless to say, please do tell us what it shows tomorrow morning!!
So the world ends tomorrow?
It does indeed say FEB 99 today. I checked this morning before I left for work. I haven’t actually driven the car since the weekend because the weather has been so nice I’ve been taking the bike to work. I’ll check it again tomorrow and let y’all know what happens.