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