VirtualBox

Ignore:
Timestamp:
Mar 14, 2012 10:53:45 AM (13 years ago)
Author:
vboxsync
Message:

Manual: Corrected typos and spelling for troubleshooting d3d file corruption.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_Troubleshooting.xml

    r40456 r40457  
    745745      <title>USB tablet coordinates wrong in Windows 98 guests</title>
    746746
    747       <para>If a Windows 98 VM is configured to use the emulated USB tablet 
    748       (absolute pointing device), the coordinate translation may be incorrect 
    749       and the pointer is restricted to the upper left quarter of the guest's 
     747      <para>If a Windows 98 VM is configured to use the emulated USB tablet
     748      (absolute pointing device), the coordinate translation may be incorrect
     749      and the pointer is restricted to the upper left quarter of the guest's
    750750      screen.
    751751      </para>
    752752
    753       <para>The USB HID (Human Interface Device) drivers in Windows 98 are very 
    754           old and do not handle tablets the same way all more recent operating 
    755           systems do (Windows 2000 and later, Mac OS X, Solaris). To 
     753      <para>The USB HID (Human Interface Device) drivers in Windows 98 are very
     754          old and do not handle tablets the same way all more recent operating
     755          systems do (Windows 2000 and later, Mac OS X, Solaris). To
    756756          work around the problem, issue the following command:
    757757      </para>
     
    783783    <sect2>
    784784      <title>Restoring d3d8.dll and d3d9.dll</title>
    785      
    786       <para>VirtualBox Guest Additions installer prior 4.1.8 had an issue, that might cause system d3d9.dll and d3d8.dll files corruption.
    787           Although this issue was fixed with VirtualBox 4.1.8, there is no way Guest Additions installer can repare these files.
    788           Corruption of these files has no implications in case 3D acceleration is enabled and "Basic" Direct3D support is installed,
    789           since all Direct3D9 and Direct3D8 applications will utilize VirtualBox Direct3D files and thus will have no problems with Direct3D.
    790           For WDDM Direct3D support system d3d9.dll and d3d8.dll files are always required for Direct3D8 and Direct3D9 applications,
    791           as a result Direct3D8 and Direct3D9 applications will not work.
    792           Note that starting Windows 7, 3D Desktop (aka Aero) uses d3d10.dll for rendering, thus d3d9.dll and d3d8.dll files corruption will not affect it.
    793           Given all the above, system d3d9.dll and d3d8.dll files corruption is not sonsidered fatal for "Basic" Direct3D installation,
    794           and for WDDM Direct3D installation on Windows 7 and later guests.
    795       </para>
    796      
    797       <para>Below is a step-by step guide for restoring original system d3d8.dll and d3d9.dll files for the case it is required.
    798       </para>
    799      
    800 
    801       <para>Extracting d3d8 and d3d9.dll from Windows XP installation CD
    802       </para>
     785
     786      <para>VirtualBox Guest Additions for Windows prior to 4.1.8 did not properly
     787          back up the original d3d8.dll and d3d9.dll system files when selecting
     788          and installing the experimental Direct3D support. This process replaces
     789          both system files with files from the VirtualBox Guest Additions so that
     790          Direct3D calls can be handled correctly. Although this issue was fixed
     791          with VirtualBox 4.1.8, there is no way the Windows Guest Additions
     792          installer can repair these files.</para>
     793
     794      <para>Corruption of these files has no implications in case 3D acceleration
     795          is enabled and basic Direct3D support is installed, that is, without WDDM
     796          (on Windows Vista or higher) or on older Windows systems like Windows XP.
     797          With the basic Direct3D support all Direct3D 8.0 and Direct3D 9.0
     798          applications will utilize VirtualBox Direct3D files directly and thus
     799          will run as expected.</para>
     800
     801      <para>For WDDM Direct3D support however, the originally shipped system files
     802          d3d8.dll and d3d9.dll files are required in order to run Direct3D 8.0
     803          and Direct3D 9.0 applications. As a result of the above mentioned system
     804          files corruption these applications will not work anymore. See below for
     805          a step-by-step guide for restoring the original d3d8.dll and d3d9.dll
     806          system files in case the VirtualBox Guest Additions installer warned
     807          about those incorrect files or when having trouble running Direct3D
     808          applications.</para>
     809
     810      <note><para>Starting at Windows 7 the 3D desktop (aka Aero) uses DirectX 10
     811          for rendering so that corrupted d3d8.dll and d3d9.dll system files will
     812          have no effect on the actual rendering. Taken this into account such a
     813          detected file corruption will not be considered as fatal for the basic
     814          Direct3D and WDDM Direct3D installation on Windows 7 and later guests.</para></note>
     815
     816      <para>Extracting d3d8 and d3d9.dll from a Windows XP installation CD:</para>
    803817
    804818      <orderedlist>
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette