Page MenuHomeFreeBSD
Files F145343817

D27455.id80317.diff
No OneTemporary
Actions

D27455.id80317.diff
View Options

Index: en_US.ISO8859-1/books/handbook/wine/chapter.xml
===================================================================
--- en_US.ISO8859-1/books/handbook/wine/chapter.xml
+++ en_US.ISO8859-1/books/handbook/wine/chapter.xml
@@ -0,0 +1,222 @@
+ <!-- START SECTION 7: WINE FAQ -->
+ <sect1 xml:id="wine-on-os-faq">
+ <title>WINE on &amp;os; FAQ</title>
+
+ <para>The following section describes some frequently asked questions,
+ tips/tricks, or common issues in running WINE on &amp;os;, along
+ with their respective answers.</para>
+
+ <sect2 xml:id="basic-installation-and-usage">
+ <title>Basic Installation and Usage</title>
+
+ <sect3 xml:id="how-to-install-32-bit-and-64-bit-wine-on-the-same-system">
+ <title>How to install 32-bit and 64-bit WINE on the same
+ system?</title>
+
+ <para>As described earlier in this section, the
+ <application>wine</application> and
+ <application>i386-wine</application> packages conflict
+ with one another, and therefore can't be installed on
+ the same system in the normal way. However, multiple
+ installs can be achieved using mechanisms like chroots/jails,
+ or by building WINE from source (note this does
+ <emphasis>not</emphasis> mean building the port).</para>
+ </sect3>
+
+ <sect3 xml:id="can-dos-programs-be-run-on-wine">
+ <title>Can DOS Programs Be Run on WINE?</title>
+
+ <para>They can, as &quot;Console User Interface&quot; applications
+ as mentioned eariler in this section. However, there is an
+ arguably better method for running DOS software:
+ <application>DOSBox</application>. On the other
+ hand, there's little reason not to at least try it. Simply
+ create a new prefix, install the software, and if it doesn't
+ work, delete the prefix.</para>
+ </sect3>
+
+ <sect3 xml:id="should-the-wine-devel-packageport-be-installed-to-use-the-development-version-of-wine-instead-of-stable">
+ <title>Should the &quot;wine-devel&quot; package/port be
+ installed to use the development version of WINE instead of
+ stable?</title>
+
+ <para>Yes, installing this version will install the
+ &quot;development&quot; version of WINE. As with the 32- and
+ 64-bit versions, they cannot be installed together with the
+ stable versions unless additional measures are taken.</para>
+
+ <para>Note that WINE also has a &quot;Staging&quot; version, which
+ contains the most recent updates. This was at one time
+ available as a &amp;os; port; however, it has since been
+ removed. It can be compiled directly from source however.</para>
+ </sect3>
+ </sect2>
+
+ <sect2 xml:id="install-optimization">
+ <title>Install Optimization</title>
+
+ <sect3 xml:id="how-should-os.windows-hardware-e.g.-graphics-drivers-be-handled">
+ <title>How should &os.windows; hardware (e.g. graphics) drivers be
+ handled?</title>
+
+ <para>Operating system drivers transfer commands between
+ applications and hardware. WINE emulates a &os.windows;
+ environment, including the drivers, which in turn use
+ &os;'s native drivers for this transfer. It's not advisable
+ to install &os.windows; drivers, as the WINE system is designed
+ to use the host systems drivers. If, for example, you have a
+ graphics card that benefits from dedicated drivers, install them
+ using the standard &os; methods, not &os.windows; installers.</para>
+ </sect3>
+
+ <sect3 xml:id="is-there-a-way-to-make-os.windows-fonts-look-better">
+ <title>Is there a way to make &amp;os.windows; fonts look
+ better?</title>
+
+ <para>A user on the FreeBSD forums suggests this configuration to
+ fix out-of-the-box look of WINE fonts, which can be slightly
+ pixelated.</para>
+
+ <para>According to <link xlink:href="https://forums.freebsd.org/threads/make-wine-ui-fonts-look-good.68273/">a post in the FreeBSD Forums</link>,
+ adding the following to the
+ <filename>.config/fontconfig/fonts.conf</filename> file will
+ add anti-aliasing and make text more readable.
+
+ <programlisting><?xml version="1.0"?>
+ <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
+
+ <fontconfig>
+
+ <!-- antialias all fonts -->
+ <match target="font">
+ <edit name="antialias" mode="assign"><bool>true</bool></edit>
+ <edit name="hinting" mode="assign"><bool>true</bool></edit>
+ <edit name="hintstyle" mode="assign"><const>hintslight</const></edit>
+ <edit name="rgba" mode="assign"><const>rgb</const> </edit>
+ </match>
+
+ </fontconfig></programlisting>
+ </sect3>
+
+ <sect3 xml:id="does-having-os.windows-installed-elsewhere-on-a-system-help-wine-operate">
+ <title>Does having &amp;os.windows; installed elsewhere on a
+ system help WINE operate?</title>
+
+ <para>It may, depending on the application being run. As mentioned
+ in the section describing <application>winecfg</application>, some
+ built-in WINE DLLs and other libraries can be overridden by providing
+ a path to an alternate version. Provided the &amp;os.windows;
+ partition or drive is mounted to the &amp;os; system and
+ accessible to the user, configuring some of these overrides
+ will use native &amp;os.windows; libraries and may decrease
+ the chance of unexpected behavior.</para>
+ </sect3>
+ </sect2>
+
+ <sect2 xml:id="application-specific">
+ <title>Application-Specific</title>
+
+ <sect3 xml:id="where-is-the-best-place-to-see-if-application-x-works-on-wine">
+ <title>Where is the best place to see if application X works on
+ WINE?</title>
+
+ <para>The first stop in determining compatibiliy should be the
+ <link xlink:href="https://appdb.winehq.org/"> WINE AppDB</link>.
+ This is a compilation of reports of programs working (or not) on
+ all supported platforms, although (as previously mentioned), solutions
+ for one platform are often applicable to others.</para>
+ </sect3>
+
+ <sect3 xml:id="is-there-anything-that-will-help-games-run-better">
+ <title>Is there anything that will help games run
+ better?</title>
+
+ <para>Perhaps. Many &amp;os.windows; games rely on DirectX, a
+ proprietary Microsoft graphics layer. However there are
+ projects in the open source community attempting to implement
+ support for this technology.</para>
+
+ <para>The <emphasis>dxvk</emphasis> project, which is an attempt to
+ implement DirectX using the &amp;os;-compatible Vulkan
+ graphics sub-system, is one such. Although its primary target
+ is WINE on Linux,
+ <link xlink:href="https://forums.freebsd.org/threads/what-about-gaming-on-freebsd.723/page-9">some
+ &amp;os; users report</link> compiling and using dxvk.</para>
+
+ <para>In addition, work is underway on a
+ <application>wine-proton</application>
+ <link xlink:href="https://www.freshports.org/emulators/wine-proton/">port</link>.
+ This will bring the work of Valve, developer of the Steam
+ gaming platform, to &amp;os;. Proton is a distribution of WINE
+ designed to allow many &amp;os.windows; games to run on other
+ operating systems with minimal setup.</para>
+ </sect3>
+
+ <sect3 xml:id="is-there-anywhere-freebsd-wine-users-gather-to-exchange-tips-and-tricks">
+ <title>Is there anywhere FreeBSD WINE users gather to exchange
+ tips and tricks?</title>
+
+ <para>There are plenty of places FreeBSD users discuss issues
+ related to WINE that can be searched for solutions:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><link xlink:href="https://forums.freebsd.org/">The FreeBSD
+ forums</link>, particularly the <emphasis>Installation and
+ Maintenance of Ports or Packages</emphasis> or
+ <emphasis>Emulation and virtualization</emphasis> forums.</para>
+ </listitem>
+
+ <listitem>
+ <para><link xlink:href="https://wiki.freebsd.org/IRC/Channels">FreeBSD
+ IRC channels</link> including #freebsd (for general
+ support), #freebsd-games, and others.</para>
+ </listitem>
+
+ <listitem>
+ <para><link xlink:href="https://discord.gg/2CCuhCt">The BSD
+ World Discord server's</link> channels including
+ <emphasis>bsd-desktop</emphasis>,
+ <emphasis>bsd-gaming</emphasis>,
+ <emphasis>bsd-wine</emphasis>, and others.</para>
+ </listitem>
+ </itemizedlist>
+ </sect3>
+ </sect2>
+
+ <sect2 xml:id="other-os-resources">
+ <title>Other OS Resources</title>
+
+ <para>There are a number of resources focused on other operating
+ systems that may be useful for &amp;os; users:</para>
+
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para><link xlink:href="https://wiki.winehq.org/">The WINE
+ Wiki</link> has a wealth of information on using WINE, much
+ of which is applicable across many of WINE's supported
+ operating systems.</para>
+ </listitem>
+
+ <listitem>
+ <para>Similarly, the documentation available from other OS
+ projects can also be of good value.
+ <link xlink:href="https://wiki.archlinux.org/index.php/wine">The
+ WINE page</link> on the Arch Linux Wiki is a particularly
+ good example, although some of the &quot;Third-party
+ applications&quot; (i.e. &quot;companion applications&quot;)
+ are obviously not avaialble on &amp;os;.</para>
+ </listitem>
+
+ <listitem>
+ <para>Finally, Codeweavers (a developer of a commerical version of
+ WINE) is an active upstream contributor. Often times answers
+ to questions in
+ <link xlink:href="https://www.codeweavers.com/support/forums">their
+ support forum</link> can be of aid in troubleshooting
+ problems with the open source version of WINE.</para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+ </sect1>
+

File Metadata

Mime Type
text/plain
Expires
Thu, Feb 19, 3:25 PM (2 h, 29 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
28859444
Default Alt Text
D27455.id80317.diff (10 KB)

Event Timeline