Initial OpenVMS 9.2-1 Installation and PuTTy problems

[rjolbrich]

Hello,
I'm attempting my first x86 installation with VirtualBox and PuTTy.
I can get past the first boot before installation with PuTTy.
From the docs:


The TELNET prompt will now show:

VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-1
Copyright 2023 VMS Software, Inc.

[...]

You can install or upgrade the OpenVMS X86-64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS X86-64 distribution media.

You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.

Please choose one of the following:

1) Upgrade, install or reconfigure OpenVMS X86-64 Version E9.2-1
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete Recovery Data
8) Execute DCL commands and procedures
9) Shut down this system

Press and hold CTRL, then press ]. The prompt changes to telnet>. You need to enter the command:

unset crlf

Press CTRL+] again and enter another command:

mode char

If you don't do this, you cannot enter a SYSTEM account password later on.


-----------------------------------------------

I cannot get ctrl-] to give me a telnet prompt.
So I cannot enter the given commands.

I'm new to PuTTy and am not familiar with its settings.
Can someone help me.

Thanks

[m_detommaso]

Try to take a look at the following post and technical documentation, they might help you :

viewtopic.php?f=1&t=8602#p18076
https://docs.vmssoftware.com/docs/vsi-o ... de-921.pdf (chapter of interest: 7.7.2. Using the PuTTY Terminal Emulator).

/Maurizio

[rjolbrich]

Thanks for the reply,

I had tried the telnet selection from the doc in PuTTy exclusively. I still cannot get a telnet prompt.

The RAW selection also results in a problem - the connection is refused a few seconds
after an attempt to open. Is 2023 the proper port? If it would connect, will the RAW selection
and a ctrl-] produce a telnet prompt?

I

[dmjb]

I don't have an answer for your problem, but I think it's worth noting that you are attempting to install the E9.2-1 field test release which has since been replaced by the V9.2-1 production release. For a new install, you are better off grabbing V9.2-1 from the service portal site since some of the layered products/compilers need the newer release.

[jreagan]

I use PuTTY with a raw connect to VirtualBox on my W10 systems. Works for me. If you use Telnet, you need to tell PuTTY to not do local echo/local edit.

[rjolbrich]

Here's the latest:

After starting the VM I opened a Powershell window and used Test-NetConnection
to check the ports status. Port 1023 showed as open while port 2023 was closed.

I'm not a VirtualBox expert, but I found a "Port Forwarding" button under the VM's
network settings under "Advanced". Without being sure I entered the following:

Rule 1
Protocol TCP
Host IP 127.0.0.1
Host Port 2023
Guest IP 127.0.0.1
Guest Port 2023

I again started the VM and the Test-NetConnection showed port 2023 as open.
I opened PuTTy with a RAW connection and the appropriate settings.
I opened the connection and it was NOT refused. However, the PuTTy window
was "frozen" - I could not get any keyboard activity to work. Eventually the
connection timed out.

Am I making progress? I don't know if both IP addresses should be 127.0.0.1!
Should I have to use port forwarding? Any ideas?

[m_detommaso]

I recommend you refer to the VMS x86-64 V9.2-1 Installation Guide (https://docs.vmssoftware.com/docs/vsi-o ... -guide.pdf).

You must configure the Virtualbox VM exactly as documented in the "VSI OpenVMS x86-64 V9.2-1 Installation Guide" (chapters of interest: 2.3 "Creating a VirtualBox Virtual Machine" and 2.3-1 "Completing Your VirtualBox Virtual Machine Configuration").

Your VM must have an active serial port that will be used as the system console.

Below, the configuration of my VM network and serial port:

The "serial port" service will be active only after you have started your VM.

I hope this helps,
/Maurizio

[rjolbrich]

I found my problem thanks to your reminder on serial port settings.
When I moved to the RAW connection I did not change the port to 2023!
Also, I was working from the ramii.org document which did not mention
the proper network settings. Now both telnet and RAW communicate
through PuTTy successfully.

However, the ctrl-] command works in neither telnet or RAW mode.
Could this be a mistake in the ramii.org document. In the PDF you
referenced I see no mention of the ctrl-] command. Should I just
proceed with the installation?

Added in 4 hours 9 minutes 31 seconds:
Following up on the previous post,

The installation guide that I was following is: https://raymii.org/s/blog/OpenVMS_9.2_f ... arted.html.

In it PuTTy is mentioned but I believe it is NOT used. Note that
an alternate terminal app is used. In the image notice that a escape
sequence ^] is used in the terminal window.

Is it possible that the ^] only works in that alternate terminal app
and NOT in PuTTy? If so, does the section that suggests using the ^]
to put the terminal in the proper mode is unnecessary in PuTTY?
Do I even have to worry about the mode and the system password?

As far as the field test vs production release, I downloaded the file
as described in the same guide.

[jreagan]

^] is a TELNET thing. You are using RAW mode.

[rjolbrich]

But I can not get ^] to work in PuTTy telnet mode either.
That's why I question the use of the escape sequence ^] in PuTTy
as opposed to some other terminal app.