24 Jul
2001
24 Jul
'01
2:50 p.m.
After connecting the VT320 to the VAX, I reset the
system password.
Fortunately, this VAX has the "real VMS" (TM) for VAXen on it:
VAX/VMS, and it's a reasonably recent version: 5.5, which was close to
the lastest version of VMS back when I last worked with a VAX for an
employer, back around 1992. :-)
Nothing wrong with newer versions, personally I prefer running 7.2 on my
VAXen, though I do keep one at 5.5 for compiles. Still for systems without
a lot of RAM V5.5-2 choice.
This far, I haven't noticed anything truly
remarkable with regards to
software, although at first glance, it looks like nothing is missing.
Fortunately, someone installed kermit, so that will make things,
such as installing TCP/IP, easier. :-)
You've a couple choices with VMS 5.5, the easiest is the freeware stack
CMUIP, I used it before the V2 Hobbyist program. I'd recommend a TCPIP
stack from Process software, one or both supports V5.5-2.
Also, there's a mention of SQL in one of the text
files that I looked
through, although I didn't notice any database software installed; of
course, I don't know the names of databases using SQL for VAXen.
Most likely either RDB or Oracle.
DECnet is installed and apparently configured, so I
guess this means
that I can use my DEC terminal server with this machine... do I need
to do anything other than connect the terminal server to the VAX and
then use it? I know nothing about DECnet.
Try saying 'connect {hostname}' on the terminal server, and see what
happens. If that doesn't work, you might need to turn on the software that
is needed for LAT.
Of course, there's still the little matter of no
tape drive being
installed in this system, which is not a good thing. I have a TK70
and a TK50, along with a TKQ70 board.
What kind of disk interfaces does it have? For that matter, what model is
this you're talking about? I never got a chance to look at the first
message you posted on this system.
Zane