Changeset 32363 in vbox for trunk/doc

Timestamp:

Sep 9, 2010 4:00:10 PM (15 years ago)

Author:

vboxsync

svn:sync-xref-src-repo-rev:

65713

Message:

doc/manual: xxe formatting.

File:

• trunk/doc/manual/en_US/user_AdvancedTopics.xml (modified) (11 diffs)

trunk/doc/manual/en_US/user_AdvancedTopics.xml

@@ -1 +1 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
 <chapter id="AdvancedTopics">
-  <title>Advanced topics</title>
+  <title>go Advanced topics</title>
 
   <sect1 id="vboxconfigdata">
@@ -295 +295 @@
       copy the file <computeroutput>VBoxGINA.dll</computeroutput> to the
       Windows <computeroutput>SYSTEM32</computeroutput> directory. Then, in
-      the registry, create the following key:
-      <screen>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL</screen>
+      the registry, create the following key: <screen>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL</screen>
       with a value of <computeroutput>VBoxGINA.dll</computeroutput>.</para>
 
       <para><note>
-        The VirtualBox GINA is implemented as a wrapper around the standard Windows GINA
-        (<computeroutput>MSGINA.DLL</computeroutput>), therefore it will most likely not
-        work correctly with 3rd party GINA modules.
-      </note></para>
+           The VirtualBox GINA is implemented as a wrapper around the standard Windows GINA (
+
+          <computeroutput>MSGINA.DLL</computeroutput>
+
+          ), therefore it will most likely not work correctly with 3rd party GINA modules. 
+        </note></para>
 
       <para>To manually install the VirtualBox credential module, extract the
@@ -319 +320 @@
       <computeroutput>(Default)</computeroutput> in each key) set to
       <computeroutput>VBoxCredProv</computeroutput>. After that a new string
-      named
-      <screen>HKEY_CLASSES_ROOT\CLSID\{275D3BCC-22BB-4948-A7F6-3A3054EBA92B}\InprocServer32\ThreadingModel</screen>
+      named <screen>HKEY_CLASSES_ROOT\CLSID\{275D3BCC-22BB-4948-A7F6-3A3054EBA92B}\InprocServer32\ThreadingModel</screen>
       with a value of <computeroutput>Apartment</computeroutput> has to be
       created.</para>
@@ -361 +361 @@
             compared to the true user name, not the user friendly name. This
             means that when you rename a user, you still have to supply the
-            original user name (internally, Windows never renames user accounts).
-            </para>
+            original user name (internally, Windows never renames user
+            accounts).</para>
           </listitem>
         </orderedlist></para>
 
       <para>The following command forces VirtualBox to keep the credentials
-      after they were read by the guest and on VM reset: <screen>VBoxManage setextradata "Windows XP" VBoxInternal/Devices/VMMDev/0/Config/KeepCredentials 1</screen>Note that
-      this is a potential security risk as a malicious application running on
-      the guest could request this information using the proper
+      after they were read by the guest and on VM reset: <screen>VBoxManage setextradata "Windows XP" VBoxInternal/Devices/VMMDev/0/Config/KeepCredentials 1</screen>Note
+      that this is a potential security risk as a malicious application
+      running on the guest could request this information using the proper
       interface.</para>
     </sect2>
@@ -479 +479 @@
       Windows Vista and 7, Sysprep is already included. Sysprep mainly
       consists of an executable called
-      <computeroutput>sysprep.exe</computeroutput> which is invoked by
-      the user to put the Windows installation into preparation mode.</para>
-
-      <para>Starting with VirtualBox 3.2.2, the Guest Additions offer a way
-      to launch a system preparation on the guest operating system in an
-      automated way, controlled from the host system. To achieve that,
-      see <xref linkend="guestadd-guestcontrol" /> for using the feature
-      with the special identifier <computeroutput>sysprep</computeroutput>
-      as the program to execute, along with the user name <computeroutput>sysprep</computeroutput>
-      and password <computeroutput>sysprep</computeroutput> for the credentials.
-      Sysprep then gets launched with the required system rights.</para>
+      <computeroutput>sysprep.exe</computeroutput> which is invoked by the
+      user to put the Windows installation into preparation mode.</para>
+
+      <para>Starting with VirtualBox 3.2.2, the Guest Additions offer a way to
+      launch a system preparation on the guest operating system in an
+      automated way, controlled from the host system. To achieve that, see
+      <xref linkend="guestadd-guestcontrol" /> for using the feature with the
+      special identifier <computeroutput>sysprep</computeroutput> as the
+      program to execute, along with the user name
+      <computeroutput>sysprep</computeroutput> and password
+      <computeroutput>sysprep</computeroutput> for the credentials. Sysprep
+      then gets launched with the required system rights.</para>
 
       <note>
@@ -504 +505 @@
               for Windows Vista, 2008 Server and 7</para>
             </listitem>
-          </itemizedlist>
-          The Guest Additions will automatically use the appropriate path to execute
-          the system preparation tool.</para>
+          </itemizedlist> The Guest Additions will automatically use the
+        appropriate path to execute the system preparation tool.</para>
       </note>
     </sect2>
@@ -538 +538 @@
     --plugcpu and --unplugcpu subcommands, which take the number of the
     virtual CPU as a parameter, like this:<screen>VBoxManage modifyvm "VM name" --plugcpu 3
