> BOOTMGR> boot
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0, Sig:0x24534D56, Exp:0x24534D56
> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.

(also posted to VSI OpenVMS Forum)

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

On 4/15/22 12:44 PM, Mark Daniel wrote:
>> BOOTMGR> boot
>> Booting...
>> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
>> 100%
>> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0,
>> Sig:0x24534D56, Exp:0x24534D56
>> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
>> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
>> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
>> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.
>
> (also posted to VSI OpenVMS Forum)

It worked fine for me under VirtualBox 6.1. I have the optical drive
defined with the AHCI controller on SATA port 0. The host is macOS
12.3.1 and the checksum and byte count of the 9.2 installer image are:

$ cksum X86E92OE.ISO
2336133403 1324777472 X86E92OE.ISO

On 16/4/22 4:21 am, Craig A. Berry wrote:
>
> On 4/15/22 12:44 PM, Mark Daniel wrote:
>>> BOOTMGR> boot
>>> Booting...
>>> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
>>> 100%
>>> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0,
>>> Sig:0x24534D56, Exp:0x24534D56
>>> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
>>> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
>>> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
>>> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.
>>
>> (also posted to VSI OpenVMS Forum)
>
> It worked fine for me under VirtualBox 6.1.  I have the optical drive
> defined with the AHCI controller on SATA port 0.  The host is macOS
> 12.3.1 and the checksum and byte count of the 9.2 installer image are:
>
> $ cksum X86E92OE.ISO
> 2336133403 1324777472 X86E92OE.ISO

Thanks Craig.

macOS 10.14.6 VirtualBox Version 6.1.32

macpro:~ mark$ cksum X86E92OE.ISO
2336133403 1324777472 X86E92OE.ISO

Seems as if the 9.2 ISO (VMS_BOOTMGR?) is device order sensitive.

With the ISO at dka0 (your config, port 0), with device specification
(quoted to prevent wrapping):

> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA100 (HD) = FS2 UEFI: V9_1_A OpenVMS: X86SYS 16384 MB SATA Disk
> DKA0 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
>
> BOOTMGR> boot dka0
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
8< snip 8<

And without device specification:

> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA100 (HD) = FS2 UEFI: V9_1_A OpenVMS: X86SYS 16384 MB SATA Disk
> DKA0 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
>
> BOOTMGR> boot
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%8< snip 8<

But with my original config (ISO at port 2):

> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
> DKA200 (DVD) = FS2 UEFI: E9_2 OpenVMS: None 1263MB SATA DVD
>
> BOOTMGR> boot dka200
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0, Sig:0x24534D56, Exp:0x24534D56
> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.

This was *not* the behaviour with the 9.1A ISO (and still isn't):

> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
> DKA200 (DVD) = FS2 UEFI: V9_1_A OpenVMS: None 918 MB SATA DVD
>
> BOOTMGR> boot dka200
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%8< snip 8<

Without device specification, still boots the install media:

> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
> DKA200 (DVD) = FS2 UEFI: V9_1_A OpenVMS: None 918 MB SATA DVD
>
> BOOTMGR> boot
> BOOT
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%8< snip 8<

So there appears to be a change in behaviour between the 9.1-A and 9.2
ISOs, requiring 9.2 to be at dka0 (or some such).

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

On 4/15/2022 3:44 PM, Mark Daniel wrote:

> So there appears to be a change in behaviour between the 9.1-A and 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).

I'm not aware of that restriction; file a case with us.

--

-- Rob

On 16/4/22 5:19 am, Robert A. Brooks wrote:
> On 4/15/2022 3:44 PM, Mark Daniel wrote:
>
>> So there appears to be a change in behaviour between the 9.1-A and 9.2
>> ISOs, requiring 9.2 to be at dka0 (or some such).
>
> I'm not aware of that restriction; file a case with us.
>

Sure Rob. Exactly how is that gone about again? :-) I'm an ISV.

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

In your "original config (ISO at port 2)", before you boot, check the
version of the boot manager.

It is shown at the top of the screen. It can be displayed with the
SYSINFO command.

It needs to be a version V9.2 boot manager.

Also, before you boot, check the BOOT MANAGER DEVICE output. It should
show the E9.2 DVD. That's where the device where the V9.2 boot manager
lives.

By the way, your DKA0 (in the original config) looks small.

On 4/15/22 22:05, Mark Daniel wrote:
> On 16/4/22 5:19 am, Robert A. Brooks wrote:
>> On 4/15/2022 3:44 PM, Mark Daniel wrote:
>>
>>> So there appears to be a change in behaviour between the 9.1-A and
>>> 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).
>>
>> I'm not aware of that restriction; file a case with us.
>>
>
> Sure Rob.  Exactly how is that gone about again?  :-)  I'm an ISV.
>

On 16/4/22 6:13 am, hb wrote:
> In your "original config (ISO at port 2)", before you boot, check the
> version of the boot manager.
>
> It is shown at the top of the screen. It can be displayed with the
> SYSINFO command.
>
> It needs to be a version V9.2 boot manager.

