Subj : Re: Spitfire's Y2k25 bug
To   : xbit
From : Dan Cross
Date : Tue Jan 07 2025 03:43:14

On 04 Jan 2025 at 05:40a, xbit pondered and said...
 
 xb>   Re: Re: Spitfire's Y2k25 bug
 xb>   By: Dan Cross to xbit on Sat Jan 04 2025 07:38 am
 xb> 
 xb>  xb>> Sadly, looks like Spitfire is RIP forever. On the morning of
 xb>  xb>> 1-1-2025 I noticed that all SF nodes would no longer boot as it
 xb>  xb>> requests to set the system date and time. 
 xb>  xb>> Looking into putting it on a VM w/ the date set to 2014 but perhaps
 xb>  xb>> its just time to say goodbye.
 xb> 
 xb>  DC> That's really sad. I know that Mike Woltz passed away in 2022; it's
 xb>  DC> a shame that the source code to Spitfire wasn't released as open sour
 xb>  DC> before that. Does anyone know how to get in touch with his estate?
 xb>  DC> Perhaps they'd be willing to transfer the code somewhere and someone
 xb>  DC> could patch it. For that matter, maybe the binary could be patched.
 xb> 
 xb> Last year I put a few days into trying to find a family contact w/ out
 xb> much luck. But, I'm not a person finding expert so I'm sure it can be
 xb> done by someone with the correct tools. 
 xb> 
 xb> I'm upset w/ myself as I had an ongoing thread with Mike before he
 xb> passed. We worked on a few bugs i found and he even updated my
 xb> spitfire.exe not long ago. I was going to ask him if he had plans on
 xb> making SF freeware and/or opensource but i knew he got a little put off
 xb> with this line of question.

Hmm, that's too bad.  As some of these folks age, the best
way to preserve their legacy in this context is to open source
their code.  Sadly, the source to Spitfire probably died with
Mike, and unless someone finds a copy and releases it, that'll
be that.

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

.