-VBoxManage modifyvm "VM name" --unplugcpu 3</screen>Note that CPU 0 can
-    never be removed.</para>
+VBoxManage modifyvm "VM name" --unplugcpu 3</screen>Note that CPU 0 can never
+    be removed.</para>
 
     <para>While the VM is running, CPUs can be added with the
@@ -880 +880 @@
         when the image is successfully created.</para>
       </sect3>
-
     </sect2>
 
@@ -1347 +1346 @@
     the GUI, that is, removing some features that the user should not
     see.<screen>VBoxManage setextradata global GUI/Customizations OPTION[,OPTION...]</screen></para>
-    <para>where <computeroutput>OPTION</computeroutput> is one of the following
-    keywords:<glosslist>
+
+    <para>where <computeroutput>OPTION</computeroutput> is one of the
+    following keywords:<glosslist>
         <glossentry>
           <glossterm><computeroutput>noSelector</computeroutput></glossterm>
@@ -1375 +1375 @@
       </glosslist></para>
 
-    <para>To disable any GUI customization do
-      <screen>VBoxManage setextradata global GUI/Customizations</screen></para>
-
-    <para>To disable all host key combinations, open the global settings and change
-      the host key to <emphasis>None</emphasis>. This might be useful when using
-      VirtualBox in a kiosk mode.</para>
+    <para>To disable any GUI customization do <screen>VBoxManage setextradata global GUI/Customizations</screen></para>
+
+    <para>To disable all host key combinations, open the global settings and
+    change the host key to <emphasis>None</emphasis>. This might be useful
+    when using VirtualBox in a kiosk mode.</para>
 
     <para>Furthermore, you can disallow certain actions when terminating a VM
-      from the GUI. To disallow specific actions, type:</para>
+    from the GUI. To disallow specific actions, type:</para>
+
     <para><screen>VBoxManage setextradata "VM name" GUI/RestrictedCloseActions OPTION[,OPTION...]</screen></para>
-    <para>where <computeroutput>OPTION</computeroutput> is one of the following
-      keywords:<glosslist>
+
+    <para>where <computeroutput>OPTION</computeroutput> is one of the
+    following keywords:<glosslist>
         <glossentry>
           <glossterm><computeroutput>SaveState</computeroutput></glossterm>
+
           <glossdef>
-            <para>Don't allow the user to save the VM state plus terminate the VM.</para>
+            <para>Don't allow the user to save the VM state plus terminate the
+            VM.</para>
           </glossdef>
         </glossentry>
+
         <glossentry>
           <glossterm><computeroutput>Shutdown</computeroutput></glossterm>
+
           <glossdef>
             <para>Don't allow the user to shutdown the VM by sending the ACPI
@@ -1400 +1405 @@
           </glossdef>
         </glossentry>
+
         <glossentry>
           <glossterm><computeroutput>PowerOff</computeroutput></glossterm>
+
           <glossdef>
             <para>Don't allow the user to power off the VM.</para>
           </glossdef>
         </glossentry>
+
         <glossentry>
           <glossterm><computeroutput>Restore</computeroutput></glossterm>
+
           <glossdef>
-            <para>Don't allow the user to return to the last snapshot when powering
-              off the VM.</para>
+            <para>Don't allow the user to return to the last snapshot when
+            powering off the VM.</para>
           </glossdef>
         </glossentry>
-    </glosslist></para>
+      </glosslist></para>
+
     <para>Combinations of all of these options are allowed. If all options are
-      specified, the VM cannot be shut down from the GUI.</para>
+    specified, the VM cannot be shut down from the GUI.</para>
   </sect1>
 
   <sect1 id="vboxwebsrv-daemon">
-    <title>Starting <computeroutput>vboxwebsrv</computeroutput> automatically</title>
+    <title>Starting <computeroutput>vboxwebsrv</computeroutput>
+    automatically</title>
 
     <para><computeroutput>vboxwebsrv</computeroutput> is used for controlling
-    VirtualBox remotely. As the client base using this interface is growing, we
-    added start scripts for the various operation systems we support. The
-    following describes how to use them.
-
-    <itemizedlist>
+    VirtualBox remotely. As the client base using this interface is growing,
+    we added start scripts for the various operation systems we support. The
+    following describes how to use them. <itemizedlist>
         <listitem>
-          <para>On Mac OS X, launchd is used. An example configuration file can
-          be found in
+          <para>On Mac OS X, launchd is used. An example configuration file
+          can be found in
           <computeroutput>$HOME/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</computeroutput>.
           It has to be enabled by changing the
           <computeroutput>Disabled</computeroutput> key from
           <computeroutput>true</computeroutput> to
-          <computeroutput>false</computeroutput>. To manually start the service
-          use the following command:
-          <screen>launchctl load ~/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</screen>
-          
+          <computeroutput>false</computeroutput>. To manually start the
+          service use the following command: <screen>launchctl load ~/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</screen>
           For additional information on how launchd services could be
-          configured see 
-          <literal><ulink
-      url="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/BPSystemStartup.html">http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/BPSystemStartup.html</ulink></literal>.
-          </para>
+          configured see <literal><ulink
+          url="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/BPSystemStartup.html">http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/BPSystemStartup.html</ulink></literal>.</para>
         </listitem>
-    </itemizedlist>
-    </para>
+      </itemizedlist></para>
   </sect1>
 </chapter>