Esbox_build.593 and Sun VirtualBox version 3.0 is installed to Windows XP.
Start Esbox with empty workspace
 - select Window - Preferences - Esbox - Build Machines
 - select VirtualBox Linux Build Machine
Esbox: "No VirtualBox VMs are registered or detected.  Please ensure the Executable field is valid first."
Change Executable: C:\Program Files\Sun\VirtualBox\VBoxManage.exe
Esbox: "Target address: Invalid address in Target address" and "Virtual Machine:" selection box
is empty.
To be able to select a machine name you need to click "Executable:" or "Command pattern:" field
with mouse.

Date: 2009-11-24 09:30
Sender: Arto Hyvarinen

Verified with Esbox_build.606.

Date: 2009-11-19 16:48
Sender: Ed Swartz

Fixed in ESbox rev 2431

Date: 2009-11-19 15:47
Sender: Ed Swartz

Okay, I figured it out.

Date: 2009-11-19 12:47
Sender: Arto Hyvarinen

Tested with Esbox_build.600
Steps taken:
Start Esbox with empty workspace
 - select Window - Preferences - Esbox - Build Machines
 - select VirtualBox Linux Build Machine
 - Executable field: c:/Program Files/Sun/xVM
VirtualBox/VBoxManage.exe
	!ENTRY org.maemo.esbox.vm.virtualbox 4 0 2009-11-19
14:27:18.006
	!MESSAGE Failed to run VirtualBox manager
	!STACK 0
	org.maemo.mica.common.core.MicaException: Failed to launch:
19.11.2009 14:27:18:
	.$ "c:\\Program Files\\Sun\\xVM VirtualBox\\VBoxManage.exe"
-nologo list vms
 - select Browse...
	!ENTRY org.maemo.esbox.vm.virtualbox 4 0 2009-11-19
14:27:30.177
	!MESSAGE Failed to run VirtualBox manager
	!STACK 0
	org.maemo.mica.common.core.MicaException: Failed to launch:
19.11.2009 14:27:30:
	.$ "c:\\Program Files\\Sun\\xVM VirtualBox\\VBoxManage.exe"
-nologo list vms
 - select VBoxManage.exe from VirtualBox folder and click Open
 - Executable field is now: C:\Program
Files\Sun\VirtualBox\VBoxManage.exe
 - nothing hapens and Virtual Machine box is empty and stays
empty
 - click first Executable field with mouse and then click Virtual
Machine selection box and Esbox runs valid VBoxManage and detects
what machine names are available

Date: 2009-11-19 04:56
Sender: Ed Swartz

I committed a fix in ESbox rev 2424 for a problem I did encounter
when running these steps -- if you follow the steps from a clean
workspace, and the executable is already valid, and you select
a machine name, then edit the executable (again to something
valid), then the machine name would get cleared out.

Let me know if that has any relation to what you saw here.

Date: 2009-11-19 01:14
Sender: Ed Swartz

Could you clarify the steps taken?  Did you use the Browse...
button to select the executable?

There is a short delay after you set the executable before it
detects what machine names are available.  If the selection box
remains empty forever, then VBoxManage might not be working properly.
Is there anything in the Error Log?