docs/en wineusr-configuring.sgml

[Dimi Paun]

ChangeSet ID:	113021209000403966692192981
CVSROOT:	/cvsroot/wine
Module name:	docs
Changes by:	dimi at sc8-pr-cvs1.sourceforge.net	2005/10/24 20:48:10

Modified files:
	en             : wineusr-configuring.sgml 

Log message:
	Brian Vincent
	wine.userreg no longer exists and the system administration tips
	were slightly misguided.


Old revision  New revision  Changes     Path
 1.8           1.9           +28 -25     docs/en/wineusr-configuring.sgml

Index: docs/en/wineusr-configuring.sgml
diff -u -p docs/en/wineusr-configuring.sgml:1.8 docs/en/wineusr-configuring.sgml:1.9
--- docs/en/wineusr-configuring.sgml	25 Oct 2005  3:48:10 -0000
+++ /dev/null	25 Oct 2005  3:48:10 -0000
@@ -502,7 +502,7 @@
         <para>
           Now, what you're probably wondering is how that translates
           into Wine's structure.   The registry layout described above
-          actually lives in four different files within each user's
+          actually lives in three different files within each user's
           ~/.wine directory:
         </para>
         <variablelist>
@@ -531,16 +531,6 @@
               </para>
             </listitem>
           </varlistentry>
-          <varlistentry>
-            <term><filename>wine.userreg</filename></term>
-            <listitem>
-              <para>
-                Wine saves HKEY_USERS to this file (both current and
-                default user), but does not load from it, unless
-                <filename>userdef.reg</filename> is missing.
-              </para>
-            </listitem>
-          </varlistentry>
         </variablelist>
         <para>
           These files are automatically created by
@@ -599,14 +589,12 @@
           Wine and any Windows application software he wants the users
           to have access to, copy the resulting
           <filename>system.reg</filename> and
-          <filename>user.reg</filename> over to the global registry
-          files (which we assume will reside in
+          over to the global registry files (which we assume will reside in
           <filename>/usr/local/etc</filename> here), with:
         </para>
         <programlisting>
-          cd ~/.wine
+          cd ~root/.wine
           cp system.reg /usr/local/etc/wine.systemreg
-          cp user.reg /usr/local/etc/wine.userreg
         </programlisting>
         <para>
           and perhaps even symlink these back to the administrator's
@@ -614,21 +602,36 @@
         </para>
         <programlisting>
           ln -sf /usr/local/etc/wine.systemreg system.reg
-          ln -sf /usr/local/etc/wine.userreg user.reg
         </programlisting>
         <para>
+          You might be tempted to do the same for <filename>user.reg</filename>
+          as well, however that file contains user specific settings.
+          Every user should have their own copy of that file along with
+          the permissions to modify it.
+        </para>
+        <para>
+          You'll want to pay attention to drive mappings.  If
+          you're sharing the system.reg file you'll want to make sure
+          the registry settings are compatible with the drive mappings
+          in <filename>~/.wine/dosdevices</filename>
+          of each individual user.  As a general rule of thumb, the closer
+          you keep your drive mappings to the default configuration
+          provided by <command>wineprefixcreate</command>, the easier
+          this will be to manage.  You may or may not be able to share
+          some or all of the actual "<filename>c:</filename>" drive you 
+          originally installed the application to.  Some applications 
+          require the ability to write specific settings to the drive, 
+          especially those designed for Windows 95/98/ME.   
+        </para>
+        <para>
           Note that the <filename>tools/wineinstall</filename> script
-          already does all of this for you, if you install Wine source as root.
-          If you then install Windows applications while logged in as
-          root, all your users will automatically be able to use them.
-          While the application setup will be taken from the global
-          registry, the users' personalized configurations will be saved
-          in their own home directories.
+          used to do some of this if you installed Wine source as root, however
+          it no longer does.
         </para>
         <para>
-          But be careful with what you do with the administrator account
-          - if you do copy or link the administrator's registry to the
-          global registry, any user might be able to read the
+          A final word of caution: be careful with what you do with the 
+          administrator account - if you do copy or link the administrator's 
+          registry to the global registry, any user might be able to read the
           administrator's preferences, which might not be good if
           sensitive information (passwords, personal information, etc)
           is stored there. Only use the administrator account to install