• Spitfire BBS

    From xbit@VERT/XBITBBS to All on Sunday, April 27, 2025 04:07:50
    Spitfire BBS software suffered a Y2K (Y2K25?) type bug on 1-1-2025. And with Mike's passing and the source code not shared, the last 3 SF board were down for good. Well... I don't like being told what to do.. so, my SF BBS is back up <g>.

    telnet://x-bit.org:23230

    Nothing that a Linux OS > Win VM > DOS BBS > 2014 date trick can't fix.

    Long live Spitfire BBS!

    ...If it ain't broke, don't fix it.

    ---
    þ Synchronet þ |15<|07<|08< +h3 |02><|08-bi+ >|07>|15>
  • From Dumas Walker@VERT/CAPCITY2 to XBIT on Sunday, April 27, 2025 08:57:00
    Spitfire BBS software suffered a Y2K (Y2K25?) type bug on 1-1-2025. And with Mike's passing and the source code not shared, the last 3 SF board were down for good. Well... I don't like being told what to do.. so, my SF BBS is back u
    <g>.

    telnet://x-bit.org:23230

    Nothing that a Linux OS > Win VM > DOS BBS > 2014 date trick can't fix.

    Long live Spitfire BBS!

    Good deal! My GT Power BBS has been suffering some odd things over the
    years. I sometimes wonder if running it in a back-dated VM wouldn't help. Guess if it completely breaks, I will find out. ;)


    * SLMR 2.1a * Engineers: often wrong, seldom in doubt.
    ---
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP