Couple of additions to the list:
1.403 - RHESUS - HP Integrity rx2600 running OpenVMS 8.3-1H1
1.404 - SAMDEV - Random development node, might be anything from a SIMH VAX to Linux
1.405 - ARIVAX - SIMH-VAX running OpenVMS 8.3
1.410 - FIDOGW - Ubuntu 9.04 (on VMware) with DECNET, running Fidonet-HECnet mail gateway.
Sampsa
On 19 Oct 2009, at 15:35, Bob Armstrong wrote:
Where is PDXVAX still noted as a 4000/VLC?
Well, on my list for one.
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Nobody sent me any corrections ...
Bob
At 1:46 PM +0100 10/19/09, Mark Wickens wrote:
I noted a couple of weeks ago that PDXVAX is listed as a VAXstation
4000/VLC with 40MB of memory. Is this true? If it is, can someone tell
me what memory chips are installed, as I have a 4000/VLC which is
'apparently' maxed out at 24 MB (6 SIMMS)
Regards, Mark (wondering whether the 32MB min. RAM requirement for
ALL-IN-1 is hard and fast)
Where is PDXVAX still noted as a 4000/VLC? The fans went out before everything went crazy for us. It's been a 4000/60 for a while now.
No idea on the RAM requirements for ALL-IN-1. My big problem is that it doesn't seem to want to install on modern versions of OpenVMS/Alpha. You now have me thinking about how I could install it on PDXVAX.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com (primary) | OpenVMS Enthusiast |
| MONK::HEALYZH (DECnet) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
On Mon, 2009-10-19 at 13:46 +0100, Mark Wickens wrote:
I noted a couple of weeks ago that PDXVAX is listed as a VAXstation
4000/VLC with 40MB of memory. Is this true? If it is, can someone tell
me what memory chips are installed, as I have a 4000/VLC which is
'apparently' maxed out at 24 MB (6 SIMMS)
OK, so I managed to answer my own question with this query on PDXVAX:
$ write sys$output f$getsyi("HW_NAME")
VAXstation 4000-60
I guess the VLC got replaced at some point (have to say that the box did
feel a little quick for a VLC :)
Regards, Mark (wondering whether the 32MB min. RAM requirement for
ALL-IN-1 is hard and fast)
Would appear to be only one way to find out...
I noted a couple of weeks ago that PDXVAX is listed as a VAXstation
4000/VLC with 40MB of memory. Is this true? If it is, can someone tell
me what memory chips are installed, as I have a 4000/VLC which is
'apparently' maxed out at 24 MB (6 SIMMS)
Regards, Mark (wondering whether the 32MB min. RAM requirement for
ALL-IN-1 is hard and fast)
I recently came across this: "RFC1762 - The PPP DECnet Phase IV Control Protocol (DNCP)" -- (http://www.faqs.org/rfcs/rfc1762.html)
What kind of software/hardware supports this? Anyone interested in having a play if it's deployable with reasonable effort?
Sampsa
Good idea - done!
Sampsa
On 15 Oct 2009, at 17:13, Fred wrote:
On Wed, 14 Oct 2009, Sampsa Laine wrote:
The obvious thing to add is a HECNETINFO command, that displays this file on a given host - we want this information to be easily accessible from the DCL side as well rather than just the Web, I think.
Could it be as simple as (predicated upon you having this command in the DECNet default directory):
@CHIMPY::HECNETINFO <nodname>
Users could also copy it locally if they saw fit.
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
Looks like you are bouncing between two routers, one of which is faulty
at the moment (PONDUS).
Why you would get to PONDUS, I don't know. I know it is faulty because
adjacency is down. The problem with PONDUS is that it can stop receiving
ethernet packets, but is still sending. There is a bug somewhere inside
the DECnet driver, which I'd like to find, if I just had the sources...
I'll have someone kick on PONDUS on sunday, when someone is physically
close to the machine again.
An endnode normally should pick the router with the highest priority,
which can be heard.
MIM is at 96, and should be picked, unless something else is funny.
PONDUS should only be at 64, even if it is working.
Johnny
Oleg Safiullin wrote:
Hi.
Is something wrong with subj?
At XPEH console (OpenVMS VAX 7.3, non-routing) I seee the following messages (repeated continuously):
--
%%%%%%%%%%% OPCOM 15-OCT-2009 14:56:05.84 %%%%%%%%%%%
Message from user DECNET on XPEH
DECnet event 4.15, adjacency up
On Wed, 14 Oct 2009, Sampsa Laine wrote:
The obvious thing to add is a HECNETINFO command, that displays this file on a given host - we want this information to be easily accessible from the DCL side as well rather than just the Web, I think.
Could it be as simple as (predicated upon you having this command in the DECNet default directory):
@CHIMPY::HECNETINFO <nodname>
Users could also copy it locally if they saw fit.
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
Thanks for the positive feedback!
The obvious thing to add is a HECNETINFO command, that displays this file on a given host - we want this information to be easily accessible from the DCL side as well rather than just the Web, I think.
Sampsa
On 14 Oct 2009, at 20:03, Fred wrote:
On Wed, 14 Oct 2009, Sampsa Laine wrote:
I made a stupid little CGI script that shows the known nodes database and also lets the user request information about a host, and sends out the INFO.TXT file of that host if found.
Very nice!
Definitely saving this one in my hecnet folder for future use. :)
I also have Zane's URL saved as well.
I put an info.txt file in the decnet default directory on MISER earlier today.
Cheers,
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.