virtualbox.org

Host: Windows Server 2000, SP4 & subsequent security patches

I attempted to install the latest version of VB on the above host platform and setup would never complete, all I would get was a brief setup screen from the msi and then all instances of setup would disappear (confirmed by watching the install via Task Manager). I found a brief event in the Event Log that states:
Product: Sun xVM VirtualBox - Installation failed, followed by a short hex code.

I searched the forums and followed some advice to extract the 'big' executable and run the appropriate msi, which I did and then ran into a new error that I needed XP or greater.

I thought that when looking through some of docs that installation was supported on 2K Workstation and Server. Does anyone know?

I also went back to previous builds of 2.2, 2.1 and 1.5, but still encountered the same issue.

Any advice would be appreciated.

Thanks,
Eric

No, W2K hasn't been supported as a host for some time -- at least 1.6.0 and on. If you browse the topic histories some manage to botch 1.6 on to W2K, but as far as 2.0.0 and later goes: forget it.

That would explain it - pretty cut and dried.

Thanks for the clarification.

valkarye wrote:Host: Windows Server 2000, SP4 & subsequent security patches

I attempted to install the latest version of VB on the above host platform and setup would never complete, all I would get was a brief setup screen from the msi and then all instances of setup would disappear (confirmed by watching the install via Task Manager). I found a brief event in the Event Log that states:
Product: Sun xVM VirtualBox - Installation failed, followed by a short hex code.

I searched the forums and followed some advice to extract the 'big' executable and run the appropriate msi, which I did and then ran into a new error that I needed XP or greater.

I thought that when looking through some of docs that installation was supported on 2K Workstation and Server. Does anyone know?

I also went back to previous builds of 2.2, 2.1 and 1.5, but still encountered the same issue.

Any advice would be appreciated.

Thanks,
Eric

Like TerryE said, if you try to install VirtualBox 1.6.2 (or later) on Windows 2000 Professional or any edition of Windows 2000 Server, the installation will fail. To install VirtualBox 1.6.2 (or later), you need to upgrade your host operating system to Windows XP or Windows Vista.

TerryE, are there any plans to drop support for early versions of Windows XP (RTM, SP1/1a, SP2/2c) host in future versions of VirtualBox? I've noticed that Windows XP SP2 will only be supported until 13 July 2010 along with Windows 2000.

ppgrainbow wrote:are there any plans to drop support for early versions of Windows XP (RTM, SP1/1a, SP2/2c) host in future versions of VirtualBox? I've noticed that Windows XP SP2 will only be supported until 13 July 2010 along with Windows 2000.

IIRC, XP need to be at least SP1a for VB to install on it (maybe even SP2). This is because of the same reasons 2000 is dropped. New APIs are available for better performance and new features, like VT-x/AMD-v and using them on a system that doesn't have them, will result in crashes.

Sasquatch wrote:

ppgrainbow wrote:are there any plans to drop support for early versions of Windows XP (RTM, SP1/1a, SP2/2c) host in future versions of VirtualBox? I've noticed that Windows XP SP2 will only be supported until 13 July 2010 along with Windows 2000.

IIRC, XP need to be at least SP1a for VB to install on it (maybe even SP2). This is because of the same reasons 2000 is dropped. New APIs are available for better performance and new features, like VT-x/AMD-v and using them on a system that doesn't have them, will result in crashes.

Thanks for the heads up. Later versions of VirtualBox won't work on Windows XP Service Pack 1, in which Microsoft included the dreaded Java Virtual Machine in its service pack. SP1a removed support for Microsoft Java as a result of the lawsuit from Sun Microsystems.

Also, I don't think that Windows XP Service Pack 1 included APIs such as Intel VT-x/AMD-v. Only Service Pack 1a did.