faq.sgml 69.9 KB
Newer Older
1
<!-- *** Wine FAQ *** -->
2 3
  <title>Wine FAQ</title>

4 5 6 7 8 9 10 11
  <qandaset>
    <qandadiv id="About-this-FAQ"><title>About this FAQ</title>
      <qandaentry>
      <question id="Who-maintains-this-FAQ">
        <para>Who maintains this FAQ ?</para>
      </question>
      <answer>
        <para>Dave Gardner maintained it from 1995-1998.</para>
Tom Wickline's avatar
Tom Wickline committed
12 13
        <para>Douglas Ridgway took it over in 1999.</para>
        <para>Andreas Mohr converted it to FAQ-O-Matic in 2000.</para>
Tom Wickline's avatar
Tom Wickline committed
14
        <para>Dimitrie O. Paun, Keith Matthews and Tom Wickline (in alphabetical order) reorganized it in 2002.</para>
15 16 17 18 19 20
        <para>For suggestions/additions/complaints regarding this FAQ, please send an email to
        <ulink url="mailto:wine-faq@winehq.org">wine-faq@winehq.org</ulink></para>
      </answer>
      </qandaentry>
      <qandaentry>
      <question id="What-is-the-copyright-on-the-FAQ-And">
Tom Wickline's avatar
Tom Wickline committed
21
        <para>What is the copyright of this FAQ? And how may I use it?</para>
22 23 24 25 26 27 28 29 30 31 32 33
      </question>
      <answer>
        <para>The original Wine FAQ, which this FAQ was based on, was copyright &copy; 1995-1998 David Gardner.</para>
        <para>It may be reproduced and modified under the same terms as Wine itself.</para>
      </answer>
      </qandaentry>
    </qandadiv>
    <qandadiv id="General-Questions-about-Wine">
      <title>General Questions about Wine</title>
      <qandaentry>

      <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 36 37 38
      </question>
      <answer>
        <para>
          Wine is a program which allows the operation of DOS and MS
39
          Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems such as Linux. 
40
          It consists of a program loader, which loads and executes a Windows
41 42
          binary, and a set of libraries that implements Windows API calls
          using their UNIX or X11 equivalents. The libraries may also be used
43 44 45
          for porting Win32 code into native UNIX executables, often
          without many changes in the source. Wine is free software, 
          and its license (contained in the file LICENSE
46
          in each distribution) is the LGPL.
47 48 49 50 51 52
        </para>
      </answer>
      </qandaentry>

     <qandaentry>
      <question id="Is-Wine-an-emulator">
53
        <para>Does Wine emulate a full computer?</para>
54 55 56
      </question>
      <answer>
        <para>
57 58
          No, as the name says, Wine Is Not a (CPU) Emulator. Wine just
          provides the Windows API. This means that you will need an
59 60 61 62
          x86-compatible processor to run an x86 Windows application, for instance from Intel or AMD. The
          advantage is that, unlike solutions that rely on CPU emulation, Wine
          runs applications at full speed. Sometimes a program run under
	  Wine will be slower than when run on a copy of Microsoft Windows, but
Tom Wickline's avatar
Tom Wickline committed
63
	  this is more due to the fact that Microsoft has heavily optimized parts of their
64 65
	  code, whereas mostly Wine is not well optimized (yet). Occasionally, an app
	  may run faster under Wine than on Windows. Most apps run at roughly the same speed.
66 67
       </para>
      </answer>
68
      </qandaentry>
69 70 71 72 73 74 75

      <qandaentry>
      <question id="Are-here-any-alternatives-to-Wine">
        <para>Are there any alternatives to Wine?</para>
      </question>
      <answer>
        <para>
76 77 78 79 80
          Yes, there are. You can use <ulink url="http://www.vmware.com">VMWare</ulink> to run a Windows installation inside a virtual machine,
	  or use <ulink url="http://www.win4lin.com">Win4Lin</ulink>
	  to run a specially adapted Windows version on Linux.
	  Both solutions cost money for both the software itself
	  and a Windows license.
81 82 83 84 85
       </para>
       <para>
         Note that, like Wine, they can only use the hardware platform that
         the target programs were originally compiled for (see below).
       </para>
Tom Wickline's avatar
Tom Wickline committed
86

87 88 89 90 91 92 93 94 95 96
      </answer>
      </qandaentry>
       
      <qandaentry>
      <question id="Difference-between-Wine-and-emulators">
        <para>What is the difference between Wine and x86 hardware emulators?</para>
      </question>
      <answer>
        <para>
          There are two free x86 hardware emulators:
97 98
          <ulink url="http://bochs.sourceforge.net">Bochs</ulink>, and
          <ulink url="http://savannah.nongnu.org/projects/plex86">Plex86</ulink>.
99
       </para>
100 101

       <para>
102
          Plex86 is the open-source free-software alternative for VMWare,
103 104 105 106 107 108 109 110
	  VirtualPC, and other IA-32 on IA-32 "Virtual PC products." It
          can only run on the IA-32 architecture.
       </para>

       <para>
          Bochs is a highly portable open source IA-32 (x86) PC emulator 
          written in C++, that runs on most popular platforms. It includes emulation
          of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently, 
111
          Bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
112 113 114 115 116
          of running most Operating Systems inside the emulation including Linux, 
          Windows® 95, DOS, and recently Windows® NT 4.
       </para>

       <para>
117 118
          Both are licensed under the GPL. Bochs is older than Plex86, seems to be
          easier to install, but Plex86 will run faster because Plex86 uses a just in
119 120 121 122 123
          time binary compiler.
       </para>
       <para>
          The drawback of all emulators is that you need a version
          of Windows in order to run Windows, and that they all have an
124 125 126
          impact on performance. Wine also gives much better desktop integration - for
	  instance, programs use your standard window manager, system tray icons will
	  appear in your tray area (if you have one), and you can run programs direct from the
Tom Wickline's avatar
Tom Wickline committed
127
	  command line as well as menus. The clipboard also works seamlessly at this time.
128 129
       </para>

130 131 132
      </answer>
      </qandaentry>

133 134 135 136 137 138 139 140 141 142 143 144 145 146
      <qandaentry>
      <question id="Integrate-an-x86-emulator">
        <para>When will Wine integrate an x86 CPU emulator so we can
          run Windows applications on non-x86 machines?</para>
      </question>
      <answer>
        <para>
          The short answer is 'probably never'. Remember, Wine Is Not a
          (CPU) Emulator. The long answer is that we probably don't want or
          need to integrate one in the traditional sense.
        </para>
        <para>
          Integrating a CPU emulator in Wine would be extremely hard,
          due to the large number of Windows APIs and the complex
Tom Wickline's avatar
Tom Wickline committed
147
          data types they exchange. It is not uncommon for a Windows API to
148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163
          take three or more pointers to structures composed of many fields,
          including pointers to other complex structures. For each of these
          we would need a conversion routine to deal with the byte order and
          alignment issues. Furthermore, Windows also contains many callback
          mechanisms that constitute as many extra places where we would have
          to handle these conversion issues. Wine already has to deal with
          16 vs. 32 bit APIs and Ansi vs. Unicode APIs which both
          introduce significant complexity. Adding support for a CPU emulator
          inside Wine would introduce at least double that complexity and
          only serve to slow down the development of Wine.
        </para>
        <para>
          Fortunately another solution exists to run Windows applications
          on non-x86 platforms: run both Wine and the application inside the
          CPU emulator. As long as the emulator provides a standard Unix
          environment, Wine should only need minimal modifications. What
Francois Gouget's avatar
Francois Gouget committed
164
          performance you lose due to Wine running inside the emulator
165 166 167 168 169 170 171 172 173 174 175
          rather than natively, you gain in complexity inside of Wine.
          Furthermore, if the emulator is fast enough to run Windows
          applications, Photoshop for instance, then it should be fast enough
          to run that same Windows application plus Wine.
        </para>
        <para>
          Two projects have started along those lines: <ulink
          url="http://fabrice.bellard.free.fr/qemu/">QEMU</>, an
          open-source project, and <ulink
          url="http://www.transitives.com/tech_overview.htm">Dynamite</>,
          a commercial CPU emulator environment from
