documentation/faq.sgml

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