[HECnet] Oldest VAX/VMS for VAX-11/730 on HECNET

[Mark J. Blair]

> On Dec 8, 2021, at 11:18 PM, Supratim Sanyal <supratim at riseup.net> wrote:
> 
> Looks like it. The lowest I could go so far is 31.31 (XLIV) @ 4.4. We should try 3.4+ with the key sometime.

I tried 3.5 with the license installed, and then upgraded it to 3.7 and tried again. It asks for an address in the range 1..1023, but I didn't see any way to specify an area. When I tried starting the network in any of them, I got errors like:

> $ @startnet   
> %RUN-S-PROC_ID, identification of created process is 0001000E
> %OPCOM,  8-DEC-2021 18:33:36.97, message from user DECNET      
> DECnet starting
> %NCP-I-NMLRSP, listener response - Invalid parameter value, Maximum address
> Executor node = 2.617 (PUGGLE)
> 
> %RUN-S-PROC_ID, identification of created process is 0001000C
> %NCP-I-NMLRSP, listener response - Invalid parameter value, Maximum address
> Executor node = 2.617 (PUGGLE)


In that case I had type in my 2.617 address without paying enough attention to the prompt asking for a number in the range 1..1023. I got the same kinds of errors after I reconfigured with an address of 617.

4.0 was the first version that prompted me for a regular Phase IV address, and it gave me errors like:

> %RUN-S-PROC_ID, identification of created process is 0000004A
> $ 
> %%%%%%%%%%%  OPCOM   8-DEC-2021 19:23:45.49  %%%%%%%%%%%
> Message from user DECNET
> DECnet event 4.19, adjacency down, operator initiated
> From node 2.617 (PUGGLE),  8-DEC-2021 19:23:45.49
> Circuit UNA-0, Adjacent node address out of range
> Packet beginning = 0B020000AA000400BB0A024F0240000A


I speculate that it was reacting poorly to traffic it saw on my local network, between my router LABRDR and my nodes HUSKY and BULDOG which were up?

4.7 is working well, but I have not tried any other versions between 4.0 and 4.7 yet.

-- 
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/