VirtualBox

Changes between Initial Version and Version 1 of Ticket #7305


Ignore:
Timestamp:
Aug 11, 2010 6:14:49 AM (14 years ago)
Author:
Frank Mehnert
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7305 – Description

    initial v1  
    77Finally, I got it to work with the following procedure:
    88
    9 1. Install the additions from the .iso
    10 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
    11 3. Boot the system back up and go back to Control Panel->Devices.  Set the startup type to "System" and then start the driver.
    12 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
    13 5. After the machine boots, the driver will be working (at least it was for me).
     9 1. Install the additions from the .iso
     10 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
     11 3. Boot the system back up and go back to Control Panel->Devices.  Set the startup type to "System" and then start the driver.
     12 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
     13 5. After the machine boots, the driver will be working (at least it was for me).
    1414
    1515I'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.
    16 

© 2023 Oracle
ContactPrivacy policyTerms of Use