24 Mar 16 14:43, you wrote to Janis Kracht:

 VC> That said a working source copy of pktdate might be useful not that I
 VC> have seen bad dates on net or echo mail but ....

apparently you do not have folks feeding from your system that get
nostalgic and restore their old BBS setup from 15+ year old tapes or CDs...
BBS software that is not y2k compatible... software that mucks up the year
because the code doesn't do modulo arithmetic [eg: "year = (year-1900)
mod 100"]... they get a result of 1xx when they subtract 1900 from the
current year while trying to make it a two digit year because they use math
manipulation instead of string manipulation... this is a quite common
problem seen in C code of that era... it is sometimes seen in code written
in other languages but it is very common in C code... today, that code will
return 116 for the year after they subtract 1900 and don't modulo it...

that's only ONE of the various problems that can happen... depending on the
rest of the processing it may make the PKT header one byte too long or it
could result in the last byte of the PKT header being truncated... then you
get to the dates in the packed messages and they could have headers that
are one byte too long or be the proper length but missing the last byte of
the message header...

anyway, i thought i'd toss that out there to try to help explain the
problem of non-y2k compliant software and the possible date problems they
can cause...

)\/(ark

Always Mount a Scratch Monkey

... Buffet: French for making a pig of yourself.
---