🚀 go-pugleaf

Microsoft Windows for Workgroups 3.11 File Manager, the version recently
provided by Microsoft to fix the Y2k display problem (98, 99, :0, :1,
...), which I may previously have reported as reducing all displayed
file dates greater than 2099 to 2099 (I then had it set to UK date
convention, dd/mm/yy), appears to have another bug. 

As recommended by sft@aegis1.demon.co.uk in "What is ISO 8601?" -
http://www.aegis1.demon.co.uk/y2kiso.htm (commended), I have set my
Windows to ISO-8601 date/time; I see that all displayed file dates after
2079 are now reduced by 100 years on my system.

GOK what other errors it may show if differently set; others may care to
look further.

The next version of http://www.merlyn.demon.co.uk/zipfiles/hunttest.zip
will contain new test files dated 2079/12/31 & 2080/01/01.

Obviously most of us will be unaffected, but future dates may become set
for various reasons ...

cc sft.
 
-- 
John Stockton, Surrey, UK.    jrs@merlyn.demon.co.uk    Turnpike v1.12    MIME.
 Web <URL: http://www.merlyn.demon.co.uk/> --- includes FAQqish topics & links.
 My list of Critical Dates is now at http://www.merlyn.demon.co.uk/critdate.htm
 Don't Mail News.  Y2k for beginners http://www.merlyn.demon.co.uk/year2000.txt