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 (ridgway@winehq.com) took it over in 1999.</para>
  13         <para>Andreas Mohr (amohr@codeweavers.com) converted it to FAQ-O-Matic in 2000.</para>
  14         <para>Dimitrie O. Paun, Keith Matthews and Thomas Wickline reorganised 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 on the 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.
  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 LGPL.
  47         </para>
  48       </answer>
  49       </qandaentry>
  50
  51      <qandaentry>
  52       <question id="Is-Wine-an-emulator">
  53         <para>Is Wine an emulator?</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. The
  60           advantage is that, unlike solutions that rely on emulation, Wine
  61           runs applications run at full speed.
  62        </para>
  63       </answer>
  64       </qandaentry
  65
  66       <qandaentry>
  67       <question id="Are-here-any-alternatives-to-Wine">
  68         <para>Are there any alternatives to Wine?</para>
  69       </question>
  70       <answer>
  71         <para>
  72           Yes, there are. You can use <ulink url="http://www.vmware.com">VMWare</ulink> to run a Windows installation inside a virtual machine,
  73           or use <ulink url="http://www.win4lin.com">Win4Lin</ulink>
  74           to run a specially adapted Windows version on Linux.
  75           Both solutions cost money for both the software itself
  76           and a Windows license.
  77        </para>
  78        <para>
  79          Note that, like Wine, they can only use the hardware platform that
  80          the target programs were originally compiled for (see below).
  81        </para>
  82       </answer>
  83       </qandaentry>
  84
  85       <qandaentry>
  86       <question id="Difference-between-Wine-and-emulators">
  87         <para>What is the difference between Wine and x86 hardware emulators?</para>
  88       </question>
  89       <answer>
  90         <para>
  91           There are two free x86 hardware emulators:
  92           <ulink url="http://bochs.sourceforge.net">bochs</ulink>, and
  93           <ulink url="http://savannah.nongnu.org/projects/plex86">plex86</ulink>.
  94        </para>
  95
  96        <para>
  97           Plex86 is the opensource free-software alternative for VMWare,
  98           VirtualPC, and other IA-32 on IA-32 "Virtual PC products." It
  99           can only run on the IA-32 architecture.
 100        </para>
 101
 102        <para>
 103           Bochs is a highly portable open source IA-32 (x86) PC emulator
 104           written in C++, that runs on most popular platforms. It includes emulation
 105           of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently,
 106           bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
 107           of running most Operating Systems inside the emulation including Linux,
 108           Windows® 95, DOS, and recently Windows® NT 4.
 109        </para>
 110
 111        <para>
 112           Both are licensed under the GPL. Bochs is older than plex86, seems to be
 113           easier to install, but plex86 will run faster because plex86 uses a just in
 114           time binary compiler.
 115        </para>
 116        <para>
 117           The drawback of all emulators is that you need a version
 118           of Windows in order to run Windows, and that they all have an
 119           impact on performance.
 120        </para>
 121
 122       </answer>
 123       </qandaentry>
 124
 125       <qandaentry>
 126       <question id="Why-would-anyone-want-Wine-Windows-suck">
 127         <para>Why would anyone want Wine? Doesn't Windows suck?</para>
 128       </question>
 129       <answer>
 130         <para>
 131           First Wine is not about running Windows but about running Windows
 132           applications.
 133         </para>
 134         <para>
 135           So if all your computing needs are fulfilled by native Unix
 136           applications, then you do not need Wine and should not be using
 137           it. However, if you depend on one or more of the tens of
 138           thousands of Windows applications, then Wine is the best way to
 139           use it without giving up on Unix. Let's look at the alternatives
 140           to see why:
 141         </para>
 142         <para>
 143           The most obvious alternative is to dual-boot. This is the solution
 144           that provides the best compatibility. However it requires that you
 145           acquire a Windows license and then dedicate a good chunk of your
 146           hard-drive to Windows. But the worst is yet to come. Each time you
 147           will want to use that application you will have to reboot to
 148           Windows. This is especially significant if external factors dictate
 149           when you must use this application (e.g. credit card to process,
 150           email to retrieve from a Lotus Notes server). Then you will find
 151           yourself forced to close all your Linux applications just to run
 152           that one Windows application. You may quickly get tired of this, or
 153           will find that such a situation is impossible to justify in a
 154           business environment.
 155         </para>
 156         <para>
 157           The next solution is to install virtual machine emulation software
 158           such as VMWare, Win4Lin or Plex86. Then you can use windows
 159           applications without suffering such a big disruption. But it still
 160           requires that you acquire a Windows license and dedicate as much
 161           disk space to Windows. Furthermore you will pay for the added
 162           convenience: if using VMWare or Win4Lin you have to buy another
 163           license, and more importantly you now have to dedicate a good chunk
 164           of your computer's memory to the virtual machine. Performance will
 165           take a significant hit too.
 166         </para>
 167         <para>
 168           Using Wine lets you avoid all of that overhead: Windows license,
 169           hard-drive space required by Windows, memory and performance hit
 170           taken by emulated virtual machines. Now you can start your Windows
 171           application straight from your regular desktop environment, place
 172           that application's window side by side with native application
 173           windows, copy/paste from one to the other, and run it all at full speed.
 174         </para>
 175         <para>
 176           It is also a pretty vital part of migrating a large organisation,
 177           you can't change a 5000 desktop setup overnight without a lot of risk.
 178        </para>
 179       </answer>
 180       </qandaentry>
 181
 182       <qandaentry>
 183       <question id="Which-one-of-the-different-Wine-packages">
 184         <para>Which one of the different Wine packages out there is good for me?</para>
 185       </question>
 186       <answer>
 187         <para>
 188           Currently there is a broad selection of different Wine packages/versions:
 189         </para>
 190         <variablelist>
 191
 192           <varlistentry>
 193            <term><ulink url="http://www.winehq.com">Wine</ulink></term>
 194            <listitem>
 195            <para>
 196               This is the "standard" source distribution of Wine. Its license is
 197               the LGPL, it can be downloaded for free.
 198             </para>
 199            </listitem>
 200           </varlistentry>
 201
 202           <varlistentry>
 203           <term><ulink url="http://rewind.sourceforge.net">ReWind</ulink></term>
 204           <listitem>
 205             <para>
 206               This is a forked Wine tree that got created when Wine changed its
 207               license from X11 to the more restrictive LGPL, in order to let
 208               people continue to maintain an X11 licensed Wine version. Its
 209               license is X11, it can be downloaded for free.
 210             </para>
 211          </listitem>
 212           </varlistentry>
 213
 214           <varlistentry>
 215           <term><ulink url="http://www.transgaming.com">Transgaming's WineX</ulink></term>
 216           <listitem>
 217             <para>
 218               This is TransGaming's Wine version specially suited for games.
 219               It includes Direct3D support (thus its DirectX support is much
 220               more complete than Wine's). Most of the code is under the AFPL
 221               and can be downloaded for free.
 222             </para>
 223             <para>
 224               However Transgaming also distributes binaries that contain
 225               improved copy protection support (needed for many
 226               games), support, and other enhancements. These packages are
 227               only available in binary form to subscribed customers
 228               ($5/month).
 229             </para>
 230          </listitem>
 231           </varlistentry>
 232
 233           <varlistentry>
 234           <term><ulink url="http://wine.codeweavers.com">CodeWeavers' Wine preview</ulink></term>
 235           <listitem>
 236             <para>
 237               This is a special packaged version of the standard Wine tree
 238               which has a nice setup for easy installation. License LGPL, free
 239               download.
 240             </para>
 241          </listitem>
 242           </varlistentry>
 243
 244           <varlistentry>
 245           <term><ulink url="http://www.codeweavers.com/products/crossover/">CodeWeavers' Crossover Plugin</ulink></term>
 246           <listitem>
 247             <para>
 248               Special Wine installation to be used for running Windows
 249               Netscape browser plugins such as e.g. QuickTime in Linux
 250               browsers. Costs $24.95.
 251               Well worth it (very stable and useful packaging).
 252             </para>
 253           </listitem>
 254           </varlistentry>
 255
 256           <varlistentry>
 257           <term><ulink url="http://www.codeweavers.com/products/office/">CodeWeavers' Crossover Office</ulink></term>
 258           <listitem>
 259             <para>
 260               Wine version with special packaging to make sure almost all
 261               important Office type programs work pretty well. Costs $54.95.
 262               Seems to be well worth it so far according to some comments.
 263               (note: you're supporting a company actively contributing to Wine
 264               if you decide to buy either Plugin or Office.
 265             </para>
 266           </listitem>
 267           </varlistentry>
 268
 269           <varlistentry>
 270           <term><ulink url="http://www.winehq.org/download/">Other packaged versions of Wine</ulink></term>
 271           <listitem>
 272             <para>
 273               Various Wine packages can be downloaded for free from
 274               Wine HQ. They are not officially packaged by Wine HQ, and as
 275               such may have some configuration inconsistencies.
 276             </para>
 277           </listitem>
 278           </varlistentry>
 279         </variablelist>
 280       </answer>
 281       </qandaentry>
 282
 283       <qandaentry>
 284       <question id="Whats-the-history-of-Wine">
 285         <para>What's the history of Wine?</para>
 286       </question>
 287       <answer>
 288         <para>
 289           The Wine project started in 1993 as a way to support running Windows 3.1
 290           programs on Linux. Bob Amstadt was the original coordinator, but turned
 291           it over fairly early on to Alexandre Julliard, who has run it ever
 292           since. A <ulink url="news:comp.emulators.ms-windows.wine">newsgroup</ulink>
 293           was created in July 1994. Over the years, ports for
 294           other Unixes have been added, along with support for Win32 as Win32
 295           applications became popular.
 296         </para>
 297         <para>
 298           For more information, see <ulink url="http://www.winehq.com/about.shtml">
 299           http://www.winehq.com/about.shtml</ulink>
 300         </para>
 301       </answer>
 302       </qandaentry>
 303
 304       <qandaentry>
 305       <question id="What-is-the-current-version-of-Wine">
 306         <para>What is the current version of Wine?</para>
 307       </question>
 308       <answer>
 309         <para>
 310           A new version of Wine is distributed about every month. You will be
 311           able to keep up on all the latest releases by reading the newsgroup
 312           <ulink url="news:comp.emulators.ms-windows.wine">
 313           comp.emulators.ms-windows.wine</ulink>, or by visiting the
 314           <ulink url="http://www.winehq.com">Wine HQ homepage</ulink>. When
 315           downloading Wine from your FTP site of choice (see
 316           <ulink url="http://www.winehq.com/download.shtml">the Download page</ulink>
 317           for some of these choices), you can make sure that you are getting
 318           the latest version by watching the version numbers in the distribution
 319           filename. For instance, the distribution released on October 31, 2002
 320           was called Wine-20021031.tar.gz. Patch files are also available. If
 321           you are current to the previous version, you can download and apply
 322           just the current patch file rather than the entire new distribution.
 323           The patch filenames follow the same conventions as the monthly
 324           distribution. <ulink url="http://www.winehq.com/dev.shtml">
 325           Read-only CVS</ulink> access is also available.
 326         </para>
 327       </answer>
 328       </qandaentry>
 329
 330       <qandaentry>
 331       <question id="What-is-the-current-Status-of-Wine">
 332         <para>What is the current Status of Wine?</para>
 333       </question>
 334       <answer>
 335         <para>
 336           As of mid 2002, Wine consists of over 1 million lines of C code,
 337           written by more than 300 developers from dozens of countries around
 338           the world. Wine is in active use by an estimated 100K people. Wine
 339           implements more than 90% of the calls in popular Windows
 340           specifications such as ECMA-234 and Open32.
 341         </para>
 342         <para>
 343           You may also want to look at the
 344           <ulink url="http://www.winehq.com/about/index.php?status">
 345           Status page</ulink> for a global view on Wine's implementation progress.
 346         </para>
 347       </answer>
 348       </qandaentry>
 349
 350       <qandaentry>
 351       <question id="When-will-Wine-be-finished">
 352         <para>When will Wine be finished?</para>
 353       </question>
 354       <answer>
 355         <para>
 356           Large software projects are never finished, only released. In any
 357           case Wine is chasing a moving target since every new release of
 358           Windows contains new API calls or variations on the existing ones.
 359         </para>
 360         <para>
 361           Because Wine is being developed by volunteers, it is difficult to
 362           predict when it will be ready for general release. But due to the
 363           much increased interest by companies in porting apps via Wine, Wine
 364           development is constantly getting more and more active. Right now
 365           we are working on releasing Wine 0.9 in 2003.
 366         </para>
 367       </answer>
 368       </qandaentry>
 369
 370       <qandaentry>
 371       <question id="Who-is-responsible-for-Wine">
 372         <para>Who is responsible for Wine?</para>
 373       </question>
 374       <answer>
 375         <para>
 376           Wine is available thanks to the work of many people. Please see the
 377           <ulink url="http://www.winehq.com/source/AUTHORS">AUTHORS</ulink>
 378           file in the distribution for the complete list. Some companies that
 379           are or have been involved with Wine development are CodeWeavers,
 380           TransGaming, Corel, and Macadamian.
 381         </para>
 382       </answer>
 383       </qandaentry>
 384
 385       <qandaentry>
 386       <question id="folks-who-contributed-money-or-equipment">
 387         <para>Who are the folks and organizations who have contributed money or equipment to the Wine project?</para>
 388       </question>
 389       <answer>
 390         <para>
 391           People and organizations who have given generous contributions of
 392           money, equipment, or licenses, include:
 393         </para>
 394         <itemizedlist spacing="compact">
 395           <listitem>
 396             <para>David L. Harper</para>
 397           </listitem>
 398           <listitem>
 399             <para>Bob Hepple</para>
 400           </listitem>
 401           <listitem>
 402             <para>Mark A. Horton</para>
 403           </listitem>
 404           <listitem>
 405             <para>Kevin P. Lawton</para>
 406           </listitem>
 407           <listitem>
 408             <para>The Syntropy Institute</para>
 409           </listitem>
 410           <listitem>
 411             <para>James Woulfe</para>
 412           </listitem>
 413           <listitem>
 414             <para>
 415              VMWare Inc. (<ulink url="http://www.vmware.com">
 416              http://www.vmware.com</ulink>)
 417             </para>
 418           </listitem>
 419           <listitem>
 420             <para>
 421              Corel (<ulink url="http://www.corel.com">
 422              http://www.corel.com</ulink>)
 423             </para>
 424           </listitem>
 425         </itemizedlist>
 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.
 444         </para>
 445       </answer>
 446       </qandaentry>
 447
 448      <qandaentry>
 449       <question id="Is-TransGamings-last-patch-included-in-Wine">
 450         <para>Is TransGaming's latest patch included in the standard Wine release?</para>
 451       </question>
 452       <answer>
 453         <para>
 454           No, it's not.
 455         </para>
 456         <para>
 457           TransGaming makes money via a subscription service and the license
 458           of their WineX tree is incompatible with the Wine license. Thus
 459           WineX patches cannot be integrated into the Wine tree without
 460           express permission by TransGaming. They have submitted some
 461           of their work for integration into Wine, most notably DirectDraw
 462           and some DirectSound work, and such work has been integrated into
 463           Wine tree. However it seems unlikely they will submit their Direct3D
 464           work.
 465         </para>
 466       </answer>
 467       </qandaentry>
 468
 469       <qandaentry>
 470       <question id="Will-there-be-a-Windows-version-of-Wine">
 471         <para>Will there be a Windows version of Wine?</para>
 472       </question>
 473       <answer>
 474         <para>
 475           Some people are working on getting Wine code to compile on Windows.
 476         </para>
 477         <itemizedlist spacing="compact">
 478           <listitem>
 479             <para>
 480               Cygwin (<ulink url="http:/www.cygwin.com">
 481               http://www.cygwin.com/</ulink>)
 482             </para>
 483           </listitem>
 484           <listitem>
 485             <para>
 486               Reactos (<ulink url="http://www.reactos.com/">
 487              http://www.reactos.com/</ulink>)
 488             </para>
 489           </listitem>
 490         </itemizedlist>
 491         <para>
 492           There's some progress, so a Wine version that's usable on Windows
 493           might be available at some time.
 494         </para>
 495       </answer>
 496       </qandaentry>
 497
 498     </qandadiv>
 499     <qandadiv id="What-do-I-need-in-order-to-use-Wine">
 500       <title>What do I need in order to use Wine?</title>
 501       <qandaentry>
 502       <question id="Under-what-platforms-will-Wine-run">
 503         <para>
 504           Under what hardware platform(s) and operating system(s) will
 505           Wine(Lib) run?
 506         </para>
 507       </question>
 508       <answer>
 509         <para>
 510           Wine is being developed specifically to run on the <emphasis>Intel x86</emphasis> class of CPUs under certain UNIXes that run on the x86 platform.
 511           Winelib however is capable of porting Windows program <emphasis>source code</emphasis> to other platforms also, not only x86.
 512         </para>
 513         <para>
 514           Thus running Windows programs via Wine on other platforms (e.g. MacOS X) is <emphasis>not</emphasis> possible; the only way to run Windows code
 515           on MacOS X would be to take Windows program source code and recompile it for e.g. MacOS X using Winelib.
 516         </para>
 517         <para>
 518           The following will list the x86 operating systems supported by
 519           Wine; Winelib support for other platforms keeps evolving,
 520           so it's not specifically listed here.
 521         </para>
 522         <para>
 523           NetBSD, OpenBSD, Unixware, and SCO OpenServer 5 worked at one time,
 524           but Wine now requires kernel-level threads which are not currently
 525           available (or understood by the Wine team) on those platforms.
 526         </para>
 527         <para>
 528           The Wine development team hopes to attract the interest of other
 529           commercial UNIX and UNIX clone vendors as well.
 530         </para>
 531         <para>
 532           BeOS: porting efforts used to be pretty strong, but BeOS has severe
 533           limitations in Unix call support, so a port will probably never
 534           happen.
 535         </para>
 536         <para>
 537           FreeBSD: Should work, with limitations in specific areas (mainly
 538           missing device/hardware support).
 539         </para>
 540         <para>
 541           Linux/x86: Works, and as most popular platform for both developers
 542           and users, it is the best supported platform of all.
 543         </para>
 544       </answer>
 545       </qandaentry>
 546
 547       <qandaentry>
 548       <question id="What-minimum-CPU-must-I-have">
 549         <para>
 550           What minimum CPU must I have in my computer to be able to run Wine
 551           and MS Windows applications smoothly?
 552         </para>
 553       </question>
 554       <answer>
 555         <para>
 556           We need to differentiate between Wine and Winelib here.
 557         </para>
 558         <para>
 559           Wine won't run on any x86 CPU less than an 80386 due to address
 560           management limitations.
 561         </para>
 562         <para>
 563           It is known to also work in the 80486 and upwards compatible CPUs.
 564           The basic test is, if you can run X11 now, you should be able to run
 565           Wine and MS Windows applications under it.
 566         </para>
 567         <para>
 568           As always, the faster your CPU, the better. Having a math coprocessor
 569           is unimportant. However, having a graphics accelerated video card
 570           supported by X will help greatly.
 571         </para>
 572         <para>
 573           Depending on your application you may find that faster speeds are
 574           required for sensible use. We can't give specific advice on that due
 575           to the vast range of applications out there. However the rule of
 576           thumb is that if your application runs fine on Windows, it should
 577           run fine on the same platform in Wine.
 578         </para>
 579       </answer>
 580       </qandaentry>
 581
 582       <qandaentry>
 583       <question id="How-much-disk-space-will-Wine-take">
 584         <para>
 585          How much disk space will the Wine source code and binaries take on my
 586          hard drive?
 587         </para>
 588       </question>
 589       <answer>
 590         <para>
 591           You need approximately 250 megabytes of free hard drive space to
 592           store and compile the source code. Wine also needs about 18 megs in
 593           your /tmp directory. And about 50 MB are needed to do a make install.
 594         </para>
 595         <para>
 596           Binary packages, especially those not containing debug information,
 597           have much lower disk space requirements, usually in the 20MB range.
 598         </para>
 599       </answer>
 600       </qandaentry>
 601
 602       <qandaentry>
 603       <question id="What-other-software-do-I-need-to-compile">
 604         <para>
 605           What other software do I need to install, compile and run
 606           Wine?
 607         </para>
 608       </question>
 609       <answer>
 610         <para>
 611           Many development tools are needed in order to compile Wine.
 612           A list of required packages for several distributions is included in
 613           the README (<ulink url="http://www.winehq.com/source/README">
 614           http://www.winehq.com/source/README</ulink>).
 615         </para>
 616         <para>
 617           To run Wine, you will need the following:
 618         </para>
 619
 620         <itemizedlist spacing="compact">
 621           <listitem>
 622             <para>The compiled Wine binary</para>
 623           </listitem>
 624           <listitem>
 625             <para>A properly configured wine.conf file (or ~/.winerc file)</para>
 626           </listitem>
 627           <listitem>
 628             <para>An installed and working X Window system</para>
 629           </listitem>
 630           <listitem>
 631             <para>Some Windows programs to test</para>
 632           </listitem>
 633         </itemizedlist>
 634       </answer>
 635       </qandaentry>
 636        <qandaentry>
 637       <question id="How-much-RAM-do-I-need">
 638         <para>
 639           How much RAM do I need to have on my UNIX system to be able to run
 640           Wine and MS Windows applications smoothly?
 641         </para>
 642       </question>
 643       <answer>
 644         <para>
 645           If you can run X smoothly on your UNIX system now, you should be
 646           able to run Wine and MS Windows applications just fine too, depending
 647           on how memory hungry the application is.
 648         </para>
 649         <para>
 650           A Wine workstation will work with 16 megabytes of RAM and a 16
 651           megabyte swap partition as long as you have a reasonable graphics
 652           card. Most applications will run reasonably with 64/64 Mb,
 653           interactive games are likely to need more. You can run Wine with 8/8,
 654           but it is going to be unusably slow and very constraining on the
 655           applications you can run. If you wish to be part of the development
 656           team and program Wine itself, be aware that the debugger is rather
 657           memory intensive. Some have suggested that 64 megabytes is the
 658           minimum RAM needed for Wine development, although some are able to
 659           work (albeit slowly) with 24 megabytes of physical RAM and lots of
 660           swap space.
 661         </para>
 662       </answer>
 663       </qandaentry>
 664
 665       <qandaentry>
 666       <question id="How-long-does-Wine-take-to-build">
 667         <para>How long does Wine take to build</para>
 668       </question>
 669       <answer>
 670         <para>
 671           Wine is getting to be quite large, and building from scratch takes a
 672           lot of processing. As of September 2002, compile times were around 20
 673           minutes on an Athlon 1200 with 640 Mb and 45-50 minutes on a Cyrix
 674           300 with 64 Mb. If you have a CVS copy, you may not need to rebuild
 675           the whole thing every time you update.
 676         </para>
 677       </answer>
 678       </qandaentry>
 679       <qandaentry>
 680       <question id="I-have-a-Drivespaced-partition">
 681         <para>
 682           I have a Drivespaced, Doublespaced or Stackered DOS partition. Can
 683           Wine run MS Windows binaries located in such a partition?
 684         </para>
 685       </question>
 686       <answer>
 687         <para>
 688           Yes, but only if the operating system supports mounting those types
 689           of drives. There is a Linux file system driver called dmsdos that
 690           will allow read/write access to Doublespaced and Drivespace 1.0
 691           drives. More specifically, it supports mounting DOS 6.0 and 6.2
 692           Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced
 693           compressed partitions (read and write access works fine, but write
 694           access is slow). It can be found at
 695           <ulink url="ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/">
 696           ftp://metalab.unc.edu/pub/Linux/system/file systems/dosfs/</ulink>
 697         </para>
 698       </answer>
 699       </qandaentry>
 700
 701       <qandaentry>
 702       <question id="Do-I-need-to-have-a-DOS-partition">
 703         <para>Do I need to have a DOS partition on my system to use Wine?</para>
 704       </question>
 705       <answer>
 706         <para>
 707           You do not need a licensed and installed copy of DOS or MS Windows to
 708           install, configure and run Wine. However, Wine has to be able to
 709           'see' an MS Windows binary (i.e. application) if it is to run it.
 710         </para>
 711       </answer>
 712       </qandaentry>
 713
 714       <qandaentry>
 715       <question id="Does-MS-Windows-need-to-be-installed">
 716         <para>
 717           Does MS Windows need to be loaded into that partition in order to
 718           run MS Windows programs under Wine?
 719         </para>
 720       </question>
 721       <answer>
 722         <para>
 723           Many folks have successfully installed and run some small programs
 724           in their UNIX filesystem without having a DOS partition or MS
 725           Windows. However, in many cases you need a directory and file
 726           infrastructure that is similar to an existing Windows installation.
 727           Some applications' installation programs want to distribute some of
 728           the package's files into the /windows and /windows/system
 729           directories in order to run, and unless these exist on your UNIX
 730           file system, those programs will not install correctly and probably
 731           will not run well, if at all.
 732         </para>
 733         <para>
 734           If you have a DOS partition with MS Windows installed in it, make
 735           sure that your UNIX system can 'see' this partition (check your
 736           /etc/fstab file or mount the partition manually) so that Wine can
 737           run the MS Windows binaries located in the DOS partition. To run
 738           without a DOS partition, you need to set a UNIX path to be your
 739           drive C, and make sure that the /windows and /windows/system
 740           directories point to some place that actually exist.
 741         </para>
 742         <para>
 743           Here's an example, copied from a machine which has no DOS partition
 744           but successfully runs Wine:
 745         </para>
 746         <screen>
 747     [Drive C]
 748           Path=/var/lib/wine
 749           Type=hd
 750           Label=MS-DOS
 751           Filesystem=win95
 752     [wine]
 753           Windows=c:\windows
 754           System=c:\windows\system
 755           Temp=e:\
 756           Path=c:\windows;c:\windows\system;c:
 757         </screen>
 758         <para>
 759          In <filename>/var/lib/wine/windows</filename>, you will need to
 760          install a <filename>win.ini</filename> config file that you might
 761          find on a typical MS Windows 3.1 machine. The directory
 762          <filename>/var/lib/wine/windows/system</filename> should exist, but
 763          doesn't need to contain anything. However, to use MS DLLs, you can
 764          copy them into that directory. Note that this is a contravention of
 765          the Windows licence unless Windows is properly installed on the
 766          machine. If you have DOS/MS Windows installed on your system, you can
 767          mount that partition at bootup by modifying the file
 768          <filename>/etc/fstab</filename> in your UNIX partition (assuming that
 769          the UNIX kernel supports the DOS/MS Windows filesystem type).
 770         </para>
 771         <para>
 772           If you edit this file by hand, it should contain something similar
 773           to the following:
 774         </para>
 775         <screen>
 776 /dev/hda1 /dosc msdos uid=0,gid=100,umask=007 0 0
 777         </screen>
 778         <para>
 779           This will allow you to read and write to the DOS partition without
 780           being root.
 781         </para>
 782       </answer>
 783       </qandaentry>
 784
 785       <qandaentry>
 786       <question id="If-Wine-completely-replaces-MS-Windows">
 787         <para>
 788           If Wine completely replaces MS Windows, will it duplicate all of the
 789           functions of MS Windows?
 790         </para>
 791       </question>
 792       <answer>
 793         <para>
 794           Most of them, yes. However, some applications and applets that come
 795           with MS Windows, such as File Manager and Calculator, can be
 796           considered by some to be redundant, since 32-bit UNIX programs that
 797           duplicate these applets' functions already exist.
 798         </para>
 799       </answer>
 800       </qandaentry>
 801
 802       <qandaentry>
 803       <question id="Will-I-install-on-ony-UNIX-file-system">
 804         <para>
 805           Will I be able to install MS Windows applications in any flavor of a
 806           UNIX file system?
 807         </para>
 808       </question>
 809       <answer>
 810         <para>
 811           Wine is written to be file system independent, so MS Windows
 812           applications will install and run under virtually any file system
 813           supported by your brand of UNIX.
 814         </para>
 815       </answer>
 816       </qandaentry>
 817
 818       <qandaentry>
 819       <question id="Will-Wine-run-only-under-X">
 820         <para>Will Wine run only under X, or can it run in character mode?</para>
 821       </question>
 822       <answer>
 823         <para>
 824           Most of Wine's development effort is geared against MS Windows' GUI,
 825           but some limited support for character mode has appeared, by setting
 826           <parameter>GraphicsDriver=ttydrv</parameter> in wine.conf's
 827           <parameter>[wine]</parameter> section.
 828         </para>
 829         <para>
 830           Wine's infrastructure is already somewhat prepared for supporting
 831           other graphics drivers than x11drv, but no real "alternative"
 832           graphics driver has been developped yet.
 833         </para>
 834       </answer>
 835       </qandaentry>
 836
 837       <qandaentry>
 838       <question id="Will-Wine-run-under-any-X-window-manager">
 839         <para>Will Wine run under any X window manager? Does it require a window manager at all?</para>
 840       </question>
 841       <answer>
 842         <para>
 843           Wine is window manager independent, so the X window manager you
 844           choose to run has (almost) no bearing on your ability to run MS
 845           Windows programs under Wine. Wine uses standard X libraries, so no
 846           additional ones are needed. Wine has its own window management,
 847           which acts like MS Windows. It can be turned off to use the native
 848           window manager by modifying Managed or Desktop settings as described
 849           in <command>man wine.conf</command>.
 850         </para>
 851       </answer>
 852       </qandaentry>
 853
 854       <qandaentry>
 855       <question id="Will-32-bit-applications-run-under-Wine">
 856         <para>Will 32-bit Windows 95/98 applications run under Wine?</para>
 857       </question>
 858       <answer>
 859         <para>
 860           Yes, 32-bit programs are now about as well supported as 16-bit
 861            programs.
 862         </para>
 863       </answer>
 864       </qandaentry>
 865
 866     </qandadiv>
 867     <qandadiv id="FAQ-Getting-Wine">
 868       <title>Getting Wine</title>
 869       <qandaentry>
 870       <question id="Where-can-I-get-Wine">
 871         <para>Where can I get Wine?</para>
 872       </question>
 873       <answer>
 874         <para>
 875           Because of lags created by using mirror, word of this newest release
 876           may reach you before the release is actually available at the ftp
 877           sites listed here. The sources are available from the following
 878           locations:
 879         </para>
 880         <itemizedlist>
 881           <listitem>
 882             <para>
 883               <ulink url="http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/">
 884                http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/
 885               </ulink>
 886             </para>
 887           </listitem>
 888           <listitem>
 889             <para>
 890               <ulink url="ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/">
 891               ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/
 892               </ulink>
 893             </para>
 894           </listitem>
 895
 896           <listitem>
 897             <para>
 898               <ulink url="ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/">
 899               ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/
 900               </ulink>
 901             </para>
 902           </listitem>
 903
 904           <listitem>
 905             <para>
 906               <ulink url="ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/">
 907               ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/
 908               </ulink>
 909             </para>
 910           </listitem>
 911
 912         </itemizedlist>
 913         <para>
 914           It should also be available from any other site that mirrors
 915           ibiblio.org. For more download locations, see
 916           <ulink url="http://ftp search.lycos.com.">lycos</ulink> Some of
 917           these ftp sites may archive previous versions of Wine as well as the
 918           current one. To determine which is the latest one, look at the
 919           distribution file name, which will take the form
 920           Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution
 921           file name with the numbers for year, month and date, respectively.
 922           The latest one is the one to get.
 923         </para>
 924         <para>
 925           Wine binary packages are available for several OS'es and
 926           distributions. See
 927           <ulink url="http://www.winehq.com/download.shtml">
 928           the download page</ulink> for the most recent list.
 929         </para>
 930       </answer>
 931       </qandaentry>
 932
 933       <qandaentry>
 934       <question id="Is-there-a-CVS-tree">
 935         <para>Is there a CVS tree?</para>
 936       </question>
 937       <answer>
 938         <para>
 939           Current Wine sources are also available via anonymous client/server
 940           CVS. You will need CVS 1.9 or above. If you are coming from behind a
 941           firewall, you will either need a hole in the firewall for the CVS
 942           port (2401) or use SOCKS.
 943         </para>
 944         <para>
 945           To login to the CVS tree, do
 946         </para>
 947         <screen>
 948 export CVSROOT=:pserver:cvs@cvs.winehq.com/home/wine
 949 cvs login
 950         </screen>
 951         <para>
 952           Use "cvs" as the password (without the quotes). Note that
 953           <filename>/home/wine</filename> is a path on the server, not on your
 954           machine. To check out the entire Wine source tree (which may be
 955           slow), use
 956         </para>
 957         <screen>
 958 cvs -z 3 checkout wine
 959         </screen>
 960         <para>
 961           or if you just want a subtree, or individual file, you can do that
 962           too with
 963         </para>
 964         <screen>
 965 cvs -z 3 checkout wine/ANNOUNCE
 966         </screen>
 967         <para>
 968           Be aware, though, that getting the entire Wine source tree via CVS
 969           is pretty slow, especially compared to getting Wine from an FTP
 970           mirror near you. For a CVS mirror list, see
 971           <ulink url="http://www.winehq.com/dev.shtml">
 972           http://www.winehq.com/dev.shtml</ulink>
 973         </para>
 974         <para>
 975           Patch files are also available, so that you don't have to download,
 976           install, and configure the entire distribution each week if you are
 977           current to the previous release. Patch file release names follow the
 978           same numbering convention as do the general releases, and take the
 979           form
 980         </para>
 981         <para>
 982           Wine-YYYYMMDD.diff.gz
 983         </para>
 984         <para>
 985           Patch files are available from the same sites that distribute the
 986           full release. To upgrade to a new release by using a patch file,
 987           first cd to the top-level directory of the release (the one
 988           containing the README file), then do a "make clean", and patch the
 989           release with
 990         </para>
 991         <screen>
 992 gunzip -c patch-file | patch -p1
 993         </screen>
 994         <para>
 995           where patch-file is the name of the patch file something like
 996           Wine-YYYYMMDD.diff.gz. You can then re-run ./configure, and then run
 997           make depend && make
 998         </para>
 999         <para>
1000           If you are mirroring the Wine distribution from the tsx-11 site and
1001           wish to be listed here in this FAQ, please add it to the
1002           "things to go into the documentation" area.
1003         </para>
1004       </answer>
1005       </qandaentry>
1006
1007       <qandaentry>
1008       <question id="Can-I-get-Wine-using-cvsup">
1009         <para>Can I get Wine using cvsup?</para>
1010       </question>
1011       <answer>
1012         <para>
1013           The CVS mirrors don't offer cvsup support yet, but the main server
1014           does. Use a <filename>wine.sup</filename> file of:
1015         </para>
1016         <screen>
1017 *default host=cvs.winehq.com
1018 *default base=/cvs
1019 *default prefix=/cvs/wine
1020 *default release=wine
1021 *default delete
1022
1023 # If your network link is a T1 or faster, comment out the following line.
1024 #*default compress
1025
1026 *default use-rel-suffix
1027 wine
1028         </screen>
1029      </answer>
1030      </qandaentry>
1031     </qandadiv>
1032
1033     <qandadiv id="Installing-And-Configuring-Wine">
1034       <title>Installing And Configuring Wine</title>
1035       <qandaentry>
1036       <question id="How-do-I-compile-the-Wine-source-code">
1037         <para>How do I compile the Wine distribution source code?</para>
1038       </question>
1039       <answer>
1040         <para>
1041           See the README (<ulink url="http://www.winehq.com/source/README">http://www.winehq.com/source/README</ulink>) for instructions.
1042           Additionally, you may want to set the <parameter>TMPDIR</parameter>
1043           environment variable <command>TMPDIR=~/tmp</command> or
1044           <command>TMPDIR=/tmp</command> (if you are root).
1045         </para>
1046       </answer>
1047       </qandaentry>
1048
1049       <qandaentry>
1050       <question id="How-do-I-install-Windows-in-Wine">
1051         <para>How do I install Windows in Wine under Linux?</para>
1052       </question>
1053       <answer>
1054         <para>
1055           Simple answer: you CAN'T. Windows demands direct access to the
1056           hardware and cannot get it with Wine and UNIX in the way
1057         </para>
1058         <para>
1059           Wine is supposed to be used WITHOUT Windows primarily. If you want
1060           to use a Windows installation, then use an existing installation
1061           alongside the UNIX installation (see the dual-boot HOWTO for your OS
1062           for more details). Or alternatively use the cabextract utility to
1063           extract Windows install archives to a directory that you want to use
1064           as Wine's Windows tree.
1065         </para>
1066       </answer>
1067       </qandaentry>
1068
1069       <qandaentry>
1070       <question id="How-do-I-configure-Wine-to-run-on-my-system">
1071         <para>How do I configure Wine to run on my system?</para>
1072       </question>
1073       <answer>
1074         <para>
1075           Wine requires that you have a config file as
1076           <filename>~/.wine/config</filename>. The format of this file is
1077           explained in the <filename>wine.conf</filename> man page. The file
1078           <filename>documentation/samples/config</filename>
1079           (<ulink url="http://www.winehq.com/source/documentation/samples/config">
1080           http://www.winehq.com/source/documentation/samples/config</ulink>)
1081           contains a config file example. More explicit directions can be
1082           found in the <filename>README</filename> file
1083           (<ulink url="http://www.winehq.com/source/README">
1084           http://www.winehq.com/source/README</ulink>) that will be located in
1085           the base Wine directory after you gunzip and untar the distribution
1086           file.
1087         </para>
1088       </answer>
1089       </qandaentry>
1090
1091       <qandaentry>
1092       <question id="How-do-I-upgrade-configuration">
1093         <para>How do I upgrade Wine without losing my working configuration?</para>
1094       </question>
1095       <answer>
1096         <para>
1097           Upgrading the wine installation does not affect the existing wine
1098           configuration. So after upgrading wine you still have the old (working )
1099           wine configuration.
1100         </para>
1101       </answer>
1102       </qandaentry>
1103
1104       <qandaentry>
1105       <question id="If-I-use-Windows-which-versions-OK">
1106         <para>If I want to use a Windows install, which versions are OK?</para>
1107       </question>
1108       <answer>
1109         <para>
1110           Either use a classic no-windows install (Wine is getter better all
1111           the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T
1112           configure Wine to use an NT-based Windows install (NT, Win2K, WinXP).
1113         </para>
1114       </answer>
1115       </qandaentry>
1116
1117       <qandaentry>
1118       <question id="If-I-use-Windows-which-one-works-best">
1119         <para>If I use a Windows install with Wine, which one works best?</para>
1120       </question>
1121       <answer>
1122         <para>
1123           As of 02/2002:
1124         </para>
1125         <para>
1126           I'd say Win98SE is the best version to use with Wine, as it's fairly
1127           widespread amongst developers and relatively old. Using Win2K files
1128           is <emphasis>definitely</emphasis> worse than a plain no-windows
1129           Wine install, and Win ME is said to be problematic, too (as probably
1130           no developer uses it). In short: all Win9x &lt;= W98SE are good.
1131         </para>
1132       </answer>
1133       </qandaentry>
1134
1135       <qandaentry>
1136       <question id="Installing-Visual-Basic-apps-wont-run">
1137         <para>
1138           Installing applications generated by Visual Basic won't run. What
1139           should I do?
1140         </para>
1141       </question>
1142       <answer>
1143         <para>
1144           Make sure you have all the VB runtime libraries installed. You may
1145           need to use the native DLL vbrun60.dll
1146         </para>
1147       </answer>
1148       </qandaentry>
1149
1150       <qandaentry>
1151       <question id="When-I-click-on-exe-file-nothing-happens">
1152         <para>When I click on *.exe file in my file Manager, nothing happens</para>
1153       </question>
1154       <answer>
1155         <para>
1156           The normal Wine releases don't have .exe extensions registered for
1157           Wine in KDE/Gnome yet. You have to open a terminal window instead
1158           (often an icon showing a "black screen") and type something like:
1159         </para>
1160         <screen>
1161 cd /my/windows/program/directory
1162 wine myprogram.exe
1163         </screen>
1164         <para>
1165           Or alternatively you could download the CodeWeavers Wine preview
1166           which includes .exe extension registration for KDE/Gnome and a nice
1167           setup program.
1168         </para>
1169       </answer>
1170       </qandaentry>
1171
1172       <qandaentry>
1173       <question id="bash-wine-Command-not-found-What-can-I-do">
1174         <para>bash "wine: Command not found" What can I do?</para>
1175       </question>
1176       <answer>
1177         <para>
1178           Try to relogin into bash. That might fix it.
1179         </para>
1180         <para>
1181           If it doesn't, then make sure the wine binary is in your
1182           <parameter>PATH</parameter>.
1183         </para>
1184         <para>
1185           Run as root:
1186         </Para>
1187         <screen>
1188 find / -name "wine" -type f -perm +111
1189         </screen>
1190         <para>
1191           to find the path where the wine binary is in. Then check whether
1192         <parameter>PATH</parameter> includes it:
1193         </para>
1194         <screen>
1195 echo $PATH
1196         </screen>
1197         <para>
1198           If not, add that e.g. to <filename>/etc/profile</filename> by doing:
1199         </para>
1200         <screen>
1201 export PATH=$PATH:/path/to/wine/binary
1202         </screen>
1203         <para>
1204           That should help.
1205         </para>
1206         <para>
1207            If you used a package manager (<command>rpm</command> or
1208            <command>apt</command>) - Verify your packages. The package
1209            <filename>winesetuptk.rpm</filename> is only a front-end for
1210            making a meaningfull config file, it DOES NOT install the wine
1211            package...
1212         </para>
1213         <para>
1214            For complete packages, use <ulink url="http://www.rpmfind.net/">
1215            www.rpmfind.net</ulink> or the <ulink url="http://www.winehq.org/download/">
1216            Download</ulink> section.
1217         </para>
1218       </answer>
1219       </qandaentry>
1220
1221       <qandaentry>
1222       <question id="How-do-I-remove-Wine-from-my-Computer">
1223         <para>How do I remove Wine from my Computer?</para>
1224       </question>
1225       <answer>
1226         <para>
1227           All you have to do is to type:
1228         </para>
1229         <screen>
1230 rm -fR \[/path/\]Wine*
1231         </screen>
1232         <para>
1233           Make sure that you specify the exact path when using the powerful
1234           <command>rm -fR</command> command. If you are afraid that you might
1235           delete something important, or might otherwise delete other files
1236           within your filesystem, <command>cd</command> into each Wine
1237           subdirectory singly and delete the files found there manually,
1238           one file or directory at a time.
1239         </para>
1240         <para>
1241         Neither the Wine developers and programmers, nor the Wine FAQ
1242         author/maintainer, can be held responsible for your deleting any
1243         files in your own filesystem.
1244         </para>
1245       </answer>
1246       </qandaentry>
1247     </qandadiv>
1248
1249     <qandadiv id="About-running-Wine">
1250       <title>About running Wine</title>
1251       <qandaentry>
1252       <question id="How-do-I-run-an-MS-Windows-program">
1253         <para>How do I run an MS Windows program under Wine?</para>
1254       </question>
1255       <answer>
1256         <para>
1257           When invoking Wine, you must specify the entire path to the
1258           executable, or by filename only. For example to run Windows'
1259           solitaire, type any of the following:
1260         </para>
1261         <itemizedlist>
1262           <listitem>
1263           <para>
1264             <command>wine sol</command> or <command>wine sol.exe</command>
1265            (using the search path to locate the file).
1266           </para>
1267           </listitem>
1268           <listitem>
1269           <para>
1270             <command>wine c:\\windows\\sol.exe</command>
1271            (using a DOS filename).
1272           </para>
1273           </listitem>
1274           <listitem>
1275           <para>
1276             <command>wine /usr/windows/sol.exe</command>
1277            (using a UNIX filename).
1278           </para>
1279           </listitem>
1280           <listitem>
1281           <para>
1282             <command>wine "c:\windows\sol.exe"</command>
1283             (using quoted DOS filename).
1284           </para>
1285           </listitem>
1286         </itemizedlist>
1287         <para>
1288           The path of the file will also be added to the path when a full name
1289           is supplied on the command line.
1290
1291         </para>
1292       </answer>
1293       </qandaentry>
1294
1295       <qandaentry>
1296       <question id="Wine-cannot-find-MS-Windows-on-my-drive">
1297         <para>
1298           I have installed and configured Wine, but Wine cannot find MS
1299           Windows on my drive. Where did I go wrong?
1300         </para>
1301       </question>
1302       <answer>
1303         <para>
1304           If you have a DOS partition, first make sure that you have mounted
1305           it, either by putting the entry into <filename>/etc/fstab</filename>,
1306           or by manually mounting it.
1307         </para>
1308         <para>
1309           Remember too that unless your version of UNIX can see through it, or
1310           you are running a utility that can see through it, your DOS
1311           partition must not be located on a Drivespaced, Doublespaced or
1312           Stackered partition, as neither Linux, FreeBSD, NetBSD or Wine can
1313           natively 'see' files located in these compressed DOS partitions.
1314         </para>
1315         <para>
1316           Check your path statements in the <filename>wine.conf</filename>
1317           file. No capital letters may be used in paths, as they are
1318           automatically converted to lowercase.
1319         </para>
1320       </answer>
1321       </qandaentry>
1322
1323       <qandaentry>
1324       <question id="Parts-of-my-app-do-not-work-What-is-wrong">
1325         <para>
1326           I was able to get various MS Windows programs to run, but parts of
1327           them do not work. What is wrong?
1328         </para>
1329       </question>
1330       <answer>
1331         <para>
1332           Wine is not complete at this time, so some of each programs'
1333           features may not work. They will in time as more of the MS
1334           Windows API calls are included in Wine.
1335         </para>
1336       </answer>
1337       </qandaentry>
1338
1339       <qandaentry>
1340       <question id="Menus-do-not-work-how-can-I-exit">
1341         <para>
1342           I have run various MS Windows programs, but since the program menus
1343           do not work, how can I exit these programs?
1344         </para>
1345       </question>
1346       <answer>
1347         <para>
1348           Kill the xterm shell window that you called up to run your MS
1349           Windows program, and the X window that appeared with the program
1350           will be killed too.
1351         </para>
1352       </answer>
1353       </qandaentry>
1354
1355       <qandaentry>
1356       <question id="Can-I-use-Wine-with-other-Linux-Distros">
1357         <para>Can I use Wine with SuSe, Peanut or other Linux Distro's?</para>
1358       </question>
1359       <answer>
1360         <para>
1361           You can use Wine on any sufficiently recent Linux installation. The
1362           amount of work getting Wine up and running depends on whether there
1363           are proper packages available or a source compile has to be done.
1364         </para>
1365       </answer>
1366       </qandaentry>
1367
1368       <qandaentry>
1369       <question id="Does-Wine-work-with-AMD-Processors">
1370         <para>Does Wine work with AMD Processors?</para>
1371       </question>
1372       <answer>
1373         <para>
1374           Yes, it does.
1375         </para>
1376       </answer>
1377       </qandaentry>
1378
1379        <qandaentry>
1380       <question id="Can-I-launch-Unix-app-from-Windows-app">
1381         <para> Can I launch a Unix program from a Windows program?</para>
1382       </question>
1383       <answer>
1384         <para>
1385           Sure, Wine supports that. Just enter the unix program name wherever
1386           a program has something that it's supposed to execute,and then it
1387           should just work.
1388         </para>
1389       </answer>
1390       </qandaentry>
1391       <qandaentry>
1392       <question id="Error-with-installshield-6">
1393         <para>
1394           I get <quote>Error installing iKernel.exe: (0x1400)</quote>
1395           when running an Installshield 6 installer
1396         </para>
1397       </question>
1398       <answer>
1399         <para>
1400           If you get the error "Error installing iKernel.exe: (0x1400)" at any
1401           point, it's probably because there are leftover processes from a
1402           previous try. You can verify this with the command
1403         </para>
1404         <para><command>$ ps augxw | grep wine</command></para>
1405         <para>
1406           If that command shows old copies of wine running your setup,
1407           you need to kill them before you can run the setup program.
1408           If there are no other Wine programs running, you can kill them
1409           all with the command
1410         </para>
1411         <para><command>$ killall wine</command></para>
1412         <para>
1413           If you're also running Wine programs you care about, you'll
1414           have to kill off the old Setup instances one by one using
1415           kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
1416           which doesn't exist yet).
1417         </para>
1418         <para>
1419           You should repeat the <command>ps</command> to make sure the old
1420           wines are gone.
1421         </para>
1422        </answer>
1423       </qandaentry>
1424     </qandadiv>
1425
1426     <qandadiv id="Getting-help">
1427       <title>Getting help</title>
1428       <qandaentry>
1429       <question id="Is-there-any-documentation-for-Wine">
1430         <para>Is there any documentation for Wine?</para>
1431       </question>
1432       <answer>
1433         <para>
1434           Yes, see <ulink url="http://www.winehq.org/support.shtml">
1435           http://www.winehq.com/support.shtml.</ulink>
1436         </para>
1437       </answer>
1438       </qandaentry>
1439
1440       <qandaentry>
1441       <question id="I-have-written-some-documententation">
1442         <para>
1443           I couldn't find the answer to my question in the documentation, but
1444           I've written a document explaining how to solve it. What should I do?
1445         </para>
1446       </question>
1447       <answer>
1448         <para>
1449           Updates and additions to the Wine documentation directory should be
1450           sent to the wine-patches mailing list at
1451           <ulink url="http://www.winehq.com/dev.shtml#ml">
1452           http://www.winehq.com/dev.shtml#ml</ulink>. Website and FAQ
1453           additions should be added to the appropriate Wine Knowledgebase
1454           directory.
1455         </para>
1456       </answer>
1457       </qandaentry>
1458
1459       <qandaentry>
1460       <question id="Is-there-a-Usenet-newsgroup-for-Wine">
1461         <para>Is there a Usenet newsgroup for Wine?</para>
1462       </question>
1463       <answer>
1464         <para>
1465           Yes, and it's called
1466           <ulink url="news:comp.emulators.ms-windows.wine">
1467           comp.emulators.ms-windows.wine</ulink>. The newsgroup serves as a
1468           place for users and developers to discuss Wine, and for minor
1469           announcements for the general public. Major announcements will be
1470           crossposted to other appropriate newsgroups, such as the following:
1471         </para>
1472         <itemizedlist>
1473           <listitem>
1474           <para>
1475             <ulink url="news:comp.os.linux.announce">
1476             comp.os.linux.announce</ulink>
1477           </para>
1478           </listitem>
1479           <listitem>
1480           <para>
1481             <ulink url="news:ccomp.windows.x.announce">
1482             comp.windows.x.announce</ulink>
1483           </para>
1484           </listitem>
1485           <listitem>
1486           <para>
1487             <ulink url="news:ccomp.emulators.announce">
1488             comp.emulators.announce</ulink>
1489           </para>
1490           </listitem>
1491         </itemizedlist>
1492         <para>
1493           If your Usenet site does not carry these newsgroups, please urge
1494           your ISP's sysadmin to add and/or uplink them.
1495         </para>
1496       </answer>
1497       </qandaentry>
1498
1499       <qandaentry>
1500       <question id="Is-there-a-World-Wide-Web-site-for-Wine">
1501         <para>Is there a World Wide Web site for Wine?</para>
1502       </question>
1503       <answer>
1504         <para>
1505           Wine HQ (<ulink url="http://www.winehq.com">http://www.winehq.com</ulink>) is the official site.
1506         </para>
1507       </answer>
1508       </qandaentry>
1509
1510       <qandaentry>
1511       <question id="Is-there-an-IRC-channel-for-Wine">
1512         <para>Is there an IRC channel for Wine?</para>
1513       </question>
1514       <answer>
1515         <para>
1516           Sure. It's channel <filename>#WineHQ</filename> on
1517           <filename>irc.freenode.net</filename> see
1518           (<ulink url="http://freenode.net">http://freenode.net</ulink>).
1519           Usually several Wine developers hang out there just to help YOU ;-)
1520         </para>
1521       </answer>
1522       </qandaentry>
1523
1524       <qandaentry>
1525       <question id="I-think-I-found-a-bug-How-do-I-report-it">
1526         <para>
1527           I think I've found a bug. How do I report this bug to the Wine
1528           programming team?
1529         </para>
1530       </question>
1531       <answer>
1532         <para>
1533           Bug reports should be submitted to our online Bugzilla system
1534           (<ulink url="http://bugs.winehq.com">http://bugs.winehq.com/</ulink>).
1535           You should include at least the following:
1536         </para>
1537         <itemizedlist>
1538           <listitem>
1539           <para>
1540             The Wine version tested
1541           </para>
1542           </listitem>
1543           <listitem>
1544           <para>
1545             The MS Windows program name and, if possible, the version number
1546             of the software tested
1547           </para>
1548           </listitem>
1549           <listitem>
1550           <para>
1551             A brief description of the bug
1552           </para>
1553           </listitem>
1554           <listitem>
1555           <para>
1556             The relevant part(s) of the output of the Wine debugger
1557           </para>
1558           </listitem>
1559           <listitem>
1560           <para>
1561             A screenshot of the visual problem, if applicable
1562           </para>
1563           </listitem>
1564         </itemizedlist>
1565         <para>
1566          For more information about reporting bugs please see the
1567          <ulink url="http://www.winehq.org/Docs/wine-user/bug-reporting.shtml">
1568          How to report a bug</ulink> section of the Wine Users Guide.
1569         </para>
1570       </answer>
1571       </qandaentry>
1572     </qandadiv>
1573
1574     <qandadiv id="Helping-Wine-or-becoming-a-Wine-developer">
1575       <title>Helping Wine or becoming a Wine developer</title>
1576       <qandaentry>
1577       <question id="How-do-I-become-a-Wine-developer">
1578         <para>How do I become a Wine developer? What do I need to know?</para>
1579       </question>
1580       <answer>
1581         <para>
1582           If you can program C, that's a good start. Download the sources via
1583           CVS, subscribe to the mailing lists, look around the source, and pay
1584           attention to the comp.emulators.ms-windows.wine newsgroup and the
1585           mailing lists (<ulink url="http://www.winehq.com/dev.shtml#ml">http://www.winehq.com/dev.shtml#ml</ulink>). See if there's anything
1586           that you think you can fix or work on. You won't have much trouble
1587           finding areas that need work in Wine (grep for FIXMEs in the source).
1588         </para>
1589       </answer>
1590       </qandaentry>
1591
1592       <qandaentry>
1593       <question id="How-can-I-contribute-to-the-Wine-project">
1594         <para>How can I help contribute to the Wine project, and in what way(s)?</para>
1595       </question>
1596       <answer>
1597         <para>
1598           You can contribute programming or documentation skills, or monetary
1599           or equipment donations, to aid the Wine developers in reaching their
1600           goals.
1601         </para>
1602         <para>
1603           For a list of ideas of how you can help, please consult the
1604           <ulink url="http://www.winehq.com/about/index.php?contrib">
1605           Wine contrib page</ulink>.
1606         </para>
1607       </answer>
1608       </qandaentry>
1609
1610       <qandaentry>
1611       <question id="I-want-to-help-beta-test-Wine">
1612         <para>I want to help beta test Wine. How can I do this?</para>
1613       </question>
1614       <answer>
1615         <para>
1616           Wine still consists of some Alpha code at this time. However, anyone
1617           is welcome to download the latest version, and try it out at any
1618           time.
1619         </para>
1620       </answer>
1621       </qandaentry>
1622
1623       <qandaentry>
1624       <question id="I-wrote-some-code-I-would-like-to-submit">
1625         <para>
1626           I have written some code that I would like to submit to the Wine
1627           project. How do I go about doing this?
1628         </para>
1629       </question>
1630       <answer>
1631         <para>
1632           Patches are greatly appreciated and should be submitted to the
1633           wine-patches mailing list
1634           (<ulink url="http://www.winehq.com/dev.shtml#ml">http://www.winehq.com/dev.shtml#ml</ulink>). Also see this page for
1635           a description of what happens to submitted patches.
1636         </para>
1637       </answer>
1638       </qandaentry>
1639     </qandadiv>
1640
1641     <qandadiv id="Developing-programs-using-Wine-WineLib">
1642       <title>Developing programs using Wine/WineLib</title>
1643       <qandaentry>
1644       <question id="Can-I-use-Wine-to-port-Win32-sources-to-Unix">
1645         <para>Can I use Wine to port my Win32 sources to Unix?</para>
1646       </question>
1647       <answer>
1648         <para>
1649           That is the idea of Winelib. Right now you may still have some
1650           difficulties, but this is changing all the time. Read the
1651           <ulink url="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</ulink> for info.
1652
1653         </para>
1654       </answer>
1655       </qandaentry>
1656       <qandaentry>
1657       <question id="Will-MFC-work-with-Wine-What-do-I-need-to-do">
1658         <para>Will MFC work with Wine? What do I need to do?</para>
1659       </question>
1660       <answer>
1661         <para>
1662           Wine is not implementing an MFC replacement nor does it intend to.
1663           However it is possible (with a lot of work) to compile the MFC from
1664           source and thus produce an <filename>mfc42.dll.so</filename> library.
1665         </para>
1666         <para>
1667           Please refer to the
1668           <ulink url="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</ulink> for how to do this.
1669         </para>
1670       </answer>
1671       </qandaentry>
1672
1673       <qandaentry>
1674       <question id="Are-there-commercial-apps-ported-using-Wine">
1675         <para>
1676           Are there any commercial applications which have been ported
1677           using Wine?
1678         </para>
1679       </question>
1680       <answer>
1681         <para>
1682           A few examples of applications using Winelib:
1683         </para>
1684         <itemizedlist>
1685           <listitem>
1686           <para>
1687             Corel's WordPerfect Office Suite
1688           </para>
1689           </listitem>
1690           <listitem>
1691           <para>
1692             Ability Office
1693             (<ulink url="http://www.ability.com/linux/abilitylinux.php">http://www.ability.com/linux/abilitylinux.php</ulink>)
1694           </para>
1695           </listitem>
1696           <listitem>
1697           <para>
1698             IBM's Websphere
1699             (<ulink url="http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)
1700           </para>
1701           </listitem>
1702         </itemizedlist>
1703         <para>
1704           Many other important applications have already been ported. (we are
1705           speaking of several top 500 applications here)
1706         </para>
1707       </answer>
1708       </qandaentry>
1709
1710       <qandaentry>
1711       <question id="How-can-I-detect-Wine">
1712         <para>How can I detect Wine?</para>
1713       </question>
1714       <answer>
1715         <para>
1716           You really shouldn't want to do this. If there's a quirk in Wine
1717           you need to work around, it's much better to fix it in Wine (after
1718           all you're a developer, so you should be able to gather enough help
1719           and knowledge to fix it for real).
1720         </para>
1721       </answer>
1722       </qandaentry>
1723
1724
1725     </qandadiv>
1726
1727     <qandadiv id="Wine-HQ-issues">
1728       <title>Wine HQ issues</title>
1729       <qandaentry>
1730       <question id="Why-are-the-maillists-set-to-reply-to-author">
1731         <para>
1732           Why are the maillists set to reply to author, not to mailing list?
1733         </para>
1734       </question>
1735       <answer>
1736         <para>
1737           There are very valid reasons for doing so.
1738         </para>
1739       </answer>
1740       </qandaentry>
1741
1742       <qandaentry>
1743       <question id="How-to-unsubscribe-from-the-mailing-lists">
1744         <para>How to unsubscribe from the mailing lists?</para>
1745       </question>
1746       <answer>
1747         <para>
1748           Please see: <ulink url="http://www.winehq.org/development/#ml">http://www.winehq.org/development/#ml</ulink>
1749         </para>
1750       </answer>
1751       </qandaentry>
1752
1753     </qandadiv>
1754
1755   </qandaset>
1756
1757 <!-- Keep this comment at the end of the file
1758 Local variables:
1759 mode: sgml
1760 sgml-parent-document:("wine-devel.sgml" "book" "part" "chapter" "")
1761 End:
1762 -->