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