Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | not@telling.you.invalid (Computer Nerd Kev) |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: Older GPS devices are facing their own mini Y2K bug |
| Date | 2019-04-06 01:57 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <q89132$mk5$1@gioia.aioe.org> (permalink) |
| References | <q88qu0$1tkm$1@gioia.aioe.org> |
Computer Nerd Kev <not@telling.you.invalid> wrote: > > Not hopeful about firmware updates for my Magellan GPS 300, circa > 1999... Actually, besides now insisting that it's the 21st of August 1999 (date of the last epoch), the coordinates still match my map perfectly. Seems it might just affect tamestamps and other clock-related functions. Perhaps the reported location-related problems are due to GPS maps being syncronised with the GPS date (my GPS 300 is unburdened by such complexities). https://www.gps-repeaters.com/blog/gps-week-number-rollover-april-6th-2019/ -- __ __ #_ < |\| |< _#
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Older GPS devices are facing their own mini Y2K bug not@telling.you.invalid (Computer Nerd Kev) - 2019-04-06 00:12 +0000 Re: Older GPS devices are facing their own mini Y2K bug not@telling.you.invalid (Computer Nerd Kev) - 2019-04-06 01:57 +0000 Re: Older GPS devices are facing their own mini Y2K bug Chris J Dixon <chris@cdixon.me.uk> - 2019-04-06 07:05 +0100
csiph-web