docs/en wineusr-configuring.sgml

[Dimi Paun]

ChangeSet ID:	1165897243237250607068749
CVSROOT:	/cvsroot/wine
Module name:	docs
Changes by:	[e-mail]	2006/12/11 20:20:43

Modified files:
    en             : wineusr-configuring.sgml

Log message:
    Detlef Riekenberg 
    - Fix system32, winecfg and Printers.

Old revision  New revision  Changes     Path
 1.9           1.10          +42 -29     docs/en/wineusr-configuring.sgml

Index: docs/en/wineusr-configuring.sgml
diff -u -p docs/en/wineusr-configuring.sgml:1.9 docs/en/wineusr-configuring.sgml:1.10
--- docs/en/wineusr-configuring.sgml	12 Dec 2006  4:20:43 -0000
+++ /dev/null	12 Dec 2006  4:20:43 -0000
@@ -50,7 +50,7 @@
             </listitem>
             <listitem>
               <para>
-                Appearance
+                Desktop Integration
               </para>
             </listitem>
             <listitem>
@@ -144,10 +144,10 @@
             It's not always possible to run an application on builtin
             DLL's.  Sometimes native DLL's simply work better.  After
             you've located a native DLL on a Windows system, you'll
-            need to place it in suitable place for Wine to find it
+            need to put it in suitable place for Wine to find it
             and then configure it to be used.  Generally the place
             you need to put it is in the directory you've configured
-            to be <filename>c:\windows\system</filename> (more on that in
+            to be <filename>c:\windows\system32</filename> (more on that in
             the drives section).  There are four DLL's you should never
             try to use the native versions of:
             <filename>kernel32.dll</filename>,
@@ -187,7 +187,7 @@
             files to trick many programs that check for file existence to
             determine whether a particular feature (such as Winsock and its
             TCP/IP networking) is available. If this is a problem for you, you
-            can create empty files in the configured c:\windows\system directory
+            can create empty files in the configured c:\windows\system32 directory
             to make the program think it's there, and Wine's built-in DLL will
             be loaded when the program actually asks for it. (Unfortunately,
             tools/wineinstall does not create such empty files itself.)
@@ -197,7 +197,7 @@
            from the physical files (for example, to determine the DirectX
            version). Empty files will not do in this case, it is rather
            necessary to install files with complete version resources. This
-           problem is currently being worked on. In the meantime, you may still
+           problem is already fixed for many files.  For others, you may still
            need to grab some real DLL files to fool these apps with.
          </para>
          <para>
@@ -260,16 +260,7 @@
           can configure.  For most people the defaults are fine.
         </para>
         <para>
-          The first is the "screen color depth" and
-          represents the number of colors that can be displayed on the
-          screen.  Older graphics cards had a hard time displaying a
-          full-range of colors and for them it's useful to be able to
-          specify an "8-bit" display.  Modern video cards, namely anything
-          with over 8MB of memory, have no problem using a full 24 or 32-bit
-          depth.
-        </para>
-        <para>
-          The next few settings primarily affect games and are somewhat
+          The first few settings primarily affect games and are somewhat
           self-explanatory.  You can prevent the mouse from leaving the
           window of a DirectX program (i.e. a game.) and the default is
           to have that box checked.  There's lots of
@@ -352,24 +343,25 @@
              the format is a letter followed by a colon, such as "a:".  So,
              if the link to your c: drive points to
                <filename> ~/.wine/drive_c</filename>, you
-             can interpret references to <filename>c:\windows\system</filename>
-             to mean <filename> ~/.wine/drive_c/windows/system</filename>.
+             can interpret references to <filename>c:\windows\system32</filename>
+             to mean <filename>~/.wine/drive_c/windows/system32</filename>.
      </para>
         </sect2>
    <sect2>
         <title>Audio Settings</title>
         <para>
           Wine can work with quite a few different audio subsystems
-          which you can choose under the "Audio" tab.  The
-          "Autodetect" button can figure it all out for you, or you can
-          manually select a driver.  Older
+          which you can choose under the "Audio" tab.  winecfg figures out all 
+          available drivers for you, but you can manually select which driver 
+          will be used.  Older
           Linux distributions using the 2.4 kernel or earlier typically
-          use the "OSS" driver.  Newer 2.6 kernels have switched to "ALSA".
-          If you're using KDE, regardless of the kernel, you can probably
-          also use "aRts".  If you're using GNOME you can probably use
+          use the "OSS" driver.  Usually 2.6 kernels have switched to "ALSA".
+          Bugs in "aRts" are not fixed from the KDE-side for a long time made
+          it recently nessesary to deactivate this driver.
+          If you're using GNOME you can probably use
           EsounD.  The OSS and ALSA audio drivers get the most testing, so
           it's recommended you stick with them if possible.  
-          If you need to use "Jack" or "NAS" you probably already know why.
+          If you need to use "Jack", "NAS" or "CoreAudio" you probably already know why.
         </para>
         <para> 
           DirectSound settings are primarily used by games.  You can
@@ -378,7 +370,7 @@
         </para>
       </sect2>
       <sect2>
-      <title>Appearance</title>
+      <title>Desktop Integration</title>
       <para>
         Wine can load Windows themes if you have them available.  While
         this certainly isn't necessary in order to use Wine or applications,
@@ -409,7 +401,7 @@
             </listitem>
             <listitem>
               <para>
-                Use the new Appearance tab of winecfg to select the new theme.
+                Use the Desktop Integration tab of winecfg to select the new theme.
               </para>
             </listitem>
           </orderedlist>
@@ -705,10 +697,31 @@
       <sect2>
         <title>Printers</title>
         <para>
-	  Wine can interact directly with the CUPS printing system to
+          Wine can interact directly with the local CUPS printing system to
           find the printers available on your system.  Configuring
-          printers with Wine is as simple as making sure your CUPS
-          configuration works.
+          printers with Wine is as simple as making sure your CUPS 
+          configuration works. Wine still needs the command
+          <userinput>lpr</userinput>(from CUPS), when printing a Document.
+        </para>
+        <para>
+          If you do not use CUPS, the old BSD-Printing system is used:
+          <itemizedlist>
+            <listitem>
+              <para>
+                All Printers from <filename>/etc/printcap</filename> are installed automatically in Wine.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Wine needs a PPD-File for every Printer (generic.ppd comes with Wine)
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                The command <userinput>lpr</userinput> is called when printing a Document
+              </para>
+            </listitem>
+          </itemizedlist>
         </para>
       </sect2>
       <sect2>