Tom Wickline's avatar
Tom Wickline committed
176
          <ulink url="http://www.transitives.com/">Transitives Technologies</>.
177 178 179 180 181
        </para>

      </answer>
      </qandaentry>

182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228
      <qandaentry>
      <question id="Why-would-anyone-want-Wine-Windows-suck">
        <para>Why would anyone want Wine? Doesn't Windows suck?</para>
      </question>
      <answer>
        <para>
          First Wine is not about running Windows but about running Windows 
          applications.
        </para>
        <para>
          So if all your computing needs are fulfilled by native Unix 
          applications, then you do not need Wine and should not be using
          it. However, if you depend on one or more of the tens of 
          thousands of Windows applications, then Wine is the best way to
          use it without giving up on Unix. Let's look at the alternatives
          to see why:
        </para>
        <para>
          The most obvious alternative is to dual-boot. This is the solution
          that provides the best compatibility. However it requires that you
          acquire a Windows license and then dedicate a good chunk of your 
          hard-drive to Windows. But the worst is yet to come. Each time you
          will want to use that application you will have to reboot to 
          Windows. This is especially significant if external factors dictate
          when you must use this application (e.g. credit card to process, 
          email to retrieve from a Lotus Notes server). Then you will find
          yourself forced to close all your Linux applications just to run
          that one Windows application. You may quickly get tired of this, or
          will find that such a situation is impossible to justify in a 
          business environment.
        </para>
        <para>
          The next solution is to install virtual machine emulation software
          such as VMWare, Win4Lin or Plex86. Then you can use windows 
          applications without suffering such a big disruption. But it still
          requires that you acquire a Windows license and dedicate as much 
          disk space to Windows. Furthermore you will pay for the added 
          convenience: if using VMWare or Win4Lin you have to buy another 
          license, and more importantly you now have to dedicate a good chunk
          of your computer's memory to the virtual machine. Performance will
          take a significant hit too.
        </para>
        <para>
          Using Wine lets you avoid all of that overhead: Windows license,
          hard-drive space required by Windows, memory and performance hit 
          taken by emulated virtual machines. Now you can start your Windows
          application straight from your regular desktop environment, place
229 230
          that application's window side by side with native applications,
          copy/paste from one to the other, and run it all at full speed.
231 232
        </para>
        <para>
Tom Wickline's avatar
Tom Wickline committed
233
          It is also a pretty vital part of migrating a large organization,
234 235
          you can't change a 5000 desktop setup overnight without a lot of risk.
       </para>
Tom Wickline's avatar
Tom Wickline committed
236

237 238 239
      </answer>
      </qandaentry>

240 241 242 243 244 245 246 247 248 249 250 251 252 253 254
      <qandaentry>
      <question id="Use-Windows-driver-with-Wine">
        <para>Can I use Wine to make the Windows driver for my network card /
          graphics card / scanner / etc. work on Unix?</para>
      </question>
      <answer>
        <para>
          The goal of Wine is to make it possible to run Windows applications
          on Unix, not Windows drivers or VxDs.
        </para>
        <para>
          Drivers and Windows applications belong to different worlds.
          Applications run in user mode and use the APIs provided by
          the kernel and the other user mode dlls. In contrast, drivers
          are loaded in the Windows kernel, i.e. in ring 0 instead of ring
Tom Wickline's avatar
Tom Wickline committed
255
          3, drivers have to deal with specific memory management issues, and use
256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273
          instructions not available to regular applications. This means
          they would not be able to run in Wine since Wine runs entirely
          in user mode. Rather you would have to modify the Linux kernel.
          But in addition, drivers use a completely different API from
          regular Windows applications. So the work performed on Wine would
          not even be of any use for such a project. In other words, making
          it possible to use Windows drivers or VxDs on Unix would be a
          completely separate project.
        </para>
        <para>
          However, if you want to reuse Windows drivers on a non-Microsoft
          operating system we recommend that you have a look at
          <ulink url="http://www.reactos.com/">ReactOS</>.
        </para>

      </answer>
      </qandaentry>

274 275 276 277 278 279 280 281 282 283 284
      <qandaentry>
      <question id="Which-one-of-the-different-Wine-packages">
        <para>Which one of the different Wine packages out there is good for me?</para>
      </question>
      <answer>
        <para>
          Currently there is a broad selection of different Wine packages/versions:
        </para>
        <variablelist>

	  <varlistentry>
285
           <term><ulink url="http://www.winehq.org">Wine</ulink></term>
286 287
           <listitem>
           <para>
Ivan Leo Murray-Smith's avatar
Ivan Leo Murray-Smith committed
288 289 290
              This is the "standard" distribution of Wine. Its license is
              the LGPL, it can be downloaded for free. Both source code and binaries
              are available in the download section of the site.
291 292 293
            </para>
           </listitem>
          </varlistentry>
Tom Wickline's avatar
Tom Wickline committed
294

295
	  <varlistentry>
Tom Wickline's avatar
Tom Wickline committed
296
          <term><ulink url="http://www.codeweavers.com/site/products/cxoffice/">CodeWeavers' CrossOver Office</ulink></term>
297 298 299
          <listitem>
            <para>
              Wine version with special packaging to make sure almost all 
Tom Wickline's avatar
Tom Wickline committed
300 301
              important Office type programs work pretty well. Costs $74.95 
              for the Pro version and $39.95 for the Standard version.
302
              Seems to be well worth it so far according to some comments. 
303
              (note: you're supporting a company actively contributing to Wine
Tom Wickline's avatar
Tom Wickline committed
304
              if you decide to buy CrossOver.)
305 306 307
            </para>
          </listitem>
          </varlistentry>
Tom Wickline's avatar
Tom Wickline committed
308 309
          
          <varlistentry>
Tom Wickline's avatar
Tom Wickline committed
310
          <term><ulink url="http://www.codeweavers.com/site/products/cxserver/">CodeWeavers' CrossOver Office Server Edition</ulink></term>
Tom Wickline's avatar
Tom Wickline committed
311 312 313 314 315 316 317
          <listitem>
            <para>
             Allows you to run your favorite Windows productivity applications in 
             a distributed thin-client environment under Linux. Server Edition is 
             also a great addition to Solaris environments, since there built-in 
             support for Solaris desktops makes running Windows applications a 
             possibility on Sun workstations as well. For pricing just follow this link: 
Tom Wickline's avatar
Tom Wickline committed
318
          <ulink url="http://www.codeweavers.com/site/products/pricing/">CrossOver Office Server Edition Pricing</ulink>
Tom Wickline's avatar
Tom Wickline committed
319 320 321 322
            </para>
          </listitem>
          </varlistentry>          

323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341
        </variablelist>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Whats-the-history-of-Wine">
        <para>What's the history of Wine?</para>
      </question>
      <answer>
        <para>
          The Wine project started in 1993 as a way to support running Windows 3.1
          programs on Linux. Bob Amstadt was the original coordinator, but turned
          it over fairly early on to Alexandre Julliard, who has run it ever 
          since. A <ulink url="news:comp.emulators.ms-windows.wine">newsgroup</ulink>
          was created in July 1994. Over the years, ports for
          other Unixes have been added, along with support for Win32 as Win32 
          applications became popular.
        </para>
        <para>
342 343
          For more information, see <ulink url="http://www.winehq.com/site/history">
          http://www.winehq.com/site/history</ulink>
344 345 346 347 348 349 350 351 352 353 354 355 356 357
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="What-is-the-current-version-of-Wine">
        <para>What is the current version of Wine?</para>
      </question>
      <answer>
        <para>
          A new version of Wine is distributed about every month. You will be 
          able to keep up on all the latest releases by reading the newsgroup
          <ulink url="news:comp.emulators.ms-windows.wine">
          comp.emulators.ms-windows.wine</ulink>, or by visiting the
358
          <ulink url="http://www.winehq.org">Wine HQ homepage</ulink>. When
