documentation/faq.sgml

   1 <!-- *** Wine FAQ *** -->
   2   <title>Wine FAQ</title>
   3
   4   <qandaset>
   5     <qandadiv id="About-this-FAQ"><title>About this FAQ</title>
   6       <qandaentry>
   7       <question id="Who-maintains-this-FAQ">
   8         <para>Who maintains this FAQ ?</para>
   9       </question>
  10       <answer>
  11         <para>Dave Gardner maintained it from 1995-1998.</para>
  12         <para>Douglas Ridgway (ridgway@winehq.org) took it over in 1999.</para>
  13         <para>Andreas Mohr (amohr@codeweavers.com) converted it to FAQ-O-Matic in 2000.</para>
  14         <para>Dimitrie O. Paun, Keith Matthews and Tom Wickline (in alphabetical order) reorganized it in 2002.</para>
  15         <para>For suggestions/additions/complaints regarding this FAQ, please send an email to
  16         <ulink url="mailto:wine-faq@winehq.org">wine-faq@winehq.org</ulink></para>
  17       </answer>
  18       </qandaentry>
  19       <qandaentry>
  20       <question id="What-is-the-copyright-on-the-FAQ-And">
  21         <para>What is the copyright on the FAQ? And how may I use it?</para>
  22       </question>
  23       <answer>
  24         <para>The original Wine FAQ, which this FAQ was based on, was copyright &copy; 1995-1998 David Gardner.</para>
  25         <para>It may be reproduced and modified under the same terms as Wine itself.</para>
  26       </answer>
  27       </qandaentry>
  28     </qandadiv>
  29     <qandadiv id="General-Questions-about-Wine">
  30       <title>General Questions about Wine</title>
  31       <qandaentry>
  32
  33       <question id="What-is-Wine-and-what-is-it-supposed-to">
  34         <para>What is Wine and what is it supposed to do?</para>
  35       </question>
  36       <answer>
  37         <para>
  38           Wine is a program which allows the operation of DOS and MS
  39           Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems such as Linux.
  40           It consists of a program loader, which loads and executes a Windows
  41           binary, and a set of libraries that implements Windows API calls
  42           using their UNIX or X11 equivalents. The libraries may also be used
  43           for porting Win32 code into native UNIX executables, often
  44           without many changes in the source. Wine is free software,
  45           and its license (contained in the file LICENSE
  46           in each distribution) is the LGPL.
  47         </para>
  48       </answer>
  49       </qandaentry>
  50
  51      <qandaentry>
  52       <question id="Is-Wine-an-emulator">
  53         <para>Does Wine emulate a full computer?</para>
  54       </question>
  55       <answer>
  56         <para>
  57           No, as the name says, Wine Is Not a (CPU) Emulator. Wine just
  58           provides the Windows API. This means that you will need an
  59           x86-compatible processor to run an x86 Windows application, for instance from Intel or AMD. The
  60           advantage is that, unlike solutions that rely on CPU emulation, Wine
  61           runs applications at full speed. Sometimes a program run under
  62           Wine will be slower than when run on a copy of Microsoft Windows, but
  63           this is more due to the fact that Microsoft have heavily optimized parts of their
  64           code, whereas mostly Wine is not well optimized (yet). Occasionally, an app
  65           may run faster under Wine than on Windows. Most apps run at roughly the same speed.
  66        </para>
  67       </answer>
  68       </qandaentry>
  69
  70       <qandaentry>
  71       <question id="Are-here-any-alternatives-to-Wine">
  72         <para>Are there any alternatives to Wine?</para>
  73       </question>
  74       <answer>
  75         <para>
  76           Yes, there are. You can use <ulink url="http://www.vmware.com">VMWare</ulink> to run a Windows installation inside a virtual machine,
  77           or use <ulink url="http://www.win4lin.com">Win4Lin</ulink>
  78           to run a specially adapted Windows version on Linux.
  79           Both solutions cost money for both the software itself
  80           and a Windows license.
  81        </para>
  82        <para>
  83          Note that, like Wine, they can only use the hardware platform that
  84          the target programs were originally compiled for (see below).
  85        </para>
  86       </answer>
  87       </qandaentry>
  88
  89       <qandaentry>
  90       <question id="Difference-between-Wine-and-emulators">
  91         <para>What is the difference between Wine and x86 hardware emulators?</para>
  92       </question>
  93       <answer>
  94         <para>
  95           There are two free x86 hardware emulators:
  96           <ulink url="http://bochs.sourceforge.net">Bochs</ulink>, and
  97           <ulink url="http://savannah.nongnu.org/projects/plex86">Plex86</ulink>.
  98        </para>
  99
 100        <para>
 101           Plex86 is the open-source free-software alternative for VMWare,
 102           VirtualPC, and other IA-32 on IA-32 "Virtual PC products." It
 103           can only run on the IA-32 architecture.
 104        </para>
 105
 106        <para>
 107           Bochs is a highly portable open source IA-32 (x86) PC emulator
 108           written in C++, that runs on most popular platforms. It includes emulation
 109           of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently,
 110           Bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
 111           of running most Operating Systems inside the emulation including Linux,
 112           Windows® 95, DOS, and recently Windows® NT 4.
 113        </para>
 114
 115        <para>
 116           Both are licensed under the GPL. Bochs is older than Plex86, seems to be
 117           easier to install, but Plex86 will run faster because Plex86 uses a just in
 118           time binary compiler.
 119        </para>
 120        <para>
 121           The drawback of all emulators is that you need a version
 122           of Windows in order to run Windows, and that they all have an
 123           impact on performance. Wine also gives much better desktop integration - for
 124           instance, programs use your standard window manager, system tray icons will
 125           appear in your tray area (if you have one), and you can run programs direct from the
 126           command line and the menus. The clipboard also works seamlessly.
 127        </para>
 128
 129       </answer>
 130       </qandaentry>
 131
 132       <qandaentry>
 133       <question id="Integrate-an-x86-emulator">
 134         <para>When will Wine integrate an x86 CPU emulator so we can
 135           run Windows applications on non-x86 machines?</para>
 136       </question>
 137       <answer>
 138         <para>
 139           The short answer is 'probably never'. Remember, Wine Is Not a
 140           (CPU) Emulator. The long answer is that we probably don't want or
 141           need to integrate one in the traditional sense.
 142         </para>
 143         <para>
 144           Integrating a CPU emulator in Wine would be extremely hard,
 145           due to the large number of Windows APIs and the complex
 146           data types they exchange. It is not uncommon for a Windows API to
 147           take three or more pointers to structures composed of many fields,
 148           including pointers to other complex structures. For each of these
 149           we would need a conversion routine to deal with the byte order and
 150           alignment issues. Furthermore, Windows also contains many callback
 151           mechanisms that constitute as many extra places where we would have
 152           to handle these conversion issues. Wine already has to deal with
 153           16 vs. 32 bit APIs and Ansi vs. Unicode APIs which both
 154           introduce significant complexity. Adding support for a CPU emulator
 155           inside Wine would introduce at least double that complexity and
 156           only serve to slow down the development of Wine.
 157         </para>
 158         <para>
 159           Fortunately another solution exists to run Windows applications
 160           on non-x86 platforms: run both Wine and the application inside the
 161           CPU emulator. As long as the emulator provides a standard Unix
 162           environment, Wine should only need minimal modifications. What
 163           performance you lose due to Wine running inside the emulator
 164           rather than natively, you gain in complexity inside of Wine.
 165           Furthermore, if the emulator is fast enough to run Windows
 166           applications, Photoshop for instance, then it should be fast enough
 167           to run that same Windows application plus Wine.
 168         </para>
 169         <para>
 170           Two projects have started along those lines: <ulink
 171           url="http://fabrice.bellard.free.fr/qemu/">QEMU</>, an
 172           open-source project, and <ulink
 173           url="http://www.transitives.com/tech_overview.htm">Dynamite</>,
 174           a commercial CPU emulator environment from
 175           <ulink url="http://www.transitives.com/">Transitives Technologies</>
 176           which has been <ulink
 177           url="http://www.transgaming.com/news.php?newsid=37">paired
 178           with Wine</>.
 179         </para>
 180
 181       </answer>
 182       </qandaentry>
 183
 184       <qandaentry>
 185       <question id="Why-would-anyone-want-Wine-Windows-suck">
 186         <para>Why would anyone want Wine? Doesn't Windows suck?</para>
 187       </question>
 188       <answer>
 189         <para>
 190           First Wine is not about running Windows but about running Windows
 191           applications.
 192         </para>
 193         <para>
 194           So if all your computing needs are fulfilled by native Unix
 195           applications, then you do not need Wine and should not be using
 196           it. However, if you depend on one or more of the tens of
 197           thousands of Windows applications, then Wine is the best way to
 198           use it without giving up on Unix. Let's look at the alternatives
 199           to see why:
 200         </para>
 201         <para>
 202           The most obvious alternative is to dual-boot. This is the solution
 203           that provides the best compatibility. However it requires that you
 204           acquire a Windows license and then dedicate a good chunk of your
 205           hard-drive to Windows. But the worst is yet to come. Each time you
 206           will want to use that application you will have to reboot to
 207           Windows. This is especially significant if external factors dictate
 208           when you must use this application (e.g. credit card to process,
 209           email to retrieve from a Lotus Notes server). Then you will find
 210           yourself forced to close all your Linux applications just to run
 211           that one Windows application. You may quickly get tired of this, or
 212           will find that such a situation is impossible to justify in a
 213           business environment.
 214         </para>
 215         <para>
 216           The next solution is to install virtual machine emulation software
 217           such as VMWare, Win4Lin or Plex86. Then you can use windows
 218           applications without suffering such a big disruption. But it still
 219           requires that you acquire a Windows license and dedicate as much
 220           disk space to Windows. Furthermore you will pay for the added
 221           convenience: if using VMWare or Win4Lin you have to buy another
 222           license, and more importantly you now have to dedicate a good chunk
 223           of your computer's memory to the virtual machine. Performance will
 224           take a significant hit too.
 225         </para>
 226         <para>
 227           Using Wine lets you avoid all of that overhead: Windows license,
 228           hard-drive space required by Windows, memory and performance hit
 229           taken by emulated virtual machines. Now you can start your Windows
 230           application straight from your regular desktop environment, place
 231           that application's window side by side with native applications,
 232           copy/paste from one to the other, and run it all at full speed.
 233         </para>
 234         <para>
 235           It is also a pretty vital part of migrating a large organization,
 236           you can't change a 5000 desktop setup overnight without a lot of risk.
 237        </para>
 238       </answer>
 239       </qandaentry>
 240
 241       <qandaentry>
 242       <question id="Use-Windows-driver-with-Wine">
 243         <para>Can I use Wine to make the Windows driver for my network card /
 244           graphics card / scanner / etc. work on Unix?</para>
 245       </question>
 246       <answer>
 247         <para>
 248           The goal of Wine is to make it possible to run Windows applications
 249           on Unix, not Windows drivers or VxDs.
 250         </para>
 251         <para>
 252           Drivers and Windows applications belong to different worlds.
 253           Applications run in user mode and use the APIs provided by
 254           the kernel and the other user mode dlls. In contrast, drivers
 255           are loaded in the Windows kernel, i.e. in ring 0 instead of ring
 256           3, have to deal with specific memory management issues, and use
 257           instructions not available to regular applications. This means
 258           they would not be able to run in Wine since Wine runs entirely
 259           in user mode. Rather you would have to modify the Linux kernel.
 260           But in addition, drivers use a completely different API from
 261           regular Windows applications. So the work performed on Wine would
 262           not even be of any use for such a project. In other words, making
 263           it possible to use Windows drivers or VxDs on Unix would be a
 264           completely separate project.
 265         </para>
 266         <para>
 267           However, if you want to reuse Windows drivers on a non-Microsoft
 268           operating system we recommend that you have a look at
 269           <ulink url="http://www.reactos.com/">ReactOS</>.
 270         </para>
 271
 272       </answer>
 273       </qandaentry>
 274
 275       <qandaentry>
 276       <question id="Which-one-of-the-different-Wine-packages">
 277         <para>Which one of the different Wine packages out there is good for me?</para>
 278       </question>
 279       <answer>
 280         <para>
 281           Currently there is a broad selection of different Wine packages/versions:
 282         </para>
 283         <variablelist>
 284
 285           <varlistentry>
 286            <term><ulink url="http://www.winehq.org">Wine</ulink></term>
 287            <listitem>
 288            <para>
 289               This is the "standard" source distribution of Wine. Its license is
 290               the LGPL, it can be downloaded for free.
 291             </para>
 292            </listitem>
 293           </varlistentry>
 294
 295           <varlistentry>
 296           <term><ulink url="http://rewind.sourceforge.net">ReWind</ulink></term>
 297           <listitem>
 298             <para>
 299               This is a forked Wine tree that got created when Wine changed its
 300               license from X11 to the more restrictive LGPL, in order to let
 301               people continue to maintain an X11 licensed Wine version. Its
 302               license is X11, it can be downloaded for free.
 303             </para>
 304           </listitem>
 305           </varlistentry>
 306
 307           <varlistentry>
 308           <term><ulink url="http://www.transgaming.com">TransGaming's WineX</ulink></term>
 309           <listitem>
 310             <para>
 311               This is TransGaming's Wine version specially suited for
 312               games.  It includes more mature Direct3D support than
 313               WineHQ, although these days WineHQ has quite advanced
 314               D3D support as well. Most of the code is under the AFPL
 315               and can be downloaded for free.
 316             </para>
 317             <para>
 318               However TransGaming also distributes binaries that contain
 319               improved copy protection support (needed for many
 320               games), support, and other enhancements. These packages are
 321               only available in binary form to subscribed customers
 322               ($5/month).
 323             </para>
 324          </listitem>
 325           </varlistentry>
 326
 327           <varlistentry>
 328           <term><ulink url="http://wine.codeweavers.com">CodeWeavers' Wine preview</ulink></term>
 329           <listitem>
 330             <para>
 331               This is a special packaged version of the standard Wine tree
 332               which has a nice setup for easy installation. License LGPL, free
 333               download. It's pretty old now, and not recommended for general use.
 334             </para>
 335          </listitem>
 336           </varlistentry>
 337
 338           <varlistentry>
 339           <term><ulink url="http://www.codeweavers.com/products/crossover/">CodeWeavers' CrossOver Plugin</ulink></term>
 340           <listitem>
 341             <para>
 342               Special Wine installation to be used for running Windows
 343               Netscape browser plugins such as e.g. QuickTime in Linux
 344               browsers. Costs $34.95.
 345               Well worth it (very stable and useful packaging).
 346             </para>
 347           </listitem>
 348           </varlistentry>
 349
 350           <varlistentry>
 351           <term><ulink url="http://www.codeweavers.com/products/office/">CodeWeavers' CrossOver Office</ulink></term>
 352           <listitem>
 353             <para>
 354               Wine version with special packaging to make sure almost all
 355               important Office type programs work pretty well. Costs $54.95.
 356               Seems to be well worth it so far according to some comments.
 357               (note: you're supporting a company actively contributing to Wine
 358               if you decide to buy either Plugin or Office.)
 359             </para>
 360           </listitem>
 361           </varlistentry>
 362
 363           <varlistentry>
 364           <term><ulink url="http://www.codeweavers.com/products/cxofficeserver/">CodeWeavers' CrossOver Office Server Edition</ulink></term>
 365           <listitem>
 366             <para>
 367              Allows you to run your favorite Windows productivity applications in
 368              a distributed thin-client environment under Linux. Server Edition is
 369              also a great addition to Solaris environments, since there built-in
 370              support for Solaris desktops makes running Windows applications a
 371              possibility on Sun workstations as well. For pricing just follow this link:
 372           <ulink url="http://www.codeweavers.com/products/pricing.php">CrossOver Office Server Edition Pricing</ulink>
 373             </para>
 374           </listitem>
 375           </varlistentry>
 376
 377           <varlistentry>
 378           <term><ulink url="http://www.winehq.org/download/">Other packaged versions of Wine</ulink></term>
 379           <listitem>
 380             <para>
 381               Various Wine packages can be downloaded for free from
 382               Wine HQ. They are not officially packaged by Wine HQ, and as
 383               such may have some configuration inconsistencies.
 384             </para>
 385           </listitem>
 386           </varlistentry>
 387         </variablelist>
 388       </answer>
 389       </qandaentry>
 390
 391       <qandaentry>
 392       <question id="Whats-the-history-of-Wine">
 393         <para>What's the history of Wine?</para>
 394       </question>
 395       <answer>
 396         <para>
 397           The Wine project started in 1993 as a way to support running Windows 3.1
 398           programs on Linux. Bob Amstadt was the original coordinator, but turned
 399           it over fairly early on to Alexandre Julliard, who has run it ever
 400           since. A <ulink url="news:comp.emulators.ms-windows.wine">newsgroup</ulink>
 401           was created in July 1994. Over the years, ports for
 402           other Unixes have been added, along with support for Win32 as Win32
 403           applications became popular.
 404         </para>
 405         <para>
 406           For more information, see <ulink url="http://www.winehq.org/site/about">
 407           http://www.winehq.org/site/about</ulink>
 408         </para>
 409       </answer>
 410       </qandaentry>
 411
 412       <qandaentry>
 413       <question id="What-is-the-current-version-of-Wine">
 414         <para>What is the current version of Wine?</para>
 415       </question>
 416       <answer>
 417         <para>
 418           A new version of Wine is distributed about every month. You will be
 419           able to keep up on all the latest releases by reading the newsgroup
 420           <ulink url="news:comp.emulators.ms-windows.wine">
 421           comp.emulators.ms-windows.wine</ulink>, or by visiting the
 422           <ulink url="http://www.winehq.org">Wine HQ homepage</ulink>. When
 423           downloading Wine from your FTP site of choice (see
 424           <ulink url="http://www.winehq.org/download.shtml">the Download page</ulink>
 425           for some of these choices), you can make sure that you are getting
 426           the latest version by watching the version numbers in the distribution
 427           file name. For instance, the distribution released on August 13, 2003
 428           was called Wine-20030813.tar.gz. Patch files are also available. If
 429           you are current to the previous version, you can download and apply
 430           just the current patch file rather than the entire new distribution.
 431           The patch file names follow the same conventions as the monthly
 432           distribution. <ulink url="http://www.winehq.org/site/cvs">
 433           Read-only CVS</ulink> access is also available.
 434         </para>
 435       </answer>
 436       </qandaentry>
 437
 438       <qandaentry>
 439       <question id="What-is-the-current-Status-of-Wine">
 440         <para>What is the current Status of Wine?</para>
 441       </question>
 442       <answer>
 443         <para>
 444           As of mid 2003, Wine consists of about 1.4 million lines of code,
 445           written by more than 550 developers from dozens of countries around
 446           the world. Wine is in active use by an estimated 100K people. Wine
 447           implements more than 90% of the calls in popular Windows
 448           specifications such as ECMA-234 and Open32.
 449         </para>
 450         <para>
 451           You may also want to look at the
 452           <ulink url="http://www.winehq.org/site/status">
 453           Status page</ulink> for a global view on Wine's implementation progress.
 454         </para>
 455       </answer>
 456       </qandaentry>
 457
 458       <qandaentry>
 459       <question id="When-will-Wine-be-finished">
 460         <para>When will Wine be finished?</para>
 461       </question>
 462       <answer>
 463         <para>
 464           Large software projects are never finished, only released. In any
 465           case Wine is chasing a moving target since every new release of
 466           Windows contains new API calls or variations on the existing ones.
 467         </para>
 468         <para>
 469           Because Wine is being developed by volunteers, it is difficult to
 470           predict when it will be ready for general release. But due to the
 471           much increased interest by companies in porting apps via Wine, Wine
 472           development is constantly getting more and more active. Right now
 473           we are working on releasing Wine 0.9 in 2003.
 474         </para>
 475       </answer>
 476       </qandaentry>
 477
 478       <qandaentry>
 479       <question id="Who-is-responsible-for-Wine">
 480         <para>Who is responsible for Wine?</para>
 481       </question>
 482       <answer>
 483         <para>
 484           Wine is available thanks to the work of many people. Please see the
 485           <ulink url="http://source.winehq.org/source/AUTHORS">AUTHORS</ulink>
 486           file in the distribution for the complete list. Some companies that
 487           are or have been involved with Wine development are CodeWeavers,
 488           TransGaming, Corel, and Macadamian.
 489         </para>
 490       </answer>
 491       </qandaentry>
 492
 493       <qandaentry>
 494       <question id="folks-who-contributed-money-or-equipment">
 495         <para>Who are the folks and organizations who have contributed money or equipment to the Wine project?</para>
 496       </question>
 497       <answer>
 498         <para>
 499           People and organizations who have given generous contributions of
 500           money, equipment, or licenses, include:
 501         </para>
 502         <itemizedlist spacing="compact">
 503           <listitem>
 504             <para>David L. Harper</para>
 505           </listitem>
 506           <listitem>
 507             <para>Bob Hepple</para>
 508           </listitem>
 509           <listitem>
 510             <para>Mark A. Horton</para>
 511           </listitem>
 512           <listitem>
 513             <para>Kevin P. Lawton</para>
 514           </listitem>
 515           <listitem>
 516             <para>The Syntropy Institute</para>
 517           </listitem>
 518           <listitem>
 519             <para>James Woulfe</para>
 520           </listitem>
 521           <listitem>
 522             <para>
 523              VMWare Inc. (<ulink url="http://www.vmware.com">
 524              http://www.vmware.com</ulink>)
 525             </para>
 526           </listitem>
 527           <listitem>
 528             <para>
 529              Corel (<ulink url="http://www.corel.com">
 530              http://www.corel.com</ulink>)
 531             </para>
 532           </listitem>
 533           <listitem>
 534             <para>
 535              CodeWeavers
 536              (<ulink url="http://www.codeweavers.com/">http://www.codeweavers.com</ulink>)
 537             </para>
 538           </listitem>
 539         </itemizedlist>
 540       </answer>
 541       </qandaentry>
 542
 543       <qandaentry>
 544       <question id="What-undocumented-APIs-are-not-understood">
 545         <para>What undocumented APIs / interfaces are not understood? Would
 546               seeing Microsoft source help?
 547         </para>
 548       </question>
 549       <answer>
 550         <para>
 551           The best would be if the Windows API was fully documented, so Wine
 552           could be a perfect "clean-room" implementation. Seeing the source
 553           code might make it harder to prove that no copyright violations have
 554           taken place. That said, the documentation is often bad, nonexistent,
 555           and even misleading where it exists, so a fair amount of reverse
 556           engineering has been necessary, particularly in the shell (Explorer)
 557           interface. The biggest problem facing Wine though is simply lack of
 558           manpower. At one point, over 5000 people were working on Windows 2000.
 559           While Wine doesn't need to replicate all of Windows (we only cover the
 560           parts needed to make Windows programs work), that's still nearly 10 times
 561           more people working simply on one release than have <emphasis>ever</emphasis>
 562           worked on Wine, in the history of the project.
 563         </para>
 564       </answer>
 565       </qandaentry>
 566
 567      <qandaentry>
 568       <question id="Is-TransGamings-last-patch-included-in-Wine">
 569         <para>Is TransGaming's latest patch included in the standard Wine release?</para>
 570       </question>
 571       <answer>
 572         <para>
 573           No, it's not.
 574         </para>
 575         <para>
 576           TransGaming makes money via a subscription service and the license
 577           of their WineX tree is incompatible with the Wine license. Thus
 578           WineX patches cannot be integrated into the Wine tree without
 579           express permission by TransGaming. They have submitted some
 580           of their work for integration into Wine, most notably DirectDraw
 581           and some DirectSound work, and such work has been integrated into
 582           the Wine tree. However it seems unlikely they will submit their
 583           Direct3D work.
 584         </para>
 585       </answer>
 586       </qandaentry>
 587
 588       <qandaentry>
 589       <question id="Will-there-be-a-Windows-version-of-Wine">
 590         <para>Will there be a Windows version of Wine?</para>
 591       </question>
 592       <answer>
 593         <para>
 594           Some people are working on getting Wine code to compile on Windows
 595           using one of the following projects as a basis:
 596         </para>
 597         <itemizedlist spacing="compact">
 598           <listitem>
 599             <para>
 600               Cygwin
 601               (<ulink url="http:/www.cygwin.com/">http://www.cygwin.com</ulink>)
 602             </para>
 603           </listitem>
 604           <listitem>
 605             <para>
 606               MinGW
 607               (<ulink url="http:/www.mingw.org/">http://www.mingw.org</ulink>)
 608             </para>
 609           </listitem>
 610           <listitem>
 611             <para>
 612               ReactOS
 613               (<ulink url="http://www.reactos.com/">http://www.reactos.com</ulink>)
 614             </para>
 615           </listitem>
 616         </itemizedlist>
 617         <para>
 618           There's some progress, so a Wine version that's usable on Windows
 619           might be available at some time.
 620         </para>
 621         <para>
 622           Part of the rationale for these projects is to find out areas where
 623           Wine portability is lacking. This is especially true of the
 624           ReactOS project which is a reimplementation of the Windows kernel
 625           and should thus be able to reuse most of Wine dlls.
 626         </para>
 627         <para>
 628           Another reason for pursuing these projects is to be able to
 629           replace a single Windows dll with its Wine counterpart. Besides
 630           being a good test for the Wine dll, this lets us detect cases where
 631           we made incorrect assumptions about how the dlls interact.
 632         </para>
 633       </answer>
 634       </qandaentry>
 635
 636     </qandadiv>
 637     <qandadiv id="What-do-I-need-in-order-to-use-Wine">
 638       <title>What do I need in order to use Wine?</title>
 639       <qandaentry>
 640       <question id="Under-what-platforms-will-Wine-run">
 641         <para>
 642           Under what hardware platform(s) and operating system(s) will
 643           Wine(Lib) run?
 644         </para>
 645       </question>
 646       <answer>
 647         <para>
 648           Wine is being developed specifically to run on the <emphasis>Intel
 649           x86</emphasis> class of CPUs under certain UNIXes that run on this
 650           platform. Winelib however is capable of porting the Windows
 651           applications <emphasis>source code</emphasis> to other platforms
 652           also, not only x86.
 653         </para>
 654         <para>
 655           Thus running Windows binaries on other platforms (e.g. Mac OS X on
 656           PowerPC) using just Wine is <emphasis>not</emphasis> possible. You
 657           would have to either run Wine in an emulated x86 environment or
 658           take the Windows application source code and recompile it using
 659           Winelib.
 660         </para>
 661         <para>
 662           These are the platforms supported by Wine.
 663           Winelib support for other platforms keeps evolving,
 664           so it's not specifically listed here.
 665         </para>
 666         <para>
 667           NetBSD, OpenBSD, UnixWare, and SCO OpenServer 5 worked at one time,
 668           but Wine now requires kernel-level threads which are not currently
 669           available (or understood by the Wine team) on those platforms.
 670         </para>
 671         <para>
 672           The Wine development team hopes to attract the interest of other
 673           commercial UNIX and UNIX clone vendors as well.
 674         </para>
 675         <para>
 676           BeOS: porting efforts (BeWine) used to be pretty strong, but BeOS
 677           has severe limitations in Unix call support. The demise of Be
 678           further hampered the project though it might come back one day on
 679           one of the open BeOS projects. In any case a functional port seems
 680           unlikely to ever happen at this stage.
 681         </para>
 682         <para>
 683           Mac OS X / Darwin: The <ulink
 684           url="http://darwine.sourceforge.net/project.html">Darwine</> is
 685           currently working on porting Wine to the Darwin/x86 platform. Their
 686           goal is to eventually make it possible to run x86 Windows
 687           applications on Darwin/PPC and then Mac OS X by using Bochs.
 688         </para>
 689         <para>
 690           FreeBSD: This port is well maintained and should work with
 691           limitations in specific areas (mainly missing device/hardware
 692           support).
 693         </para>
 694         <para>
 695           Linux/x86: Works, and as the most popular platform for both
 696           developers and users, it is the best supported platform of all.
 697         </para>
 698       </answer>
 699       </qandaentry>
 700
 701       <qandaentry>
 702       <question id="What-minimum-CPU-must-I-have">
 703         <para>
 704           What minimum CPU must I have in my computer to be able to run Wine
 705           and MS Windows applications smoothly?
 706         </para>
 707       </question>
 708       <answer>
 709         <para>
 710           We need to differentiate between Wine and Winelib here.
 711         </para>
 712         <para>
 713           Wine won't run on any x86 CPU less than an 80386 due to address
 714           management limitations.
 715         </para>
 716         <para>
 717           It is known to also work in the 80486 and upwards compatible CPUs.
 718           The basic test is, if you can run X11 now, you should be able to run
 719           Wine and MS Windows applications under it.
 720         </para>
 721         <para>
 722           As always, the faster your CPU, the better. Having a math coprocessor
 723           is unimportant. However, having a graphics accelerated video card
 724           supported by X will help greatly.
 725         </para>
 726         <para>
 727           Depending on your application you may find that faster speeds are
 728           required for sensible use. We can't give specific advice on that due
 729           to the vast range of applications out there. However the rule of
 730           thumb is that if your application runs fine on Windows, it should
 731           run fine on the same platform in Wine.
 732         </para>
 733       </answer>
 734       </qandaentry>
 735
 736       <qandaentry>
 737       <question id="How-much-disk-space-will-Wine-take">
 738         <para>
 739          How much disk space will the Wine source code and binaries take on my
 740          hard drive?
 741         </para>
 742       </question>
 743       <answer>
 744         <para>
 745           You need approximately 250 megabytes of free hard drive space to
 746           store and compile the source code. Wine also needs about 18 megs in
 747           your /tmp directory. And about 50 MB are needed to do a make install.
 748         </para>
 749         <para>
 750           Binary packages, especially those not containing debug information,
 751           have much lower disk space requirements, usually in the 20MB range.
 752         </para>
 753       </answer>
 754       </qandaentry>
 755
 756       <qandaentry>
 757       <question id="What-other-software-do-I-need-to-compile">
 758         <para>
 759           What other software do I need to install, compile and run
 760           Wine?
 761         </para>
 762       </question>
 763       <answer>
 764         <para>
 765           Many development tools are needed in order to compile Wine.
 766           A list of required packages for several distributions is included in
 767           the README (<ulink url="http://source.winehq.org/source/README">
 768           http://source.winehq.org/source/README</ulink>).
 769         </para>
 770         <para>
 771           To run Wine, you will need the following:
 772         </para>
 773
 774         <itemizedlist spacing="compact">
 775           <listitem>
 776             <para>The compiled Wine binary</para>
 777           </listitem>
 778           <listitem>
 779             <para>A properly configured wine.conf file (or ~/.winerc file)</para>
 780           </listitem>
 781           <listitem>
 782             <para>An installed and working X Window system</para>
 783           </listitem>
 784           <listitem>
 785             <para>Some Windows programs to test</para>
 786           </listitem>
 787         </itemizedlist>
 788       </answer>
 789       </qandaentry>
 790        <qandaentry>
 791       <question id="How-much-RAM-do-I-need">
 792         <para>
 793           How much RAM do I need to have on my UNIX system to be able to run
 794           Wine and MS Windows applications smoothly?
 795         </para>
 796       </question>
 797       <answer>
 798         <para>
 799           If you can run X smoothly on your UNIX system now, you should be
 800           able to run Wine and MS Windows applications just fine too, depending
 801           on how memory hungry the application is.
 802         </para>
 803         <para>
 804           A Wine workstation will work with 16 megabytes of RAM and a 16
 805           megabyte swap partition as long as you have a reasonable graphics
 806           card. Most applications will run reasonably with 64/64 Mb,
 807           interactive games are likely to need more. You can run Wine with 8/8,
 808           but it is going to be unusably slow and very constraining on the
 809           applications you can run. If you wish to be part of the development
 810           team and program Wine itself, be aware that the debugger is rather
 811           memory intensive. Some have suggested that 64 megabytes is the
 812           minimum RAM needed for Wine development, although some are able to
 813           work (albeit slowly) with 24 megabytes of physical RAM and lots of
 814           swap space.
 815         </para>
 816       </answer>
 817       </qandaentry>
 818
 819       <qandaentry>
 820       <question id="How-long-does-Wine-take-to-build">
 821         <para>How long does Wine take to build</para>
 822       </question>
 823       <answer>
 824         <para>
 825           Wine is getting to be quite large, and building from scratch takes a
 826           lot of processing. As of September 2002, compile times were around 20
 827           minutes on an Athlon 1200 with 640 Mb and 45-50 minutes on a Cyrix
 828           300 with 64 Mb. If you have a CVS copy, you may not need to rebuild
 829           the whole thing every time you update.
 830         </para>
 831       </answer>
 832       </qandaentry>
 833       <qandaentry>
 834       <question id="I-have-a-Drivespaced-partition">
 835         <para>
 836           I have a Drivespaced, Doublespaced or Stackered DOS partition. Can
 837           Wine run MS Windows binaries located in such a partition?
 838         </para>
 839       </question>
 840       <answer>
 841         <para>
 842           Yes, but only if the operating system supports mounting those types
 843           of drives. There is a Linux file system driver called dmsdos that
 844           will allow read/write access to Doublespaced and Drivespace 1.0
 845           drives. More specifically, it supports mounting DOS 6.0 and 6.2
 846           Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced
 847           compressed partitions (read and write access works fine, but write
 848           access is slow). It can be found at
 849           <ulink url="ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/">
 850           ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>
 851         </para>
 852       </answer>
 853       </qandaentry>
 854
 855       <qandaentry>
 856       <question id="Do-I-need-to-have-a-DOS-partition">
 857         <para>Do I need to have a DOS partition on my system to use Wine?</para>
 858       </question>
 859       <answer>
 860         <para>
 861           You do not need a licensed and installed copy of DOS or MS Windows to
 862           install, configure and run Wine. However, Wine has to be able to
 863           'see' an MS Windows binary (i.e. application) if it is to run it.
 864         </para>
 865       </answer>
 866       </qandaentry>
 867
 868       <qandaentry>
 869       <question id="Does-MS-Windows-need-to-be-installed">
 870         <para>
 871           Does MS Windows need to be loaded into that partition in order to
 872           run MS Windows programs under Wine?
 873         </para>
 874       </question>
 875       <answer>
 876         <para>
 877           Many folks have successfully installed and run programs
 878           in their UNIX file system without having a DOS partition or MS
 879           Windows. However, in many cases you need a directory and file
 880           infrastructure that is similar to an existing Windows installation.
 881           Some applications' installation programs want to distribute some of
 882           the package's files into the /windows and /windows/system
 883           directories in order to run, and unless these exist on your UNIX
 884           file system, those programs will not install correctly and probably
 885           will not run well, if at all. Most packages will set that up for you
 886           as part of the install process.
 887         </para>
 888         <para>
 889           If you have a DOS partition with MS Windows installed in it, make
 890           sure that your UNIX system can 'see' this partition (check your
 891           /etc/fstab file or mount the partition manually) so that Wine can
 892           run the MS Windows binaries located in the DOS partition. To run
 893           without a DOS partition, you need to set a UNIX path to be your
 894           drive C, and make sure that the /windows and /windows/system
 895           directories point to some place that actually exist.
 896         </para>
 897         <para>
 898           Here's an example, copied from a machine which has no DOS partition
 899           but successfully runs Wine:
 900         </para>
 901         <screen>
 902     [Drive C]
 903           Path=/var/lib/wine
 904           Type=hd
 905           Label=MS-DOS
 906           Filesystem=win95
 907     [wine]
 908           Windows=c:\windows
 909           System=c:\windows\system
 910           Temp=e:\
 911           Path=c:\windows;c:\windows\system;c:
 912         </screen>
 913         <para>
 914          In <filename>/var/lib/wine/windows</filename>, you will need to
 915          install a <filename>win.ini</filename> config file that you might
 916          find on a typical MS Windows 3.1 machine. The directory
 917          <filename>/var/lib/wine/windows/system</filename> should exist, but
 918          doesn't need to contain anything. However, to use MS DLLs, you can
 919          copy them into that directory. Note that this is a contravention of
 920          the Windows licence unless Windows is properly installed on the
 921          machine. If you have DOS/MS Windows installed on your system, you can
 922          mount that partition at bootup by modifying the file
 923          <filename>/etc/fstab</filename> in your UNIX partition (assuming that
 924          the UNIX kernel supports the DOS/MS Windows file system type).
 925         </para>
 926         <para>
 927           If you edit this file by hand, it should contain something similar
 928           to the following:
 929         </para>
 930         <screen>
 931 /dev/hda1 /dosc msdos uid=0,gid=100,umask=007 0 0
 932         </screen>
 933         <para>
 934           This will allow you to read and write to the DOS partition without
 935           being root.
 936         </para>
 937       </answer>
 938       </qandaentry>
 939
 940       <qandaentry>
 941       <question id="If-Wine-completely-replaces-MS-Windows">
 942         <para>
 943           If Wine completely replaces MS Windows, will it duplicate all of the
 944           functions of MS Windows?
 945         </para>
 946       </question>
 947       <answer>
 948         <para>
 949           Wine's goal is to make it possible to run Windows applications on
 950           Unix. To this end it will provide replacements for just those
 951           DLLs and APIs that are needed by these Windows applications.
 952           This means that Wine will not provide replacements for DLLs that
 953           are not shipped with Windows or are always shipped with Windows
 954           application (e.g. the Visual Basic run time). This also
 955           means that implementing an API that no application ever uses is not
 956           a priority. Similarly, until there are applications out there that
 957           use the Win64 API, it will not be a priority. That being said,
 958           we will certainly try to keep our options open and to improve our API
 959           coverage as we can.
 960         </para>
 961         <para>
 962           Also Wine is not an operating system, so that writing device
 963           drivers is not part of Wine's goals. However if you are interested
 964           in device drivers, the <ulink url="http://www.kernel.org/">Linux</ulink>,
 965           <ulink url="http://www.freebsd.org/">FreeBSD</ulink> and
 966           <ulink url="http://www.reactos.com/">ReactOS</ulink> kernel developers
 967           would certainly appreciate your contribution.
 968         </para>
 969         <para>
 970           Similarly Wine does not try to be a desktop environment so
 971           providing applets such as a calculator, a file manager or even
 972           window manager that look like Windows, are low priority or would
 973           even best be done as a separate project. Such projects would also
 974           to a large extant be redundant with other open-source projects.
 975           Again, there are projects that would certainly appreciate your
 976           contributions in this areas, such as the
 977           <ulink url="http://www.gnome.org/">Gnome</ulink> or
 978           <ulink url="http://www.kde.org/">KDE</ulink> desktop environments. You
 979           will get the added benefit that your contribution will then be
 980           usable by everyone, not just by Wine users.
 981         </para>
 982       </answer>
 983       </qandaentry>
 984
 985       <qandaentry>
 986       <question id="Will-I-install-on-any-UNIX-file-system">
 987         <para>
 988           Will I be able to install MS Windows applications in any flavor of a
 989           UNIX file system?
 990         </para>
 991       </question>
 992       <answer>
 993         <para>
 994           Wine is written to be file system independent, so MS Windows
 995           applications will install and run under virtually any file system
 996           supported by your brand of UNIX.
 997         </para>
 998       </answer>
 999       </qandaentry>
1000
1001       <qandaentry>
1002       <question id="Will-Wine-run-only-under-X">
1003         <para>Will Wine run only under X, or can it run in character mode?</para>
1004       </question>
1005       <answer>
1006         <para>
1007           Most of Wine's development effort is geared towards MS Windows' GUI,
1008           but some limited support for character mode has appeared, by setting
1009           <parameter>GraphicsDriver=ttydrv</parameter> in wine.conf's
1010           <parameter>[wine]</parameter> section.
1011         </para>
1012         <para>
1013           Wine's infrastructure is already somewhat prepared for supporting
1014           other graphics drivers than x11drv, but no real "alternative"
1015           graphics driver has been developed yet.
1016         </para>
1017       </answer>
1018       </qandaentry>
1019
1020       <qandaentry>
1021       <question id="Will-Wine-run-under-any-X-window-manager">
1022         <para>Will Wine run under any X window manager? Does it require a window manager at all?</para>
1023       </question>
1024       <answer>
1025         <para>
1026           Wine is window manager independent, so the X window manager you
1027           choose to run has (almost) no bearing on your ability to run MS
1028           Windows programs under Wine. Wine uses standard X libraries, so no
1029           additional ones are needed. Wine has its own window management,
1030           which acts like MS Windows. It can be turned off to use the native
1031           window manager by modifying Managed or Desktop settings as described
1032           in <command>man wine.conf</command>.
1033         </para>
1034       </answer>
1035       </qandaentry>
1036
1037       <qandaentry>
1038       <question id="Will-32-bit-applications-run-under-Wine">
1039         <para>Will 32-bit Windows 95/98 applications run under Wine?</para>
1040       </question>
1041       <answer>
1042         <para>
1043           Yes, 32-bit programs are now about as well supported as 16-bit
1044            programs.
1045         </para>
1046       </answer>
1047       </qandaentry>
1048
1049     </qandadiv>
1050     <qandadiv id="FAQ-Getting-Wine">
1051       <title>Getting Wine</title>
1052       <qandaentry>
1053       <question id="Where-can-I-get-Wine">
1054         <para>Where can I get Wine?</para>
1055       </question>
1056       <answer>
1057         <para>
1058           Because of lags created by using mirror, word of this newest release
1059           may reach you before the release is actually available at the ftp
1060           sites listed here. The sources are available from the following
1061           locations:
1062         </para>
1063         <itemizedlist>
1064           <listitem>
1065             <para>
1066               <ulink url="http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/">
1067                http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/
1068               </ulink>
1069             </para>
1070           </listitem>
1071           <listitem>
1072             <para>
1073               <ulink url="ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/">
1074               ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/
1075               </ulink>
1076             </para>
1077           </listitem>
1078
1079           <listitem>
1080             <para>
1081               <ulink url="ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/">
1082               ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/
1083               </ulink>
1084             </para>
1085           </listitem>
1086
1087           <listitem>
1088             <para>
1089               <ulink url="ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/">
1090               ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/
1091               </ulink>
1092             </para>
1093           </listitem>
1094
1095         </itemizedlist>
1096         <para>
1097           It should also be available from any other site that mirrors
1098           ibiblio.org, see <ulink url="http://www.ibiblio.org/pub/Linux/MIRRORS.html">http://www.ibiblio.org/pub/Linux/MIRRORS.html</>. Some of
1099           these sites may archive previous versions of Wine as well as the
1100           current one. To determine which is the latest one, look at the
1101           distribution file name, which will take the form
1102           Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution
1103           file name with the numbers for year, month and date, respectively.
1104           The latest one is the one to get.
1105         </para>
1106         <para>
1107           Wine binary packages are available for several OS'es and
1108           distributions. See
1109           <ulink url="http://www.winehq.org/site/download">
1110           the download page</ulink> for the most recent list.
1111         </para>
1112       </answer>
1113       </qandaentry>
1114
1115       <qandaentry>
1116       <question id="Is-there-a-CVS-tree">
1117         <para>Is there a CVS tree?</para>
1118       </question>
1119       <answer>
1120         <para>
1121           Current Wine sources are also available via anonymous client/server
1122           CVS. You will need CVS 1.9 or above. If you are coming from behind a
1123           firewall, you will either need a hole in the firewall for the CVS
1124           port (2401) or use SOCKS.
1125         </para>
1126         <para>
1127           To login to the CVS tree, do
1128         </para>
1129         <screen>
1130 export CVSROOT=:pserver:cvs@cvs.winehq.org/home/wine
1131 cvs login
1132         </screen>
1133         <para>
1134           Use "cvs" as the password (without the quotes). Note that
1135           <filename>/home/wine</filename> is a path on the server, not on your
1136           machine. To check out the entire Wine source tree (which may be
1137           slow), use
1138         </para>
1139         <screen>
1140 cvs -z 3 checkout wine
1141         </screen>
1142         <para>
1143           or if you just want a subtree, or individual file, you can do that
1144           too with
1145         </para>
1146         <screen>
1147 cvs -z 3 checkout wine/ANNOUNCE
1148         </screen>
1149         <para>
1150           Be aware, though, that getting the entire Wine source tree via CVS
1151           is pretty slow, especially compared to getting Wine from an FTP
1152           mirror near you. For a CVS mirror list, see
1153           <ulink url="http://www.winehq.org/site/cvs#cvsservers">
1154           http://www.winehq.org/site/cvs#cvsservers</ulink>
1155         </para>
1156         <para>
1157           Patch files are also available, so that you don't have to download,
1158           install, and configure the entire distribution each week if you are
1159           current to the previous release. Patch file release names follow the
1160           same numbering convention as do the general releases, and take the
1161           form
1162         </para>
1163         <para>
1164           Wine-YYYYMMDD.diff.gz
1165         </para>
1166         <para>
1167           Patch files are available from the same sites that distribute the
1168           full release. To upgrade to a new release by using a patch file,
1169           first cd to the top-level directory of the release (the one
1170           containing the README file), then do a "make clean", and patch the
1171           release with
1172         </para>
1173         <screen>
1174 gunzip -c patch-file | patch -p1
1175         </screen>
1176         <para>
1177           where patch-file is the name of the patch file something like
1178           Wine-YYYYMMDD.diff.gz. You can then re-run ./configure, and then run
1179           make depend && make
1180         </para>
1181         <para>
1182           If you are mirroring the Wine distribution from the tsx-11 site and
1183           wish to be listed here in this FAQ, please add it to the
1184           "things to go into the documentation" area.
1185         </para>
1186       </answer>
1187       </qandaentry>
1188
1189       <qandaentry>
1190       <question id="Can-I-get-Wine-using-cvsup">
1191         <para>Can I get Wine using cvsup?</para>
1192       </question>
1193       <answer>
1194         <para>
1195           The CVS mirrors don't offer cvsup support yet, but the main server
1196           does. Use a <filename>wine.sup</filename> file of:
1197         </para>
1198         <screen>
1199 *default host=cvs.winehq.org
1200 *default base=/cvs
1201 *default prefix=/cvs/wine
1202 *default release=wine
1203 *default delete
1204
1205 # If your network link is a T1 or faster, comment out the following line.
1206 #*default compress
1207
1208 *default use-rel-suffix
1209 wine
1210         </screen>
1211      </answer>
1212      </qandaentry>
1213     </qandadiv>
1214
1215     <qandadiv id="Installing-And-Configuring-Wine">
1216       <title>Installing and Configuring Wine</title>
1217       <qandaentry>
1218       <question id="How-do-I-compile-the-Wine-source-code">
1219         <para>How do I compile the Wine distribution source code?</para>
1220       </question>
1221       <answer>
1222         <para>
1223           See the README (<ulink url="http://source.winehq.org/source/README">http://source.winehq.org/source/README</ulink>) for instructions.
1224           Additionally, you may want to set the <parameter>TMPDIR</parameter>
1225           environment variable <command>TMPDIR=~/tmp</command> or
1226           <command>TMPDIR=/tmp</command> (if you are root).
1227         </para>
1228       </answer>
1229       </qandaentry>
1230
1231       <qandaentry>
1232       <question id="How-do-I-install-Windows-in-Wine">
1233         <para>How do I install Windows in Wine under Linux?</para>
1234       </question>
1235       <answer>
1236         <para>
1237           Simple answer: you CAN'T. Windows demands direct access to the
1238           hardware and cannot get it with Wine and UNIX in the way
1239         </para>
1240         <para>
1241           Wine is supposed to be primarily used WITHOUT Windows. If you want
1242           to use a Windows installation, then use an existing installation
1243           alongside the UNIX installation (see the dual-boot HOWTO for your OS
1244           for more details). Or alternatively use the cabextract utility to
1245           extract Windows install archives to a directory that you want to use
1246           as Wine's Windows tree.
1247         </para>
1248       </answer>
1249       </qandaentry>
1250
1251       <qandaentry>
1252       <question id="How-do-I-configure-Wine-to-run-on-my-system">
1253         <para>How do I configure Wine to run on my system?</para>
1254       </question>
1255       <answer>
1256         <para>
1257           Wine requires that you have a config file as
1258           <filename>~/.wine/config</filename>. The format of this file is
1259           explained in the <filename>wine.conf</filename> man page. The file
1260           <filename>documentation/samples/config</filename>
1261           (<ulink url="http://source.winehq.org/source/documentation/samples/config">
1262           http://source.winehq.org/source/documentation/samples/config</ulink>)
1263           contains a config file example. More explicit directions can be
1264           found in the <filename>README</filename> file
1265           (<ulink url="http://source.winehq.org/source/README">
1266           http://source.winehq.org/source/README</ulink>) that will be located in
1267           the base Wine directory after you gunzip and untar the distribution
1268           file.
1269         </para>
1270       </answer>
1271       </qandaentry>
1272
1273       <qandaentry>
1274       <question id="How-do-I-upgrade-configuration">
1275         <para>How do I upgrade Wine without losing my working configuration?</para>
1276       </question>
1277       <answer>
1278         <para>
1279           Upgrading the wine installation does not affect the existing wine
1280           configuration. So after upgrading wine you still have the old (working )
1281           wine configuration.
1282         </para>
1283       </answer>
1284       </qandaentry>
1285
1286       <qandaentry>
1287       <question id="If-I-use-Windows-which-versions-OK">
1288         <para>If I want to use a Windows install, which versions are OK?</para>
1289       </question>
1290       <answer>
1291         <para>
1292           Either use a classic no-windows install (Wine is getting better all
1293           the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T
1294           configure Wine to use an NT-based Windows install (NT, Win2K, WinXP, Win2K3).
1295         </para>
1296         <para>
1297           In general, most Windows installations contain vast quantities of garbage
1298           that can confuse Wine and make it less reliable. If you can, it's best to
1299           install the programs you want into Wines fake windows drive.
1300         </para>
1301       </answer>
1302       </qandaentry>
1303
1304       <qandaentry>
1305       <question id="If-I-use-Windows-which-one-works-best">
1306         <para>If I use a Windows install with Wine, which one works best?</para>
1307       </question>
1308       <answer>
1309         <para>
1310           As of 02/2002:
1311         </para>
1312         <para>
1313           I'd say Win98SE is the best version to use with Wine, as it's fairly
1314           widespread amongst developers and relatively old. Using Win2K files
1315           is <emphasis>definitely</emphasis> worse than a plain no-windows
1316           Wine install, and Win ME is said to be problematic, too (as probably
1317           no developer uses it). In short: all Win9x &lt;= W98SE are good.
1318         </para>
1319       </answer>
1320       </qandaentry>
1321
1322       <qandaentry>
1323       <question id="Installing-Visual-Basic-apps-wont-run">
1324         <para>
1325           Installing applications generated by Visual Basic won't run. What
1326           should I do?
1327         </para>
1328       </question>
1329       <answer>
1330         <para>
1331           Make sure you have all the VB run time libraries installed. You may
1332           need to use the native DLL vbrun60.dll. You can get some from dll-files.com.
1333         </para>
1334       </answer>
1335       </qandaentry>
1336
1337       <qandaentry>
1338       <question id="When-I-click-on-exe-file-nothing-happens">
1339         <para>When I click on *.exe file in my file Manager, nothing happens.</para>
1340       </question>
1341       <answer>
1342         <para>
1343           The normal Wine releases don't have .exe extensions registered for
1344           Wine in KDE/Gnome yet. You have to open a terminal window instead
1345           (often an icon showing a "black screen") and type something like:
1346         </para>
1347         <screen>
1348 cd /my/windows/program/directory
1349 wine myprogram.exe
1350         </screen>
1351         <para>
1352           Or alternatively you could download the CodeWeavers Wine preview
1353           which includes .exe extension registration for KDE/Gnome and a nice
1354           setup program.
1355         </para>
1356       </answer>
1357       </qandaentry>
1358
1359       <qandaentry>
1360       <question id="bash-wine-Command-not-found-What-can-I-do">
1361         <para>bash says "wine: Command not found" What can I do?</para>
1362       </question>
1363       <answer>
1364         <para>
1365           Try to re login into bash. That might fix it.
1366         </para>
1367         <para>
1368           If it doesn't, then make sure the wine binary is in your
1369           <parameter>PATH</parameter>.
1370         </para>
1371         <para>
1372           Run as root:
1373         </Para>
1374         <screen>
1375 find / -name "wine" -type f -perm +111
1376         </screen>
1377         <para>
1378           to find the path where the wine binary is in. Then check whether
1379         <parameter>PATH</parameter> includes it:
1380         </para>
1381         <screen>
1382 echo $PATH
1383         </screen>
1384         <para>
1385           If not, add that e.g. to <filename>/etc/profile</filename> by doing:
1386         </para>
1387         <screen>
1388 export PATH=$PATH:/path/to/wine/binary
1389         </screen>
1390         <para>
1391           That should help.
1392         </para>
1393         <para>
1394            If you used a package manager (<command>rpm</command> or
1395            <command>apt</command>) - Verify your packages. The package
1396            <filename>winesetuptk.rpm</filename> is only a front-end for
1397            making a meaningful config file, it DOES NOT install the wine
1398            package...
1399         </para>
1400         <para>
1401            For complete packages, use <ulink url="http://rpmseek.com/rpm-pl/wine.html?hl=com&amp;cx=0::">
1402            http://rpmseek.com/</ulink> or the <ulink url="http://www.winehq.org/site/download">
1403            Download</ulink> section.
1404         </para>
1405       </answer>
1406       </qandaentry>
1407
1408       <qandaentry>
1409       <question id="How-do-I-remove-Wine-from-my-Computer">
1410         <para>How do I remove Wine from my Computer?</para>
1411       </question>
1412       <answer>
1413         <para>
1414           It depends on how you installed. If you used an RPM, the right command is this:
1415          <command>rpm -e wine (as root)</command>
1416         </para>
1417        <para>
1418          If you installed from source (the .tar.gz file), the right
1419          way to do it is to change to the root of the source tree (the directory with the configure script,
1420          readme etc) then run as root:
1421          <command>make uninstall</command>
1422        </para>
1423       </answer>
1424       </qandaentry>
1425     </qandadiv>
1426
1427     <qandadiv id="About-running-Wine">
1428       <title>About running Wine</title>
1429       <qandaentry>
1430       <question id="How-do-I-run-an-MS-Windows-program">
1431         <para>How do I run an MS Windows program under Wine?</para>
1432       </question>
1433       <answer>
1434         <para>
1435           When invoking Wine, you must specify the entire path to the
1436           executable, or by file name only. For example to run Windows'
1437           solitaire, type any of the following:
1438         </para>
1439         <itemizedlist>
1440           <listitem>
1441           <para>
1442             <command>wine sol</command> or <command>wine sol.exe</command>
1443            (using the search path to locate the file).
1444           </para>
1445           </listitem>
1446           <listitem>
1447           <para>
1448             <command>wine c:\\windows\\sol.exe</command>
1449            (using a DOS file name).
1450           </para>
1451           </listitem>
1452           <listitem>
1453           <para>
1454             <command>wine /usr/windows/sol.exe</command>
1455            (using a UNIX file name).
1456           </para>
1457           </listitem>
1458           <listitem>
1459           <para>
1460             <command>wine "c:\windows\sol.exe"</command>
1461             (using quoted DOS file name).
1462           </para>
1463           </listitem>
1464         </itemizedlist>
1465         <para>
1466           The path of the file will also be added to the path when a full name
1467           is supplied on the command line.
1468
1469         </para>
1470       </answer>
1471       </qandaentry>
1472
1473       <qandaentry>
1474       <question id="Wine-cannot-find-MS-Windows-on-my-drive">
1475         <para>
1476           I have installed and configured Wine, but Wine cannot find MS
1477           Windows on my drive. Where did I go wrong?
1478         </para>
1479       </question>
1480       <answer>
1481         <para>
1482           If you have a DOS partition, first make sure that you have mounted
1483           it, either by putting the entry into <filename>/etc/fstab</filename>,
1484           or by manually mounting it.
1485         </para>
1486         <para>
1487           Remember too that unless your version of UNIX can see through it, or
1488           you are running a utility that can see through it, your DOS
1489           partition must not be located on a Drivespaced, Doublespaced or
1490           Stackered partition, as neither Linux, FreeBSD, NetBSD or Wine can
1491           natively 'see' files located in these compressed DOS partitions.
1492         </para>
1493         <para>
1494           Check your path statements in the <filename>wine.conf</filename>
1495           file. No capital letters may be used in paths, as they are
1496           automatically converted to lowercase.
1497         </para>
1498       </answer>
1499       </qandaentry>
1500
1501       <qandaentry>
1502       <question id="Parts-of-my-app-do-not-work-What-is-wrong">
1503         <para>
1504           I was able to get various MS Windows programs to run, but parts of
1505           them do not work. What is wrong?
1506         </para>
1507       </question>
1508       <answer>
1509         <para>
1510           Wine is not complete at this time, so some of each programs'
1511           features may not work. They will in time as more of the MS
1512           Windows API calls are included in Wine.
1513         </para>
1514       </answer>
1515       </qandaentry>
1516
1517       <qandaentry>
1518       <question id="Menus-do-not-work-how-can-I-exit">
1519         <para>
1520           I have run various MS Windows programs, but since the program menus
1521           do not work, how can I exit these programs?
1522         </para>
1523       </question>
1524       <answer>
1525         <para>
1526           Kill the xterm shell window that you called up to run your MS
1527           Windows program, and the X window that appeared with the program
1528           will be killed too.
1529         </para>
1530       </answer>
1531       </qandaentry>
1532
1533       <qandaentry>
1534         <question id="My-app-doesnt-work-what-can-i-do">
1535           <para>
1536             My program doesn't work, what can I do?
1537           </para>
1538         </question>
1539         <answer>
1540           <para>
1541             If you are a programmer and know C, then start debugging
1542             Wine and help us make it better! If you can't, then you will
1543             have to either convince a Wine developer to try and make your
1544             program work (there must be a downloadable version or demo for
1545             that), or hire somebody to do it for you. If this application
1546             is an internal corporate application, you may be able to hire a
1547             Wine developer to do consulting work for you on the matter.
1548           </para>
1549           <para>
1550             Alternatively, you may be able to get the app working by
1551             taking native DLLs from a Microsoft Windows install, and using
1552             them (set the dlls to native in the config file). Not all DLLs
1553             can be replaced that way - in particular DirectX cannot be, nor
1554             can some core system DLLs like user, ntdll, kernel32 etc
1555           </para>
1556         </answer>
1557       </qandaentry>
1558
1559       <qandaentry>
1560       <question id="Can-I-use-Wine-with-other-Linux-Distros">
1561         <para>Can I use Wine with SuSE, Peanut or other Linux Distro's?</para>
1562       </question>
1563       <answer>
1564         <para>
1565           You can use Wine on any sufficiently recent Linux installation. The
1566           amount of work getting Wine up and running depends on whether there
1567           are proper packages available or a source compile has to be done.
1568         </para>
1569       </answer>
1570       </qandaentry>
1571
1572       <qandaentry>
1573       <question id="Does-Wine-work-with-AMD-Processors">
1574         <para>Does Wine work with AMD Processors?</para>
1575       </question>
1576       <answer>
1577         <para>
1578           Yes, it does. Wine should work on any processor compatible with
1579           the Pentium or greater.
1580         </para>
1581       </answer>
1582       </qandaentry>
1583
1584        <qandaentry>
1585       <question id="Can-I-launch-Unix-app-from-Windows-app">
1586         <para> Can I launch a Unix program from a Windows program?</para>
1587       </question>
1588       <answer>
1589         <para>
1590           Sure, Wine supports that. Just enter the unix program name wherever
1591           a program has something that it's supposed to execute, and it
1592           should just work.
1593         </para>
1594       </answer>
1595       </qandaentry>
1596       <qandaentry>
1597       <question id="Error-with-installshield-6">
1598         <para>
1599           I get <quote>Error installing iKernel.exe: (0x1400)</quote>
1600           when running an InstallShield 6 installer.
1601         </para>
1602       </question>
1603       <answer>
1604         <para>
1605           If you get the error "Error installing iKernel.exe: (0x1400)" at any
1606           point, it's probably because there are leftover processes from a
1607           previous try. You can verify this with the command
1608         </para>
1609         <para><prompt>$ </><command>ps augxw | grep wine</command></para>
1610         <para>
1611           If that command shows old copies of wine running your setup,
1612           you need to kill them before you can run the setup program.
1613           If there are no other Wine programs running, you can kill them
1614           all with the command
1615         </para>
1616         <para><prompt>$ </><command>killall wine</command></para>
1617         <para>
1618           If you're also running Wine programs you care about, you'll
1619           have to kill off the old Setup instances one by one using
1620           kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
1621           which doesn't exist yet).
1622         </para>
1623         <para>
1624           You should repeat the <command>ps</command> to make sure the old
1625           Wine processes are gone.
1626         </para>
1627        </answer>
1628       </qandaentry>
1629     </qandadiv>
1630
1631     <qandadiv id="Getting-help">
1632       <title>Getting help</title>
1633       <qandaentry>
1634       <question id="Is-there-any-documentation-for-Wine">
1635         <para>Is there any documentation for Wine?</para>
1636       </question>
1637       <answer>
1638         <para>
1639           Yes, see <ulink url="http://www.winehq.org/site/documentation">
1640           http://www.winehq.org/site/documentation.</ulink>
1641         </para>
1642       </answer>
1643       </qandaentry>
1644
1645       <qandaentry>
1646       <question id="I-have-written-some-documententation">
1647         <para>
1648           I couldn't find the answer to my question in the documentation, but
1649           I've written a document explaining how to solve it. What should I do?
1650         </para>
1651       </question>
1652       <answer>
1653         <para>
1654           Updates and additions to the Wine documentation directory should be
1655           sent to the wine-patches mailing list at
1656           <ulink url="http://www.winehq.org/site/forums">
1657           http://www.winehq.org/site/forums</ulink>. Website and FAQ
1658           additions should be added to the appropriate Wine Knowledge base directory.
1659         </para>
1660       </answer>
1661       </qandaentry>
1662
1663       <qandaentry>
1664       <question id="Is-there-a-Usenet-newsgroup-for-Wine">
1665         <para>Is there a Usenet newsgroup for Wine?</para>
1666       </question>
1667       <answer>
1668         <para>
1669           Yes, and it's called
1670           <ulink url="news:comp.emulators.ms-windows.wine">
1671           comp.emulators.ms-windows.wine</ulink>. The newsgroup serves as a
1672           place for users and developers to discuss Wine, and for minor
1673           announcements for the general public. Major announcements will be
1674           cross posted to other appropriate newsgroups, such as the following:
1675         </para>
1676         <itemizedlist>
1677           <listitem>
1678           <para>
1679             <ulink url="news:comp.os.linux.announce">
1680             comp.os.linux.announce</ulink>
1681           </para>
1682           </listitem>
1683           <listitem>
1684           <para>
1685             <ulink url="news:ccomp.windows.x.announce">
1686             comp.windows.x.announce</ulink>
1687           </para>
1688           </listitem>
1689           <listitem>
1690           <para>
1691             <ulink url="news:ccomp.emulators.announce">
1692             comp.emulators.announce</ulink>
1693           </para>
1694           </listitem>
1695         </itemizedlist>
1696         <para>
1697           If your Usenet site does not carry these newsgroups, please urge
1698           your ISP's sysadmin to add and/or uplink them.
1699         </para>
1700       </answer>
1701       </qandaentry>
1702
1703       <qandaentry>
1704       <question id="Is-there-a-World-Wide-Web-site-for-Wine">
1705         <para>Is there a World Wide Web site for Wine?</para>
1706       </question>
1707       <answer>
1708         <para>
1709           Wine HQ (<ulink url="http://www.winehq.org">http://www.winehq.org</ulink>) is the official site.
1710         </para>
1711       </answer>
1712       </qandaentry>
1713
1714       <qandaentry>
1715       <question id="Is-there-an-IRC-channel-for-Wine">
1716         <para>Is there an IRC channel for Wine?</para>
1717       </question>
1718       <answer>
1719         <para>
1720           Sure. It's channel <filename>#WineHQ</filename> on
1721           <filename>irc.freenode.net</filename> see
1722           (<ulink url="http://freenode.net">http://freenode.net</ulink>).
1723           Usually several Wine developers hang out there just to help YOU ;-)
1724         </para>
1725       </answer>
1726       </qandaentry>
1727
1728       <qandaentry>
1729       <question id="I-think-I-found-a-bug-How-do-I-report-it">
1730         <para>
1731           I think I've found a bug. How do I report this bug to the Wine
1732           programming team?
1733         </para>
1734       </question>
1735       <answer>
1736         <para>
1737           Bug reports should be submitted to our online Bugzilla system
1738           (<ulink url="http://bugs.winehq.org/">http://bugs.winehq.org/</ulink>).
1739           You should include at least the following:
1740         </para>
1741         <itemizedlist>
1742           <listitem>
1743           <para>
1744             The Wine version tested
1745           </para>
1746           </listitem>
1747           <listitem>
1748           <para>
1749             The Windows application name, including the version, and, if
1750             applicable, a URL the application can be downloaded from
1751           </para>
1752           </listitem>
1753           <listitem>
1754           <para>
1755             A brief description of the bug
1756           </para>
1757           </listitem>
1758           <listitem>
1759           <para>
1760             The relevant part(s) of the output of the Wine debugger
1761           </para>
1762           </listitem>
1763           <listitem>
1764           <para>
1765             A screenshot of the visual problem, if applicable
1766           </para>
1767           </listitem>
1768         </itemizedlist>
1769         <para>
1770          For more information about reporting bugs please see the
1771          <ulink url="http://www.winehq.org/Docs/wine-user/bug-reporting.shtml">
1772          How to report a bug</ulink> section of the Wine Users Guide.
1773         </para>
1774       </answer>
1775       </qandaentry>
1776     </qandadiv>
1777
1778     <qandadiv id="Helping-Wine-or-becoming-a-Wine-developer">
1779       <title>Helping Wine or becoming a Wine developer</title>
1780       <qandaentry>
1781       <question id="How-do-I-become-a-Wine-developer">
1782         <para>How do I become a Wine developer? What do I need to know?</para>
1783       </question>
1784       <answer>
1785         <para>
1786           If you can program C, that's a good start. Download the sources via
1787           (<ulink url="http://www.winehq.org/site/cvs">CVS,</ulink>)
1788           subscribe to the mailing lists, look around the source, and
1789           pay attention to the comp.emulators.ms-windows.wine newsgroup
1790           and the mailing lists (<ulink
1791           url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>).
1792           See if there's anything that you think you can fix or work
1793           on. You won't have much trouble finding areas that need work
1794           in Wine (grep for FIXMEs in the source).
1795         </para>
1796       </answer>
1797       </qandaentry>
1798
1799       <qandaentry>
1800       <question id="How-can-I-contribute-to-the-Wine-project">
1801         <para>How can I help contribute to the Wine project, and in what way(s)?</para>
1802       </question>
1803       <answer>
1804         <para>
1805           You can contribute programming or documentation skills, or monetary
1806           or equipment donations, to aid the Wine developers in reaching their
1807           goals.
1808         </para>
1809         <para>
1810           For a list of ideas of how you can help, please consult the
1811           <ulink url="http://www.winehq.org/site/contributing">
1812           Wine contrib page</ulink>.
1813         </para>
1814       </answer>
1815       </qandaentry>
1816
1817       <qandaentry>
1818       <question id="I-want-to-help-beta-test-Wine">
1819         <para>I want to help beta test Wine. How can I do this?</para>
1820       </question>
1821       <answer>
1822         <para>
1823           Wine still consists of some Alpha code at this time. However, anyone
1824           is welcome to download the latest version, and try it out at any
1825           time.
1826         </para>
1827       </answer>
1828       </qandaentry>
1829
1830       <qandaentry>
1831       <question id="I-wrote-some-code-I-would-like-to-submit">
1832         <para>
1833           I have written some code that I would like to submit to the Wine
1834           project. How do I go about doing this?
1835         </para>
1836       </question>
1837       <answer>
1838         <para>
1839           Submitting a patch for inclusion in Wine is pretty simple.
1840           Basically all you have to do is send the patch to the
1841           wine-patches mailing list
1842           (<ulink url="http://www.winehq.org/mailman/listinfo/wine-patches">http://www.winehq.org/mailman/listinfo/wine-patches</>).
1843           Still there are a couple of recommendations about the patch format
1844           and all so it's best to read our page describing <ulink
1845           url="http://www.winehq.org/site/sending_patches">how to submit
1846           patches</>. This will also give you more details about the whole
1847           process and in particular to what will happen to your patch once
1848           submitted.
1849         </para>
1850       </answer>
1851       </qandaentry>
1852     </qandadiv>
1853
1854     <qandadiv id="Developing-programs-using-Wine-WineLib">
1855       <title>Developing programs using Wine/WineLib</title>
1856       <qandaentry>
1857       <question id="Can-I-use-Wine-to-port-Win32-sources-to-Unix">
1858         <para>Can I use Wine to port my Win32 sources to Unix?</para>
1859       </question>
1860       <answer>
1861         <para>
1862           That is the idea of Winelib. Right now you may still have some
1863           difficulties, but this is changing all the time. Read the
1864           <ulink url="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</ulink> for info.
1865
1866         </para>
1867       </answer>
1868       </qandaentry>
1869       <qandaentry>
1870       <question id="Will-MFC-work-with-Wine-What-do-I-need-to-do">
1871         <para>Will MFC work with Wine? What do I need to do?</para>
1872       </question>
1873       <answer>
1874         <para>
1875           Wine is not implementing an MFC replacement nor does it intend to.
1876           However it is possible (with a lot of work) to compile the MFC from
1877           source and thus produce an <filename>mfc42.dll.so</filename> library.
1878         </para>
1879         <para>
1880           Please refer to the
1881           <ulink url="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</ulink> for how to do this.
1882         </para>
1883       </answer>
1884       </qandaentry>
1885
1886       <qandaentry>
1887       <question id="Are-there-commercial-apps-ported-using-Wine">
1888         <para>
1889           Are there any commercial applications which have been ported
1890           using Wine?
1891         </para>
1892       </question>
1893       <answer>
1894         <para>
1895           Here are few examples of applications ported using Wine or Winelib:
1896         </para>
1897         <itemizedlist>
1898           <listitem>
1899           <para>
1900             Corel's WordPerfect Office Suite 2000 was ported to Linux using
1901             Wine.
1902           </para>
1903           </listitem>
1904           <listitem>
1905           <para>
1906             Kylix, the Linux version of Delphi, was ported to Linux using
1907             Winelib. The IDE actually uses a combination of QT and Winelib
1908             which would not have been possible to achieve using only Wine.
1909             The generated applications however do not depend on Wine in
1910             any way.
1911           </para>
1912           </listitem>
1913           <listitem>
1914           <para>
1915             MusicMatch Jukebox 5 has also been
1916             <ulink url="http://www.itworld.com/nl/lnx_desktop/01042001/">ported</>
1917             to Linux using Winelib. However more recent versions have not, and
1918             version 5 is no longer available.
1919           </para>
1920           </listitem>
1921           <listitem>
1922           <para>
1923             Ability Office
1924             (<ulink url="http://www.ability.com/linux/abilitylinux.php">http://www.ability.com/linux/abilitylinux.php</ulink>)
1925           </para>
1926           </listitem>
1927           <listitem>
1928           <para>
1929             IBM's Websphere
1930             (<ulink url="http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)
1931           </para>
1932           </listitem>
1933         </itemizedlist>
1934         <para>
1935           Many other important applications have already been ported. (we are
1936           speaking of several top 500 applications here)
1937         </para>
1938       </answer>
1939       </qandaentry>
1940
1941       <qandaentry>
1942       <question id="How-can-I-detect-Wine">
1943         <para>How can I detect Wine?</para>
1944       </question>
1945       <answer>
1946         <para>
1947           You really shouldn't want to do this. If there's a quirk in Wine
1948           you need to work around, it's much better to fix it in Wine.
1949         </para>
1950       </answer>
1951       </qandaentry>
1952
1953
1954     </qandadiv>
1955
1956     <qandadiv id="Wine-HQ-issues">
1957       <title>Wine HQ issues</title>
1958       <qandaentry>
1959       <question id="Why-are-the-maillists-set-to-reply-to-author">
1960         <para>
1961           Why are the mailing lists set to reply to author, not to mailing list?
1962         </para>
1963       </question>
1964       <answer>
1965         <para>
1966           There are very valid reasons for doing so.
1967         </para>
1968       </answer>
1969       </qandaentry>
1970
1971       <qandaentry>
1972       <question id="How-to-unsubscribe-from-the-mailing-lists">
1973         <para>How to unsubscribe from the mailing lists?</para>
1974       </question>
1975       <answer>
1976         <para>
1977           Please see: <ulink url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>
1978           And select [(Un-)Subscribe]
1979         </para>
1980       </answer>
1981       </qandaentry>
1982
1983     </qandadiv>
1984
1985   </qandaset>
1986
1987 <!-- Keep this comment at the end of the file
1988 Local variables:
1989 mode: sgml
1990 sgml-parent-document:("wine-devel.sgml" "book" "part" "chapter" "")
1991 End:
1992 -->