Whooo it is a Leap day.

  • Dave@lemmy.nzM
    link
    fedilink
    arrow-up
    3
    ·
    5 months ago

    Y2K was a real issue, and a one off. I don’t understand how a system that is otherwise functional could break when Feb 29 hit. It’s gotta be either time-related encryption. Or maybe a stupid hard coded value, though I still can’t imagine how that could cause an issue.

      • eagleeyedtiger@lemmy.nz
        link
        fedilink
        English
        arrow-up
        3
        ·
        5 months ago

        About 14 years ago I worked for a company that looked after the POS and pump controllers for a few gas companies. They were outdated even then. Many of them still ran on Win 95 or 98 and used coax cables with old BNC connectors to talk to the pump controller.

        I’d hope they’re a bit more up to date now

        • Dave@lemmy.nzM
          link
          fedilink
          arrow-up
          3
          ·
          5 months ago

          Well the Gregorian calendar was introduced in 1582, so maybe these guys are running an even older version of Windows that predates this change.

          Although the Julian calendar had leap days too so 🤷

      • Dave@lemmy.nzM
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        By using a standard calendar system the same way it handles any dates and times. All the more reason why it’s so confusing how Feb 29 could screw anything up!