[HECnet] Configuring py-decnet.

[Thomas DeBellis]

Yeah, that's what I found out, too.

On Tops-20, the CTERM client is called CTERM-SERVER (don't ask) whereas 
the NRT client is called SETHOST.  SETHOST is /quite/ old and I had been 
hacking it for efficiency and fixing a few bugs.

It now has an alternate debugging entry to try to force Tops-20 NRT 
(which will also work on Tops-10) and ignore the remote node type until 
it can't proceed any further.  Here are the results from my own tests; 
they indicate that a CTERM (server) object does not exist on ELVIRA.  
I'm not sure, but I had thought that CTERM had not been done on RSTS/E.

!cterm-sERVER.EXE.2 elvira

[Attempting a connection,
_CTERM Connect failed - Destination process does not exist_
!g ds:sethost
!ree
Escape character(^Y):
Host name: ELVIRA::
[Connecting to remote host: ELVIRA]
_?RSTS/E type systems do not support Tops-20 NRT communications._


On 8/25/20 8:09 PM, Paul Koning wrote:
> John,
>
> Some systems, like VMS, will use CTERM by default, and there isn't a CTERM listener on RSTS.  So you have to tell it to use the "old protocol", whatever that involves on your OS.
>
> 	paul
>
>> On Aug 25, 2020, at 7:24 PM, jy at xtra.co.nz wrote:
>>
>> Hi Thord,
>>
>> Congratulations, I can see you're up at:
>>
>> http://akdesign.dyndns.org:8080/map/data
>>
>> I just tried a set host elvira and set hsot 59.53 but I'm getting "network object unknown at remote node".
>>
>> Cheers, John
>>
>>
>>
>>> On 26 August 2020 at 11:14 Thord Nilson <thordn at gmail.com> wrote:
>>>
>>> Hi all!
>>> Update!
>>> Basic connections are now working,  so for a limited time you can:
>>> set host elvira::
>>> login as 99,99 psw: testing
>>> Nothing much to see though.
>>> Thanks to all for your help!
>>>
>>> /Thord.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20200825/5689b7a5/attachment-0001.html>