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 @@ + + + WINE on &os; FAQ + + The following section describes some frequently asked questions, + tips/tricks, or common issues in running WINE on &os;, along + with their respective answers. + + + Basic Installation and Usage + + + How to install 32-bit and 64-bit WINE on the same + system? + + As described earlier in this section, the + wine and + i386-wine 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 + not mean building the port). + + + + Can DOS Programs Be Run on WINE? + + They can, as "Console User Interface" applications + as mentioned eariler in this section. However, there is an + arguably better method for running DOS software: + DOSBox. 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. + + + + Should the "wine-devel" package/port be + installed to use the development version of WINE instead of + stable? + + Yes, installing this version will install the + "development" 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. + + Note that WINE also has a "Staging" version, which + contains the most recent updates. This was at one time + available as a &os; port; however, it has since been + removed. It can be compiled directly from source however. + + + + + Install Optimization + + + How should &os.windows; hardware (e.g. graphics) drivers be + handled? + + 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. + + + + Is there a way to make &os.windows; fonts look + better? + + A user on the FreeBSD forums suggests this configuration to + fix out-of-the-box look of WINE fonts, which can be slightly + pixelated. + + According to a post in the FreeBSD Forums, + adding the following to the + .config/fontconfig/fonts.conf file will + add anti-aliasing and make text more readable. + + + + + + + + + true + true + hintslight + rgb + + + + + + + Does having &os.windows; installed elsewhere on a + system help WINE operate? + + It may, depending on the application being run. As mentioned + in the section describing winecfg, some + built-in WINE DLLs and other libraries can be overridden by providing + a path to an alternate version. Provided the &os.windows; + partition or drive is mounted to the &os; system and + accessible to the user, configuring some of these overrides + will use native &os.windows; libraries and may decrease + the chance of unexpected behavior. + + + + + Application-Specific + + + Where is the best place to see if application X works on + WINE? + + The first stop in determining compatibiliy should be the + WINE AppDB. + 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. + + + + Is there anything that will help games run + better? + + Perhaps. Many &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. + + The dxvk project, which is an attempt to + implement DirectX using the &os;-compatible Vulkan + graphics sub-system, is one such. Although its primary target + is WINE on Linux, + some + &os; users report compiling and using dxvk. + + In addition, work is underway on a + wine-proton + port. + This will bring the work of Valve, developer of the Steam + gaming platform, to &os;. Proton is a distribution of WINE + designed to allow many &os.windows; games to run on other + operating systems with minimal setup. + + + + Is there anywhere FreeBSD WINE users gather to exchange + tips and tricks? + + There are plenty of places FreeBSD users discuss issues + related to WINE that can be searched for solutions: + + + + The FreeBSD + forums, particularly the Installation and + Maintenance of Ports or Packages or + Emulation and virtualization forums. + + + + FreeBSD + IRC channels including #freebsd (for general + support), #freebsd-games, and others. + + + + The BSD + World Discord server's channels including + bsd-desktop, + bsd-gaming, + bsd-wine, and others. + + + + + + + Other OS Resources + + There are a number of resources focused on other operating + systems that may be useful for &os; users: + + + + The WINE + Wiki has a wealth of information on using WINE, much + of which is applicable across many of WINE's supported + operating systems. + + + + Similarly, the documentation available from other OS + projects can also be of good value. + The + WINE page on the Arch Linux Wiki is a particularly + good example, although some of the "Third-party + applications" (i.e. "companion applications") + are obviously not avaialble on &os;. + + + + Finally, Codeweavers (a developer of a commerical version of + WINE) is an active upstream contributor. Often times answers + to questions in + their + support forum can be of aid in troubleshooting + problems with the open source version of WINE. + + + + +