On Oct 29, 2012, at 10:12 PM, Dave McGuire <mcguire at neurotica.com> wrote:
On 10/29/2012 08:55 PM, Sampsa Laine wrote:
So I've got a SIMH PDP-11 running RSTS/E up, but am trying to figure
out how to change the node number and name.
I've tried re-installing DECNET from tape, but that doesn't seem to
work, as it says DECNET is running and must be shut down first.
So how do I:
a) Set the node name / number of a previously installed DECNET
install
This is a guess, as I've done very little DECnet under RSTS/E, but
possibly try:
$ @decnet$:net cfg
$ @decnet$:netcfg
$ delete/nolog/nowarnings dnet:addcrc.dat
^
?Not a valid device
Before you ask, yes. I eat logicals for snacks it would seem.
b) Shut down the DECNET process so I can reinstall
Try:
$ ncp set executor state off
That MIGHT be enough.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 10/29/2012 08:55 PM, Sampsa Laine wrote:
So I've got a SIMH PDP-11 running RSTS/E up, but am trying to figure
out how to change the node number and name.
I've tried re-installing DECNET from tape, but that doesn't seem to
work, as it says DECNET is running and must be shut down first.
So how do I:
a) Set the node name / number of a previously installed DECNET
install
This is a guess, as I've done very little DECnet under RSTS/E, but
possibly try:
$ @decnet$:netcfg
b) Shut down the DECNET process so I can reinstall
Try:
$ ncp set executor state off
That MIGHT be enough.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
So I've got a SIMH PDP-11 running RSTS/E up, but am trying to figure out how to change the node number and name.
I've tried re-installing DECNET from tape, but that doesn't seem to work, as it says DECNET is running and must be shut down first.
So how do I:
a) Set the node name / number of a previously installed DECNET install
or
b) Shut down the DECNET process so I can reinstall
Sampsa
On 29 Oct 2012, at 17:48, Cory Smelosky <b4 at gewt.net> wrote:
On 29 Oct 2012, at 17:03, Cory Smelosky <b4 at gewt.net> wrote:
On 29 Oct 2012, at 16:55, Marc Chametzky <marc at bluevine.net> wrote:
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
Had it bind to eth0 instead of vmbr0, the error went away and it can see an adjacent node.
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
That is now configured correctly. Seems this problem can easily be solved by just bringing up another VM, I have the RAM and DISK. ;)
Got it running in a VM but now?
https://www.refheap.com/paste/9b3f3fb3baae4d8ef23814976
Everything seems configured correctly, but it doesn't work. What'd I miss?
I have no idea what I missed or how I fixed it, but it works now. It seems I needed to install some ia32 libs.
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
On 29 Oct 2012, at 17:03, Cory Smelosky <b4 at gewt.net> wrote:
On 29 Oct 2012, at 16:55, Marc Chametzky <marc at bluevine.net> wrote:
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
Had it bind to eth0 instead of vmbr0, the error went away and it can see an adjacent node.
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
That is now configured correctly. Seems this problem can easily be solved by just bringing up another VM, I have the RAM and DISK. ;)
Got it running in a VM but now?
https://www.refheap.com/paste/9b3f3fb3baae4d8ef23814976
Everything seems configured correctly, but it doesn't work. What'd I miss?
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
On 29 Oct 2012, at 16:55, Marc Chametzky <marc at bluevine.net> wrote:
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
Had it bind to eth0 instead of vmbr0, the error went away and it can see an adjacent node.
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
That is now configured correctly. Seems this problem can easily be solved by just bringing up another VM, I have the RAM and DISK. ;)
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
There are three places I'd check:
1) The actual network Interface on the Unix system (should be able to verify with ifconfig)
2) The address configured in klt20.ini (assuming you're using the Panda distribution)
3) The DECnet address specified in 7-1-CONFIG.CMD
--Marc
On 29 Oct 2012, at 16:40, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 10/29/2012 4:23 PM, Jordi Guillaumes i Pons wrote:
El 29/10/2012, a les 21:21, Marc Chametzky <marc at bluevine.net> va escriure:
1) Preconfigure the Ethernet interface with the right MAC address with ifconfig xxx ether aa:00:04:00:xx:xx
Happen to know what MAC i'd want for 33.254? I'm bad with figuring hexadecimal stuff and i've not quite figured out the order for DECnet mac addresses yet.
If my math is correct, it'd be aa:00:04:00:fe:84.
If you are so lazy as am I:
http://www.powerdog.com/addrconv.cgi
On the other hand, the current linux dnet-tools contains a setether command which does the math for you.
I was just going to post that link. :)
-brian
29-Oct-2012 13:49:58 ***BUGCHK KNIADR*** Monitor address does not match NIA20 address, Data: 0, 524000040000, 524000040000, 77502000
0000
Hmmm, Where'd I screw up? the MAC and configured DECnet addresses match.
On 10/29/2012 4:23 PM, Jordi Guillaumes i Pons wrote:
El 29/10/2012, a les 21:21, Marc Chametzky <marc at bluevine.net> va escriure:
1) Preconfigure the Ethernet interface with the right MAC address with ifconfig xxx ether aa:00:04:00:xx:xx
Happen to know what MAC i'd want for 33.254? I'm bad with figuring hexadecimal stuff and i've not quite figured out the order for DECnet mac addresses yet.
If my math is correct, it'd be aa:00:04:00:fe:84.
If you are so lazy as am I:
http://www.powerdog.com/addrconv.cgi
On the other hand, the current linux dnet-tools contains a setether command which does the math for you.
I was just going to post that link. :)
-brian
