Not finding the boot partition may also be caused by a SATA controller. On real hardware, some SATA systems shift drive numbers. There's a compensation attempt in the Syllable installation troubleshooting options, but that doesn't include the options for VMware
You mean the screen resolution? That is stored when you change it in the Preferences
it doesn't seem to be made permanent, though
Was that when you forced the VM to stop?
no, I think it wasn't retained even when I shut down cleanly
but I'll try again once I'm finished re-installing
That has never happened before. It should mean some corruption in the emulation somewhere
if it was a SATA issue with the boot, would that not make it impossible to find it with the auto find option?
because it does find it, like that
Maybe, but the auto-find option is there for when the static configuration doesn't work. So you're lucky that the next option does work :-)
And it points to the partition number being shifted
did the install again, and have the same boot issue - will try it yet again and see if I can fix it by editing menu.lst - do you think that should work?
Yes, look in the System Manager or df in the terminal what partition number you have, then adapt the menu.lst
The fundamental way to fix it would be to change the VMware emulation to ATA/IDE
I believe it is using ata/ide
df shows /dev/disk/ata/hdd/0
menu.lst has root=/dev/disk/ata/hdd/0
isn't that OK
Did you mount the image in an odd position in VMware? A normal boot drive is hda