On 16.7.2011 1:41, Johnny Billquist wrote:
On 2011-07-16 00.30, Mark Wickens wrote:
The VAX isn't turned on. I can turn it on and try this, but I would
expect the connection to then succeed.
Yes, that probably would make it succeed.
What I'd really like to be able to do is have both Alpha and VAX
configured to act as area routers, so that I can have either switched on
independently, and not have them rely on each other.
So, why not do that.
There may be an unlikely situation where both are switched on at the
same time, is it an unsupported configuration to have two area routers
enabled at the same time?
No. That is perfectly legal. And you don't really need to do anything
special. The machines will figure it out themself. All you need is to
just enable area routing on both.
I'm presuming setting a box up as an area router requires a sequence of
NCP commands?
There is some command, yes. Something like SET EXEC TYPE, or something
like that.
However, the one thing you should be aware of is that DEC never
officially supported Alpha machines as area routers. But I seem to
remember hearing someone saying that it actually worked anyway. But you
need to test, I guess...
There was some versions of DECnet on Alpha, which didn't allow area routing. I don't remember exactly now, but I think it was re-enabled since VMS V7.3 (and thus DECnet IV for AXPVMS V7.3).
Johnny
Thanks for the help, Mark
On Fri, 15 Jul 2011, hvlems at zonnet.nl wrote:
You always need one area router to connect to nodes outside your area.
With one exception: on a lan with no decnet routers present, nodes can
connect irrespective what area tjey're in.
So you need the bridge program AND an area router for yet another
decnet node to see all the others.
If your vax is the area router (try mc ncp sho exeec char) does the
alpha connect to the vax?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Area configuration
Verzonden: 16 juli 2011 00:12
Hi, SteveD is the best person to answer this question, but I'm not sure
whether he's about at the moment.
I'm in my own area, area 4, and I normally run a VAX, BUBBLE which I
believe does area routing.
I'm setting up an Alpha system, but am currently unable to see any other
areas via hecnet. For the most part, either the Alpha or VAX will be
running, but not both.
Do I need to setup the Alpha as an area router also?
Thanks for the help, Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
.
On 2011-07-16 00.30, Mark Wickens wrote:
The VAX isn't turned on. I can turn it on and try this, but I would
expect the connection to then succeed.
Yes, that probably would make it succeed.
What I'd really like to be able to do is have both Alpha and VAX
configured to act as area routers, so that I can have either switched on
independently, and not have them rely on each other.
So, why not do that.
There may be an unlikely situation where both are switched on at the
same time, is it an unsupported configuration to have two area routers
enabled at the same time?
No. That is perfectly legal. And you don't really need to do anything special. The machines will figure it out themself. All you need is to just enable area routing on both.
I'm presuming setting a box up as an area router requires a sequence of
NCP commands?
There is some command, yes. Something like SET EXEC TYPE, or something like that.
However, the one thing you should be aware of is that DEC never officially supported Alpha machines as area routers. But I seem to remember hearing someone saying that it actually worked anyway. But you need to test, I guess...
Johnny
Thanks for the help, Mark
On Fri, 15 Jul 2011, hvlems at zonnet.nl wrote:
You always need one area router to connect to nodes outside your area.
With one exception: on a lan with no decnet routers present, nodes can
connect irrespective what area tjey're in.
So you need the bridge program AND an area router for yet another
decnet node to see all the others.
If your vax is the area router (try mc ncp sho exeec char) does the
alpha connect to the vax?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Area configuration
Verzonden: 16 juli 2011 00:12
Hi, SteveD is the best person to answer this question, but I'm not sure
whether he's about at the moment.
I'm in my own area, area 4, and I normally run a VAX, BUBBLE which I
believe does area routing.
I'm setting up an Alpha system, but am currently unable to see any other
areas via hecnet. For the most part, either the Alpha or VAX will be
running, but not both.
Do I need to setup the Alpha as an area router also?
Thanks for the help, Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
The VAX isn't turned on. I can turn it on and try this, but I would expect the connection to then succeed.
What I'd really like to be able to do is have both Alpha and VAX configured to act as area routers, so that I can have either switched on independently, and not have them rely on each other.
There may be an unlikely situation where both are switched on at the same time, is it an unsupported configuration to have two area routers enabled at the same time?
I'm presuming setting a box up as an area router requires a sequence of NCP commands?
Thanks for the help, Mark
On Fri, 15 Jul 2011, hvlems at zonnet.nl wrote:
You always need one area router to connect to nodes outside your area.
With one exception: on a lan with no decnet routers present, nodes can connect irrespective what area tjey're in.
So you need the bridge program AND an area router for yet another decnet node to see all the others.
If your vax is the area router (try mc ncp sho exeec char) does the alpha connect to the vax?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Area configuration
Verzonden: 16 juli 2011 00:12
Hi, SteveD is the best person to answer this question, but I'm not sure
whether he's about at the moment.
I'm in my own area, area 4, and I normally run a VAX, BUBBLE which I
believe does area routing.
I'm setting up an Alpha system, but am currently unable to see any other
areas via hecnet. For the most part, either the Alpha or VAX will be
running, but not both.
Do I need to setup the Alpha as an area router also?
Thanks for the help, Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
You always need one area router to connect to nodes outside your area.
With one exception: on a lan with no decnet routers present, nodes can connect irrespective what area tjey're in.
So you need the bridge program AND an area router for yet another decnet node to see all the others.
If your vax is the area router (try mc ncp sho exeec char) does the alpha connect to the vax?
------Origineel bericht------
Van: Mark Wickens
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Area configuration
Verzonden: 16 juli 2011 00:12
Hi, SteveD is the best person to answer this question, but I'm not sure
whether he's about at the moment.
I'm in my own area, area 4, and I normally run a VAX, BUBBLE which I
believe does area routing.
I'm setting up an Alpha system, but am currently unable to see any other
areas via hecnet. For the most part, either the Alpha or VAX will be
running, but not both.
Do I need to setup the Alpha as an area router also?
Thanks for the help, Mark.
Verzonden vanaf mijn draadloze BlackBerry -toestel
On 2011-07-16 00.12, Mark Wickens wrote:
Hi, SteveD is the best person to answer this question, but I'm not sure
whether he's about at the moment.
I'm in my own area, area 4, and I normally run a VAX, BUBBLE which I
believe does area routing.
I'm setting up an Alpha system, but am currently unable to see any other
areas via hecnet. For the most part, either the Alpha or VAX will be
running, but not both.
Do I need to setup the Alpha as an area router also?
Thanks for the help, Mark.
Yes.
You need an area router (in your area) to talk to machines in any other area.
Johnny
Hi, SteveD is the best person to answer this question, but I'm not sure whether he's about at the moment.
I'm in my own area, area 4, and I normally run a VAX, BUBBLE which I believe does area routing.
I'm setting up an Alpha system, but am currently unable to see any other areas via hecnet. For the most part, either the Alpha or VAX will be running, but not both.
Do I need to setup the Alpha as an area router also?
Thanks for the help, Mark.
On 15.7.2011 15:02, Mark Wickens wrote:
On 15/07/11 12:44, hvlems at zonnet.nl wrote:
The first DEC system I worked with was a pdp-11/40. It had a CR11, an
LP11, one RK05, an RX01 and a DECtape I unit. It did have MMU but just
32 kB core, which was expanded to 64 KB core. That allowed KED to run
with RT-11 (V3, V4).
I did experiment with RSX-11D but preferred RT-11. The pdp served in a
laboratory, it got an LPS-11 interface later on.
Hans
Verzonden vanaf mijn draadloze BlackBerry -toestel
OK, so we need someone to code a trigger a the notes server to post to
the email list and write an email gateway that will process emails and
add notes posts. Best of both worlds. Now who will step up to the plate?
Sounds like the kind of crazed idea that Sampsa gets involved in ;)
Mark.
.
I do have everything needed for setting up a Notes server. The gateway thing is something that has to be worked on.
Do everybody want to post messages through emails and not directly (using the CLI interface or the DECwindows interface)?
The nice thing with them are the DECnet connection.
Kari
On Thu, Jul 14, 2011 at 4:44 PM, Joe Ferraro <jferraro at gmail.com> wrote:
Although I hate to mention it... I have about 30 micro PDP 11/83's sitting
in a lab right beside me; unfortunately they do not (yet... nor might they
ever) belong to me... are they, in fact, "rare"?
On Thu, Jul 14, 2011 at 3:49 PM, Mark Wickens <mark at wickensonline.co.uk>
wrote:
Are the MicroPDPs (desktop, deskside, rackmount) rare beasts? They seem to
be of a fairly hobbyist-friendly size, although presumably they are less
expandable (much like a VAXstation versus VAXserver I would imagine)
Mark.
Hello!
Joe, what's going to happen to them when they become redundant, as the
English would put it?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Fri, Jul 15, 2011 at 1:13 PM, John Wilson <wilson at dbit.com> wrote:
From: "Steve Davidson" <jeep at scshome.net>
This is simple. If the backplane has 2 slots per row then it is a QBUS
(/2 variant). If it has 4 slots per row then it is also QBUS but could
be either 18-bit or 22-bit - the part number on the side of the
backplane will tell you for sure. If the backplane has 6 slots per row
then it is UNIBUS.
In the wild this seems to be true, but the DDV11B (a hex-high Q-bus
backplane) existed at least in the minds of the handbook authors
(see p. 159 of Microcomputer Interfaces Handbook 1980).
John Wilson
D Bit
Hello!
John W, do you recall what sort of wire wrapping board you sent me? I
keep thinking its a typical Q Bus one, but is it?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
From: "Steve Davidson" <jeep at scshome.net>
This is simple. If the backplane has 2 slots per row then it is a QBUS
(/2 variant). If it has 4 slots per row then it is also QBUS but could
be either 18-bit or 22-bit - the part number on the side of the
backplane will tell you for sure. If the backplane has 6 slots per row
then it is UNIBUS.
In the wild this seems to be true, but the DDV11B (a hex-high Q-bus
backplane) existed at least in the minds of the handbook authors
(see p. 159 of Microcomputer Interfaces Handbook 1980).
John Wilson
D Bit
