I've been playing around a little with out 8650 lately, and finally got
irritated enough at the limitation of some diagnostics that I decided to
read up a bit.
The problem is that we have a lot of diagnostics for the 8650, however,
they are from around 1990, when the console pack was created. Some
devices, such as RA73 (of which we have a bunch connected) are newer
than that, so our diagnostics do not know about them, and therefore
ignore them.
Reading up on this turned out that the autosized tool, called EVSBA, is
generic and used on all models. And we have version 7.2 on our pack, and
we need to have version 7.5 in order to have it handle RA73 disks.
Reading more, it sounded like these programs would normally live in VMS
as well, under [SYS0.SYSMAINT]. However, the VMS I have, which was
installed from the 7.3 CD distribution, have nothing in [SYS0.SYSMAINT],
so now my obvious question is, do anyone have "modern" versions of the
diagnostics programs?
EVSBA would be one obvious one I'm looking for, but EVRL* which are all
the tools for RA disks are also interesting. I'm not sure if our current
versions would handle an RA73 either.
If people have other bits, that would also be nice. If they are on
HECnet, even better, since if I boot VMS, our 8650 is also on HECnet, so
that would make copying really easy. But if you have them somewhere
else, that's also usable.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Greetings,
Time to update those node databases ... BAN.AI Public Access Multics, the premier public access Multics system, has joined HECnet, as node number 1.770 (BANAI).
It's just an initial implementation (based on the Linux DECnet source) and performance is lacking, but I hope to get things better optimized and support more services in the near future.
There are currently 16 outgoing channels for HECnet connections, and up to 128 dynamically allocated incoming login channels.
Outgoing connections to HECnet are allowed only for registered users, but any incoming login from the Internet or HECnet is permitted, including anonymous Guest users.
For more information, you can visit https://ban.ai/, ssh or mosh to dps8 at m.trnsz.com, or SET HOST to BANAI/1.770.
Feel free to request an account or ask any questions.
--
Jeffrey H. Johnson
jhj at trnsz.comhttps://ban.ai/multicshttp://mim.update.uu.se/hecnet?node=BANAI
.. on HECnet?
Igor Mirvaleev
John Floren
Thierry Dusset
or their nodes ?
2.100 (SEGUE) unreachable
2.150 (LOKI) unreachable
2.201 (SELENE) unreachable
2.300 (LEXX) unreachable
2.301 (DREAM) unreachable
2.302 (BEE) unreachable
I'm looking to purge some obsolete nodes from my database.
Bob
OK, so who is "SANYAL" at node 1.550? If you'd like an account on my RSTS/E
system, all you need do is ask. I'm one of those sys admins who actually
reads his event logs. :)
Regards,
Mark
Hi,
I'm off to Seattle in a few days for a bit of a break. I'll be visiting the Living Computers Museum there to play with their VAX 785, DECSystem 20, etc. while sitting right next to them :)
There may be photos...
Just FYI
Keith
Hi all
Anyone know the turn around time for licenses for OpenVMS these days?
Like a dummy I let mine expire and put in for them at the usual spot.
However, it's been more than 36 hours and I've seen nary a peep. :(
However, my PMDF and Multinet licenses are still valid, so the mail still
rolls in....ha.
Fred
Johnny Billquist wrote:
> Object 23 is the predecessor of CTERM. I'm not entirely sure of the name
> of that protocol.
>From some code:
[ASCIZ |NRT|] ;23 NRT program
Supported by tops10 and 20. If you need to do testing you can use
my machines, athena (20) and topsy (10).
--another Johnny
. is down temporarily. It is a simulation and I'm upgrading the Ubuntu
host OS on that machine. With Linux, nothing actually works "out of the
box" but most everything can be made to work with some effort. I'm still
on that last step. I should have everything fixed up and LEGATO will be
back today or tomorrow.
Bob
HECnet area 19 has returned. It has only one node (SGC::) at the moment. DECnet is the only network stack functioning. Multinet is not yet available due to problems with SG1::.
Johnny?s software bridge has been started so it should only be a matter of time before the rest of HECnet sees SGC::. An old set of sources to MWATCH (the system that controls address changes for Multinet) can be found in:
SGC::[.MWATCH]
It has some issues but works well enough if needed.
-Steve
Sent from my iPad
Hi,
I suppose this happens a lot with newcomers to HECnet, especially when there are long periods of apparent silence. I'm currently reconciling remembering the '80s while listening to (having read several times) Ready Player One audio book (incidentally, I thought the recent film was... OK... but nothing like the book), playing around in VAX/VMS on a 86x0 SIMH simulator and doing 'real world' work in .NET (C#) for a salary, goggling in almost disbelief at the megabytes required to do what we used to be able to do in kilobytes.
I have a vague recollection of TOPS-20 (possibly TOPS-10) so I built a SIMH environment.
I have a vague recollection of RSTS/E so... etc..
I have no recollection of RSX-11M but I tried.... and yeah, etc...
It seems it's VMS, VAX architecture (Alpha seems so new-fangled by comparison) for me.
(I'm sooo glad Itanium is dying by the way - what an evolutionary dead-end - but what do I know - 'Itanic' seemed prophetic)
Do any of you remember when UK Academia connected its universities together with X25 and 'coloured books' software? Yellow book was the transport, extending the addressing beyond the 12 digit DTE address, so you ended up with 000010500401.FTP.MAIL for example, to send Greybook mail via Bluebook FTP protocol. Redbook was to do with job transfer (remote batch job entry and processing, reporting). Pinkbook (I kid you not) was X25 over Ethernet.... And for a short while, I had set up X25 over Ethernet for DECnet between departmental microVAXen to the university's VAXcluster.
Well, getting to the point, the 'coloured books' software on VMS was rather monolithic so I began the task of splitting it up. First, I wrote a device driver to create a pseudo-device to handle opening a Yellowbook connection. From then on, using the queue/batch system for processing FTP requests etc.. I can remember it all but it seems so pointless trying to recreate past 'glories'.
When (in university days) you share a vaxcluster with at least 40 concurrents students EDTing then ALGOL68ing their programming assignments, it was fun to write a kind of 'TELL <userid> message' which mailbox'd a message to a central server which worked out if they were on the local node or somewhere else in the cluster, passed the message along and then broadcast it to the target user's logged in terminal.
Incidentally, I'm missing Algol68RS for VAX/VMS - not part of the hobbyist programme possibly because it was never a DEC/Compaq/HP product)....
Though why neither Bliss32 (in which I wrote the above device driver and support for Yellowbook) nor VaxLisp (don't ask why I would like this) are part of the hobbyist programme, I have no idea.
So, what am I doing now? Apart from working in the real world, I'm resurrecting the Star Trek game I wrote in Ada ('83) using SMG$ routines - a more or less realtime version of the turns-based versions you see written in BASIC. Sad? Probably. I don't care. I'm reliving some of my happiest times. I may retreat to VAX Pascal if it proves too much.
I'd still like VAX/VMS Algol68RS, VAXLisp and Bliss32.... because, well, just because.
Sorry
Keith
