Page MenuHomeFreeBSD
Files F142799323

D27146.diff
No OneTemporary
Actions

D27146.diff
View Options

Index: chapter.xml
===================================================================
--- chapter.xml
+++ chapter.xml
@@ -0,0 +1,441 @@
+ <!--- Start SECTION 5, Configuring WINE Installations --->
+ <sect1 xml:id="configuring-wine-installation">
+ <title>Configuring WINE Installation</title>
+
+ <para>With an understanding of what WINE is and how it works at a high
+ level, the next step to effectively using it on your &os;
+ system is becoming familiar with its configuration. The following
+ sections will describe the key concept of the <emphasis>WINE
+ prefix</emphasis>, and illustrate how it's used to control the
+ behavior of applications run through WINE.</para>
+
+ <sect2 xml:id="wine-prefixes">
+ <title>WINE Prefixes</title>
+
+ <para>A WINE <emphasis>prefix</emphasis> is a directory, usually
+ located beneath the default location of $HOME/.wine though it
+ can be located elsewhere. The prefix is a set of configurations
+ and support files used by the the
+ <application>wine</application> to configure and run
+ the &os.windows; environment a given application needs. By
+ default, a brand new WINE installation will create the following
+ structure when first launched by a user:</para>
+
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para><filename>.update-timestamp</filename>: This file contains
+ the last modified date of the
+ <filename>file /usr/share/wine/wine.inf</filename>. It's used
+ by WINE to determine if a prefix is out of date, and automatically
+ update it if needed.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>dosdevices/</filename>: This directory contains
+ information on mappings of &os.windows; resources to resources
+ on the host &os; system. For example, after a new WINE installation,
+ this should contain at least two entries which enable access to the
+ &os; filesystem using &os.windows;-style drive letters:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><filename>c:@</filename>: A link to the
+ <filename>drive_c</filename> directory described below.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>z:@</filename>: A link to the root directory of
+ the system.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para><filename>drive_c/</filename>: This directory emulates the
+ main (i.e. &quot;C:&quot;) drive of a &os.windows;
+ system. It contains a directory structure and associated
+ files mirroring that of standard &os.windows; systems. A
+ fresh WINE prefix will contain &os.windows; 10
+ directories such as <emphasis>Users</emphasis> and the
+ <emphasis>Windows</emphasis> directory that holds the OS
+ itself. Furthermore, applications installed within a prefix
+ will be located in either the <emphasis>Program
+ Files</emphasis> or <emphasis>Program Files (x86)</emphasis>
+ directories, depending on their architecture.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>system.reg</filename>: This Registry file contains information on the
+ &os.windows; installation, which in the case of WINE is
+ the environment in the drive_c directory.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>user.reg</filename>: This Registry file contains the current user's
+ personal configurations, made either by varous software or
+ through the use of the Registry Editor.</para>
+ </listitem>
+
+ <listitem>
+ <para><filename>userdef.reg</filename>: This Registry file is a default set of
+ configurations for newly-created users.</para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+
+ <sect2 xml:id="creating-and-using-wine-prefixes">
+ <title>Creating and Using WINE Prefixes</title>
+
+ <para>While WINE will create a default prefix in the user's
+ $HOME/.wine/ directory, it's possible to set up multiple
+ prefixes. There are a few reasons to do this:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>The most common reason is to emulate different versions of
+ &os.windows;, according to the compatibility needs of
+ the software in question.</para>
+ </listitem>
+
+ <listitem>
+ <para>In addition, it's common to encounter software that doesn't
+ work correctly in the default environment, and requires
+ special configuration. It's useful to isolate these in their
+ own, custom prefixes, so the changes don't impact other
+ applications.</para>
+ </listitem>
+
+ <listitem>
+ <para>Similarly, copying the default or &quot;main&quot; prefix
+ into a separate &quot;testing&quot; one in order to evaluate
+ an application's compatibilty can reduce the chance of
+ corruption.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Creating a prefix from the terminal requires the following
+ command:</para>
+
+ <screen>&prompt;<userinput>WINEPREFIX=&quot;/home/username/.wine-new&quot; winecfg</userinput></screen>
+
+ <para>This will run the <application>winecfg</application>
+ program, which can be used to configure wine prefixes (more on
+ this in a later section). But by providing a directory path
+ value for the <varname>WINEPREFIX</varname> environment
+ variable, a new prefix is created at that location if one
+ doesn't already exist.</para>
+
+ <para>Supplying the same variable to the
+ <application>wine</application> program will
+ similarly cause the selected program to be run with the
+ specified prefix:</para>
+
+ <screen>&prompt;<userinput>WINEPREFIX=&quot;/home/username/.wine-new&quot; wine program.exe</userinput></screen>
+
+ </sect2>
+
+ <sect2 xml:id="configuring-wine-prefixes-with-winecfg">
+ <title>Configuring WINE Prefixes with winecfg</title>
+
+ <para>As described above WINE includes a tool called
+ <application>winecfg</application> to configure
+ prefixes from within a GUI. It contains a variety of functions,
+ which are detailed in the sections below. When
+ <application>winecfg</application> is run from
+ within a prefix, or provided the location of a prefix within the
+ <varname>WINEPREFIX</varname> variable, it enables the
+ configuration of the selected prefix as described in the below
+ sections.</para>
+
+ <para>Selections made on the <emphasis>Applications</emphasis> tab
+ will affect the scope of changes made in the
+ <emphasis>Libraries</emphasis> and
+ <emphasis>Graphics</emphasis> tabs, which will be limited to
+ the application selected. See the section on
+ <link xlink:href="https://wiki.winehq.org/Wine_User%27s_Guide#Using_Winecfg">Using
+ Winecfg</link> in the WINE Wiki for more details.</para>
+
+ <sect3 xml:id="applications">
+ <title>Applications</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-1.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>The <emphasis>Applications</emphasis> contains controls
+ enabling the association of programs with a particular version
+ of &os.windows;. On first start-up the
+ <emphasis>Application settings</emphasis> section will contain
+ a single entry: <emphasis>Default Settings</emphasis>. This
+ corresponds to all the default configurations of the prefix,
+ which (as the disabled <emphasis>Remove application</emphasis>
+ button implies) cannot be deleted.</para>
+
+ <para>But additional applications can be added with the following
+ process:</para>
+
+ <orderedlist spacing="compact">
+ <listitem>
+ <para>Click the <emphasis>Add application</emphasis> button.</para>
+ </listitem>
+
+ <listitem>
+ <para>Use the provided dialog to select the desired program's
+ executable.</para>
+ </listitem>
+
+ <listitem>
+ <para>Select the version of &os.windows; to be used with the
+ selected program.</para>
+ </listitem>
+ </orderedlist>
+ </sect3>
+
+ <sect3 xml:id="libraries">
+ <title>Libraries</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-2.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>WINE provides a set of open source library files as part of
+ its distribution that provide the same functions as their
+ &os.windows; counterparts. However, as noted earlier in
+ this chapter, the WINE project is always trying to keep pace
+ with new updates to these libraries. As a result, the versions
+ that ship with WINE may be missing functionality that the
+ latest &os.windows; programs are expecting.</para>
+
+ <para>However, &lt;application&gt;winecfg&lt;/application&gt; makes
+ it possible specify overrides for the built-in libraries,
+ particularly there is a version of &os.windows; available
+ on the same machine as the host &os; installation. For
+ each library to be overriden, do the following:</para>
+
+ <orderedlist spacing="compact">
+ <listitem>
+ <para>Open the <emphasis>New override for library</emphasis>
+ drop-down and select the library to be replaced.</para>
+ </listitem>
+
+ <listitem>
+ <para>Click the <emphasis>Add</emphasis> button.</para>
+ </listitem>
+
+ <listitem>
+ <para>The new override will appear in the <emphasis>Existing
+ overrides</emphasis> list, notice the <emphasis>native,
+ builtin</emphasis> designation in parentheses.</para>
+ </listitem>
+
+ <listitem>
+ <para>Click to select the library.</para>
+ </listitem>
+
+ <listitem>
+ <para>Click the <emphasis>Edit</emphasis> button.</para>
+ </listitem>
+
+ <listitem>
+ <para>Use the provided dialog to select a corresponding library
+ to be used in place of the built-in one.</para>
+ </listitem>
+ </orderedlist>
+
+ <para>Be sure to select a file that is truly the corresponding
+ version of the built-in one, otherwise there may be unexpected
+ behavior.</para>
+ </sect3>
+
+ <sect3 xml:id="graphics">
+ <title>Graphics</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-3.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>The <emphasis>Graphics</emphasis> tab provides some options to
+ make the windows of programs run via WINE operate smoothly with
+ &os;</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Automatic mouse capture when windows are full-screen</para>
+ </listitem>
+
+ <listitem>
+ <para>Allowing the &os; window manager to decorate the
+ windows, such as their title bars, for programs running
+ via WINE.</para>
+ </listitem>
+
+ <listitem>
+ <para>Allowing the window manager to control windows for
+ programs running via WINE, such as running resizing
+ functions on them.</para>
+ </listitem>
+
+ <listitem>
+ <para>Create an emulated virtual desktop, within which all WINE
+ programs will run. If this item is selected, the size of
+ the virtual desktop can be specified using the
+ <emphasis>Desktop size</emphasis> input boxes.</para>
+ </listitem>
+
+ <listitem>
+ <para>Setting the screen resolution for programs running via
+ WINE.</para>
+ </listitem>
+ </itemizedlist>
+ </sect3>
+
+ <sect3 xml:id="desktop-integration">
+ <title>Desktop Integration</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-4.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>
+ This tab allows configuration of the following items:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>The theme and related visual settings to be used for
+ programs running via WINE.</para>
+ </listitem>
+
+ <listitem>
+ <para>Whether the WINE sub-system should manage MIME types (used
+ to determine which application opens a particular file
+ type) internally.</para>
+ </listitem>
+
+ <listitem>
+ <para>Mappings of directories in the host &os; system to
+ useful folders within the &os.windows; environment. To
+ change an existing association, select the desired item
+ and click <emphasis>Browse</emphasis>, then use the
+ provided dialog to select a directory.</para>
+ </listitem>
+ </itemizedlist>
+ </section3>
+
+ <sect3 xml:id="drives">
+ <title>Drives</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-5.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>The <emphasis>Drives</emphasis> tab allows linking of
+ directories in the host &os; system to drive letters in
+ the &os.windows; environment. The default values in this
+ tab should look familiar, as they're displaying the contents
+ of dosdevices/ directory in the current WINE prefix. Changes
+ made via this dialog will reflect in the
+ <fliename>dosdevices/</filename> directory, and properly-
+ formatted links created in that directory will display in
+ this tab.</para>
+
+ <para>To create a new entry, such as for a CD-ROM (mounted at
+ <filename>/mnt/cdrom</filename>), take the following steps:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Click the <emphasis>Add </emphasis> button.</para>
+ </listitem>
+
+ <listitem>
+ <para>In the provided dialog, choose a free drive letter.</para>
+ </listitem>
+
+ <listitem>
+ <para>Click <emphasis>OK</emphasis>.</para>
+ </listitem>
+
+ <listitem>
+ <para>Fill in the <emphasis>Path</emphasis> input box by either
+ typing the path to the resource, or click
+ <emphasis>Browse </emphasis> and use the provided dialog
+ to select it.</para>
+ </listitem>
+ </orderedlist>
+
+ <para>By default WINE will autodetect the type of resource linked,
+ but this can be manually overridden. See
+ <link xlink:href="https://wiki.winehq.org/Wine_User%27s_Guide#Drive_Settings">the
+ section in the WINE Wiki</link> for more detail on advanced
+ options.</para>
+ </sect3>
+
+ <sect3 xml:id="audio">
+ <title>Audio</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-6.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>This tab contains some configurable options for routing sound
+ from &os.windows; programs to the native &os; sound
+ system, including:</para>
+
+ <itemizedlist>
+ <listitem>
+ <>para>Driver selection</para>
+ </listitem>
+
+ <listitem>
+ <para>Default device selection</para>
+ </listitem>
+
+ <listitem>
+ <para>Sound test</para>
+ </listitem>
+ </itemizedlist>
+ </sect3>
+
+ <sect3 xml:id="about">
+ <title>About</title>
+
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="./includes/wine-config-7.png" />
+ </imageobject>
+ </inlinemediaobject>
+ </para>
+
+ <para>The final tab contains information on the WINE project,
+ including a link to the website. It also allows entry of
+ (entirely optional) user information, although this is not
+ sent anywhere as it is in other operating systems.</para>
+ </sect3>
+ </sect2>
+ </sect1>
+

File Metadata

Mime Type
text/plain
Expires
Sat, Jan 24, 6:15 PM (15 h, 23 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
27902756
Default Alt Text
D27146.diff (17 KB)

Event Timeline