Re: Millenium bug in 2010 ?

[David Brant]

Atom Lite+ works ok with BDOS 1.5a. But that's using DVAR command to get the 
date.

Happy new year to all.

Dave
----- Original Message ----- 
From: "Ian Spencer" <ian.spen...@freenet.de>
To: <sam-users@nvg.ntnu.no>
Sent: Saturday, January 02, 2010 8:09 AM
Subject: Re: Millenium bug in 2010 ?


Actually I was having a senior moment there as BDOS doesn't seem to have a 
DATE command so it must be from Masterbasic.

Ian

----- Original Message ----- 
From: "Ian Spencer" <ian.spen...@freenet.de>
To: <sam-users@nvg.ntnu.no>
Sent: Saturday, January 02, 2010 9:01 AM
Subject: Re: Millenium bug in 2010 ?


Hi Si,

and I hope you had a very happy new year and to all other Sam users of 
course as well.

Well it wasn't Master DOS but I had merged Masterbasic into BDOS so it 
could be the problem comes from there. I'll have to have a look to see if 
I still have a version of BDOS without Masterbasic, just to try the Date 
command.

Ian



----- Original Message ----- 
From: "Simon Owen" <simon.o...@simcoupe.org>
To: <sam-users@nvg.ntnu.no>
Sent: Saturday, January 02, 2010 1:06 AM
Subject: Re: Millenium bug in 2010 ?


Ian Spencer wrote:
just started simcoupe with BDOS v1.7b this morning and noticed that
instead of 1.1.2010 ( that is 01/01/10) the 'DATE' command gives 
01/01/00
has anyone else seen this problem ?

Is that MasterDOS rather than BDOS?  I tried BDOS 1.5a and 1.7d here,
but that doesn't have a DATE command or DATE$ variable.

MasterDOS shows 01/01/00 in v1.0, but 01/01/10 in my development
version, so looks like I fixed it when enhancing the clock for the fancy
new DALLAS chip Edwin includes with some AtomLite+ boards.

I'll build a hotfix version of v1.0 with the updated clock, as there's
too much new and experimental stuff outstanding to risk a development
build.  I should manage that before I go back to work in a few days.

Happy New Year all!

Si