Code: Select all
Just more whiny complaints.
Recently, I managed somehow to confuse VMware Fusion Pro 13.5.2 into
configuring both a SATA CD/DVD drive and an equivalent SCSI CD/DVD drive
(which was invisible in the VM Settings panel). The spurious SCSI
adapter ("device type HP LSI1030 Ultra320 SCSI") appeared in VMS as
PKA0, so the legitimate SATA devices were promoted to PKBx, DKBx, ...
I used the "B" devices for a while, but eventually I found the
spurious "scsi0" lines in the ".vmx" file, and deleted them.
After telling the BOOT MANAGER to use DKA0 instead of DKB0, all went
as expected, except that the SSH server failed to start. (That's
"OPENSSH V8.9-1G" on the Community VMDK.)
That was because SYS$STARTUP:SSH$DEFINE_ROOT.COM was created to use
the physical system disk device name ("V89$DKB0") instead of something
more helpful, like, say, "SYS$SYSDEVICE":
$ DEFINE/SYSTEM/EXEC/NOLOG SSH$ROOT V89$DKB0:[SYS0.SYSCOMMON.OPENSSH.]/TRANS=CONCEALED
Editing (EDIT /TPU) this file seemed to work, except for the usual
startling/tachistoscopic message, "File format is being converted to a
supported type", thanks to:
Record format: VFC, 2 byte header, maximum 0 bytes, longest 86 bytes
Record attributes: Print file carriage control
Is someone using PIPE as if this were UNIX, or what?
