At 03:42 PM 11/21/98 +0000, you wrote:
>There's gotta be thousands of MSX programs, and probably hundreds or
>more dealing with dates in one way or another. I would simply say
>here: SURELY plenty of programs that don't get it right, so bugs are
>in here as well.
Sure the whole Y2K thing is a serious problem, but I don't think it is very
relevant for MSX. And in those few cases it might be relevant, it would be
MSXes still in professional operation somewhere, not our home computers.
There are lots of bugs caused by bad programming practice in MSX programs.
I'll name a few:
- main RAM is assumed to be located in slot 3
- performing sector I/O on a harddisk, assuming it is a floppy
- memory managament that is not compatible with DOS2
I think these examples are more serious problems for us MSX users than the
Y2K on MSX will be.
If you can give me an example of a useful MSX program that will exhibit
serious bad behaviour because of Y2K, I will listen. Otherwise, please end
this thread.
Bye,
Maarten
****
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/)
****
