World: r4wp

I did choose that option when installing, but I can re-create the 
VM to try to fix a little hassle with the startup menu. What happens 
now is that on the default first option, 'Start Syllable', you get 
an error saying that the selected disk does not exist. Choosing the 
second option, 'Start Syllable (automatic boot drive search), finds 
the OS and boots. I'm not sure what went wron there - I tried to 
install grub to the MBR - basically, I pretty much accepted the defaults 
or suggestions when installing. I'll go through it again just to 
make sure that I didn't mess something up, though, since it doesn't 
take very long.

I will give a quick try at installing 0.6.7 on VMware.

during VM setup, I chose "Other" and 32 bit for the OS choices - 
not sure if that was what I should have chosen

I did the same, but installation stops rapidly when detecting hardware: 
fails to initialize ATA PCI controllers

It fails with the same error whatever VM target I choose.

I'll wait for a proper VM image I guess.

If it's anything like the recent VirtualBox, you probably have to 
change the hardware emulation from a SATA disk controller to an ATA 
one

Adrian, your selection in VMware should work. A generic Linux option 
should also have a good chance of working

well, it did seem to work, except for the boot menu thing

also, is there a way for the desktop size to be remembered?

I'm just re-doing the VM now to try and correct that

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

not SATA

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

In ATA terms, hdd is the slave drive on the second controller

What does the GrUB root() command in menu.lst say?

(hd3,0)

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?

Back later

k

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

riots?

btw, confirmed that the screen resolution isn't persisted

even with a clean shutdown

Odd

More about the riots in Chit Chat

Do the virtual desktops work for switching resolution, as described 
in the Welcome?