359
          downloading Wine from your FTP site of choice (see
Tom Wickline's avatar
Tom Wickline committed
360
          <ulink url="http://www.winehq.org/site/download">the Download page</ulink>
361 362
          for some of these choices), you can make sure that you are getting 
          the latest version by watching the version numbers in the distribution
363 364
          file name. For instance, the distribution released on August 13, 2004
          was called Wine-20040813.tar.gz. Patch files are also available. If
365 366
          you are current to the previous version, you can download and apply 
          just the current patch file rather than the entire new distribution.
Tom Wickline's avatar
Tom Wickline committed
367 368
          The patch file names follow the same conventions as the monthly 
          distribution. <ulink url="http://www.winehq.org/site/cvs">
369 370 371 372 373 374 375 376 377 378 379
          Read-only CVS</ulink> access is also available.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="What-is-the-current-Status-of-Wine">
        <para>What is the current Status of Wine?</para>
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
380 381
          As of mid 2004, Wine consists of about 1.6 million lines of code,
          written by more than 600 developers from dozens of countries around
382 383 384 385 386 387
          the world. Wine is in active use by an estimated 100K people. Wine
          implements more than 90% of the calls in popular Windows 
          specifications such as ECMA-234 and Open32.
        </para>
        <para>
          You may also want to look at the
Tom Wickline's avatar
Tom Wickline committed
388
          <ulink url="http://www.winehq.org/site/status">
389 390 391 392 393 394 395 396 397 398 399 400 401
          Status page</ulink> for a global view on Wine's implementation progress.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="When-will-Wine-be-finished">
        <para>When will Wine be finished?</para>
      </question>
      <answer>
        <para>
          Large software projects are never finished, only released. In any
          case Wine is chasing a moving target since every new release of 
402
          Windows contains new API calls or variations on the existing ones.
403 404 405 406 407 408
        </para>
        <para>
          Because Wine is being developed by volunteers, it is difficult to
          predict when it will be ready for general release. But due to the
          much increased interest by companies in porting apps via Wine, Wine
          development is constantly getting more and more active. Right now
409
          we are working on releasing Wine 0.9 Real Soon Now(tm).
410 411 412 413 414 415
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Who-is-responsible-for-Wine">
416
        <para>Who is responsible for Wine?</para>
417 418 419 420
      </question>
      <answer>
        <para>
          Wine is available thanks to the work of many people. Please see the
Tom Wickline's avatar
Tom Wickline committed
421
          <ulink url="http://source.winehq.org/source/AUTHORS">AUTHORS</ulink>
422
          file in the distribution for the complete list. Some companies that
423
          are or have been involved with Wine development are CodeWeavers,
424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441
          TransGaming, Corel, and Macadamian.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="What-undocumented-APIs-are-not-understood">
        <para>What undocumented APIs / interfaces are not understood? Would
              seeing Microsoft source help?
        </para>
      </question>
      <answer>
        <para>
          The best would be if the Windows API was fully documented, so Wine
          could be a perfect "clean-room" implementation. Seeing the source
          code might make it harder to prove that no copyright violations have
          taken place. That said, the documentation is often bad, nonexistent,
          and even misleading where it exists, so a fair amount of reverse
442
          engineering has been necessary, particularly in the shell (Explorer)
443 444 445 446 447 448
          interface. The biggest problem facing Wine though is simply lack of
	  manpower. At one point, over 5000 people were working on Windows 2000.
	  While Wine doesn't need to replicate all of Windows (we only cover the
	  parts needed to make Windows programs work), that's still nearly 10 times
	  more people working simply on one release than have <emphasis>ever</emphasis>
	  worked on Wine, in the history of the project.
449 450 451 452 453 454 455 456 457 458
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Will-there-be-a-Windows-version-of-Wine">
        <para>Will there be a Windows version of Wine?</para>
      </question>
      <answer>
        <para>
459 460
          Some people are working on getting Wine code to compile on Windows
          using one of the following projects as a basis:
461 462 463 464
        </para>
        <itemizedlist spacing="compact">
          <listitem> 
            <para>
465
              Cygwin
