There might be some interesting things in the industry going on in the moment that it wraps, like programmers forgetting to mask on a carry or subtracting time without expecting it to go "backward". I'd be surprised if any Oregon-class device totally "broke". Time wraparounds and overflow and underflow are things that programmers just tend to handle poorly because they're hard. We've definitely seen GPSes handling things like this badly in the past and I'm sure we'll see devices failing in some way this time, too. Somehow he connected the amount it was wrong to the 10-bit week overflow next year but it's entirely possible that it's numerology and his GPS is just slightly broken. Even after a factory reset, it remained stuck a few decades in the future.
GARMIN NUVI 255W UPDATE FILE CORRUPTED SERIAL
He was able to find a very similar failure on a Legend (an even older serial model) that had a similar weird stuck time, but it was stuck at the first rollover in '99. This meant his unit was reporting a time that was after the "4.2 billion microseconds since " epoch rollover time in 2038 so he was getting on overflow when he ran a 32-bit OS, but a different (still wrong) behavior on a 64-bit build of the same OS.
On the GPSBabel list a week or two ago, we had someone with an older model Garmin seeing a failure that realized he was N weeks before the rollover and his unit was reporting that it was N weeks after the rollover, but resulting in it being 19.7 years off.
0 kommentar(er)
