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