Re: Y2K aftermath on the MSX??
] 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) Is this problem going to be resolved before the end of the year? Or is everybody using the internet instead of the BBS systems anyway ;-) Kind regards, Alex Wulms -- Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever See my homepage for info on the *** XSA *** format http://www.inter.nl.net/users/A.P.Wulms MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
] AFAIK, the clockchip uses BCD for storing its info, so H99 means decimal ] 99, not 155... This is correct. The RTC works with a BCD format. So, the MSX2 hardware has a 2079 problem. After that year we have to fallback to the MSX1, which does not have a hardware clock and can therefore not have a hardware related date problem. I hope I live long enough to be affected by this particular problem... Kind regards, Alex Wulms -- Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever See my homepage for info on the *** XSA *** format http://www.inter.nl.net/users/A.P.Wulms MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
Hans-Peter Zeedijk wrote: I 've tried the MSX system clock and the clock runs fine till 2072. afterthat 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
RE: Y2K aftermath on the MSX??
Hello all, 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 ... AFAIK, the clockchip uses BCD for storing its info, so H99 means decimal 99, not 155... +-- Eric Boon ---+ | this signature was | | intentionally left blank | ++ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
Hello all, 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 ... AFAIK, the clockchip uses BCD for storing its info, so H99 means decimal 99, not 155... Yeah. Read your docs a little more careful. You know what BCD is, do you? Storing a decimal value in hexadecimal form, so #09 + #01 = #10 (where # means Hex). The Z80 has even got a special instruction for this. ~Grauw -- email me: [EMAIL PROTECTED] or ICQ: 10196372 visit the Datax homepage at http://datax.cjb.net/ MSX fair Bussum / MSX Marathon homepage: http://msxfair.cjb.net/ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Y2K aftermath on the MSX?? (2nd part)
[I ask and then find a reply!] Hi y'all, I've just downloaded the MSX2 Technical handbook (thanks Konamiman!) and read in the DATE section: --- The format of the date to be set by the DATE command has three fields: year, month, and day. Each field is separated by "-", "/", or ".". Each field can have the following numerical values: year: 1980 to 2079 0 to 79 (considered as 2000 to 2079) 80 to 99 (considered as 1980 to 1999) month:1 to 12 day: 1 to 31 --- So that's it! Our MSX computers are already prepared to deal with the year 2000! :) Or so it seems. Now, can anybody confirm whether the same applies to MSX1 computers? Manuel PS to Konamiman: hey! there's no way to make your mem.com program run on my MSX2! I do have msxdos.sys and command.com (MSX-DOS2) yet it says DOS2 required. = MSX Database members.xoom.com/z80msx/msx.htm www.msxnet.org/manuel/msx.htm MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
Hi there, Just been wondering lately whether the Y2K bug will have any effect on our MSX computers. Are our MSXs ready to deal with the year 2000 date? Will there be any conflict with programs who look at file dates? Or is it just a nonsense we should not be really worried about? Hardware is compatible until 2079. Some software may display the dat incorrectly. To answer your last question: yes it's just nonsense we should really not worry about. In large companies there are probably some date-dependant tasks on their computers but we, as home-users really have nothing to worry about (at least, concerning our MSX system functionality). ~Grauw -- email me: [EMAIL PROTECTED] or ICQ: 10196372 visit the Datax homepage at http://datax.cjb.net/ MSX fair Bussum / MSX Marathon homepage: http://msxfair.cjb.net/ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
Hi, Manuel Soler wrote: Just been wondering lately whether the Y2K bug will have any effect on our MSX computers. Are our MSXs ready to deal with the year 2000 date? Will there be any conflict with programs who look at file dates? Or is it just a nonsense we should not be really worried about? I've tried it...put my Philips MSX2 (NMS8250) on the following date time: December 31 1999 23:59. And after 10 minutes it said: January 1st 2000 12:05a. After turning it on and off it still said 2000. Greetz, Daniel MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
Hi! I've tried it...put my Philips MSX2 (NMS8250) on the following date time: December 31 1999 23:59. And after 10 minutes it said: January 1st 2000 12:05a. Damn, so now we have an new problem. Where did those 4 minutes go? Was it a time-gap or something like that? Anyone else missed 4 minutes while testing it on their MSX? Greetz Collin MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Y2K aftermath on the MSX??
Collin van Ginkel wrote: Hi! I've tried it...put my Philips MSX2 (NMS8250) on the following date time: December 31 1999 23:59. And after 10 minutes it said: January 1st 2000 12:05a. Damn, so now we have an new problem. Where did those 4 minutes go? Was it a time-gap or something like that? ;-) Daniel. MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Y2K aftermath on the MSX??
Hi there, Just been wondering lately whether the Y2K bug will have any effect on our MSX computers. Are our MSXs ready to deal with the year 2000 date? Will there be any conflict with programs who look at file dates? Or is it just a nonsense we should not be really worried about? Thoughs are welcome... Sincerely, Manuel = MSX Database members.xoom.com/z80msx/msx.htm www.msxnet.org/manuel/msx.htm MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
