Thanks for your reply! I tried a complete uninstall/reinstall following carefully the steps in:http://developer.palm.com/index.php?opt
and it still doesn't work. I didn't even install Eclipse.
I've tried pointing VB at an old VMDK file when it's there someplace (and I have no idea what produces that file, it seems to just magically appear at some point in some random place), but that's when it comes up without the Pre video mode available (as I said before).
However, after following the steps closely (and deleting all the .VirtualBox directories), the VMDK and ISO files are nowhere to be found. If I start VB, it can't find any bootable media.
After installing the SDK, is there some step that I've missed that needs to be run to provoke the SDK into producing the VMDK and ISO files in the proper format?
Woops! I just found the newly-created .VirtualBox with the ISO/VMDK images under my C:\exe area, why it got put there or when I have no idea. But the VB program wants to find it under my C:\emacs area, so there's one under there too, but the latter has no VMDK image. So when I point the VB storage pointer over to the VDI file under the C:\exe area which has the VMDK/ISO file, it still says no bootable media found. If I point it to the VMDK file there, when I try to start VB, it hangs in the virtual box window and says [Running] but nothing ever displays. If I cut/paste the .VirtualBox area from my emacs area to the exe area and try to recreate a new virtual machine, it is still looking for the path to emacs.
It appears that the SDK is creating the .VirtualDBox area under one directory, and VB is looking for it under another directory and I can't convince either to use the other directory, and moving the file from one place to another doesn't work.
Help! Somebody must know what's going on.