466
              (<ulink url="http://www.cygwin.com/">http://www.cygwin.com</ulink>)
467 468 469 470
            </para>
          </listitem>
          <listitem>
            <para>
471
              MinGW
472
              (<ulink url="http://www.mingw.org/">http://www.mingw.org</ulink>)
473 474 475 476 477
            </para>
          </listitem>
          <listitem>
            <para>
              ReactOS
Tom Wickline's avatar
Tom Wickline committed
478
              (<ulink url="http://www.reactos.com/">http://www.reactos.com</ulink>)
479 480 481 482 483
            </para>
          </listitem>
        </itemizedlist>
        <para>
          There's some progress, so a Wine version that's usable on Windows
484
          might be available at some time in the future.
485
        </para>
486 487 488
        <para>
          Part of the rationale for these projects is to find out areas where
          Wine portability is lacking. This is especially true of the
489
          ReactOS project which is a reimplementation of the Windows kernel
490 491 492 493 494 495 496 497
          and should thus be able to reuse most of Wine dlls.
        </para>
        <para>
          Another reason for pursuing these projects is to be able to
          replace a single Windows dll with its Wine counterpart. Besides
          being a good test for the Wine dll, this lets us detect cases where
          we made incorrect assumptions about how the dlls interact.
        </para>
498 499
      </answer>
      </qandaentry>
500

501 502 503 504 505 506 507 508 509 510 511 512 513 514
      <qandaentry>
      <question id="Can-I-use-native-drivers">
        <para>Can I use Windows printer drivers in Wine?</para>
      </question>
      <answer>
        <para>
          Native printer drivers are not supported. At one time Wine supported 16bit 
          native drivers but that was long ago. Wine uses the printers (and other 
          devices) installed in your operating system. For the most part if you don't 
          have the device installed on your OS then wine can't use it. 
        </para>
      </answer>
      </qandaentry>

515 516 517 518 519 520 521 522 523 524 525 526
    </qandadiv>
    <qandadiv id="What-do-I-need-in-order-to-use-Wine">
      <title>What do I need in order to use Wine?</title>
      <qandaentry>
      <question id="Under-what-platforms-will-Wine-run">
        <para>
          Under what hardware platform(s) and operating system(s) will
          Wine(Lib) run?
        </para>
      </question>
      <answer>
        <para>
527 528 529 530 531 532 533 534 535 536 537 538
          Wine is being developed specifically to run on the <emphasis>Intel
          x86</emphasis> class of CPUs under certain UNIXes that run on this
          platform. Winelib however is capable of porting the Windows
          applications <emphasis>source code</emphasis> to other platforms
          also, not only x86.
        </para>
        <para>
          Thus running Windows binaries on other platforms (e.g. Mac OS X on
          PowerPC) using just Wine is <emphasis>not</emphasis> possible. You
          would have to either run Wine in an emulated x86 environment or
          take the Windows application source code and recompile it using
          Winelib.
539 540
	</para>
	<para>
541 542
	  These are the platforms supported by Wine.
	  Winelib support for other platforms keeps evolving,
543 544
	  so it's not specifically listed here.
	</para>
545
        <para>
546
          NetBSD, OpenBSD, UnixWare, and SCO OpenServer 5 worked at one time,
547
          but Wine now requires kernel-level threads which are not currently 
548
          available (or understood by the Wine team) on those platforms.
549 550 551 552 553 554
        </para>
        <para>
          The Wine development team hopes to attract the interest of other
          commercial UNIX and UNIX clone vendors as well.
        </para>
        <para>
555 556 557 558 559 560 561 562 563 564 565 566
          BeOS: porting efforts (BeWine) used to be pretty strong, but BeOS
          has severe limitations in Unix call support. The demise of Be
          further hampered the project though it might come back one day on
          one of the open BeOS projects. In any case a functional port seems
          unlikely to ever happen at this stage.
        </para>
        <para>
          Mac OS X / Darwin: The <ulink
          url="http://darwine.sourceforge.net/project.html">Darwine</> is
          currently working on porting Wine to the Darwin/x86 platform. Their
          goal is to eventually make it possible to run x86 Windows
          applications on Darwin/PPC and then Mac OS X by using Bochs.
567 568
        </para>
        <para>
569 570 571
          FreeBSD: This port is well maintained and should work with
          limitations in specific areas (mainly missing device/hardware
          support).
572 573
        </para>
        <para>
574 575
          Linux/x86: Works, and as the most popular platform for both
          developers and users, it is the best supported platform of all.
576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="What-minimum-CPU-must-I-have">
        <para>
          What minimum CPU must I have in my computer to be able to run Wine 
          and MS Windows applications smoothly?
        </para>
      </question>
      <answer>
        <para>
          We need to differentiate between Wine and Winelib here.
        </para>
        <para>
          Wine won't run on any x86 CPU less than an 80386 due to address
593
          management limitations.
594 595 596 597 598 599 600 601 602
        </para>
        <para>
          It is known to also work in the 80486 and upwards compatible CPUs.
          The basic test is, if you can run X11 now, you should be able to run
          Wine and MS Windows applications under it.
        </para>
        <para>
          As always, the faster your CPU, the better. Having a math coprocessor
          is unimportant. However, having a graphics accelerated video card
603
          supported by X will help greatly.
604 605 606 607
        </para>
        <para>
          Depending on your application you may find that faster speeds are
          required for sensible use. We can't give specific advice on that due
608 609 610
          to the vast range of applications out there. However the rule of
          thumb is that if your application runs fine on Windows, it should
          run fine on the same platform in Wine.
611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-much-disk-space-will-Wine-take">
        <para>
         How much disk space will the Wine source code and binaries take on my
         hard drive?
        </para>
      </question>
      <answer>
        <para>
          You need approximately 250 megabytes of free hard drive space to
          store and compile the source code. Wine also needs about 18 megs in
          your /tmp directory. And about 50 MB are needed to do a make install.
        </para>
628 629 630 631
        <para>
          Binary packages, especially those not containing debug information,
          have much lower disk space requirements, usually in the 20MB range.
        </para>
632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-much-RAM-do-I-need">
        <para>
          How much RAM do I need to have on my UNIX system to be able to run 
          Wine and MS Windows applications smoothly?
        </para>
      </question>
      <answer>
        <para>
          If you can run X smoothly on your UNIX system now, you should be 
          able to run Wine and MS Windows applications just fine too, depending
          on how memory hungry the application is.
        </para>
        <para>
Tom Wickline's avatar
Tom Wickline committed
649 650 651 652 653
          Wine's memory requirements will depend on the application or game
          that you choose to run. You will need to meet the minimum requirements for
          the application as well as the overhead of your underlying OS.
          You may want to check with the vendor of the application for its 
          suggested memory requirements.
654 655 656 657 658 659 660 661 662 663 664
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-long-does-Wine-take-to-build">
        <para>How long does Wine take to build</para>
      </question>
      <answer>
        <para>
          Wine is getting to be quite large, and building from scratch takes a
Tom Wickline's avatar
Tom Wickline committed
665 666 667 668
          lot of processing. As of May 2004, compile times were around 10
          minutes on a Athlon 2000 with 512 MB of RAM and 20 minutes on a Athlon 
          1200 with 640 MB of RAM. If you have a CVS copy of wine, you may not need
          to rebuild every thing each update.
669 670 671 672 673 674 675 676 677 678 679 680 681
        </para>
      </answer>
      </qandaentry>
      <qandaentry>
      <question id="I-have-a-Drivespaced-partition">
        <para>
          I have a Drivespaced, Doublespaced or Stackered DOS partition. Can 
          Wine run MS Windows binaries located in such a partition?
        </para>
      </question>
      <answer>
        <para>
          Yes, but only if the operating system supports mounting those types
682 683
          of drives. There is a Linux file system driver called dmsdos that
          will allow read/write access to Doublespaced and Drivespace 1.0
684 685 686 687 688
          drives. More specifically, it supports mounting DOS 6.0 and 6.2 
          Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced 
          compressed partitions (read and write access works fine, but write 
          access is slow). It can be found at 
          <ulink url="ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/">
689
          ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>
690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Do-I-need-to-have-a-DOS-partition">
        <para>Do I need to have a DOS partition on my system to use Wine?</para>
      </question>
      <answer>
        <para>
          You do not need a licensed and installed copy of DOS or MS Windows to
          install, configure and run Wine. However, Wine has to be able to 
          'see' an MS Windows binary (i.e. application) if it is to run it.
        </para>
      </answer>
      </qandaentry>
Tom Wickline's avatar
Tom Wickline committed
706

707 708 709 710 711 712 713 714 715
      <qandaentry>
      <question id="If-Wine-completely-replaces-MS-Windows">
        <para>
          If Wine completely replaces MS Windows, will it duplicate all of the
          functions of MS Windows?
        </para>
      </question>
      <answer>
        <para>
716 717 718 719 720
          Wine's goal is to make it possible to run Windows applications on
          Unix. To this end it will provide replacements for just those
          DLLs and APIs that are needed by these Windows applications.
          This means that Wine will not provide replacements for DLLs that
          are not shipped with Windows or are always shipped with Windows
Tom Wickline's avatar
Tom Wickline committed
721
          application (e.g. the Visual Basic run time). This also
722 723 724 725 726 727 728 729 730
          means that implementing an API that no application ever uses is not
          a priority. Similarly, until there are applications out there that
          use the Win64 API, it will not be a priority. That being said,
          we will certainly try to keep our options open and to improve our API
          coverage as we can.
        </para>
        <para>
          Also Wine is not an operating system, so that writing device
          drivers is not part of Wine's goals. However if you are interested
Tom Wickline's avatar
Tom Wickline committed
731 732 733
          in device drivers, the <ulink url="http://www.kernel.org/">Linux</ulink>,
          <ulink url="http://www.freebsd.org/">FreeBSD</ulink> and
          <ulink url="http://www.reactos.com/">ReactOS</ulink> kernel developers
734 735 736 737 738 739 740 741 742 743
          would certainly appreciate your contribution.
        </para>
        <para>
          Similarly Wine does not try to be a desktop environment so
          providing applets such as a calculator, a file manager or even
          window manager that look like Windows, are low priority or would
          even best be done as a separate project. Such projects would also
          to a large extant be redundant with other open-source projects.
          Again, there are projects that would certainly appreciate your
          contributions in this areas, such as the
Tom Wickline's avatar
Tom Wickline committed
744 745
          <ulink url="http://www.gnome.org/">Gnome</ulink> or
          <ulink url="http://www.kde.org/">KDE</ulink> desktop environments. You
746 747
          will get the added benefit that your contribution will then be
          usable by everyone, not just by Wine users.
748 749 750 751 752
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
753
      <question id="Will-I-install-on-any-UNIX-file-system">
754 755 756 757 758 759 760 761 762 763 764 765 766
        <para> 
          Will I be able to install MS Windows applications in any flavor of a
          UNIX file system?
        </para>
      </question>
      <answer>
        <para>
          Wine is written to be file system independent, so MS Windows 
          applications will install and run under virtually any file system
          supported by your brand of UNIX.
        </para>
      </answer>
      </qandaentry>
Tom Wickline's avatar
Tom Wickline committed
767

768 769
      <qandaentry>
      <question id="Will-Wine-run-only-under-X">
770
        <para>Will Wine run only under X, or can it run in character mode?</para>
771 772 773
      </question>
      <answer>
        <para>
774
          Most of Wine's development effort is geared towards MS Windows' GUI,
775
          but some limited support for character mode has appeared, by setting
776
          <parameter>GraphicsDriver=ttydrv</parameter> in ~/.wine/config's
777 778 779 780 781
          <parameter>[wine]</parameter> section.
        </para>
        <para>
          Wine's infrastructure is already somewhat prepared for supporting
          other graphics drivers than x11drv, but no real "alternative" 
782
          graphics driver has been developed yet.
783 784 785
        </para>
      </answer>
      </qandaentry>
Tom Wickline's avatar
Tom Wickline committed
786

787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805
      <qandaentry>
      <question id="Will-Wine-run-under-any-X-window-manager">
        <para>Will Wine run under any X window manager? Does it require a window manager at all?</para>
      </question>
      <answer>
        <para>
          Wine is window manager independent, so the X window manager you
          choose to run has (almost) no bearing on your ability to run MS
          Windows programs under Wine. Wine uses standard X libraries, so no
          additional ones are needed. Wine has its own window management,
          which acts like MS Windows. It can be turned off to use the native
          window manager by modifying Managed or Desktop settings as described
          in <command>man wine.conf</command>.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Will-32-bit-applications-run-under-Wine">
Tom Wickline's avatar
Tom Wickline committed
806
        <para>Will 32-bit Windows 95/98/ME/NT/2000/XP applications run under Wine?</para>
807 808 809
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
810
          Yes, 32-bit programs are now well supported.
811 812 813
        </para>
      </answer>
      </qandaentry>
Tom Wickline's avatar
Tom Wickline committed
814

815
    </qandadiv>
816
    <qandadiv id="FAQ-Getting-Wine">
817 818 819 820 821 822 823
      <title>Getting Wine</title>
      <qandaentry>
      <question id="Where-can-I-get-Wine">
        <para>Where can I get Wine?</para>
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
824
          Because of lags created by using a mirror, word of the latest release
825 826 827 828 829
          may reach you before the release is actually available at the ftp
          sites listed here. The sources are available from the following
          locations:
        </para>
        <itemizedlist>
Ivan Leo Murray-Smith's avatar
Ivan Leo Murray-Smith committed
830 831 832 833 834 835 836
          <listitem>
            <para>
              <ulink url="http://sourceforge.net/project/showfiles.php?group_id=6241&amp;package_id=77449">
               http://sourceforge.net/project/showfiles.php?group_id=6241&amp;package_id=77449
              </ulink>
            </para>
          </listitem>
837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870
          <listitem>
            <para>
              <ulink url="http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/">
               http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/
              </ulink>
            </para>
          </listitem>
          <listitem>
            <para>
              <ulink url="ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/">
              ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/ 
              </ulink>
            </para>
          </listitem>

          <listitem>
            <para>
              <ulink url="ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/">
              ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/ 
              </ulink>
            </para>
          </listitem>

          <listitem>
            <para>
              <ulink url="ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/">
              ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/ 
              </ulink>
            </para>
          </listitem>

        </itemizedlist>
        <para>
          It should also be available from any other site that mirrors 
Tom Wickline's avatar
Tom Wickline committed
871 872
          ibiblio.org, see <ulink url="http://www.ibiblio.org/pub/Linux/MIRRORS.html">http://www.ibiblio.org/pub/Linux/MIRRORS.html</>.
          Some of these sites may archive previous versions of Wine as well as the
873 874 875 876 877 878 879 880 881
          current one. To determine which is the latest one, look at the 
          distribution file name, which will take the form 
          Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution
          file name with the numbers for year, month and date, respectively.
          The latest one is the one to get.
        </para>
        <para>
          Wine binary packages are available for several OS'es and 
          distributions. See 
Tom Wickline's avatar
Tom Wickline committed
882
          <ulink url="http://www.winehq.org/site/download">
883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902
          the download page</ulink> for the most recent list.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Is-there-a-CVS-tree">
        <para>Is there a CVS tree?</para>
      </question>
      <answer>
        <para>
          Current Wine sources are also available via anonymous client/server
          CVS. You will need CVS 1.9 or above. If you are coming from behind a
          firewall, you will either need a hole in the firewall for the CVS
          port (2401) or use SOCKS.
        </para>
        <para>
          To login to the CVS tree, do
        </para>
        <screen>
903
export CVSROOT=:pserver:cvs@cvs.winehq.org/home/wine
904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925
cvs login
        </screen>
        <para>
          Use "cvs" as the password (without the quotes). Note that 
          <filename>/home/wine</filename> is a path on the server, not on your
          machine. To check out the entire Wine source tree (which may be 
          slow), use
        </para>
        <screen>
cvs -z 3 checkout wine 
        </screen>
        <para>
          or if you just want a subtree, or individual file, you can do that 
          too with
        </para>
        <screen>
cvs -z 3 checkout wine/ANNOUNCE 
        </screen>
        <para>
          Be aware, though, that getting the entire Wine source tree via CVS
          is pretty slow, especially compared to getting Wine from an FTP 
          mirror near you. For a CVS mirror list, see 
926 927
          <ulink url="http://www.winehq.org/site/cvs#cvsservers">
          http://www.winehq.org/site/cvs#cvsservers</ulink>
928 929 930
        </para>
        <para>
          Patch files are also available, so that you don't have to download,
Tom Wickline's avatar
Tom Wickline committed
931
          install, and configure the entire distribution each month if you are
932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971
          current to the previous release. Patch file release names follow the
          same numbering convention as do the general releases, and take the 
          form
        </para>
        <para>
          Wine-YYYYMMDD.diff.gz  
        </para>
        <para>
          Patch files are available from the same sites that distribute the
          full release. To upgrade to a new release by using a patch file,
          first cd to the top-level directory of the release (the one
          containing the README file), then do a "make clean", and patch the
          release with
        </para>
        <screen>
gunzip -c patch-file | patch -p1 
        </screen>
        <para>
          where patch-file is the name of the patch file something like
          Wine-YYYYMMDD.diff.gz. You can then re-run ./configure, and then run
          make depend && make
        </para>
        <para>
          If you are mirroring the Wine distribution from the tsx-11 site and
          wish to be listed here in this FAQ, please add it to the 
          "things to go into the documentation" area.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Can-I-get-Wine-using-cvsup">
        <para>Can I get Wine using cvsup?</para>
      </question>
      <answer>
        <para>
          The CVS mirrors don't offer cvsup support yet, but the main server
          does. Use a <filename>wine.sup</filename> file of:
        </para>
        <screen>
972
*default host=cvs.winehq.org
973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988
*default base=/cvs
*default prefix=/cvs/wine
*default release=wine
*default delete 

# If your network link is a T1 or faster, comment out the following line.
#*default compress 

*default use-rel-suffix 
wine 
        </screen>
     </answer>
     </qandaentry>
    </qandadiv>

    <qandadiv id="Installing-And-Configuring-Wine">
989
      <title>Installing and Configuring Wine</title>
990 991 992 993 994 995
      <qandaentry>
      <question id="How-do-I-compile-the-Wine-source-code">
        <para>How do I compile the Wine distribution source code?</para>
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
996
          See the README (<ulink url="http://source.winehq.org/source/README">http://source.winehq.org/source/README</ulink>) for instructions.
997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013
          Additionally, you may want to set the <parameter>TMPDIR</parameter>
          environment variable <command>TMPDIR=~/tmp</command> or
          <command>TMPDIR=/tmp</command> (if you are root).
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-do-I-install-Windows-in-Wine">
        <para>How do I install Windows in Wine under Linux?</para>
      </question>
      <answer>
        <para>
          Simple answer: you CAN'T. Windows demands direct access to the
          hardware and cannot get it with Wine and UNIX in the way
        </para>
        <para>
1014
          Wine is supposed to be primarily used WITHOUT Windows. If you want
1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032
          to use a Windows installation, then use an existing installation 
          alongside the UNIX installation (see the dual-boot HOWTO for your OS
          for more details). Or alternatively use the cabextract utility to
          extract Windows install archives to a directory that you want to use
          as Wine's Windows tree.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-do-I-configure-Wine-to-run-on-my-system">
        <para>How do I configure Wine to run on my system?</para>
      </question>
      <answer>
        <para>
          Wine requires that you have a config file as 
          <filename>~/.wine/config</filename>. The format of this file is
          explained in the <filename>wine.conf</filename> man page. The file
1033
          <filename>documentation/samples/config</filename>
Tom Wickline's avatar
Tom Wickline committed
1034 1035
          (<ulink url="http://source.winehq.org/source/documentation/samples/config">
          http://source.winehq.org/source/documentation/samples/config</ulink>) 
1036
          contains a config file example. More explicit directions can be 
1037
          found in the <filename>README</filename> file
Tom Wickline's avatar
Tom Wickline committed
1038 1039
          (<ulink url="http://source.winehq.org/source/README">
          http://source.winehq.org/source/README</ulink>) that will be located in
1040 1041 1042 1043 1044 1045
          the base Wine directory after you gunzip and untar the distribution
          file.
        </para>
      </answer>
      </qandaentry>

1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058
      <qandaentry>
      <question id="How-do-I-upgrade-configuration">
        <para>How do I upgrade Wine without losing my working configuration?</para>
      </question>
      <answer>
        <para>
          Upgrading the wine installation does not affect the existing wine
          configuration. So after upgrading wine you still have the old (working )
          wine configuration.
        </para>
      </answer>
      </qandaentry>

1059 1060 1061 1062 1063 1064
      <qandaentry>
      <question id="If-I-use-Windows-which-versions-OK">
        <para>If I want to use a Windows install, which versions are OK?</para>
      </question>
      <answer>
        <para>
1065
          Either use a classic no-windows install (Wine is getting better all
1066
          the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T 
1067
          configure Wine to use an NT-based Windows install (NT, Win2K, WinXP, Win2K3).
1068
        </para>
1069 1070 1071
	<para>
	  In general, most Windows installations contain vast quantities of garbage
	  that can confuse Wine and make it less reliable. If you can, it's best to
1072
	  install the programs you want into Wine's fake windows drive.
1073
	</para>
1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="If-I-use-Windows-which-one-works-best">
        <para>If I use a Windows install with Wine, which one works best?</para>
      </question>
      <answer>
        <para>
          As of 02/2002:
        </para>
        <para>
          I'd say Win98SE is the best version to use with Wine, as it's fairly
          widespread amongst developers and relatively old. Using Win2K files
          is <emphasis>definitely</emphasis> worse than a plain no-windows 
          Wine install, and Win ME is said to be problematic, too (as probably
          no developer uses it). In short: all Win9x &lt;= W98SE are good.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Installing-Visual-Basic-apps-wont-run">
        <para>
          Installing applications generated by Visual Basic won't run. What
          should I do?
        </para>
      </question>
      <answer>
        <para>
Ivan Leo Murray-Smith's avatar
Ivan Leo Murray-Smith committed
1104
          Make sure you have all the VB run time libraries installed. You can
1105
          get the latest version from the Microsoft web site.
1106 1107 1108 1109 1110 1111
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="When-I-click-on-exe-file-nothing-happens">
1112
        <para>When I click on *.exe file in my file Manager, nothing happens.</para>
1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128
      </question>
      <answer>
        <para>
          The normal Wine releases don't have .exe extensions registered for
          Wine in KDE/Gnome yet. You have to open a terminal window instead
          (often an icon showing a "black screen") and type something like:
        </para>
        <screen>
cd /my/windows/program/directory
wine myprogram.exe
        </screen>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="bash-wine-Command-not-found-What-can-I-do">
Francois Gouget's avatar
Francois Gouget committed
1129
        <para>bash says "wine: Command not found" What can I do?</para>
1130 1131 1132
      </question>
      <answer>
        <para>
1133
          Try to logout and login again into bash. That might fix it.
1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164
        </para>
        <para>
          If it doesn't, then make sure the wine binary is in your 
          <parameter>PATH</parameter>.
        </para>
        <para>
          Run as root:
        </Para>
        <screen>
find / -name "wine" -type f -perm +111
        </screen>
        <para>
          to find the path where the wine binary is in. Then check whether
        <parameter>PATH</parameter> includes it:
        </para>
        <screen>
echo $PATH 
        </screen>
        <para>
          If not, add that e.g. to <filename>/etc/profile</filename> by doing:
        </para>
        <screen>
export PATH=$PATH:/path/to/wine/binary 
        </screen>
        <para>
          That should help.
        </para>
        <para>
           If you used a package manager (<command>rpm</command> or 
           <command>apt</command>) - Verify your packages. The package 
           <filename>winesetuptk.rpm</filename> is only a front-end for 
1165
           making a meaningful config file, it DOES NOT install the wine
1166 1167 1168
           package...
        </para>
        <para>
Tom Wickline's avatar
Tom Wickline committed
1169 1170
           For complete packages, use <ulink url="http://rpmseek.com/rpm-pl/wine.html?hl=com&amp;cx=0::">
           http://rpmseek.com/</ulink> or the <ulink url="http://www.winehq.org/site/download">
1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181
           Download</ulink> section.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-do-I-remove-Wine-from-my-Computer">
        <para>How do I remove Wine from my Computer?</para>
      </question>
      <answer>
        <para>
1182 1183
          It depends on how you installed. If you used an RPM, the right command is this:
         <command>rpm -e wine (as root)</command>
1184
        </para>
1185 1186 1187 1188 1189 1190
       <para>
         If you installed from source (the .tar.gz file), the right
         way to do it is to change to the root of the source tree (the directory with the configure script,
         readme etc) then run as root:
         <command>make uninstall</command>
       </para>
1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203
      </answer>
      </qandaentry>
    </qandadiv>

    <qandadiv id="About-running-Wine">
      <title>About running Wine</title>
      <qandaentry>
      <question id="How-do-I-run-an-MS-Windows-program">
        <para>How do I run an MS Windows program under Wine?</para>
      </question>
      <answer>
        <para>
          When invoking Wine, you must specify the entire path to the
Tom Wickline's avatar
Tom Wickline committed
1204
          executable, or by file name only. For example to run Windows'
1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216
          solitaire, type any of the following:
        </para>
        <itemizedlist>
          <listitem>
          <para>
            <command>wine sol</command> or <command>wine sol.exe</command>
           (using the search path to locate the file).
          </para>
          </listitem>
          <listitem>
          <para>
            <command>wine c:\\windows\\sol.exe</command> 
Tom Wickline's avatar
Tom Wickline committed
1217
           (using a DOS file name).
1218 1219 1220 1221 1222
          </para>
          </listitem>
          <listitem>
          <para>
            <command>wine /usr/windows/sol.exe</command>
Tom Wickline's avatar
Tom Wickline committed
1223
           (using a UNIX file name).
1224 1225 1226 1227 1228
          </para>
          </listitem>
          <listitem>
          <para>
            <command>wine "c:\windows\sol.exe"</command>
Tom Wickline's avatar
Tom Wickline committed
1229
            (using quoted DOS file name).
1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256
          </para>
          </listitem>
        </itemizedlist>
        <para>
          The path of the file will also be added to the path when a full name
          is supplied on the command line.

        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Wine-cannot-find-MS-Windows-on-my-drive">
        <para>
          I have installed and configured Wine, but Wine cannot find MS 
          Windows on my drive. Where did I go wrong?
        </para>
      </question>
      <answer>
        <para>
          If you have a DOS partition, first make sure that you have mounted
          it, either by putting the entry into <filename>/etc/fstab</filename>,
          or by manually mounting it.
        </para>
        <para>
          Remember too that unless your version of UNIX can see through it, or
          you are running a utility that can see through it, your DOS
1257
          partition must not be located on a Drivespaced, Doublespaced or
1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300
          Stackered partition, as neither Linux, FreeBSD, NetBSD or Wine can
          natively 'see' files located in these compressed DOS partitions.
        </para>
        <para>
          Check your path statements in the <filename>wine.conf</filename> 
          file. No capital letters may be used in paths, as they are 
          automatically converted to lowercase.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Parts-of-my-app-do-not-work-What-is-wrong">
        <para>
          I was able to get various MS Windows programs to run, but parts of
          them do not work. What is wrong?
        </para>
      </question>
      <answer>
        <para>
          Wine is not complete at this time, so some of each programs' 
          features may not work. They will in time as more of the MS 
          Windows API calls are included in Wine.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Menus-do-not-work-how-can-I-exit">
        <para>
          I have run various MS Windows programs, but since the program menus
          do not work, how can I exit these programs?
        </para>
      </question>
      <answer>
        <para>
          Kill the xterm shell window that you called up to run your MS 
          Windows program, and the X window that appeared with the program 
          will be killed too.
        </para>
      </answer>
      </qandaentry>

1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311
      <qandaentry>
	<question id="My-app-doesnt-work-what-can-i-do">
	  <para>
	    My program doesn't work, what can I do?
	  </para>
	</question>
	<answer>
	  <para>
	    If you are a programmer and know C, then start debugging
	    Wine and help us make it better! If you can't, then you will
	    have to either convince a Wine developer to try and make your
Tom Wickline's avatar
Tom Wickline committed
1312 1313 1314 1315 1316 1317 1318 1319 1320 1321
	    program work (there must be a downloadable version or demo for that). 
          </para>
          <para>  
            You can submit your application to the <ulink url="http://appdb.winehq.org/">
            Wine Application DB </ulink> and gather tips on ways to get your app to work its best.
          </para>
          <para> 
            You can also submit your application to the CodeWeavers CrossOver 
            <ulink url="http://www.codeweavers.com/site/compatibility/"> Compatibility </ulink> Center.
            Where you can pledge/vote toward future support of your favorite application.
1322 1323 1324 1325 1326 1327
	  </para>
	  <para>
	    Alternatively, you may be able to get the app working by
	    taking native DLLs from a Microsoft Windows install, and using
	    them (set the dlls to native in the config file). Not all DLLs
	    can be replaced that way - in particular DirectX cannot be, nor
Tom Wickline's avatar
Tom Wickline committed
1328
	    can some core system DLLs like gdi32, user, ntdll, kernel32 etc.
1329 1330 1331
	  </para>
	</answer>
      </qandaentry>
Tom Wickline's avatar
Tom Wickline committed
1332

1333 1334
      <qandaentry>
      <question id="Can-I-use-Wine-with-other-Linux-Distros">
Tom Wickline's avatar
Tom Wickline committed
1335
        <para>Can I use Wine with SUSE, RedHat or other Linux Distro's?</para>
1336 1337 1338 1339
      </question>
      <answer>
        <para>
          You can use Wine on any sufficiently recent Linux installation. The
Tom Wickline's avatar
Tom Wickline committed
1340 1341
          amount of work getting Wine up and running depends on whether you
          install a binary packages or do a source install.
1342 1343 1344 1345 1346 1347 1348 1349 1350 1351
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Does-Wine-work-with-AMD-Processors">
        <para>Does Wine work with AMD Processors?</para>
      </question>
      <answer>
        <para>
1352 1353
          Yes, it does. Wine should work on any processor compatible with
          the Pentium or greater.
1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364
        </para>
      </answer>
      </qandaentry>

       <qandaentry>
      <question id="Can-I-launch-Unix-app-from-Windows-app">
        <para> Can I launch a Unix program from a Windows program?</para>
      </question>
      <answer>
        <para>
          Sure, Wine supports that. Just enter the unix program name wherever
1365
          a program has something that it's supposed to execute, and it
1366 1367 1368 1369
          should just work.
        </para>
      </answer>
      </qandaentry>
1370 1371 1372 1373
      <qandaentry>
      <question id="Error-with-installshield-6">
        <para>
          I get <quote>Error installing iKernel.exe: (0x1400)</quote>
1374
          when running an InstallShield 6 installer.
1375 1376 1377 1378 1379 1380 1381 1382
        </para>
      </question>
      <answer>
        <para>
          If you get the error "Error installing iKernel.exe: (0x1400)" at any
          point, it's probably because there are leftover processes from a
          previous try. You can verify this with the command
        </para>
1383
        <para><prompt>$ </><command>ps augxw | grep wine</command></para>
1384 1385 1386 1387 1388 1389
        <para>
          If that command shows old copies of wine running your setup,
          you need to kill them before you can run the setup program.
          If there are no other Wine programs running, you can kill them
          all with the command
        </para>
1390
        <para><prompt>$ </><command>killall wine</command></para>
1391 1392 1393 1394 1395 1396 1397
        <para>
          If you're also running Wine programs you care about, you'll
          have to kill off the old Setup instances one by one using
          kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
          which doesn't exist yet).
        </para>
        <para>
Tom Wickline's avatar
Tom Wickline committed
1398
          You should repeat the <command>ps</command> to make sure all of the old 
1399
          Wine processes are gone.
1400 1401 1402
        </para>
       </answer>
      </qandaentry>
1403
    </qandadiv>
Tom Wickline's avatar
Tom Wickline committed
1404

1405 1406 1407 1408 1409 1410 1411 1412
    <qandadiv id="Getting-help">
      <title>Getting help</title>
      <qandaentry>
      <question id="Is-there-any-documentation-for-Wine">
        <para>Is there any documentation for Wine?</para>
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
1413 1414
          Yes, see <ulink url="http://www.winehq.org/site/documentation">
          http://www.winehq.org/site/documentation.</ulink>
1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="I-have-written-some-documententation">
        <para>
          I couldn't find the answer to my question in the documentation, but
          I've written a document explaining how to solve it. What should I do?
        </para>
      </question>
      <answer>
        <para>
          Updates and additions to the Wine documentation directory should be
          sent to the wine-patches mailing list at 
1430 1431
          <ulink url="http://www.winehq.org/site/forums">
          http://www.winehq.org/site/forums</ulink>. Website and FAQ 
Tom Wickline's avatar
Tom Wickline committed
1432
          additions should be added to the appropriate Wine Knowledge base directory.
1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Is-there-a-Usenet-newsgroup-for-Wine">
        <para>Is there a Usenet newsgroup for Wine?</para>
      </question>
      <answer>
        <para>
          Yes, and it's called 
          <ulink url="news:comp.emulators.ms-windows.wine">
          comp.emulators.ms-windows.wine</ulink>. The newsgroup serves as a
          place for users and developers to discuss Wine, and for minor 
          announcements for the general public. Major announcements will be
Tom Wickline's avatar
Tom Wickline committed
1448
          cross posted to other appropriate newsgroups, such as the following:
1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482
        </para>
        <itemizedlist>
          <listitem>
          <para>
            <ulink url="news:comp.os.linux.announce">
            comp.os.linux.announce</ulink>
          </para>
          </listitem>
          <listitem>
          <para>
            <ulink url="news:ccomp.windows.x.announce">
            comp.windows.x.announce</ulink>
          </para>
          </listitem>
          <listitem>
          <para>
            <ulink url="news:ccomp.emulators.announce">
            comp.emulators.announce</ulink>
          </para>
          </listitem>
        </itemizedlist>
        <para>
          If your Usenet site does not carry these newsgroups, please urge 
          your ISP's sysadmin to add and/or uplink them.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Is-there-a-World-Wide-Web-site-for-Wine">
        <para>Is there a World Wide Web site for Wine?</para>
      </question>
      <answer>
        <para>
1483
          Wine HQ (<ulink url="http://www.winehq.org">http://www.winehq.org</ulink>) is the official site.
1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Is-there-an-IRC-channel-for-Wine">
        <para>Is there an IRC channel for Wine?</para>
      </question>
      <answer>
        <para>
          Sure. It's channel <filename>#WineHQ</filename> on 
1495
          <filename>irc.freenode.net</filename> see 
1496 1497
          (<ulink url="http://freenode.net">http://freenode.net</ulink>).
          Usually several Wine developers hang out there just to help YOU ;-)
1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="I-think-I-found-a-bug-How-do-I-report-it">
        <para>
          I think I've found a bug. How do I report this bug to the Wine
          programming team?
        </para>
      </question>
      <answer>
        <para>
          Bug reports should be submitted to our online Bugzilla system 
1512
          (<ulink url="http://bugs.winehq.org/">http://bugs.winehq.org/</ulink>).
1513
          You should include at least the following:
1514 1515 1516 1517 1518 1519 1520 1521 1522
        </para>
        <itemizedlist>
          <listitem>
          <para>
            The Wine version tested
          </para>
          </listitem>
          <listitem>
          <para>
1523 1524
            The Windows application name, including the version, and, if
            applicable, a URL the application can be downloaded from
1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538
          </para>
          </listitem>
          <listitem>
          <para>
            A brief description of the bug
          </para>
          </listitem>
          <listitem>
          <para>
            The relevant part(s) of the output of the Wine debugger
          </para>
          </listitem>
          <listitem>
          <para>
1539
            A screenshot of the visual problem, if applicable
1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560
          </para>
          </listitem>
        </itemizedlist>
        <para>
         For more information about reporting bugs please see the 
         <ulink url="http://www.winehq.org/Docs/wine-user/bug-reporting.shtml">
         How to report a bug</ulink> section of the Wine Users Guide.
        </para>
      </answer>
      </qandaentry>
    </qandadiv>
 
    <qandadiv id="Helping-Wine-or-becoming-a-Wine-developer">
      <title>Helping Wine or becoming a Wine developer</title>
      <qandaentry>
      <question id="How-do-I-become-a-Wine-developer">
        <para>How do I become a Wine developer? What do I need to know?</para>
      </question>
      <answer>
        <para>
          If you can program C, that's a good start. Download the sources via
1561
          (<ulink url="http://www.winehq.org/site/cvs">CVS,</ulink>)
Tom Wickline's avatar
Tom Wickline committed
1562 1563 1564
          subscribe to the mailing lists, look around the source, and
          pay attention to the comp.emulators.ms-windows.wine newsgroup
          and the mailing lists (<ulink
1565
          url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>).
Tom Wickline's avatar
Tom Wickline committed
1566 1567 1568
          See if there's anything that you think you can fix or work
          on. You won't have much trouble finding areas that need work
          in Wine (grep for FIXMEs in the source).
1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-can-I-contribute-to-the-Wine-project">
        <para>How can I help contribute to the Wine project, and in what way(s)?</para>
      </question>
      <answer>
        <para>
          You can contribute programming or documentation skills, or monetary
          or equipment donations, to aid the Wine developers in reaching their 
          goals.
        </para>
        <para>
          For a list of ideas of how you can help, please consult the 
1585
          <ulink url="http://www.winehq.org/site/contributing">
1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612
          Wine contrib page</ulink>.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="I-want-to-help-beta-test-Wine">
        <para>I want to help beta test Wine. How can I do this?</para>
      </question>
      <answer>
        <para>
          Wine still consists of some Alpha code at this time. However, anyone
          is welcome to download the latest version, and try it out at any
          time.
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="I-wrote-some-code-I-would-like-to-submit">
        <para>
          I have written some code that I would like to submit to the Wine
          project. How do I go about doing this?
        </para>
      </question>
      <answer>
        <para>
1613 1614
          Submitting a patch for inclusion in Wine is pretty simple.
          Basically all you have to do is send the patch to the
1615
          wine-patches mailing list 
Tom Wickline's avatar
Tom Wickline committed
1616
          (<ulink url="http://www.winehq.org/mailman/listinfo/wine-patches">http://www.winehq.org/mailman/listinfo/wine-patches</>).
1617 1618
          Still there are a couple of recommendations about the patch format
          and all so it's best to read our page describing <ulink
1619
          url="http://www.winehq.org/site/sending_patches">how to submit
1620 1621 1622
          patches</>. This will also give you more details about the whole
          process and in particular to what will happen to your patch once
          submitted.
1623 1624 1625 1626
        </para>
      </answer>
      </qandaentry>
    </qandadiv>
Tom Wickline's avatar
Tom Wickline committed
1627

1628 1629 1630 1631 1632 1633 1634 1635 1636 1637
    <qandadiv id="Developing-programs-using-Wine-WineLib">
      <title>Developing programs using Wine/WineLib</title>
      <qandaentry>
      <question id="Can-I-use-Wine-to-port-Win32-sources-to-Unix">
        <para>Can I use Wine to port my Win32 sources to Unix?</para>
      </question>
      <answer>
        <para>
          That is the idea of Winelib. Right now you may still have some 
          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 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654

        </para>
      </answer>
      </qandaentry>
      <qandaentry>
      <question id="Will-MFC-work-with-Wine-What-do-I-need-to-do">
        <para>Will MFC work with Wine? What do I need to do?</para>
      </question>
      <answer>
        <para>
          Wine is not implementing an MFC replacement nor does it intend to.
          However it is possible (with a lot of work) to compile the MFC from
          source and thus produce an <filename>mfc42.dll.so</filename> library.
        </para>
        <para>
          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 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="Are-there-commercial-apps-ported-using-Wine">
        <para>
          Are there any commercial applications which have been ported
          using Wine?
        </para>
      </question>
      <answer>
        <para>
1669
          Here are few examples of applications ported using Wine or Winelib:
1670 1671 1672 1673
        </para>
        <itemizedlist>
          <listitem>
          <para>
1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688
            Corel's WordPerfect Office Suite 2000 was ported to Linux using
            Wine.
          </para>
          </listitem>
          <listitem>
          <para>
            Kylix, the Linux version of Delphi, was ported to Linux using
            Winelib. The IDE actually uses a combination of QT and Winelib
            which would not have been possible to achieve using only Wine.
            The generated applications however do not depend on Wine in
            any way.
          </para>
          </listitem>
          <listitem>
          <para>
Tom Wickline's avatar
Tom Wickline committed
1689
            MusicMatch Jukebox 5 has also been
1690 1691 1692
            <ulink url="http://www.itworld.com/nl/lnx_desktop/01042001/">ported</>
            to Linux using Winelib. However more recent versions have not, and
            version 5 is no longer available.
1693 1694 1695 1696
          </para>
          </listitem>
          <listitem>
          <para>
1697
            Ability Office
1698
            (<ulink url="http://www.ability.com/linux/abilitylinux.php">http://www.ability.com/linux/abilitylinux.php</ulink>)
1699 1700 1701 1702 1703
          </para>
          </listitem>
          <listitem>
          <para>
            IBM's Websphere
1704
            (<ulink url="http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)
1705 1706 1707 1708 1709 1710 1711 1712 1713 1714
          </para>
          </listitem>
        </itemizedlist>
        <para>
          Many other important applications have already been ported. (we are
          speaking of several top 500 applications here)
        </para>
      </answer>
      </qandaentry>

1715
      <qandaentry>
1716
      <question id="Can-I-bundle-everything-in-one-huge-exe">
1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732
        <para>
          Is there a way to bind the Wine code, a Windows .exe, associated DLLs,
          and any necessary accompanying files into a single Linux executable which
          can execute as if it were a native linux binary (ie without also having
          Wine pre-installed)?
        </para>
      </question>
      <answer>
        <para>
          No. However, if you don't want Wine as a dependency, you can bundle your 
          private version of Wine into your package (.rpm/.deb). Wine has good
          support for such a setup via the WINEPREFIX environment variable.
        </para>
      </answer>
      </qandaentry>

1733 1734 1735 1736 1737 1738 1739
      <qandaentry>
      <question id="How-can-I-detect-Wine">
        <para>How can I detect Wine?</para>
      </question>
      <answer>
        <para>
          You really shouldn't want to do this. If there's a quirk in Wine 
Tom Wickline's avatar
Tom Wickline committed
1740
          you need to work around, it's much better to fix it in Wine.
1741 1742 1743 1744
        </para>
      </answer>
      </qandaentry>

Tom Wickline's avatar
Tom Wickline committed
1745

1746 1747 1748 1749 1750 1751 1752
    </qandadiv>

    <qandadiv id="Wine-HQ-issues">
      <title>Wine HQ issues</title>
      <qandaentry>
      <question id="Why-are-the-maillists-set-to-reply-to-author">
        <para>
1753
          Why are the mailing lists set to reply to author, not to mailing list?
1754 1755 1756 1757
        </para>
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
1758
          There are some very valid reasons for doing so.
1759 1760 1761 1762 1763 1764 1765 1766 1767 1768
        </para>
      </answer>
      </qandaentry>

      <qandaentry>
      <question id="How-to-unsubscribe-from-the-mailing-lists">
        <para>How to unsubscribe from the mailing lists?</para>
      </question>
      <answer>
        <para>
Tom Wickline's avatar
Tom Wickline committed
1769 1770
          Please see: <ulink url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>
          And select [(Un-)Subscribe]
1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781
        </para>
      </answer>
      </qandaentry>

    </qandadiv>
 
  </qandaset>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
1782
sgml-parent-document:("wine-devel.sgml" "book" "part" "chapter" "")
1783 1784
End:
-->