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

[babydr]

@rjolbrich , ^] is to get out of a true telent session , to allow one to enter telnet's interior commands .
As "jreagan" mentioned the systems as they are setup at this time are not using telnet to communicate but are in the mode known as RAW .
I'd suggest forget the ^] area at this time .
Hth , JimL

[rjolbrich]

more info,


In the PuTTy settings under Terminal under Keyboard there is

Shift/Ctrl/Alt with the arrow keys

which defaults to

Ctrl toggles app mode.

This sounds relevant, but I'm not sure it is working.

[pjacobi]

^] works with the TELNET app on VMS/Linux/Mac.

For Putty, use the GUI to change session parameters.


Paul A. Jacobi
VMS Software

[rjolbrich]

I went ahead with the installation and it was successful.
The missing ctrl-] was not needed!


Next problem.
I can't get a shell prompt.
Nothing but bootmgr. "?" works as do most of the summarized commands.
Can't use the EDIT command to setup an auto-boot.
Invalid or incomplete command error.
If I try EXIT it simply returns to bootmgr.
Nothing but uppercase letters are available in bootmgr.
I've got efi on and secure boot off in VirtualBox SETTINGS > MOTHERBOARD
I think I've got to this point without ever seeing a shell prompt!

Any ideas?

[sms]

Code: Select all

> I can't get a shell prompt.

   "can't" is not a useful problem description.  It does not say what
you did.  It does not say what happened when you did it.  As usual,
showing actual actions (commands) with their actual results (behavior,
error messages, ...) can be more helpful than vague descriptions or
interpretations of what does _not_ happen when you do something
invisible.

   The advice here worked for me:

      https://forum.vmssoftware.com/viewtopic.php?f=37&t=8573#p17967

      To enter the UEFI boot manager, type BOOTMGR> EXIT and hit <ESC> a
      couple of times until the UEFI menue shows up.

   That is, at the "BOOTMGR> " prompt, put in an "EXIT" command, and
immediately hit <ESC> a few times.

   Also, see the VSI OpenVMS x86-64 Boot Manager User Guide:

      https://docs.vmssoftware.com/vsi-openvms-x86-64-boot-manager-user-guide-921/#d0e1009

(Specifically, the end of section "3.2.1. Automatic Launching".)

[spoofy]

I went ahead with the installation and it was successful.
The missing ctrl-] was not needed!


Next problem.
I can't get a shell prompt.
Nothing but bootmgr. "?" works as do most of the summarized commands.
Can't use the EDIT command to setup an auto-boot.
Invalid or incomplete command error.
If I try EXIT it simply returns to bootmgr.
Nothing but uppercase letters are available in bootmgr.
I've got efi on and secure boot off in VirtualBox SETTINGS > MOTHERBOARD
I think I've got to this point without ever seeing a shell prompt!

Any ideas?

You need to issue boot command from gui console interface, you can not make this from telnet console session.

[hb]

You need to issue boot command from gui console interface, you can not make this from telnet console session.

Maybe vbox changed, but the last time I used it, I ran it without the GUI:

Code: Select all

$ vboxmanage startvm X86VMS --type headless

and then I connected to localhost:2023

But, as far as I understand, the BOOT command is not the problem. The OP wants to get into the (U)EFI shell to set up/edit an (U)EFI shell script. The question, how to get from the VMS Boot Manager to the (U)EFI shell is already answered, in a "code box". (Depending on your browser and its window you may need to scroll down in the box to see the answer. )

[cct]

No experience with Virtualbox and VMS, but under KVM I just start the VM, then from a terminal session issue the command:
$ virsh console <VM_name>
I can enter the boot comand from there

Chris

[rjolbrich]

Sorry if this is verbose, from the beginning,

I completed an initial installation, setup a system account, and can boot without
problems from the Bootmgr prompt. (BOOT DKA0). I can login to SYSTEM without
problems.

My next task is to setup an auto-boot. To do this I need to edit a startup.nsh file
from the Shell prompt. Up until now I have never seen the shell prompt. When I
start the VM from the GUI a couple of temporary windows are displayed before
the Bootmgr window is displayed. If I type EXIT <cr> a temporary window is
displayed for a half of a second before disappearing and the Bootmgr is
redisplayed. EXIT <esc> <esc> <esc> ... seems to do nothing.

From the docs I know that some systems cannot show a shell prompt. I
have an HP Envy x360 which is relatively new - late 2019. I think I have
the right settings in the VM. I believe I have a TPM chip. I experimented
with the TPM settings but it had no effect on the system's behavior.

Is there an alternate way to create the startup file? That is the only reason
that I need a shell prompt.

[pocketprobe]

On my bare metal machine at the BOOTMGR> prompt, I was able to tell it
BOOTMGR> AUTO B DKA0

And it boots automaticall.