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