Changeset 56250 in vbox for trunk/doc/manual/en_US

Timestamp:

Jun 5, 2015 10:31:44 AM (10 years ago)

Author:

vboxsync

Message:

doc/manual: 32-bit/64-bit consistency

Location:

trunk/doc/manual/en_US

Files:

• SDKRef.xml (modified) (15 diffs)
• user_Frontends.xml (modified) (1 diff)
• user_Troubleshooting.xml (modified) (3 diffs)

trunk/doc/manual/en_US/SDKRef.xml

@@ -2541 +2541 @@
       request is constructed in the guest physical memory, which must be
       locked by the guest. The physical address is passed to the VMM device
-      using a 32 bit <computeroutput>out edx, eax</computeroutput>
-      instruction. The physical memory must be allocated below 4GB by 64 bit
+      using a 32-bit <computeroutput>out edx, eax</computeroutput>
+      instruction. The physical memory must be allocated below 4GB by 64-bit
       guests.</para>
 
@@ -2632 +2632 @@
             <itemizedlist>
               <listitem>
-                <para>All fields are 32 bit.</para>
+                <para>All fields are 32-bit.</para>
               </listitem>
 
@@ -2675 +2675 @@
                   (<computeroutput>62</computeroutput>)</entry>
 
-                  <entry>Call a HGCM function using the 32 bit
+                  <entry>Call a HGCM function using the 32-bit
                   interface.</entry>
                 </row>
@@ -2683 +2683 @@
                   (<computeroutput>63</computeroutput>)</entry>
 
-                  <entry>Call a HGCM function using the 64 bit
+                  <entry>Call a HGCM function using the 64-bit
                   interface.</entry>
                 </row>
@@ -2770 +2770 @@
 
                   <entry>The client identifier assigned to the connecting
-                  client by the HGCM subsystem (32 bit).</entry>
+                  client by the HGCM subsystem (32-bit).</entry>
                 </row>
               </tbody>
@@ -2858 +2858 @@
 
                   <entry>The client identifier previously returned by the
-                  connect request (32 bit).</entry>
+                  connect request (32-bit).</entry>
                 </row>
               </tbody>
@@ -2868 +2868 @@
         <title>Call32 and Call64</title>
 
-        <para>Calls the HGCM service entry point (VMMDevHGCMCall) using 32 bit
-        or 64 bit addresses: <table>
+        <para>Calls the HGCM service entry point (VMMDevHGCMCall) using 32-bit
+        or 64-bit addresses: <table>
             <title>Call request</title>
 
@@ -2894 +2894 @@
 
                   <entry>The client identifier previously returned by the
-                  connect request (32 bit).</entry>
+                  connect request (32-bit).</entry>
                 </row>
 
@@ -2907 +2907 @@
                   <entry>cParms</entry>
 
-                  <entry>The number of following parameters (32 bit). This
+                  <entry>The number of following parameters (32-bit). This
                   value is 0 if the function requires no parameters.</entry>
                 </row>
@@ -2922 +2922 @@
           </table></para>
 
-        <para>The 32 bit parameter description (HGCMFunctionParameter32)
-        consists of 32 bit type field and 8 bytes of an opaque value, so 12
-        bytes in total. The 64 bit variant (HGCMFunctionParameter64) consists
+        <para>The 32-bit parameter description (HGCMFunctionParameter32)
+        consists of 32-bit type field and 8 bytes of an opaque value, so 12
+        bytes in total. The 64-bit variant (HGCMFunctionParameter64) consists
         of the type and 12 bytes of a value, so 16 bytes in total.</para>
 
@@ -2942 +2942 @@
                   <entry>VMMDevHGCMParmType_32bit (1)</entry>
 
-                  <entry>A 32 bit value.</entry>
+                  <entry>A 32-bit value.</entry>
                 </row>
 
@@ -2948 +2948 @@
                   <entry>VMMDevHGCMParmType_64bit (2)</entry>
 
-                  <entry>A 64 bit value.</entry>
+                  <entry>A 64-bit value.</entry>
                 </row>
 
@@ -2954 +2954 @@
                   <entry>VMMDevHGCMParmType_PhysAddr (3)</entry>
 
-                  <entry>A 32 bit size followed by a 32 bit or 64 bit guest
+                  <entry>A 32-bit size followed by a 32-bit or 64-bit guest
                   physical address.</entry>
                 </row>
@@ -2961 +2961 @@
                   <entry>VMMDevHGCMParmType_LinAddr (4)</entry>
 
-                  <entry>A 32 bit size followed by a 32 bit or 64 bit guest
+                  <entry>A 32-bit size followed by a 32-bit or 64-bit guest
                   linear address. The buffer is used both for guest to host
                   and for host to guest data.</entry>
@@ -3863 +3863 @@
           <computeroutput>IMachine</computeroutput>. This straightens out the
           logical placement of methods and was necessary to resolve a
-          long-standing issue, preventing 32 bit API clients from invoking
+          long-standing issue, preventing 32-bit API clients from invoking
           those operations in the case where no VM is running.
           <itemizedlist>

trunk/doc/manual/en_US/user_Frontends.xml

@@ -289 +289 @@
 
           <listitem>
-            <para>Create a virtual hard disk for the VM (in this case, 10GB in
+            <para>Create a virtual hard disk for the VM (in this case, 10 GB in
             size):<screen>VBoxManage createhd --filename "WinXP.vdi" --size 10000</screen></para>
           </listitem>

trunk/doc/manual/en_US/user_Troubleshooting.xml

@@ -892 +892 @@
 
         <listitem>
-          <para>Browse into installation CD for example E:\i386 (or AMD64 for 64bit version)</para>
+          <para>Browse into the installation CD for example E:\i386 (or amd64 for the 64-bit version)</para>
         </listitem>
 
@@ -940 +940 @@
 
         <listitem>
-          <para>After entering into the one of the numeric folders, browse into Windows\System32 (or C:\Windows\SysWOW64 for 64 bit version) directory locate d3d8.dll and d3d9.dll and extract</para>
+          <para>After entering into the one of the numeric folders, browse into Windows\System32 (or C:\Windows\SysWOW64 for the 64-bit version) directory locate d3d8.dll and d3d9.dll and extract</para>
         </listitem>
 
@@ -1469 +1469 @@
 
       <para>When running a large number of VMs with a lot of RAM on a Linux
-      system (say 20 VMs with 1GB of RAM each), additional VMs might fail to
+      system (say 20 VMs with 1 GB of RAM each), additional VMs might fail to
       start with a kernel error saying that the vmalloc pool is exhausted and
       should be extended. The error message also tells you to specify