(Ahh, another person with only 500 bytes remaining space left on his
HDD...)
Very funny!
There's a simple check, to see if your 'OS' (& Yarn) is
'2000-compliant': change the computers clock and check if
(1) your computer is still working,
(2) your 'OS' is still working,
(3) Yarn is still working,
(4) your trial software packages are still working.
If conditions (1)-(3) are fulfilled, generate dummy messages (mail and
news) and check if
(1) Yarn can still do this,
(2) your editor can handle messages > 2000.
If both successful, transmit the messages to USENET/Internet and check
if
(1) Souper can transmit this kind of messages,
(2) USENET/Internet can handle messages > 2000 (perhaps messages
returned from the future will be filtered...),
(3) Souper is capable receiving the messages again,
(4) Yarn is capable of displaying them.
If all the above can be done successfully the whole system should be
more or less '2000-compliant' (perhaps (or better for sure) I have
forgotten some steps - everybody is asked to complete the
'2000-compliant'-test algorithm!).
Hardy
PS: there is another of course much more simple approach to check
for '2000-compliance': wait...
PPS: stupid question at the end: which part of Yarn shouldn't
'2000-compliant'? Date/time sorting or what? For that case I
doubt, that Yarn will have any problems because for sure it's
using a binary representation of time stamps (not a truncated
text form). Common format will get problems in 2157 (or 2063)
which is out of the area of interest for most of us (I hope at
least for me...)
-- Hardy Griech, Ernetstr. 10/1, D-77933 Lahr http://privat.swol.de/ReinhardGriech/