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