3 Aug
2022
3 Aug
'22
12:04 a.m.
You are correct about the 36 bit NRT servers.
The Tops-10 and Tops-20 variants are similar enough so that I only have
to check one byte in the configuration message; you'll recall that very
nice sheet you sent me with some notes about all this. What's puzzling
is that the operating system numbers are not the same between RMterm and
DAP.
Once that configuration check is done, there is absolutely no code
whatsoever in (my largely rewritten) sethost, Kermit-20 or TELNET which
pays any further attention. No special casing at all.
Actually, I don't think it's possible to directly tell the difference
after configuration although you might be able to deduce something from
information about the connection. There is no external or meta-data to
parse. Finally, if you try to do something 'clever' like send a DECnet
interrupt message on an NRT, you will irrevocably hang the session. At
least I did. It's on my list of things to look at.
On 8/2/22 4:50 PM, Johnny Billquist wrote:
Should have been RSTS/E, since RSX comes with the
client side
applications for connecting to TOPS-20, RSTS/E, RSX and VMS.
I think the TOPS-20 variant was also what worked to Tops-10.
Johnny
On 2022-08-02 19:22, Thomas DeBellis wrote:
Do you have a pointer anywhere for the
"RMterm" suite of protocols?
I only have documentation for CTerm and LAT, plus some reverse
engineering that Johnny and I did on various flavors of NRT for
Tops-10/20, RSX and I think something else, maybe RSTS.
On 8/2/22 11:43 AM, Paul Koning wrote:
The earlier "RMterm" suite of protocols
(it's really four, wrapped
in a single object number) would be a good first step.
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se