Anyone had issues with their clocks resetting after the new year? (Not me, but its snowing outside so car has been OFF)

https://tinyurl.com/yckrmb9k

EDIT: The result would be that a clock would display January 1st 2002, 12:00

 

Mine's right, showing 03/01/2022 (yes, I have my date display set that way). I just finished a map update and confirmed that. Side note: This is only the second update I've done. There's no way I'd do it every year.

 

That would take some really, really, stupid programmers to produce that. Not that there aren’t plenty of them around.

I believe I’ve had the F-type display the year 2136, or something like that. I don’t expect to be driving it then.

 

I do!

 

It's not just the programmers that suffer from lapses of intelligence. The standards organizations do some odd things too. I'm not sure what it was that I ran across this (perhaps PID?) where the standard called for signed integers where negative numbers made no sense.

Nevertheless, One would be foolish (or human) to underestimate the power of human stupidity.

 

Are you saying that you are NOT planning on joining us for the 2136 Jaguar F-Type Afterlife Tour? Who’s gonna take pictures if not you?

Marko’s in!

 

True Story: My father worked for Michigan Bell Telephone for 35 years in the database division. Discharged from the Army in '59 and started work with Ma Bell thereafter...so early 60s. Early days of computer mainframes. I recall even in the early 70s (when I was a wee lad) him bringing home aluminum magnetic storage discs (roughly 36" in diameter) that had had "head-crashes" (rendering them completely useless). To buy them new, with total storage capacity of 1 MB, it cost Ma Bell $100K (USD) at that time....1 MB. As soon as there was a head crash, it was worth $0. So he would bring them home and we used them to keep squirrels off our bird feeders. The point of this was that storage was at a PREMIUM in those days, so the phone company looked for every opportunity to "save bits" such as dropping the 19 in the 4-digit year. Which is why there was the whole Y2K concerns. BUT, today, when I can buy 2 TBs of storage for $50 or less, there should be ZERO reason for this same phenomenon to be happening in a $60-$120K auto.

 

OK, sorry to have raised the issue. Our 2014's clock does NOT suffer from the Y2K22 bug...verified.

 

It's just a Microsoft thing, I think. I recall som eyears ago when the clocks went back a colleague was working (very) late and his clock went back an hour every time it got to 2am! The third time it did it he shut down and went to bed.