Ticket #7305 (closed defect: obsolete)

Opened 8 years ago

Last modified 23 months ago

VBoxVideo fails on NT 4.0 (with workaround)

Reported by: mbehensky Owned by:
Priority: major Component: guest additions
Version: VirtualBox 3.2.8 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description (last modified by aeichner) (diff)

I just installed virtualbox 3.2.8 on Mandriva Linux 2009.1. I backed up my old NT Server 4.0 (sp6a) hard drive and installed the image into virtual box. Much to my amazement, the system just booted up the first time I tried it.

I installed the 3.2.8 additions from the .iso file, and everything worked with the exception of the video driver. It complained on reboot, saying 'The currently selected display driver can not be used. It is not available or not congigurated correctly. The System was started using the standard VGA driver ...'

I messed around for hours, removing the driver and re-installing it, extracting the driver files directly and installing them, installing the standard VGA driver and re-installing, and trying old versions (3.2.6 and 2.2.4) without success.

Finally, I got it to work with the following procedure:

  1. Install the additions from the .iso
  2. When the system boots back up, just close all the display warning windows. Go to Control Panel->Devices and set the startup type to "Disabled" on the VBoxVideo Driver
  3. Boot the system back up and go back to Control Panel->Devices. Set the startup type to "System" and then start the driver.
  4. Get the display properties. When you select the "Settings" tab the screen will flash like the driver just got activated. The "Color Palette" section won't be blank anymore. Set the palette to "True Color", exit, and reboot the machine
  5. After the machine boots, the driver will be working (at least it was for me).

I'm not sure what is going on, but I've had similar problems on NT with the drivers for hardware cards if the color palette was initially set to something the driver couldn't support.

Change History

comment:1 Changed 8 years ago by frank

  • Description modified (diff)

I assume that this workaround is necessary because you migrated an existing installation to a VM. A virgin NT4 installation should work fine with the Additions.

comment:2 Changed 23 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use