29 Dec
2020
29 Dec
'20
5:52 a.m.
Sure, you can always lie to Tops-10 about the date; but it seems to me
that it might be more friendly to not have it crash, say if some
neophyte is just poking around.
It might be difficult with the KLH micro-engine; as I recall, this gets
the date and time from the host, I forget what happens if you try to
override that.? You can't override it until you're booted, by which time
you've already crashed if somebody wants you to log a DECnet event.
Tops-10 can pull the date from elsewhere (like other processors), but I
don't think that's relevant anymore.
On 12/28/20 11:15 PM, Peter Lothberg wrote:
I think the best fix here is to change the base date
to for
example 2020 on systems we knew how to do this on.
It will send a happy positive number to everyone and some will think
it's in the past and some will get it right.
(Johnny already said this..)
-P
----- Original Message -----
> From: "tommytimesharing" <tommytimesharing at gmail.com>
> To: "hecnet" <hecnet at Update.UU.SE>
> Sent: Monday, December 28, 2020 11:06:24 PM
> Subject: Re: [HECnet] DECnet-10 doesn't work past Nov 9 2021?
> I did some date arithmetic; there are 16,383 days between 1/1/1977 and
> 11/9/2021.
>
> Since Tops-10 is calculating by half days, that's why I clamp it to the
> unsigned octal value of 177777 (3FFF hex).
>
> Would a later version of NICE have expanded this to four bytes? That
> seems like the thing to do.