Hans-Peter Zeedijk wrote:

 
>I 've tried the MSX system clock and the clock runs fine till 2072. after
>that it returns to 1973. Problems with programm's I have not encountered.
>no Y2K problem in hardware, the software could have a problem. So if you do
 
Well, BASIC, MSX-DOS (1 and 2) are also software, isn't it?
 
Try the following in BASIC (version 2.1): 
get date d$ : print d$
Then a date string will appear on your screen, which only gives the last two digits of the year!
Programs which use this method for getting the date will have trouble I guess
 
Try the following in MSX-DOS (1): 
> date
current date is: 29-11-1999 
enter new date: 
Here you see the date in four digits!
After entering the date of 31/12/2079 there and the time of 23:59 and switching the power off for a minute, the date of 1/1/1980 appears. The problems will rise again in 2079..
 
I have also tested the year 2072 you named, but DOS(1) jumps to 2073, as it should be.
Which OS did you use?
 
I haven't tried MSX-DOS 2 yet. But from the DOS2 function codes specification I conclude that it makes no difference with DOS1.
 
Research in the MILC learned me, that the clockchip uses two nibbles for storing the date. The max value stored is &H99, this is decimal 155, and 1980+155 = 2135. So the clockchip gives the correct date until 2135 (Doubt if I make it till then ..) It's only the software ...
 
For instance the dutch echomail system (i.e. sending electronic messages from one BBS to another) will have trouble with the millenium. (the only prog i know so far)
 
Grtz, Siebe
 
 

Reply via email to