X86E92OE ISO on port 2; quoted to prevent wrapping:

+++++++++++++++++++++++++++++++++++++++++++++++

> BOOTMGR> DEVICES
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>>>> Press any key to continue:
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
------------------------------^^^^^^^^^^^^

> DKA200 (DVD) = FS2 UEFI: E9_2 OpenVMS: None 1263MB SATA DVD
>
> BOOTMGR> SYSINFO
>
> OpenVMS Boot Manager: V9.1-x Build 101 - Jul 13 2021
------------------------^^^^^^^^^^^^^^^^

>>>> Enter 'Y' to display decoded CPU ID information:
> PROCESSORS: Actual: 1, Max: 64, SMP? Yes, Hyperthreads? No
> Type: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
>
> PERFORMING HARDWARE COMPATIBILITY TEST.
>
> Checking Required Processor Features:
> PASSED
>
> Checking Optional Features:
> - No x2APIC (Extended Advanced Programmable Interrupt Controller)
> - No XSAVEOPT instruction
> - No TSX-HLE instruction
> - No TSX-RTM instruction
> - No UMIP instruction
> FAILED
>
> **********************************************************************
> This machine lacks some features used by OpenVMS, BUT CAN CONTINUE.
> **********************************************************************
>
> **********************************************************************
> This machine satisfies the requirements for running OpenVMS
> **********************************************************************
>
>>>> Enter 'E' to Exit or any other key to decode the CPU ID fields:
>
>>>> Enter 'Y' to display APIC information:
>
>>>> Enter 'Y' to list ACPI Tables:
>
>>>> Enter 'Y' to display SMBIOS Tables:
>
>
> BOOTMGR> BOOT DKA200
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0, Sig:0x24534D56, Exp:0x24534D56
>
> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
>
> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
>
> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
>
> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.

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

X86E92OE ISO on port 0; quoted to prevent wrapping:

+++++++++++++++++++++++++++++++++++++++++++++++

> BOOTMGR> DEVICES
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA100 (HD) = FS2 UEFI: V9_1_A OpenVMS: X86SYS 16384 MB SATA Disk
> DKA0 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
------------------------------^^^^^^^^^^

> BOOTMGR> SYSINFO
>
> OpenVMS Boot Manager: V9.2 Build 112 (Feb 4 2022)
------------------------^^^^^^^^^^^^^^

>>>> Enter 'Y' to display decoded CPU ID information:
> PROCESSORS: Max Supported: 64, SMP? Yes, Hyperthreads? No
> Type: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
>
> PERFORMING HARDWARE COMPATIBILITY TEST.
>
> Checking Required Processor Features:
> PASSED
>
> Checking Optional Features:
> - No x2APIC (Extended Advanced Programmable Interrupt Controller)
> - No XSAVEOPT instruction
> - No TSX-HLE instruction
> - No TSX-RTM instruction
> - No UMIP instruction
> FAILED
>
> **********************************************************************
> This machine lacks some features used by OpenVMS, BUT CAN CONTINUE.
> **********************************************************************
>
> **********************************************************************
> This machine satisfies the requirements for running OpenVMS
> **********************************************************************
>
>>>> Enter 'Q' to Quit or any other key to decode the CPU ID fields:
>
>>>> Enter 'Y' to display APIC information:
>
>>>> Enter 'Y' to list ACPI Tables:
>
>>>> Enter 'Y' to display SMBIOS Tables:
>
>
> BOOTMGR> BOOT DKA0
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
>
>
> _______________________________________________
>
> GRAPHICAL OUTPUT HAS BEEN SUSPENDED
> USE A TERMINAL UTILITY FOR ACCESS
> _______________________________________________
>
> VSI Primary Kernel SYSBOOT Mar 8 2022 14:47:10
>
> %SYSBOOT-I-VMTYPE, Booting as a VirtualBox (tm) Guest
>
>
> VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2
> Copyright 2022 VMS Software, Inc.
>
> MDS Mitigation active, variant verw(MD_CLEAR)
>
> %SMP-I-CPUTRN, CPU #2 has joined the active set.
> %SMP-I-CPUTRN, CPU #1 has joined the active set.
>
>
>
> Installing required known files...
>
> Configuring devices...
>
> %EIA0, Link up: 1000 mbit, fdx, flow control (rcv only), 08-00-27-1C-76-CA
>
>
> ****************************************************************
>
> 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
> 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
>
> Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 9
>
> Shutting down the system
>
>
>
> VSI Dump Kernel SYSBOOT Mar 8 2022 14:47:10
>
> ** Error logs not dumped, system disk is write locked
> SYSTEM SHUTDOWN COMPLETE
>
> **** Hit any key to reboot system ****

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

So the upshot appears to be the VMS_BOOTMGR is taken from the first
bootable device (FS0...FSn), meaning you need to have the latest version
first in the device list.

