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