[Info-vax] X8691AOE boots OK - X8692OE fails as follows
Mark Daniel
mark.daniel at wasd.vsm.com.au
Fri Apr 15 15:44:10 EDT 2022
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.
More information about the Info-vax
mailing list