1 <!-- *** Wine FAQ *** -->
2 <title>Wine FAQ</title>
5 <qandadiv id="About-this-FAQ"><title>About this FAQ</title>
7 <question id="Who-maintains-this-FAQ">
8 <para>Who maintains this FAQ ?</para>
11 <para>Dave Gardner maintained it from 1995-1998.</para>
12 <para>Douglas Ridgway took it over in 1999.</para>
13 <para>Andreas Mohr converted it to FAQ-O-Matic in 2000.</para>
14 <para>Dimitrie O. Paun, Keith Matthews and Tom Wickline (in alphabetical order) reorganized it in 2002.</para>
15 <para>For suggestions/additions/complaints regarding this FAQ, please send an email to
16 <ulink url="mailto:wine-faq@winehq.org">wine-faq@winehq.org</ulink></para>
20 <question id="What-is-the-copyright-on-the-FAQ-And">
21 <para>What is the copyright of this FAQ? And how may I use it?</para>
24 <para>The original Wine FAQ, which this FAQ was based on, was copyright © 1995-1998 David Gardner.</para>
25 <para>It may be reproduced and modified under the same terms as Wine itself.</para>
29 <qandadiv id="General-Questions-about-Wine">
30 <title>General Questions about Wine</title>
33 <question id="What-is-Wine-and-what-is-it-supposed-to">
34 <para>What is Wine and what is it supposed to do?</para>
38 Wine is a program which allows the operation of DOS and MS
39 Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems such as Linux.
40 It consists of a program loader, which loads and executes a Windows
41 binary, and a set of libraries that implements Windows API calls
42 using their UNIX or X11 equivalents. The libraries may also be used
43 for porting Win32 code into native UNIX executables, often
44 without many changes in the source. Wine is free software,
45 and its license (contained in the file LICENSE
46 in each distribution) is the LGPL.
52 <question id="Is-Wine-an-emulator">
53 <para>Does Wine emulate a full computer?</para>
57 No, as the name says, Wine Is Not a (CPU) Emulator. Wine just
58 provides the Windows API. This means that you will need an
59 x86-compatible processor to run an x86 Windows application, for instance from Intel or AMD. The
60 advantage is that, unlike solutions that rely on CPU emulation, Wine
61 runs applications at full speed. Sometimes a program run under
62 Wine will be slower than when run on a copy of Microsoft Windows, but
63 this is more due to the fact that Microsoft has heavily optimized parts of their
64 code, whereas mostly Wine is not well optimized (yet). Occasionally, an app
65 may run faster under Wine than on Windows. Most apps run at roughly the same speed.
71 <question id="Are-here-any-alternatives-to-Wine">
72 <para>Are there any alternatives to Wine?</para>
76 Yes, there are. You can use <ulink url="http://www.vmware.com">VMWare</ulink> to run a Windows installation inside a virtual machine,
77 or use <ulink url="http://www.win4lin.com">Win4Lin</ulink>
78 to run a specially adapted Windows version on Linux.
79 Both solutions cost money for both the software itself
80 and a Windows license.
83 Note that, like Wine, they can only use the hardware platform that
84 the target programs were originally compiled for (see below).
91 <question id="Difference-between-Wine-and-emulators">
92 <para>What is the difference between Wine and x86 hardware emulators?</para>
96 There are two free x86 hardware emulators:
97 <ulink url="http://bochs.sourceforge.net">Bochs</ulink>, and
98 <ulink url="http://savannah.nongnu.org/projects/plex86">Plex86</ulink>.
102 Plex86 is the open-source free-software alternative for VMWare,
103 VirtualPC, and other IA-32 on IA-32 "Virtual PC products." It
104 can only run on the IA-32 architecture.
108 Bochs is a highly portable open source IA-32 (x86) PC emulator
109 written in C++, that runs on most popular platforms. It includes emulation
110 of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently,
111 Bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
112 of running most Operating Systems inside the emulation including Linux,
113 Windows® 95, DOS, and recently Windows® NT 4.
117 Both are licensed under the GPL. Bochs is older than Plex86, seems to be
118 easier to install, but Plex86 will run faster because Plex86 uses a just in
119 time binary compiler.
122 The drawback of all emulators is that you need a version
123 of Windows in order to run Windows, and that they all have an
124 impact on performance. Wine also gives much better desktop integration - for
125 instance, programs use your standard window manager, system tray icons will
126 appear in your tray area (if you have one), and you can run programs direct from the
127 command line as well as menus. The clipboard also works seamlessly at this time.
134 <question id="Integrate-an-x86-emulator">
135 <para>When will Wine integrate an x86 CPU emulator so we can
136 run Windows applications on non-x86 machines?</para>
140 The short answer is 'probably never'. Remember, Wine Is Not a
141 (CPU) Emulator. The long answer is that we probably don't want or
142 need to integrate one in the traditional sense.
145 Integrating a CPU emulator in Wine would be extremely hard,
146 due to the large number of Windows APIs and the complex
147 data types they exchange. It is not uncommon for a Windows API to
148 take three or more pointers to structures composed of many fields,
149 including pointers to other complex structures. For each of these
150 we would need a conversion routine to deal with the byte order and
151 alignment issues. Furthermore, Windows also contains many callback
152 mechanisms that constitute as many extra places where we would have
153 to handle these conversion issues. Wine already has to deal with
154 16 vs. 32 bit APIs and Ansi vs. Unicode APIs which both
155 introduce significant complexity. Adding support for a CPU emulator
156 inside Wine would introduce at least double that complexity and
157 only serve to slow down the development of Wine.
160 Fortunately another solution exists to run Windows applications
161 on non-x86 platforms: run both Wine and the application inside the
162 CPU emulator. As long as the emulator provides a standard Unix
163 environment, Wine should only need minimal modifications. What
164 performance you lose due to Wine running inside the emulator
165 rather than natively, you gain in complexity inside of Wine.
166 Furthermore, if the emulator is fast enough to run Windows
167 applications, Photoshop for instance, then it should be fast enough
168 to run that same Windows application plus Wine.
171 Two projects have started along those lines: <ulink
172 url="http://fabrice.bellard.free.fr/qemu/">QEMU</>, an
173 open-source project, and <ulink
174 url="http://www.transitives.com/tech_overview.htm">Dynamite</>,
175 a commercial CPU emulator environment from
176 <ulink url="http://www.transitives.com/">Transitives Technologies</>.
183 <question id="Why-would-anyone-want-Wine-Windows-suck">
184 <para>Why would anyone want Wine? Doesn't Windows suck?</para>
188 First Wine is not about running Windows but about running Windows
192 So if all your computing needs are fulfilled by native Unix
193 applications, then you do not need Wine and should not be using
194 it. However, if you depend on one or more of the tens of
195 thousands of Windows applications, then Wine is the best way to
196 use it without giving up on Unix. Let's look at the alternatives
200 The most obvious alternative is to dual-boot. This is the solution
201 that provides the best compatibility. However it requires that you
202 acquire a Windows license and then dedicate a good chunk of your
203 hard-drive to Windows. But the worst is yet to come. Each time you
204 will want to use that application you will have to reboot to
205 Windows. This is especially significant if external factors dictate
206 when you must use this application (e.g. credit card to process,
207 email to retrieve from a Lotus Notes server). Then you will find
208 yourself forced to close all your Linux applications just to run
209 that one Windows application. You may quickly get tired of this, or
210 will find that such a situation is impossible to justify in a
211 business environment.
214 The next solution is to install virtual machine emulation software
215 such as VMWare, Win4Lin or Plex86. Then you can use windows
216 applications without suffering such a big disruption. But it still
217 requires that you acquire a Windows license and dedicate as much
218 disk space to Windows. Furthermore you will pay for the added
219 convenience: if using VMWare or Win4Lin you have to buy another
220 license, and more importantly you now have to dedicate a good chunk
221 of your computer's memory to the virtual machine. Performance will
222 take a significant hit too.
225 Using Wine lets you avoid all of that overhead: Windows license,
226 hard-drive space required by Windows, memory and performance hit
227 taken by emulated virtual machines. Now you can start your Windows
228 application straight from your regular desktop environment, place
229 that application's window side by side with native applications,
230 copy/paste from one to the other, and run it all at full speed.
233 It is also a pretty vital part of migrating a large organization,
234 you can't change a 5000 desktop setup overnight without a lot of risk.
241 <question id="Use-Windows-driver-with-Wine">
242 <para>Can I use Wine to make the Windows driver for my network card /
243 graphics card / scanner / etc. work on Unix?</para>
247 The goal of Wine is to make it possible to run Windows applications
248 on Unix, not Windows drivers or VxDs.
251 Drivers and Windows applications belong to different worlds.
252 Applications run in user mode and use the APIs provided by
253 the kernel and the other user mode dlls. In contrast, drivers
254 are loaded in the Windows kernel, i.e. in ring 0 instead of ring
255 3, drivers have to deal with specific memory management issues, and use
256 instructions not available to regular applications. This means
257 they would not be able to run in Wine since Wine runs entirely
258 in user mode. Rather you would have to modify the Linux kernel.
259 But in addition, drivers use a completely different API from
260 regular Windows applications. So the work performed on Wine would
261 not even be of any use for such a project. In other words, making
262 it possible to use Windows drivers or VxDs on Unix would be a
263 completely separate project.
266 However, if you want to reuse Windows drivers on a non-Microsoft
267 operating system we recommend that you have a look at
268 <ulink url="http://www.reactos.com/">ReactOS</>.
275 <question id="Which-one-of-the-different-Wine-packages">
276 <para>Which one of the different Wine packages out there is good for me?</para>
280 Currently there is a broad selection of different Wine packages/versions:
285 <term><ulink url="http://www.winehq.org">Wine</ulink></term>
288 This is the "standard" distribution of Wine. Its license is
289 the LGPL, it can be downloaded for free. Both source code and binaries
290 are available in the download section of the site.
296 <term><ulink url="http://www.transgaming.com">TransGaming's Cedega</ulink></term>
299 This is TransGaming's Wine version specially suited for
300 games. It includes more mature Direct3D support than
301 WineHQ, although these days WineHQ has quite advanced
302 D3D support as well. Most of the code is under the AFPL
303 and can be downloaded for free.
306 However TransGaming also distributes binaries that contain
307 improved copy protection support (needed for many
308 games), support, and other enhancements. These packages are
309 only available in binary form to subscribed customers
310 ($5/month, minimum three months).
316 <term><ulink url="http://www.codeweavers.com/site/products/cxoffice/">CodeWeavers' CrossOver Office</ulink></term>
319 Wine version with special packaging to make sure almost all
320 important Office type programs work pretty well. Costs $74.95
321 for the Pro version and $39.95 for the Standard version.
322 Seems to be well worth it so far according to some comments.
323 (note: you're supporting a company actively contributing to Wine
324 if you decide to buy CrossOver.)
330 <term><ulink url="http://www.codeweavers.com/site/products/cxserver/">CodeWeavers' CrossOver Office Server Edition</ulink></term>
333 Allows you to run your favorite Windows productivity applications in
334 a distributed thin-client environment under Linux. Server Edition is
335 also a great addition to Solaris environments, since there built-in
336 support for Solaris desktops makes running Windows applications a
337 possibility on Sun workstations as well. For pricing just follow this link:
338 <ulink url="http://www.codeweavers.com/site/products/pricing/">CrossOver Office Server Edition Pricing</ulink>
348 <question id="Whats-the-history-of-Wine">
349 <para>What's the history of Wine?</para>
353 The Wine project started in 1993 as a way to support running Windows 3.1
354 programs on Linux. Bob Amstadt was the original coordinator, but turned
355 it over fairly early on to Alexandre Julliard, who has run it ever
356 since. A <ulink url="news:comp.emulators.ms-windows.wine">newsgroup</ulink>
357 was created in July 1994. Over the years, ports for
358 other Unixes have been added, along with support for Win32 as Win32
359 applications became popular.
362 For more information, see <ulink url="http://www.winehq.com/site/history">
363 http://www.winehq.com/site/history</ulink>
369 <question id="What-is-the-current-version-of-Wine">
370 <para>What is the current version of Wine?</para>
374 A new version of Wine is distributed about every month. You will be
375 able to keep up on all the latest releases by reading the newsgroup
376 <ulink url="news:comp.emulators.ms-windows.wine">
377 comp.emulators.ms-windows.wine</ulink>, or by visiting the
378 <ulink url="http://www.winehq.org">Wine HQ homepage</ulink>. When
379 downloading Wine from your FTP site of choice (see
380 <ulink url="http://www.winehq.org/site/download">the Download page</ulink>
381 for some of these choices), you can make sure that you are getting
382 the latest version by watching the version numbers in the distribution
383 file name. For instance, the distribution released on August 13, 2004
384 was called Wine-20040813.tar.gz. Patch files are also available. If
385 you are current to the previous version, you can download and apply
386 just the current patch file rather than the entire new distribution.
387 The patch file names follow the same conventions as the monthly
388 distribution. <ulink url="http://www.winehq.org/site/cvs">
389 Read-only CVS</ulink> access is also available.
395 <question id="What-is-the-current-Status-of-Wine">
396 <para>What is the current Status of Wine?</para>
400 As of mid 2004, Wine consists of about 1.6 million lines of code,
401 written by more than 600 developers from dozens of countries around
402 the world. Wine is in active use by an estimated 100K people. Wine
403 implements more than 90% of the calls in popular Windows
404 specifications such as ECMA-234 and Open32.
407 You may also want to look at the
408 <ulink url="http://www.winehq.org/site/status">
409 Status page</ulink> for a global view on Wine's implementation progress.
415 <question id="When-will-Wine-be-finished">
416 <para>When will Wine be finished?</para>
420 Large software projects are never finished, only released. In any
421 case Wine is chasing a moving target since every new release of
422 Windows contains new API calls or variations on the existing ones.
425 Because Wine is being developed by volunteers, it is difficult to
426 predict when it will be ready for general release. But due to the
427 much increased interest by companies in porting apps via Wine, Wine
428 development is constantly getting more and more active. Right now
429 we are working on releasing Wine 0.9 Real Soon Now(tm).
435 <question id="Who-is-responsible-for-Wine">
436 <para>Who is responsible for Wine?</para>
440 Wine is available thanks to the work of many people. Please see the
441 <ulink url="http://source.winehq.org/source/AUTHORS">AUTHORS</ulink>
442 file in the distribution for the complete list. Some companies that
443 are or have been involved with Wine development are CodeWeavers,
444 TransGaming, Corel, and Macadamian.
450 <question id="What-undocumented-APIs-are-not-understood">
451 <para>What undocumented APIs / interfaces are not understood? Would
452 seeing Microsoft source help?
457 The best would be if the Windows API was fully documented, so Wine
458 could be a perfect "clean-room" implementation. Seeing the source
459 code might make it harder to prove that no copyright violations have
460 taken place. That said, the documentation is often bad, nonexistent,
461 and even misleading where it exists, so a fair amount of reverse
462 engineering has been necessary, particularly in the shell (Explorer)
463 interface. The biggest problem facing Wine though is simply lack of
464 manpower. At one point, over 5000 people were working on Windows 2000.
465 While Wine doesn't need to replicate all of Windows (we only cover the
466 parts needed to make Windows programs work), that's still nearly 10 times
467 more people working simply on one release than have <emphasis>ever</emphasis>
468 worked on Wine, in the history of the project.
474 <question id="Is-TransGamings-last-patch-included-in-Wine">
475 <para>Is TransGaming's latest patch included in the standard Wine release?</para>
482 TransGaming makes money via a subscription service and the license
483 of their Cedega tree is incompatible with the Wine license. Thus
484 Cedega patches cannot be integrated into the Wine tree without
485 express permission by TransGaming. They have submitted some
486 of their work for integration into Wine, most notably DirectDraw
487 and some DirectSound work, and such work has been integrated into
488 the Wine tree. However it seems highly unlikely they will ever submit their
495 <question id="Will-there-be-a-Windows-version-of-Wine">
496 <para>Will there be a Windows version of Wine?</para>
500 Some people are working on getting Wine code to compile on Windows
501 using one of the following projects as a basis:
503 <itemizedlist spacing="compact">
507 (<ulink url="http:/www.cygwin.com/">http://www.cygwin.com</ulink>)
513 (<ulink url="http:/www.mingw.org/">http://www.mingw.org</ulink>)
519 (<ulink url="http://www.reactos.com/">http://www.reactos.com</ulink>)
524 There's some progress, so a Wine version that's usable on Windows
525 might be available at some time in the future.
528 Part of the rationale for these projects is to find out areas where
529 Wine portability is lacking. This is especially true of the
530 ReactOS project which is a reimplementation of the Windows kernel
531 and should thus be able to reuse most of Wine dlls.
534 Another reason for pursuing these projects is to be able to
535 replace a single Windows dll with its Wine counterpart. Besides
536 being a good test for the Wine dll, this lets us detect cases where
537 we made incorrect assumptions about how the dlls interact.
543 <question id="Can-I-use-native-drivers">
544 <para>Can I use Windows printer drivers in Wine?</para>
548 Native printer drivers are not supported. At one time Wine supported 16bit
549 native drivers but that was long ago. Wine uses the printers (and other
550 devices) installed in your operating system. For the most part if you don't
551 have the device installed on your OS then wine can't use it.
557 <qandadiv id="What-do-I-need-in-order-to-use-Wine">
558 <title>What do I need in order to use Wine?</title>
560 <question id="Under-what-platforms-will-Wine-run">
562 Under what hardware platform(s) and operating system(s) will
568 Wine is being developed specifically to run on the <emphasis>Intel
569 x86</emphasis> class of CPUs under certain UNIXes that run on this
570 platform. Winelib however is capable of porting the Windows
571 applications <emphasis>source code</emphasis> to other platforms
575 Thus running Windows binaries on other platforms (e.g. Mac OS X on
576 PowerPC) using just Wine is <emphasis>not</emphasis> possible. You
577 would have to either run Wine in an emulated x86 environment or
578 take the Windows application source code and recompile it using
582 These are the platforms supported by Wine.
583 Winelib support for other platforms keeps evolving,
584 so it's not specifically listed here.
587 NetBSD, OpenBSD, UnixWare, and SCO OpenServer 5 worked at one time,
588 but Wine now requires kernel-level threads which are not currently
589 available (or understood by the Wine team) on those platforms.
592 The Wine development team hopes to attract the interest of other
593 commercial UNIX and UNIX clone vendors as well.
596 BeOS: porting efforts (BeWine) used to be pretty strong, but BeOS
597 has severe limitations in Unix call support. The demise of Be
598 further hampered the project though it might come back one day on
599 one of the open BeOS projects. In any case a functional port seems
600 unlikely to ever happen at this stage.
603 Mac OS X / Darwin: The <ulink
604 url="http://darwine.sourceforge.net/project.html">Darwine</> is
605 currently working on porting Wine to the Darwin/x86 platform. Their
606 goal is to eventually make it possible to run x86 Windows
607 applications on Darwin/PPC and then Mac OS X by using Bochs.
610 FreeBSD: This port is well maintained and should work with
611 limitations in specific areas (mainly missing device/hardware
615 Linux/x86: Works, and as the most popular platform for both
616 developers and users, it is the best supported platform of all.
622 <question id="What-minimum-CPU-must-I-have">
624 What minimum CPU must I have in my computer to be able to run Wine
625 and MS Windows applications smoothly?
630 We need to differentiate between Wine and Winelib here.
633 Wine won't run on any x86 CPU less than an 80386 due to address
634 management limitations.
637 It is known to also work in the 80486 and upwards compatible CPUs.
638 The basic test is, if you can run X11 now, you should be able to run
639 Wine and MS Windows applications under it.
642 As always, the faster your CPU, the better. Having a math coprocessor
643 is unimportant. However, having a graphics accelerated video card
644 supported by X will help greatly.
647 Depending on your application you may find that faster speeds are
648 required for sensible use. We can't give specific advice on that due
649 to the vast range of applications out there. However the rule of
650 thumb is that if your application runs fine on Windows, it should
651 run fine on the same platform in Wine.
657 <question id="How-much-disk-space-will-Wine-take">
659 How much disk space will the Wine source code and binaries take on my
665 You need approximately 250 megabytes of free hard drive space to
666 store and compile the source code. Wine also needs about 18 megs in
667 your /tmp directory. And about 50 MB are needed to do a make install.
670 Binary packages, especially those not containing debug information,
671 have much lower disk space requirements, usually in the 20MB range.
677 <question id="What-other-software-do-I-need-to-compile">
679 What other software do I need to install, compile and run
685 Many development tools are needed in order to compile Wine.
686 A list of required packages for several distributions is included in
687 the README (<ulink url="http://source.winehq.org/source/README">
688 http://source.winehq.org/source/README</ulink>).
691 To run Wine, you will need the following:
694 <itemizedlist spacing="compact">
696 <para>The compiled Wine binary</para>
699 <para>A properly configured wine.conf file (or ~/.winerc file)</para>
702 <para>An installed and working X Window system</para>
705 <para>Some Windows programs to test</para>
711 <question id="How-much-RAM-do-I-need">
713 How much RAM do I need to have on my UNIX system to be able to run
714 Wine and MS Windows applications smoothly?
719 If you can run X smoothly on your UNIX system now, you should be
720 able to run Wine and MS Windows applications just fine too, depending
721 on how memory hungry the application is.
724 Wine's memory requirements will depend on the application or game
725 that you choose to run. You will need to meet the minimum requirements for
726 the application as well as the overhead of your underlying OS.
727 You may want to check with the vendor of the application for its
728 suggested memory requirements.
734 <question id="How-long-does-Wine-take-to-build">
735 <para>How long does Wine take to build</para>
739 Wine is getting to be quite large, and building from scratch takes a
740 lot of processing. As of May 2004, compile times were around 10
741 minutes on a Athlon 2000 with 512 MB of RAM and 20 minutes on a Athlon
742 1200 with 640 MB of RAM. If you have a CVS copy of wine, you may not need
743 to rebuild every thing each update.
748 <question id="I-have-a-Drivespaced-partition">
750 I have a Drivespaced, Doublespaced or Stackered DOS partition. Can
751 Wine run MS Windows binaries located in such a partition?
756 Yes, but only if the operating system supports mounting those types
757 of drives. There is a Linux file system driver called dmsdos that
758 will allow read/write access to Doublespaced and Drivespace 1.0
759 drives. More specifically, it supports mounting DOS 6.0 and 6.2
760 Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced
761 compressed partitions (read and write access works fine, but write
762 access is slow). It can be found at
763 <ulink url="ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/">
764 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>
770 <question id="Do-I-need-to-have-a-DOS-partition">
771 <para>Do I need to have a DOS partition on my system to use Wine?</para>
775 You do not need a licensed and installed copy of DOS or MS Windows to
776 install, configure and run Wine. However, Wine has to be able to
777 'see' an MS Windows binary (i.e. application) if it is to run it.
783 <question id="Does-MS-Windows-need-to-be-installed">
785 Does MS Windows need to be loaded into that partition in order to
786 run MS Windows programs under Wine?
791 Many folks have successfully installed and run programs
792 in their UNIX file system without having a DOS partition or MS
793 Windows. However, in many cases you need a directory and file
794 infrastructure that is similar to an existing Windows installation.
795 Some applications' installation programs want to distribute some of
796 the package's files into the /windows and /windows/system
797 directories in order to run, and unless these exist on your UNIX
798 file system, those programs will not install correctly and probably
799 will not run well, if at all. Most packages will set that up for you
800 as part of the install process.
803 If you have a DOS partition with MS Windows installed in it, make
804 sure that your UNIX system can 'see' this partition (check your
805 /etc/fstab file or mount the partition manually) so that Wine can
806 run the MS Windows binaries located in the DOS partition. To run
807 without a DOS partition, you need to set a UNIX path to be your
808 drive C, and make sure that the /windows and /windows/system
809 directories point to some place that actually exist.
812 Here's an example, copied from a machine which has no DOS partition
813 but successfully runs Wine:
821 System=c:\windows\system
825 In <filename>/var/lib/wine/windows</filename>, you will need to
826 install a <filename>win.ini</filename> config file that you might
827 find on a typical MS Windows 3.1 machine. The directory
828 <filename>/var/lib/wine/windows/system</filename> should exist, but
829 doesn't need to contain anything. However, to use MS DLLs, you can
830 copy them into that directory. Note that this is a contravention of
831 the Windows licence unless Windows is properly installed on the
832 machine. If you have DOS/MS Windows installed on your system, you can
833 mount that partition at bootup by modifying the file
834 <filename>/etc/fstab</filename> in your UNIX partition (assuming that
835 the UNIX kernel supports the DOS/MS Windows file system type).
838 If you edit this file by hand, it should contain something similar
842 /dev/hda1 /dosc msdos uid=0,gid=100,umask=007 0 0
845 This will allow you to read and write to the DOS partition without
852 <question id="If-Wine-completely-replaces-MS-Windows">
854 If Wine completely replaces MS Windows, will it duplicate all of the
855 functions of MS Windows?
860 Wine's goal is to make it possible to run Windows applications on
861 Unix. To this end it will provide replacements for just those
862 DLLs and APIs that are needed by these Windows applications.
863 This means that Wine will not provide replacements for DLLs that
864 are not shipped with Windows or are always shipped with Windows
865 application (e.g. the Visual Basic run time). This also
866 means that implementing an API that no application ever uses is not
867 a priority. Similarly, until there are applications out there that
868 use the Win64 API, it will not be a priority. That being said,
869 we will certainly try to keep our options open and to improve our API
873 Also Wine is not an operating system, so that writing device
874 drivers is not part of Wine's goals. However if you are interested
875 in device drivers, the <ulink url="http://www.kernel.org/">Linux</ulink>,
876 <ulink url="http://www.freebsd.org/">FreeBSD</ulink> and
877 <ulink url="http://www.reactos.com/">ReactOS</ulink> kernel developers
878 would certainly appreciate your contribution.
881 Similarly Wine does not try to be a desktop environment so
882 providing applets such as a calculator, a file manager or even
883 window manager that look like Windows, are low priority or would
884 even best be done as a separate project. Such projects would also
885 to a large extant be redundant with other open-source projects.
886 Again, there are projects that would certainly appreciate your
887 contributions in this areas, such as the
888 <ulink url="http://www.gnome.org/">Gnome</ulink> or
889 <ulink url="http://www.kde.org/">KDE</ulink> desktop environments. You
890 will get the added benefit that your contribution will then be
891 usable by everyone, not just by Wine users.
897 <question id="Will-I-install-on-any-UNIX-file-system">
899 Will I be able to install MS Windows applications in any flavor of a
905 Wine is written to be file system independent, so MS Windows
906 applications will install and run under virtually any file system
907 supported by your brand of UNIX.
913 <question id="Will-Wine-run-only-under-X">
914 <para>Will Wine run only under X, or can it run in character mode?</para>
918 Most of Wine's development effort is geared towards MS Windows' GUI,
919 but some limited support for character mode has appeared, by setting
920 <parameter>GraphicsDriver=ttydrv</parameter> in wine.conf's
921 <parameter>[wine]</parameter> section.
924 Wine's infrastructure is already somewhat prepared for supporting
925 other graphics drivers than x11drv, but no real "alternative"
926 graphics driver has been developed yet.
932 <question id="Will-Wine-run-under-any-X-window-manager">
933 <para>Will Wine run under any X window manager? Does it require a window manager at all?</para>
937 Wine is window manager independent, so the X window manager you
938 choose to run has (almost) no bearing on your ability to run MS
939 Windows programs under Wine. Wine uses standard X libraries, so no
940 additional ones are needed. Wine has its own window management,
941 which acts like MS Windows. It can be turned off to use the native
942 window manager by modifying Managed or Desktop settings as described
943 in <command>man wine.conf</command>.
949 <question id="Will-32-bit-applications-run-under-Wine">
950 <para>Will 32-bit Windows 95/98/ME/NT/2000/XP applications run under Wine?</para>
954 Yes, 32-bit programs are now well supported.
960 <qandadiv id="FAQ-Getting-Wine">
961 <title>Getting Wine</title>
963 <question id="Where-can-I-get-Wine">
964 <para>Where can I get Wine?</para>
968 Because of lags created by using a mirror, word of the latest release
969 may reach you before the release is actually available at the ftp
970 sites listed here. The sources are available from the following
976 <ulink url="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=77449">
977 http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=77449
983 <ulink url="http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/">
984 http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/
990 <ulink url="ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/">
991 ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/
998 <ulink url="ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/">
999 ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/
1006 <ulink url="ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/">
1007 ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/
1014 It should also be available from any other site that mirrors
1015 ibiblio.org, see <ulink url="http://www.ibiblio.org/pub/Linux/MIRRORS.html">http://www.ibiblio.org/pub/Linux/MIRRORS.html</>.
1016 Some of these sites may archive previous versions of Wine as well as the
1017 current one. To determine which is the latest one, look at the
1018 distribution file name, which will take the form
1019 Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution
1020 file name with the numbers for year, month and date, respectively.
1021 The latest one is the one to get.
1024 Wine binary packages are available for several OS'es and
1026 <ulink url="http://www.winehq.org/site/download">
1027 the download page</ulink> for the most recent list.
1033 <question id="Is-there-a-CVS-tree">
1034 <para>Is there a CVS tree?</para>
1038 Current Wine sources are also available via anonymous client/server
1039 CVS. You will need CVS 1.9 or above. If you are coming from behind a
1040 firewall, you will either need a hole in the firewall for the CVS
1041 port (2401) or use SOCKS.
1044 To login to the CVS tree, do
1047 export CVSROOT=:pserver:cvs@cvs.winehq.org/home/wine
1051 Use "cvs" as the password (without the quotes). Note that
1052 <filename>/home/wine</filename> is a path on the server, not on your
1053 machine. To check out the entire Wine source tree (which may be
1057 cvs -z 3 checkout wine
1060 or if you just want a subtree, or individual file, you can do that
1064 cvs -z 3 checkout wine/ANNOUNCE
1067 Be aware, though, that getting the entire Wine source tree via CVS
1068 is pretty slow, especially compared to getting Wine from an FTP
1069 mirror near you. For a CVS mirror list, see
1070 <ulink url="http://www.winehq.org/site/cvs#cvsservers">
1071 http://www.winehq.org/site/cvs#cvsservers</ulink>
1074 Patch files are also available, so that you don't have to download,
1075 install, and configure the entire distribution each month if you are
1076 current to the previous release. Patch file release names follow the
1077 same numbering convention as do the general releases, and take the
1081 Wine-YYYYMMDD.diff.gz
1084 Patch files are available from the same sites that distribute the
1085 full release. To upgrade to a new release by using a patch file,
1086 first cd to the top-level directory of the release (the one
1087 containing the README file), then do a "make clean", and patch the
1091 gunzip -c patch-file | patch -p1
1094 where patch-file is the name of the patch file something like
1095 Wine-YYYYMMDD.diff.gz. You can then re-run ./configure, and then run
1099 If you are mirroring the Wine distribution from the tsx-11 site and
1100 wish to be listed here in this FAQ, please add it to the
1101 "things to go into the documentation" area.
1107 <question id="Can-I-get-Wine-using-cvsup">
1108 <para>Can I get Wine using cvsup?</para>
1112 The CVS mirrors don't offer cvsup support yet, but the main server
1113 does. Use a <filename>wine.sup</filename> file of:
1116 *default host=cvs.winehq.org
1118 *default prefix=/cvs/wine
1119 *default release=wine
1122 # If your network link is a T1 or faster, comment out the following line.
1125 *default use-rel-suffix
1132 <qandadiv id="Installing-And-Configuring-Wine">
1133 <title>Installing and Configuring Wine</title>
1135 <question id="How-do-I-compile-the-Wine-source-code">
1136 <para>How do I compile the Wine distribution source code?</para>
1140 See the README (<ulink url="http://source.winehq.org/source/README">http://source.winehq.org/source/README</ulink>) for instructions.
1141 Additionally, you may want to set the <parameter>TMPDIR</parameter>
1142 environment variable <command>TMPDIR=~/tmp</command> or
1143 <command>TMPDIR=/tmp</command> (if you are root).
1149 <question id="How-do-I-install-Windows-in-Wine">
1150 <para>How do I install Windows in Wine under Linux?</para>
1154 Simple answer: you CAN'T. Windows demands direct access to the
1155 hardware and cannot get it with Wine and UNIX in the way
1158 Wine is supposed to be primarily used WITHOUT Windows. If you want
1159 to use a Windows installation, then use an existing installation
1160 alongside the UNIX installation (see the dual-boot HOWTO for your OS
1161 for more details). Or alternatively use the cabextract utility to
1162 extract Windows install archives to a directory that you want to use
1163 as Wine's Windows tree.
1169 <question id="How-do-I-configure-Wine-to-run-on-my-system">
1170 <para>How do I configure Wine to run on my system?</para>
1174 Wine requires that you have a config file as
1175 <filename>~/.wine/config</filename>. The format of this file is
1176 explained in the <filename>wine.conf</filename> man page. The file
1177 <filename>documentation/samples/config</filename>
1178 (<ulink url="http://source.winehq.org/source/documentation/samples/config">
1179 http://source.winehq.org/source/documentation/samples/config</ulink>)
1180 contains a config file example. More explicit directions can be
1181 found in the <filename>README</filename> file
1182 (<ulink url="http://source.winehq.org/source/README">
1183 http://source.winehq.org/source/README</ulink>) that will be located in
1184 the base Wine directory after you gunzip and untar the distribution
1191 <question id="How-do-I-upgrade-configuration">
1192 <para>How do I upgrade Wine without losing my working configuration?</para>
1196 Upgrading the wine installation does not affect the existing wine
1197 configuration. So after upgrading wine you still have the old (working )
1204 <question id="If-I-use-Windows-which-versions-OK">
1205 <para>If I want to use a Windows install, which versions are OK?</para>
1209 Either use a classic no-windows install (Wine is getting better all
1210 the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T
1211 configure Wine to use an NT-based Windows install (NT, Win2K, WinXP, Win2K3).
1214 In general, most Windows installations contain vast quantities of garbage
1215 that can confuse Wine and make it less reliable. If you can, it's best to
1216 install the programs you want into Wine's fake windows drive.
1222 <question id="If-I-use-Windows-which-one-works-best">
1223 <para>If I use a Windows install with Wine, which one works best?</para>
1230 I'd say Win98SE is the best version to use with Wine, as it's fairly
1231 widespread amongst developers and relatively old. Using Win2K files
1232 is <emphasis>definitely</emphasis> worse than a plain no-windows
1233 Wine install, and Win ME is said to be problematic, too (as probably
1234 no developer uses it). In short: all Win9x <= W98SE are good.
1240 <question id="Installing-Visual-Basic-apps-wont-run">
1242 Installing applications generated by Visual Basic won't run. What
1248 Make sure you have all the VB run time libraries installed. You can
1249 get the latest version from the Microsoft web site.
1255 <question id="When-I-click-on-exe-file-nothing-happens">
1256 <para>When I click on *.exe file in my file Manager, nothing happens.</para>
1260 The normal Wine releases don't have .exe extensions registered for
1261 Wine in KDE/Gnome yet. You have to open a terminal window instead
1262 (often an icon showing a "black screen") and type something like:
1265 cd /my/windows/program/directory
1272 <question id="bash-wine-Command-not-found-What-can-I-do">
1273 <para>bash says "wine: Command not found" What can I do?</para>
1277 Try to logout and login again into bash. That might fix it.
1280 If it doesn't, then make sure the wine binary is in your
1281 <parameter>PATH</parameter>.
1287 find / -name "wine" -type f -perm +111
1290 to find the path where the wine binary is in. Then check whether
1291 <parameter>PATH</parameter> includes it:
1297 If not, add that e.g. to <filename>/etc/profile</filename> by doing:
1300 export PATH=$PATH:/path/to/wine/binary
1306 If you used a package manager (<command>rpm</command> or
1307 <command>apt</command>) - Verify your packages. The package
1308 <filename>winesetuptk.rpm</filename> is only a front-end for
1309 making a meaningful config file, it DOES NOT install the wine
1313 For complete packages, use <ulink url="http://rpmseek.com/rpm-pl/wine.html?hl=com&cx=0::">
1314 http://rpmseek.com/</ulink> or the <ulink url="http://www.winehq.org/site/download">
1315 Download</ulink> section.
1321 <question id="How-do-I-remove-Wine-from-my-Computer">
1322 <para>How do I remove Wine from my Computer?</para>
1326 It depends on how you installed. If you used an RPM, the right command is this:
1327 <command>rpm -e wine (as root)</command>
1330 If you installed from source (the .tar.gz file), the right
1331 way to do it is to change to the root of the source tree (the directory with the configure script,
1332 readme etc) then run as root:
1333 <command>make uninstall</command>
1339 <qandadiv id="About-running-Wine">
1340 <title>About running Wine</title>
1342 <question id="How-do-I-run-an-MS-Windows-program">
1343 <para>How do I run an MS Windows program under Wine?</para>
1347 When invoking Wine, you must specify the entire path to the
1348 executable, or by file name only. For example to run Windows'
1349 solitaire, type any of the following:
1354 <command>wine sol</command> or <command>wine sol.exe</command>
1355 (using the search path to locate the file).
1360 <command>wine c:\\windows\\sol.exe</command>
1361 (using a DOS file name).
1366 <command>wine /usr/windows/sol.exe</command>
1367 (using a UNIX file name).
1372 <command>wine "c:\windows\sol.exe"</command>
1373 (using quoted DOS file name).
1378 The path of the file will also be added to the path when a full name
1379 is supplied on the command line.
1386 <question id="Wine-cannot-find-MS-Windows-on-my-drive">
1388 I have installed and configured Wine, but Wine cannot find MS
1389 Windows on my drive. Where did I go wrong?
1394 If you have a DOS partition, first make sure that you have mounted
1395 it, either by putting the entry into <filename>/etc/fstab</filename>,
1396 or by manually mounting it.
1399 Remember too that unless your version of UNIX can see through it, or
1400 you are running a utility that can see through it, your DOS
1401 partition must not be located on a Drivespaced, Doublespaced or
1402 Stackered partition, as neither Linux, FreeBSD, NetBSD or Wine can
1403 natively 'see' files located in these compressed DOS partitions.
1406 Check your path statements in the <filename>wine.conf</filename>
1407 file. No capital letters may be used in paths, as they are
1408 automatically converted to lowercase.
1414 <question id="Parts-of-my-app-do-not-work-What-is-wrong">
1416 I was able to get various MS Windows programs to run, but parts of
1417 them do not work. What is wrong?
1422 Wine is not complete at this time, so some of each programs'
1423 features may not work. They will in time as more of the MS
1424 Windows API calls are included in Wine.
1430 <question id="Menus-do-not-work-how-can-I-exit">
1432 I have run various MS Windows programs, but since the program menus
1433 do not work, how can I exit these programs?
1438 Kill the xterm shell window that you called up to run your MS
1439 Windows program, and the X window that appeared with the program
1446 <question id="My-app-doesnt-work-what-can-i-do">
1448 My program doesn't work, what can I do?
1453 If you are a programmer and know C, then start debugging
1454 Wine and help us make it better! If you can't, then you will
1455 have to either convince a Wine developer to try and make your
1456 program work (there must be a downloadable version or demo for that).
1459 You can submit your application to the <ulink url="http://appdb.winehq.org/">
1460 Wine Application DB </ulink> and gather tips on ways to get your app to work its best.
1463 You can also submit your application to the CodeWeavers CrossOver
1464 <ulink url="http://www.codeweavers.com/site/compatibility/"> Compatibility </ulink> Center.
1465 Where you can pledge/vote toward future support of your favorite application.
1468 Alternatively, you may be able to get the app working by
1469 taking native DLLs from a Microsoft Windows install, and using
1470 them (set the dlls to native in the config file). Not all DLLs
1471 can be replaced that way - in particular DirectX cannot be, nor
1472 can some core system DLLs like gdi32, user, ntdll, kernel32 etc.
1478 <question id="Can-I-use-Wine-with-other-Linux-Distros">
1479 <para>Can I use Wine with SUSE, RedHat or other Linux Distro's?</para>
1483 You can use Wine on any sufficiently recent Linux installation. The
1484 amount of work getting Wine up and running depends on whether you
1485 install a binary packages or do a source install.
1491 <question id="Does-Wine-work-with-AMD-Processors">
1492 <para>Does Wine work with AMD Processors?</para>
1496 Yes, it does. Wine should work on any processor compatible with
1497 the Pentium or greater.
1503 <question id="Can-I-launch-Unix-app-from-Windows-app">
1504 <para> Can I launch a Unix program from a Windows program?</para>
1508 Sure, Wine supports that. Just enter the unix program name wherever
1509 a program has something that it's supposed to execute, and it
1515 <question id="Error-with-installshield-6">
1517 I get <quote>Error installing iKernel.exe: (0x1400)</quote>
1518 when running an InstallShield 6 installer.
1523 If you get the error "Error installing iKernel.exe: (0x1400)" at any
1524 point, it's probably because there are leftover processes from a
1525 previous try. You can verify this with the command
1527 <para><prompt>$ </><command>ps augxw | grep wine</command></para>
1529 If that command shows old copies of wine running your setup,
1530 you need to kill them before you can run the setup program.
1531 If there are no other Wine programs running, you can kill them
1532 all with the command
1534 <para><prompt>$ </><command>killall wine</command></para>
1536 If you're also running Wine programs you care about, you'll
1537 have to kill off the old Setup instances one by one using
1538 kill and the individual PIDs (or perhaps Wine's spiffy Task Manager,
1539 which doesn't exist yet).
1542 You should repeat the <command>ps</command> to make sure all of the old
1543 Wine processes are gone.
1549 <qandadiv id="Getting-help">
1550 <title>Getting help</title>
1552 <question id="Is-there-any-documentation-for-Wine">
1553 <para>Is there any documentation for Wine?</para>
1557 Yes, see <ulink url="http://www.winehq.org/site/documentation">
1558 http://www.winehq.org/site/documentation.</ulink>
1564 <question id="I-have-written-some-documententation">
1566 I couldn't find the answer to my question in the documentation, but
1567 I've written a document explaining how to solve it. What should I do?
1572 Updates and additions to the Wine documentation directory should be
1573 sent to the wine-patches mailing list at
1574 <ulink url="http://www.winehq.org/site/forums">
1575 http://www.winehq.org/site/forums</ulink>. Website and FAQ
1576 additions should be added to the appropriate Wine Knowledge base directory.
1582 <question id="Is-there-a-Usenet-newsgroup-for-Wine">
1583 <para>Is there a Usenet newsgroup for Wine?</para>
1587 Yes, and it's called
1588 <ulink url="news:comp.emulators.ms-windows.wine">
1589 comp.emulators.ms-windows.wine</ulink>. The newsgroup serves as a
1590 place for users and developers to discuss Wine, and for minor
1591 announcements for the general public. Major announcements will be
1592 cross posted to other appropriate newsgroups, such as the following:
1597 <ulink url="news:comp.os.linux.announce">
1598 comp.os.linux.announce</ulink>
1603 <ulink url="news:ccomp.windows.x.announce">
1604 comp.windows.x.announce</ulink>
1609 <ulink url="news:ccomp.emulators.announce">
1610 comp.emulators.announce</ulink>
1615 If your Usenet site does not carry these newsgroups, please urge
1616 your ISP's sysadmin to add and/or uplink them.
1622 <question id="Is-there-a-World-Wide-Web-site-for-Wine">
1623 <para>Is there a World Wide Web site for Wine?</para>
1627 Wine HQ (<ulink url="http://www.winehq.org">http://www.winehq.org</ulink>) is the official site.
1633 <question id="Is-there-an-IRC-channel-for-Wine">
1634 <para>Is there an IRC channel for Wine?</para>
1638 Sure. It's channel <filename>#WineHQ</filename> on
1639 <filename>irc.freenode.net</filename> see
1640 (<ulink url="http://freenode.net">http://freenode.net</ulink>).
1641 Usually several Wine developers hang out there just to help YOU ;-)
1647 <question id="I-think-I-found-a-bug-How-do-I-report-it">
1649 I think I've found a bug. How do I report this bug to the Wine
1655 Bug reports should be submitted to our online Bugzilla system
1656 (<ulink url="http://bugs.winehq.org/">http://bugs.winehq.org/</ulink>).
1657 You should include at least the following:
1662 The Wine version tested
1667 The Windows application name, including the version, and, if
1668 applicable, a URL the application can be downloaded from
1673 A brief description of the bug
1678 The relevant part(s) of the output of the Wine debugger
1683 A screenshot of the visual problem, if applicable
1688 For more information about reporting bugs please see the
1689 <ulink url="http://www.winehq.org/Docs/wine-user/bug-reporting.shtml">
1690 How to report a bug</ulink> section of the Wine Users Guide.
1696 <qandadiv id="Helping-Wine-or-becoming-a-Wine-developer">
1697 <title>Helping Wine or becoming a Wine developer</title>
1699 <question id="How-do-I-become-a-Wine-developer">
1700 <para>How do I become a Wine developer? What do I need to know?</para>
1704 If you can program C, that's a good start. Download the sources via
1705 (<ulink url="http://www.winehq.org/site/cvs">CVS,</ulink>)
1706 subscribe to the mailing lists, look around the source, and
1707 pay attention to the comp.emulators.ms-windows.wine newsgroup
1708 and the mailing lists (<ulink
1709 url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>).
1710 See if there's anything that you think you can fix or work
1711 on. You won't have much trouble finding areas that need work
1712 in Wine (grep for FIXMEs in the source).
1718 <question id="How-can-I-contribute-to-the-Wine-project">
1719 <para>How can I help contribute to the Wine project, and in what way(s)?</para>
1723 You can contribute programming or documentation skills, or monetary
1724 or equipment donations, to aid the Wine developers in reaching their
1728 For a list of ideas of how you can help, please consult the
1729 <ulink url="http://www.winehq.org/site/contributing">
1730 Wine contrib page</ulink>.
1736 <question id="I-want-to-help-beta-test-Wine">
1737 <para>I want to help beta test Wine. How can I do this?</para>
1741 Wine still consists of some Alpha code at this time. However, anyone
1742 is welcome to download the latest version, and try it out at any
1749 <question id="I-wrote-some-code-I-would-like-to-submit">
1751 I have written some code that I would like to submit to the Wine
1752 project. How do I go about doing this?
1757 Submitting a patch for inclusion in Wine is pretty simple.
1758 Basically all you have to do is send the patch to the
1759 wine-patches mailing list
1760 (<ulink url="http://www.winehq.org/mailman/listinfo/wine-patches">http://www.winehq.org/mailman/listinfo/wine-patches</>).
1761 Still there are a couple of recommendations about the patch format
1762 and all so it's best to read our page describing <ulink
1763 url="http://www.winehq.org/site/sending_patches">how to submit
1764 patches</>. This will also give you more details about the whole
1765 process and in particular to what will happen to your patch once
1772 <qandadiv id="Developing-programs-using-Wine-WineLib">
1773 <title>Developing programs using Wine/WineLib</title>
1775 <question id="Can-I-use-Wine-to-port-Win32-sources-to-Unix">
1776 <para>Can I use Wine to port my Win32 sources to Unix?</para>
1780 That is the idea of Winelib. Right now you may still have some
1781 difficulties, but this is changing all the time. Read the
1782 <ulink url="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</ulink> for info.
1788 <question id="Will-MFC-work-with-Wine-What-do-I-need-to-do">
1789 <para>Will MFC work with Wine? What do I need to do?</para>
1793 Wine is not implementing an MFC replacement nor does it intend to.
1794 However it is possible (with a lot of work) to compile the MFC from
1795 source and thus produce an <filename>mfc42.dll.so</filename> library.
1799 <ulink url="http://www.winehq.org/Docs/winelib-user/">Winelib User's Guide</ulink> for how to do this.
1805 <question id="Are-there-commercial-apps-ported-using-Wine">
1807 Are there any commercial applications which have been ported
1813 Here are few examples of applications ported using Wine or Winelib:
1818 Corel's WordPerfect Office Suite 2000 was ported to Linux using
1824 Kylix, the Linux version of Delphi, was ported to Linux using
1825 Winelib. The IDE actually uses a combination of QT and Winelib
1826 which would not have been possible to achieve using only Wine.
1827 The generated applications however do not depend on Wine in
1833 MusicMatch Jukebox 5 has also been
1834 <ulink url="http://www.itworld.com/nl/lnx_desktop/01042001/">ported</>
1835 to Linux using Winelib. However more recent versions have not, and
1836 version 5 is no longer available.
1842 (<ulink url="http://www.ability.com/linux/abilitylinux.php">http://www.ability.com/linux/abilitylinux.php</ulink>)
1848 (<ulink url="http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)
1853 Many other important applications have already been ported. (we are
1854 speaking of several top 500 applications here)
1860 <question id="How-can-I-detect-Wine">
1861 <para>How can I detect Wine?</para>
1865 You really shouldn't want to do this. If there's a quirk in Wine
1866 you need to work around, it's much better to fix it in Wine.
1874 <qandadiv id="Wine-HQ-issues">
1875 <title>Wine HQ issues</title>
1877 <question id="Why-are-the-maillists-set-to-reply-to-author">
1879 Why are the mailing lists set to reply to author, not to mailing list?
1884 There are some very valid reasons for doing so.
1890 <question id="How-to-unsubscribe-from-the-mailing-lists">
1891 <para>How to unsubscribe from the mailing lists?</para>
1895 Please see: <ulink url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>
1896 And select [(Un-)Subscribe]
1905 <!-- Keep this comment at the end of the file
1908 sgml-parent-document:("wine-devel.sgml" "book" "part" "chapter" "")