B/1
or
B/R5:1
Sent from my iPad
On Mar 5, 2011, at 12:23 AM, Sampsa Laine <sampsa at mac.com> wrote:
Guys,
Anybody got a quick answer for how to do a conversational boot on SIMH VAX?
I've managed to get the disk filled up on GORVAX and need to get in to clean up the disk.
Sampsa
Cheers, that worked.
Sampsa
On 4 Mar 2011, at 22:36, hvlems at zonnet.nl wrote:
B/R5:1 ddun
Will get you to SYSBOOT, assuming you're not running the simh VAX 11/780 ;-)
Verzonden vanaf mijn draadloze BlackBerry -toestel
-----Original Message-----
From: Sampsa Laine <sampsa at mac.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 04 Mar 2011 22:23:00
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: [HECnet] Boot flags on SIMH MicroVAX 3900
Guys,
Anybody got a quick answer for how to do a conversational boot on SIMH VAX?
I've managed to get the disk filled up on GORVAX and need to get in to clean up the disk.
Sampsa
B/R5:1 ddun
Will get you to SYSBOOT, assuming you're not running the simh VAX 11/780 ;-)
Verzonden vanaf mijn draadloze BlackBerry -toestel
-----Original Message-----
From: Sampsa Laine <sampsa at mac.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 04 Mar 2011 22:23:00
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: [HECnet] Boot flags on SIMH MicroVAX 3900
Guys,
Anybody got a quick answer for how to do a conversational boot on SIMH VAX?
I've managed to get the disk filled up on GORVAX and need to get in to clean up the disk.
Sampsa
Guys,
Anybody got a quick answer for how to do a conversational boot on SIMH VAX?
I've managed to get the disk filled up on GORVAX and need to get in to clean up the disk.
Sampsa
Guys,
I'm going to try running the phone directory on FIDOGW yet again and uploading the results to RHESUS as before.
However, instead of polling every node in the node DB, I will only poll those nodes that have indicated that they should be included - so let me know if you want some nodes included.
This should reduce the amount of junk traffic drastically.
Johnny, let me know if you still see a lot of errors on your side.
Sampsa
On 03/03/11 21:19, Marc Chametzky wrote:
This is embarrassing.
I've got a DECnet-over-IP connection set up on my SIMH VAX. It had been
working, but then I switched firewalls some time back and messed up the
configuration so that packets from my VAX were coming from the wrong IP
address. I only recently discovered that this was the problem and have
now fixed it.
My TCP-0-0 circuit remains in the "-starting" state, so either I've
still got something wrong or maybe the other end of the circuit is
disabled since I was misconfigured for so long. Another possibility is
that the other end's IP address changed and I haven't updated my side.
My problem is that I don't recall who set up the connection for me to be
on HECnet.
So, if you've got a DECnet-over-IP connection configured to DUSTY, would
you please help me get reconnected... Pretty please? :-)
Well, if you tell us what IP address you have configured as the remote address, maybe someone will recognize it?
Johnny
Also check that port 700 is forwarded.
UDP, right? I've got that enabled in my firewall.
I did a quick trace and I see packets going out on port 700, but I don't see anything coming back. (That's assuming that I did my packet trace on the firewall correctly, of course.)
I forgot to ask... Where are you located? If you are in the Eastern US (or Eastern Canada) then you can connect to my systems.
I'm in Pittsburgh.
--Marc
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Marc Chametzky
Sent: Thu 3/3/2011 15:19
To: hecnet at Update.UU.SE
Subject: [HECnet] Can't remember how I'm connected to HECnet
This is embarrassing.
I've got a DECnet-over-IP connection set up on my SIMH VAX. It had been
working, but then I switched firewalls some time back and messed up the
configuration so that packets from my VAX were coming from the wrong IP
address. I only recently discovered that this was the problem and have
now fixed it.
My TCP-0-0 circuit remains in the "-starting" state, so either I've
still got something wrong or maybe the other end of the circuit is
disabled since I was misconfigured for so long. Another possibility is
that the other end's IP address changed and I haven't updated my side.
My problem is that I don't recall who set up the connection for me to be
on HECnet.
So, if you've got a DECnet-over-IP connection configured to DUSTY, would
you please help me get reconnected... Pretty please? :-)
--Marc
I forgot to ask... Where are you located? If you are in the Eastern US (or Eastern Canada) then you can connect to my systems.
-Steve
-----Original Message----- From: owner-hecnet at Update.UU.SE on behalf of Marc Chametzky Sent: Thu 3/3/2011 15:19 To: hecnet at Update.UU.SE Subject: [HECnet] Can't remember how I'm connected to HECnet This is embarrassing. I've got a DECnet-over-IP connection set up on my SIMH VAX. It had been working, but then I switched firewalls some time back and messed up the configuration so that packets from my VAX were coming from the wrong IP address. I only recently discovered that this was the problem and have now fixed it. My TCP-0-0 circuit remains in the "-starting" state, so either I've still got something wrong or maybe the other end of the circuit is disabled since I was misconfigured for so long. Another possibility is that the other end's IP address changed and I haven't updated my side. My problem is that I don't recall who set up the connection for me to be on HECnet. So, if you've got a DECnet-over-IP connection configured to DUSTY, would you please help me get reconnected... Pretty please? :-) --Marc > > > Also check that port 700 is forwarded. -Steve
This is embarrassing.
I've got a DECnet-over-IP connection set up on my SIMH VAX. It had been working, but then I switched firewalls some time back and messed up the configuration so that packets from my VAX were coming from the wrong IP address. I only recently discovered that this was the problem and have now fixed it.
My TCP-0-0 circuit remains in the "-starting" state, so either I've still got something wrong or maybe the other end of the circuit is disabled since I was misconfigured for so long. Another possibility is that the other end's IP address changed and I haven't updated my side.
My problem is that I don't recall who set up the connection for me to be on HECnet.
So, if you've got a DECnet-over-IP connection configured to DUSTY, would you please help me get reconnected... Pretty please? :-)
--Marc
