|
MainPage
Main Page: virtual-box-windows-guest-additions-installer
Featured VirtualBox Guest Additions for Windows OSEBinary/Compiled version of the VirtualBox Guest Additions for Windows, Open Source Edition (OSE) version. Including installer. Visual C++ 2005 runtime dllsIt might be necessary to install the correct or most current version of the "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package" to run the additions. A "side-by-side installation error" is thrown, otherwise. The current packages are:
Though I rather believe no C nor C++ dlls are needed. 3.3.0-#Sorry for the version numbering mixup. The 3.3.0 downloads are 3.0.0, of course. Corrected since 3.0.0-3. DetailsThe current version of the installer, VirtualBox_OSE_GuestAdditions-2.2.0-1.exe, is based on the 2.2.0 version of VirtualBox OSE. It has been compiled with MS Visual Studio 2005 (aka Visual C++ 8.0). It should be possible to install the additions on any VBox guest system running Windows 2000, XP, or later. Provided are the following:
The installation has not been yet thoroughly tested, only on Windows XP. Graphics performance, especially OpenGL, appears to be less than the PUEL version provided by SUN. Some issues are still open:
Please uninstall any Guest Additions provided by SUN or InnoTek (PUEL/commercial). VirtualBox 3.0.0 and Direct3D3.0.0 has a problem, so does 3.0.2 - check Issue 18 -- VBoxService does not start. Therefore, the current installs contain the VBoxService.exe from 2.2.4 which still does work. Thus, 3.0.0-2 is "featured", again - and will be replaced by 3.0.2, soon. An installer for the 3.0.0 additions has just been created. When installed in safe mode, the Direct3D dlls (d3d8.dll and d3d9.dll) in the system32 directory are replaced. VirtualBox then routes the D3D calls to the wine3d implementation which "converts" them to OpenGL, which is already supported in the guest->host setup. Alternative to Safe Mode InstallationThanks to Jérôme Poulin I don't know if it has been talked before on the mailing list, but there's no need to have to force installation in safe mode. You can simply rename the following values while installing: SourcePath ServicePackSourcePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ and warn the user that Windows could pop-up a warning during installation, to just cancel and accept and of course make sure there's no Windows CD in the drive, but in the case of additions installation, it should not happen. You should also make sure the files do not appear in %windir%\system32\dllcache and finally rename the files to replace and select them for deletion on reboot. Put the new files and undo the values renaming, reboot, all done! Windows 7For windows 7, you need to install the graphics driver manually. Device Manager, Update graphics driver, Search on computer, "C:\Program Files\VirtualBox OSE Guest Additions", VirtualBox graphics driver. In seamless mode, the "gadgets" are shown on the host desktop, and can be moved around - alpha blending is missing, though. According to the discussion group, some people also had success with using the "compatibility assistant" and installing in Vista mode. I'm not even asked about the unsigned drivers. Maybe driver signing needs to be disabled? Or I should sign the drivers ... I'm getting the impression that it is possible to install the drivers, but very hard to replace them ... "just" copying the .exe and .dll may be the best solution here? Updating the graphics driver: "Update graphics driver", "Search on computer", "Select from (a?) list of ...", "Disk", "C:\Program Files\VirtualBox OSE Guest Additions", VirtualBox graphics driver (current version). Updating some of the OpenGL dlls seem to work in safe mode, otherwise they are locked (Vista compatibility mode). VBoxService and VBoxTray.exe are not replaced in compat mode, but you can just kill the two processes and replace them manually via explorer (at least two dialog boxes, file replacing and UAC). CompilationAccording to Frank Mehnert (Sun/Oracle), it is possible to compile the additions only with kmk VBOX_ONLY_ADDITIONS=1 Adding BUILD_TARGET=win even allows to compile the windows additions on a linux system, with MSC (Visual Studio) (+ Wine on Linux) installed. Sounds difficult. Unfortunately, to compile the additions only on windows, you still need the complete VBox "kit" for the configure.vbs to finish correctly. Maybe, this can be helped by creating a reduced configure.vbs that only contains the stuff for the additions. You need at least:
LicenseGNU General Public License (GPL) v2 |
► Sign in to add a comment