21 Mar
2025
21 Mar
'25
4:19 p.m.
I have DECnet Phase V set up on my x86 community package running VMS 9.2-2,
mainly because it did not come with Phase IV. That pushed me into learning
Phase V "stuff" after 30 years of managing to avoid it.
I do find that it takes a few minutes after booting for it to recognise
that Phase IV nodes exist on the LAN, but that it works at a sensible speed
after that.
I only have the one Phase V system, but several Phase IV systems, so
perhaps it is expecting to find other phase V nodes "out there" and getting
confused when there are none.
Cheers
Peter Allan
On Thu, 20 Mar 2025 at 22:01, Zane Healy <healyzh(a)avanthar.com> wrote:
On Mar 20, 2025, at 9:50 AM, Johnny Billquist
<bqt(a)softjar.se> wrote:
I've never heard of that problem that I can remember. But I do know that
in general Phase V can be considered a significant downgrade to phase IV.
Not sure why anyone really would want to run it. But there are some who do.
Johnny
I have to agree. MONK originally ran Phase V, and I *upgraded* it to
Phase IV something like 25 years ago.
Zane
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se