The version of NCP I posted before was incomplete: it handles "show circuit"
correctly but fails on "show node". I just posted a new version that fixes
this. The version on NI1D:: (in the default account) has also been updated so
you can grab it that way if you prefer.
paul
> On Jun
20-07-02 19:00,jw...@classiccmp.org wrote:
>
>> Message: 6
>> Date: Wed, 1 Jul 2020 12:51:42 -0500
>> From:
>> To: "'Paul Koning'" , "'General Discussion:
>> On-Topic and Off-Topic Posts'" , "'Tony
>>
On 2020-07-02 19:00,jw...@classiccmp.org wrote:
> Message: 6
> Date: Wed, 1 Jul 2020 12:51:42 -0500
> From:
> To: "'Paul Koning'" , "'General Discussion:
> On-Topic and Off-Topic Posts'" , "'Tony
> Nicholson'&
On Thu, Jul 2, 2020 at 3:52 AM wrote:
> --
> Nice. I looked at fixing RT11 RTS applications like MACRO, but that's not
> possible because the RT11 date format stops in the early 21st century (5
> bit
> year field). Perhaps RT-11 has created a solution, but if so I don't know
> it.
> ---
--
Nice. I looked at fixing RT11 RTS applications like MACRO, but that's not
possible because the RT11 date format stops in the early 21st century (5 bit
year field). Perhaps RT-11 has created a solution, but if so I don't know
it.
--
It was my understanding that Jerome Fine did
> On Jul 1, 2020, at 3:13 AM, Tony Nicholson
> wrote:
>
> Hi Paul,
>
> Thanks for posting some Y2K fixes and enhancements for DECnet/E under RSTS/E.
>
> I've also used the Bitsavers source files for RSTS/E V10.1 to fix a Y2K bug
> with handling RT-11 Y2k3 dates by the FIT program.
Nice.
Hi Paul,
Thanks for posting some Y2K fixes and enhancements for DECnet/E under
RSTS/E.
I've also used the Bitsavers source files for RSTS/E V10.1 to fix a Y2K bug
with handling RT-11 Y2k3 dates by the FIT program.
Are you interested in including my patched FIT.TSK for RSTS/E along with
your fixe