I have been trying to install virtualbox v.2.0 (64 bit) on my vista machine
(64 bit).
After creating the virtual hard drive I get the message "Virtualbox.exe has stopped working." I also get the following program details:

You have gotten farther than me. I cannot even get it to install on my Vista 64, just like with all the previous version it just will not install. It starts the install and then gets to one point then starts to rollback with "Sun xVM VirtualBox Setup Wizard ended prematurely".

Somehow I have managed to get as far as trying to install Windows in the VM. However whenever I click on auto install I get the message:
" FATAL: Could not read from the host medium? System halted.
What does this mean? What should I do?

@lierre: Which size did you use for your newly create hard disk? If the number is odd (like 25 GB), the 2.0 GUI will crash. This bug will be fixed in the next maintenance release. As a workaround please use an even number (22 or 24 GB for example) for it.

Hello,
The set up suggested 1024 MB, so that is what I did.
I have now moved on (somehow) from that problem and hae now encountered these. First, the settings and delete boxes are greyed out.
Second, I get a black screen that says "Virtualbox Temporary boot device selection"; it then lists the following:
Detected Hard Disks:
IDE Controller:
1) Primary Master
Other boot devices:
f)Floppy
c) CD-Rom
l)LAN

pentagonik wrote:@lierre: Which size did you use for your newly create hard disk? If the number is odd (like 25 GB), the 2.0 GUI will crash. This bug will be fixed in the next maintenance release. As a workaround please use an even number (22 or 24 GB for example) for it.

Okay...if you created a new hard disk image that includes a decimal number like 1.2 GB or 1.6 GB or images as small as 85 MB or 540 MB, will the Virtual Box 2.0 GUI crash as well?

If you want to be safe, use 1.6.6 or an older version to create the VDI files. You can install VB inside your Guest VM, but it won't allow you to run any VMs you create. Move the created VDI to the host using Shared Folders or network shares and use it in 2.0.
We do suggest that unless you really need the extra features of 2.0, to stick to 1.6.6.

Sasquatch wrote:If you want to be safe, use 1.6.6 or an older version to create the VDI files. You can install VB inside your Guest VM, but it won't allow you to run any VMs you create. Move the created VDI to the host using Shared Folders or network shares and use it in 2.0.We do suggest that unless you really need the extra features of 2.0, to stick to 1.6.6.

I have a feeling that Sun needs to made a maintenance release to fix a bug that will not allow the virtual machines to be run off of another storage device such as a USB hard drive or USB memory stick. Because the VDI images were created under v1.6.4 and v1.6.6 is the last stable release for the time being.

The internal hard drive is riddled with 280 reallocated sectors that could attempt to corrupt the data on the VDI file if moved in the near future.