On Monday 06 December 2004 14:21, Diego 'Flameeyes' Pettenà wrote: > I think the documentation should be updated, I'll try to do something later > today. Ok I hope this patch can do the trick. I updated the documentation telling to use the HKEY_CURRENT_USER/Environment key instead of the section for Path, Temp and System variables. HTH, -- Diego "Flameeyes" Pettenà flameeyes@xxxxxxxxxxxxxxxx - http://flameeyes.web.ctonet.it/
Index: configuring.sgml
===================================================================
RCS file: /home/wine/wine/documentation/configuring.sgml,v
retrieving revision 1.51
diff -u -3 -r1.51 configuring.sgml
--- configuring.sgml 18 Oct 2004 23:14:24 -0000 1.51
+++ configuring.sgml 6 Dec 2004 13:51:24 -0000
@@ -359,16 +359,13 @@
<sect3 id="config-wine">
<title>The Section </title>
<para>
- The section of the configuration file contains all kinds
- of general settings for Wine.
+ The section of the configuration file contains basic settings for Wine.
</para>
<para>
<programlisting>
"Windows" = "c:\\windows"
-"System" = "c:\\windows\\system"
-"Temp" = "c:\\temp"
-"Path" = "c:\\windows;c:\\windows\\system;c:\\blanco"
"ShowDirSymlinks" = "1"
+"ShowDotFiles" = "1"
</programlisting>
For a detailed description of drive layer configuration and
the meaning of these parameters, please look at the <link
@@ -973,35 +970,6 @@
recommended, as Windows programs always assume write access
to the Windows directory!
</para>
- <para>
- <programlisting>"System" = "c:\\windows\\system"</programlisting>
- This sets up where the windows system files are. The Windows
- system directory should reside below the directory used for the
- <literal>Windows</literal> setting.
- Thus when using the example above, the system directory would be
- <filename>/usr/local/wine_c/windows/system</filename>.
- Again, no trailing slash, and write access!
- </para>
- <para>
- <programlisting>"Temp" = "c:\\temp"</programlisting> This should
- be the directory you want your temp files stored in,
- /usr/local/wine_c/temp in our example.
- Again, no trailing slash, and <emphasis>write
- access</emphasis>!!
- </para>
- <para>
- <programlisting>"Path" = "c:\\windows;c:\\windows\\system;c:\\blanco"</programlisting>
- Behaves like the <envar>PATH</envar> setting on UNIX
- boxes. When wine is run like <userinput>wine
- sol.exe</userinput>, if <filename>sol.exe</filename>
- resides in a directory specified in the
- <literal>Path</literal> setting, wine will run it (Of
- course, if <filename>sol.exe</filename> resides in the
- current directory, wine will run that one). Make sure it
- always has your <filename>windows</filename> directory and
- system directory (For this setup, it must have
- <filename>"c:\\windows;c:\\windows\\system"</filename>).
- </para>
<para id="dirsymlinks">
<programlisting>"ShowDirSymlinks" = "1"</programlisting>
Wine doesn't pass directory symlinks to Windows programs by
@@ -1017,6 +985,9 @@
Windows programs when using the above method! (in other words:
enabling it is certainly not recommended)
</para>
+ <para>Old Path, Temp, System configuration are now moved into the
+ registry. See the <link linkend="environment-variables">Environment
+ Variables</link> paragraph.</para>
</sect2>
<sect2>
Index: faq.sgml
===================================================================
RCS file: /home/wine/wine/documentation/faq.sgml,v
retrieving revision 1.35
diff -u -3 -r1.35 faq.sgml
--- faq.sgml 16 Aug 2004 19:58:08 -0000 1.35
+++ faq.sgml 6 Dec 2004 13:51:27 -0000
@@ -820,7 +820,6 @@
Windows=c:\windows
System=c:\windows\system
Temp=e:\
- Path=c:\windows;c:\windows\system;c:
</screen>
<para>
In <filename>/var/lib/wine/windows</filename>, you will need to
Index: running.sgml
===================================================================
RCS file: /home/wine/wine/documentation/running.sgml,v
retrieving revision 1.30
diff -u -3 -r1.30 running.sgml
--- running.sgml 6 May 2004 23:51:43 -0000 1.30
+++ running.sgml 6 Dec 2004 13:51:28 -0000
@@ -88,16 +88,14 @@
<para>
The first argument should be the name of the file you
want <command>wine</command> to execute. If the executable is
- in the <parameter>Path</parameter> parameter in the
- configuration file, you can simply give the executable file
- name. However, if the executable is not in
- <parameter>Path</parameter>, you must give the full path to
+ in the <parameter>Path</parameter> environment variable, you can
+ simply give the executable file name. However, if the executable
+ is not in <parameter>Path</parameter>, you must give the full path to
the executable (in Windows format, not UNIX format!). For
example, given a <parameter>Path</parameter> of the following:
</para>
<screen>
-
-"Path"="c:\\windows;c:\\windows\\system;e:\\;e:\\test;f:\\"
+Path="c:\windows;c:\windows\system;e:\;e:\test;f:\"
</screen>
<para>
You could run the file
@@ -375,16 +373,47 @@
place the setting into /etc/profile, or also ~/.bashrc in the case of
bash.
</para>
- <para>
- Note however that there is an exception to the rule:
- If you want to change the PATH environment variable, then of
- course you can't modify it that way, since this will alter the
- Unix PATH environment setting. Instead, you should set the
- WINEPATH environment variable. An alternative way to
- indicate the content of the DOS PATH environment variable would
- be to change the "path" setting in the wine config file's <link
- linkend="config-wine"></link> section.
- </para>
+ <sect2 id="special-environment">
+ <para>Note however that ther is some exceptions to the rule:
+ If you want to change the PATH, SYSTEM or TEMP variables, the of course
+ you can't modify it that way, since this will alter the Unix environment
+ settings. Instead, you should set them into the registry. To set them
+ you should launch <userinput>wine regedit</userinput> and then go to the
+ <screen>HKEY_CURRENT_USER/Environment</screen> key. Now you can create
+ or modify the values of the variables you need
+ </para>
+ <para>
+ <programlisting>"System" = "c:\\windows\\system"</programlisting>
+ This sets up where the windows system files are. The Windows
+ system directory should reside below the directory used for the
+ <literal>Windows</literal> setting.
+ Thus when using /usr/local/wine_c_windows as Windows path,
+ the system directory would be
+ <filename>/usr/local/wine_c/windows/system</filename>.
+ It must be set with no trailing slash, and you must be sure that
+ you have write access to it.
+ </para>
+ <para>
+ <programlisting>"Temp" = "c:\\temp"</programlisting> This should
+ be the directory you want your temp files stored in,
+ /usr/local/wine_c/temp in our previous example.
+ Again, no trailing slash, and <emphasis>write
+ access</emphasis>!!
+ </para>
+ <para>
+ <programlisting>"Path" = "c:\\windows;c:\\windows\\system;c:\\blanco"</programlisting>
+ Behaves like the <envar>PATH</envar> setting on UNIX
+ boxes. When wine is run like <userinput>wine
+ sol.exe</userinput>, if <filename>sol.exe</filename>
+ resides in a directory specified in the
+ <literal>Path</literal> setting, wine will run it (Of
+ course, if <filename>sol.exe</filename> resides in the
+ current directory, wine will run that one). Make sure it
+ always has your <filename>windows</filename> directory and
+ system directory (For this setup, it must have
+ <filename>"c:\\windows;c:\\windows\\system"</filename>).
+ </para>
+ </sect2>
</sect1>
Attachment:
pgpSRXC9lcLTL.pgp
Description: PGP signature
