<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Wed, 22 Mar 2006 19:19:08 +0000 (GMT)
From   : Sprow <info@...>
Subject: Re: Web site: Mainly Master 512

In article <001f01c64d95$2b651af0$0301a8c0@...>,
   David Harper <dl.harper@...> wrote:

[snip]

> > I'm having a problem with the date, though, as it likes to think that 
> > it's 2130, although the time is correct.  If I set the date, it is OK
> > but I seem
> > to have to do this every time I boot the machine.  Does anybody else
> > have this problem and is there a cure?

> I have included the source code, for anyone interested. OK, it is not
> brilliant programming. It is what happens when one knocks something 
> together quickly.

Nice one. 

You could also extend it to read the time as a string, and interpret the
first two digits of the year and use BCD to get the last two digits (or just
interpret all 4 from the string). This would allow the value of *TIME to
match that used in DOS without fiddling,
Sprow.
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>