Did you mount the image in an odd position in VMware? A normal boot drive is hda
In ATA terms, hdd is the slave drive on the second controller
What does the GrUB root() command in menu.lst say?
At least that's consistent. I don't know why that boot menu option would not work
Can't you mount the image as primary master in VMware?
I don't think I had the choice
You mount it somewhere when you create it, don't you?
Was watching Arnold's riots
I've re-installed yet again and gotten it to work by selecting the first controller - for some reason the installation defaults to putting the HD on controller 1 as the second device - the CD being the first on the same controller
I guess the logic in grub should be able to find it even on the second controller, no? In any case, it works now with the first menu option
btw, confirmed that the screen resolution isn't persisted
even with a clean shutdown
More about the riots in Chit Chat
Do the virtual desktops work for switching resolution, as described in the Welcome?