1 Jun
2023
1 Jun
'23
6:51 p.m.
I've been testing my changes to Tops-20 NFT and ran into what what I
thought were some perhaps interesting results, viz:
NFT>*i twonky*
Attempting connection to TWONKY:: [31.37]
Maximum buffer size: _0!_
Operating System: Tops-10, File System: Tops-10
DAP: 7.0, DECnet: _0.0_
NFT>*i ostara*
Attempting connection to OSTARA:: [31.15]
Maximum buffer size: 4096
Operating System: Ultrix-32, File System: _13 (Unknown)_
DAP: 7.0, DECnet: 1.0
Note that I am clipping the capability display for these examples. By
"interesting", I was surprised to find that Tops-10 is reporting a
buffer size of zero, but more by it reporting a DECnet version of 0.0.
Where are these version numbers defined? For Ultrix, I would assume that
I need a more up-to-date list of file systems, given that the highest
that DAP 5.6 states is 9 for OS-8 (!!)
As a comparison, this is what I see for VENTI2:: (Tops-20) and a random
RSTS host.
NFT>*i*
Local Executor is: VENTI2:: [2.522]
Maximum buffer size: 4096
Operating System: Tops-20, File System: Tops-20
DAP: 5.6.1, DECnet: 2.0
NFT>*i pirsts*
Attempting connection to PIRSTS:: [29.205]
Maximum buffer size: 636
Operating System: RSTS/E, File System: RMS-11
DAP: 5.6, DECnet: 4.1
I want to sign on to MIM:: later to see what the RSX NFT client says;
it's certainly possible that I am not displaying this correctly.