🚀 go-pugleaf

As the fix is supposed to be in the new loader, I assume that the
Netware OS itself did already handle the year 2000 properly and that
there was only a problem getting the date from the BIOS or DOS.

Marcel


Phil Randal <philr@hwcces.demon.co.uk> wrote:

>In article <3235929f.8086003@news.execpc.com>
>   tom.kustner@emjay.com (Tom Kustner) writes:
>>In laboriously reading the README.TXT files and searching Novell's
>>site, there is only specific mention of a fixed year 2000 problem with
>>regards to NetWare 4.10.  Did 312PT9.EXE fix a year 2000 problem with
>>NetWare 3.12, or was there none to fix?  Does anyone know?

>Read the install.txt file in the 312pt9 archive - it is mentioned there.

>>>The patch is available now:  the latest patch kits for NW3.12 and NW4.10
>>>which were released on August 19th, 1996 contain new loader.exe files
>>>which fix the "Year 2000" problem.
>>>
>>>  ftp://ftp.novell.com/pub/updates/nwos/nw312/312pt9.exe
>>>  ftp://ftp.novell.com/pub/updates/nwos/nw410/410pt6.exe

>and
>    ftp://ftp.novell.com/pub/updates/nwos/nw311/311ptf.exe

>Readers concerned about the year 2000 bugs in general should visit
>http://www.year2000.com/

>There are at least 4 possible year 2000 bugs:

>1:  The NetWare one, whatever it is;

>2:  The PC BIOS 1999/2000 wraparound problem;

>3:  2 digit years in application programs;

>4:  Programs which insist that the year 2000 is not a leap year (it is).

>Phil

>-------------------------------------------------------------------
>Phil Randal                                philr@hwcces.demon.co.uk
>Environmental Services Department
>Hereford and Worcester County Council
>Worcester, UK