rebuild RSTS/E monitor, was Re: [HECnet] RSTS/E 10.1 and OpenVMS via DECnet

Cory Smelosky b4 at gewt.net
Sun Oct 28 17:22:11 PDT 2012


On Oct 28, 2012, at 8:19 PM, Dave McGuire <mcguire at neurotica.com> wrote:

On 10/28/2012 07:36 PM, Cory Smelosky wrote:
Got it reinstalled   it still doesn't work the way you said to do
it, but doing it through @[0,1]instal works   so i'll just use that
route any time I need to build a monitor   

Urr?   You did a CLEAN install on a blank destination disk?   From
the tape image that I gave you?   I just did it that way..

   Well it wasn't blank, but I did choose "erase", so maybe that was my
mistake. Regardless, I know what to do next time I need to install
RSTS/E   just need to fix the DECnet issues.

Hmm.   Ok.   That's still a bit fishy, but at least we know why you
couldn't run a sysgen.

What's up with your DECnet installation, again?

It's connected to the network, yet it can't reach any other nodes. Adjacency notices between nodes are seen, but they cannot communicate. 

Alpha to RSTS/E resulted in 

$ set host/app=rterm 33.301
%REM-I-CONNECTION, connection made using RTERM protocol
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000517000008AA4, PC=0000517000008AA4, PS=0000001B

  Improperly handled condition, image exit forced.
      Signal arguments:     Number = 0000000000000005
                                              Name     = 000000000000000C
                                                                0000000000000000
                                                                0000517000008AA4
                                                                0000517000008AA4
                                                                000000000000001B

      Register dump:
      R0   = 0000000000000003   R1   = 0000000000008F50   R2   = 0000000000008134
      R3   = 0000000000034804   R4   = 000000007FFCF814   R5   = 0000000000009AEF
      R6   = 0000000000000000   R7   = 0000000000000001   R8   = 000000000003481D
      R9   = 000000007FF9DDF0   R10 = 000000007FFA4F28   R11 = 000000007FFCDC18
      R12 = 000000007FFCDA98   R13 = 0000000000005170   R14 = 0000000000008E28
      R15 = 0000000000008E28   R16 = 0000000002A83089   R17 = 0000000000200000
      R18 = FFFFFFFF809043A0   R19 = FFFFFFFF816367D0   R20 = 0000000000000002
      R21 = 0000000000000000   R22 = 000000007AE4BA54   R23 = FFFFFFFF80190A50
      R24 = 0000000000000001   R25 = 0000000000000003   R26 = FFFFFFFF80190A8C
      R27 = 000000007AE4BA54   R28 = 0000000000000006   R29 = 000000007AE4BA60
      SP   = 000000007AE4BA30   PC   = 0000517000008AA4   PS   = 300000000000001B
$ 

And VAX to RSTS/E just results in a timeout. Attempting to dir from an Alpha results in the request being seen on RSTS/E, but it fails.

RSTS/E to Alpha results in 

$ set host 33.302
Connection Established to VAX/VMS Node 33.302

?Unsupported Virtual Terminal Protocol.

Control returned to node MINDY

So, I don't know what I misconfigured.


                      -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA



More information about the Hecnet-list mailing list