This is a multi-part message in MIME format.

------=_NextPart_000_000E_01BDF2B4.46A69800
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Dear Mr. Perry,

        I tested my PC again with other Y2K scan tools AMI2000.EXE (from
American MegaTrends) and Yes2K, I found that the result is different with
NTSL YMARK2000, my PC failed at RTC Y2000 roll over test.

        I wrote a program RTC.C to access the CMOS RAM directly bypassing
BIOS, it is confirm that my PC fail when roll over from Y1999 to Y2000 (it
has rolled over to 1900). But my BIOS is Y2K compliance.

        Here I attach my program RTC.C for your reference.

        Is any help for running NetBSD in non-Y2K compliance RTC BUT Y2K
compliance BIOS PC ?


-----Original Message-----
From: Perry E. Metzger <perry@piermont.com>
To: NG Yew Ban <ybng@cpm.com.my>
Cc: perry@piermont.com <perry@piermont.com>; tech-userlevel@netbsd.org
<tech-userlevel@netbsd.org>; tech-kern@netbsd.org <tech-kern@netbsd.org>;
Y.H.LOK <yhl@cpm.com.my>; asu@cpm.com.my <asu@cpm.com.my>
Date: Wednesday, October 07, 1998 1:32 AM
Subject: Re: NetBSD-1.3.2 Y2K problem


>
>"NG Yew Ban" writes:
>> 3) May I know the exact URL? Can I apply clock.c (V1.5.3) in older
version
>> of NetBSD (like NetBSD-1.1)?
>
>it is 1.53, not 1.5.3
>
>just go to the current sources tree on ftp.netbsd.org and dig it out
>-- its in src/sys/arch/i386/isa/clock.c to have a fuller path.
>
>It might work with 1.1, but 1.1 is full of other Y2K holes so there
>isn't much point.
>
>.pm
>
>
>>
>> Thanks in advance.
>>
>>
>> -----Original Message-----
>> From: Perry E. Metzger <perry@piermont.com>
>> To: NG Yew Ban <ybng@cpm.com.my>
>> Cc: perry@piermont.com <perry@piermont.com>; tech-userlevel@netbsd.org
>> <tech-userlevel@netbsd.org>; tech-kern@netbsd.org <tech-kern@netbsd.org>;
>> Y.H.LOK <yhl@cpm.com.my>; asu@cpm.com.my <asu@cpm.com.my>
>> Date: Tuesday, October 06, 1998 2:10 PM
>> Subject: Re: NetBSD-1.3.2 Y2K problem
>>
>>
>> >
>> >"NG Yew Ban" writes:
>> >> Dear Mr. Perry,
>> >>
>> >> For more info about the NSTL, you can access to
>> >> http://www.nstl.com/html/ymark_2000.html
>> >> I can reproduce the problem easily.
>> >
>> >1) Can you tell me if there are any console warnings during boot about
>> >the date?
>> >2) Can you tell me the exact date in 1997 the machine resets to?
>> >3) There is a new version of i386/isa/clock.c (v1.53) in tonight's SUP
>> >(or at least, will be in a few hours after the sup scanner runs). It
>> >may (or may not) fix a bug. Can you substitute this for your clock.c
>> >and tell me if the problem goes away when you build a kernel?
>> >
>> >Perry
>> >
>> >>
>> >> -----Original Message-----
>> >> From: Perry E. Metzger <perry@piermont.com>
>> >> To: NG Yew Ban <ybng@cpm.com.my>
>> >> Cc: tech-userlevel@netbsd.org <tech-userlevel@netbsd.org>; Y.H.LOK
>> >> <yhl@cpm.com.my>; asu@cpm.com.my <asu@cpm.com.my>
>> >> Date: Saturday, October 03, 1998 1:02 AM
>> >> Subject: Re: NetBSD-1.3.2 Y2K problem
>> >>
>> >>
>> >> >
>> >> >"NG Yew Ban" writes:
>> >> >> I have a Y2K compliance clone PC and pass with NSTL YMARK2000 test
>> >> >> program (Version 97.08.15),
>> >> >
>> >> >I'm unfamiliar with the program.
>> >> >
>> >> >> whereas when I ran NetBSD-1.3.2, NetBSD-1.3.2 can roll over from
>> >> >> year 1999 to year 2000, but after I rebooted the PC, the date
>> >> >> reverted back to year 1997.
>> >> >
>> >> >Can you reproduce this problem at will?
>> >> >
>> >> >Perry
>> >> >
>> >>
>> >
>>
>

------=_NextPart_000_000E_01BDF2B4.46A69800
Content-Type: application/octet-stream;
	name="rtc.C"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="rtc.C"

#include <conio.h>
#include <stdio.h>

void main()
{
   int port[7]={0x32,0x09,0x08,0x07,0x04,0x02,0x00};
   int s[7];
   int loop;

   clrscr();
   gotoxy(25,23); printf("Press any key to exit...");
   while(!kbhit())
   {
	  for(loop=0;loop<7;loop++)
	  {
		 outp(0x70,port[loop]);
		 s[loop]=inp(0x71);
	  }
	  gotoxy(20,10); printf("%02x%02x-%02x-%02x %02x:%02x:%02x",
	  s[0], s[1], s[2], s[3], s[4], s[5], s[6]);
   }
}
------=_NextPart_000_000E_01BDF2B4.46A69800--