Code: Select all
As provided, the new "community.vmdk" "Disk DescriptorFile"
specifies:
ddb.adapterType = "ide"
The environment here is VMware Fusion Player Version 13.5.1
(23298085) on a Mac Pro 2013 with Sonoma 14.4.
Virtual Machine > Settings... > Add Device... > Existing Hard Disk
(specifying "<path/>community.vmdk" as the "File name:") created "Hard
Disk (IDE)" along side the existing "Hard Disk (SATA)" (where the
existing/old VMS installation resides). This apparently was
unsatisfactory to "VSI OpenVMS Boot Manager: V9.2-x Build 136", which
complained:
%VMS_BOOTMGR-W-DEVICE, Ignoring ATAPI device...
The EFI device list was:
EFI VMware Virtual SATA Hard Drive (0.0)
EFI VMware Virtual IDE Hard Drive (IDE 0:0)
EFI VMware Virtual SATA Hard Drive (1.0)
EFI VMware Virtual SATA Hard Drive (2.0)
[...]
In the Virtual Machine > Settings..., changing the "Bus type" on
"IDE Hard Drive" to "SATA" (after shutting down the VM) changed
"Hard Disk (IDE)" to "Hard Disk 2 (SATA)", which changed the EFI device
list to:
EFI VMware Virtual SATA Hard Drive (0.0)
EFI VMware Virtual SATA Hard Drive (3.0)
EFI VMware Virtual SATA Hard Drive (1.0)
EFI VMware Virtual SATA Hard Drive (2.0)
[...]
DKA300 was now visible to VMS (and bootable). ("SATA Hard Drive
(1.0)" and "SATA Hard Drive (2.0)" are what VMware calls "CD/DVD (SATA)"
and "CD/DVD 2 (SATA)", two VMS installation DVDs.)
The butt-pain associated with configuring everything needed to use
the software on the new VMDK didn't seem attractive, so I mounted the
new VMDK disk:
mount /noass /system DKA300: V922
and copied (the small but non-empty)
DKA300:[SYS0.SYSCOMMON.SYSEXE]LMF$LICENSE.LDB to the corresponding spot
on my existing system disk.
This might do for a while, but having no access to patches or product
kits is a BIG step down from the old scheme. Configuring a VMS system
to make it useful is not so much fun that I'm eager to do it annually on
every system.