1. Forum
  2. MicroNet
  3. MIN TEST

  • Re: Patch

    From digimaus@618:618/1 to Deon George on Mon Sep 9 00:53:14 2024
    Is this Y2K stuff would fix Shawn's messages with a 2060 timestamp?

    I think so but I know very little about it.

    If so, do you have more details, I'd like to include that processing in clrghouz, since there are a bunch of messages data Oct 2060.

    I found this:

    Fido Year 2000 Tools Rel. 6 by Tobias Ernst ===========================================
    PKTDATE 1.5 is a program that can analyse
    PKT files for structural errors that result
    from year 2000 related bugs in the creating
    software and automatically fix such broken
    PKT files. It is intended for use at hub
    level in the Fidonet distribution structure
    in order to alleviate the effects of the
    year 2000 problem on the smooth operation
    of Fidonet. Also included are a general
    information text on the year 2000 problem
    in Fidonet, and tools for analysing MSG,
    JAM and Squish message base files.
    Includes OS/2, Win32, DOS, Linux and Amiga
    binaries and source. Unzip with -d option!

    It is Y2KTOOL6.ZIP at http://archives.thebbs.org/ra53a.htm.

    However, it only fixes inbound packets. It won't fix outbound packets.

    -- Sean




    --- MBSE BBS v1.1.0 (Linux-x86_64)
    * Origin: Outpost BBS * Johnson City, TN (618:618/1)
  • From Deon George@618:510/2 to digimaus on Fri Sep 13 09:16:08 2024
    Re: Re: Patch
    By: digimaus to Deon George on Mon Sep 09 2024 12:53 am

    Howdy,

    Is this Y2K stuff would fix Shawn's messages with a 2060 timestamp?

    I think so but I know very little about it.
    I found this:

    Fido Year 2000 Tools Rel. 6 by Tobias Ernst

    Oh, I was actually wanting to find out more detail about how the 2060 date is made or fixed, so that I could reverse it and put it back to what it should be. Does MBSE do it automatically?

    I havent spent any time on it, so dont know if I need to convert it back to epoch seconds and kill off a bit or two, or if there is some other formula.

    A first glance 2060 is 60 years ahead of 2000, but we are not 60 years ahead of 1970 (so its not that simple). I also figured that its more than that, because the month doesnt add up, unless it is also because (from memory?), months start from zero in packed messages and hence why his dates were october.

    My initial plan was to update clrghouz to reject any messages more an "x" days from the current date (and send a netmail to the sender), but if I can fix predicatable bad ones first, I'd prefer to do that.


    ...oEoN
    --- SBBSecho 3.20-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (618:510/2)
  • From Sean Dennis@618:618/1 to Deon George on Thu Sep 12 22:07:52 2024

    Hello Deon!

    13 Sep 24 09:16, you wrote to digimaus:

    Oh, I was actually wanting to find out more detail about how the 2060
    date is made or fixed, so that I could reverse it and put it back to
    what it should be. Does MBSE do it automatically?

    MBSE can use PKTDATE to correct dates on incoming packets but does no actual correction on its own. The Y2K problem was 24 years ago.

    -- Sean

    ... Documentation: the worst part of programming.
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: Outpost BBS * Johnson City, TN (618:618/1)