Year 2038 problem

#1

Post by turingspiritfly » Sat, Aug 25, 2018, 3:44 AM UTC

Year 2038 problem
en.wikipedia.org

Re: Year 2038 problem

#2

Post by FullyFunctional » Sat, Aug 25, 2018, 7:20 AM UTC

Museums and old-computer enthusiasts will feel the pain of this; most modern systems have long moved on to 64-bit.

Re: Year 2038 problem

#3

Post by supergirl » Sat, Aug 25, 2018, 2:24 PM UTC

FullyFunctional wrote: post #2

Museums and old-computer enthusiasts will feel the pain of this; most modern systems have long moved on to 64-bit.

a lot of software uses 32 bit integers to store dates so it doesn’t matter on what cpu it runs

Re: Year 2038 problem

#4

Post by perl4ever » Sat, Aug 25, 2018, 4:39 PM UTC

From the linked Deep Impact space probe page:

The spacecraft was lost and: "the most probable reason of software malfunction was a Y2K-like problem. August 11, 2013, 00:38:49, was 2^32 of one-tenth seconds from January 1, 2000, leading to speculation that a system on the craft tracked time in one-tenth second increments since January 1, 2000, and stored it in a signed 32-bit integer, which then overflowed at this time, similar to the Year 2038 problem"

Re: Year 2038 problem

#5

Post by pasbesoin » Sat, Aug 25, 2018, 8:39 PM UTC

I remember Y2K (there was a weekend lost), and that 38 seemed a fair length of time away.

We're almost halfway there, now.

"Objects in mirror are closer than they appear."

(Context/origin of the phrase: https://en.wikipedia.org/wiki/Objects_in_mirror_are_closer_t... )