> Also, before you boot, check the BOOT MANAGER DEVICE output. It should
> show the E9.2 DVD. That's where the device where the V9.2 boot manager
> lives.
>
> By the way, your DKA0 (in the original config) looks small.

I cloned the entire VM so that represents the system disk of 9.1-A. I
was planning to clobber it (the clone device) with 9.2 install. Which I
can now proceed with :-)

> On 4/15/22 22:05, Mark Daniel wrote:
>> On 16/4/22 5:19 am, Robert A. Brooks wrote:
>>> On 4/15/2022 3:44 PM, Mark Daniel wrote:
>>>
>>>> So there appears to be a change in behaviour between the 9.1-A and
>>>> 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).
>>>
>>> I'm not aware of that restriction; file a case with us.
>>>
>>
>> Sure Rob.  Exactly how is that gone about again?  :-)  I'm an ISV.

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

On 16/4/22 9:16 am, Mark Daniel wrote:
8< snip 8<
> So the upshot appears to be the VMS_BOOTMGR is taken from the first
> bootable device (FS0...FSn), meaning you need to have the latest version
> first in the device list.

*** NOT (strictly) TRUE - RTFM ***

The "2.1. Booting the Virtual Machine" states:

1. The following figure shows the graphics console that comes up when
the VM is started. At the Shell> prompt, enter the command map fs* to
display the file systems available on your system.

2. Choose the file system that maps to the .ISO file that you have
downloaded and set up as a CDROM/DVD. The shell sees the .ISO file as a
CDROM, so you need to choose an FSn that is labeled CDROM. In the above
example, we know that fs1 is the .ISO that we want to boot.

3. Knowing that fs1 is associated with the CDROM that is the .ISO, enter
the following command to run the Boot Manager:
fs1:\efi\vms\vms_bootmgr.efi

I must have gotten into the habit of running the BootMgr

Shell> vms_bootmgr

and then booting 9.1-A VMS with a simple

BOOTMGR> BOOT

which was happy as long as DKA0 (bootable system disk) had the 9.1-A
BootMgr. It was a poor recipe when "upgrading".

And of course...

Had the 9.2 installation had a non-bootable .VDI (DKA0) the previous
BootMgr would not have been invoked and the simple BOOT would have
picked up the most recent ISO as DKA200 (only bootable device).

Confirmed that suspicion (quoted to prevent wrapping):

++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Shell> vms_bootmgr
8< snip 8<
> BOOTMGR> DEVICES
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA200 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
>
> BOOTMGR> BOOT
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
>
>
> _______________________________________________
>
> GRAPHICAL OUTPUT HAS BEEN SUSPENDED
> USE A TERMINAL UTILITY FOR ACCESS
> _______________________________________________
>
> VSI Primary Kernel SYSBOOT Mar 8 2022 14:47:10
>
> %SYSBOOT-I-VMTYPE, Booting as a VirtualBox (tm) Guest
>
>
> VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2
> Copyright 2022 VMS Software, Inc.
8< snip 8<
-------------------------------------------------------

Couple of gotchas here.

But not suspect, only expected behaviour it seems.

My regrets Rob.

>> Also, before you boot, check the BOOT MANAGER DEVICE output. It should
>> show the E9.2 DVD. That's where the device where the V9.2 boot manager
>> lives.
>>
>> By the way, your DKA0 (in the original config) looks small.
>
> I cloned the entire VM so that represents the system disk of 9.1-A.  I
> was planning to clobber it (the clone device) with 9.2 install.  Which I
> can now proceed with :-)
>
>> On 4/15/22 22:05, Mark Daniel wrote:
>>> On 16/4/22 5:19 am, Robert A. Brooks wrote:
>>>> On 4/15/2022 3:44 PM, Mark Daniel wrote:
>>>>
>>>>> So there appears to be a change in behaviour between the 9.1-A and
>>>>> 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).
>>>>
>>>> I'm not aware of that restriction; file a case with us.
>>>>
>>>
>>> Sure Rob.  Exactly how is that gone about again?  :-)  I'm an ISV.

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.

On 16/4/22 5:35 am, Mark Daniel wrote:
> On 16/4/22 5:19 am, Robert A. Brooks wrote:
>> On 4/15/2022 3:44 PM, Mark Daniel wrote:
>>
>>> So there appears to be a change in behaviour between the 9.1-A and
>>> 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).
>>
>> I'm not aware of that restriction; file a case with us.
>>
>
> Sure Rob.  Exactly how is that gone about again?  :-)  I'm an ISV.

Just received new reading glasses but that's not my excuse this time.

Was just puddling around on the https://sp.vmssoftware.com/ page and
think I've always been distracted by the pull-down menus and never
explored the icons on the far right (apart from using "Log out"). The
slightly obscured pen-and-paper icon reveals "Log a support issue". D'oh!

--
Anyone, who using social-media, forms an opinion regarding anything
other than the relative cuteness of this or that puppy-dog, needs
seriously to examine their critical thinking.