<!-- *** Wine FAQ *** -->
<title>Wine FAQ</title>
- <para>
- For technical questions, visit the
- <ulink url="http://www.winehq.org/fom-meta/cache/19.html">
- Wine Troubleshooting Guide</ulink> instead.
- </para>
<qandaset>
<qandadiv id="About-this-FAQ"><title>About this FAQ</title>
</question>
<answer>
<para>Dave Gardner maintained it from 1995-1998.</para>
- <para>Douglas Ridgway (ridgway@winehq.com) took it over in 1999.</para>
- <para>Andreas Mohr (amohr@codeweavers.com) converted it to FAQ-O-Matic in 2000.</para>
- <para>Dimitrie O. Paun, Keith Matthews and Thomas Wickline reorganised it in 2002.</para>
+ <para>Douglas Ridgway took it over in 1999.</para>
+ <para>Andreas Mohr converted it to FAQ-O-Matic in 2000.</para>
+ <para>Dimitrie O. Paun, Keith Matthews and Tom Wickline (in alphabetical order) reorganized it in 2002.</para>
<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">
- <para>What is the copyright on the FAQ? And how may I use it?</para>
+ <para>What is the copyright of this FAQ? And how may I use it?</para>
</question>
<answer>
<para>The original Wine FAQ, which this FAQ was based on, was copyright © 1995-1998 David Gardner.</para>
<answer>
<para>
Wine is a program which allows the operation of DOS and MS
- Windows programs (Windows 3.x and Win32 executables) on UNIX.
+ Windows programs (Windows 3.x and Win32 executables) on UNIX operating systems such as Linux.
It consists of a program loader, which loads and executes a Windows
- binary, and a library that implements Windows API calls using
- their UNIX or X11 equivalents. The library may also be used
+ binary, and a set of libraries that implements Windows API calls
+ using their UNIX or X11 equivalents. The libraries may also be used
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
- in each distribution) is LGPL style.
+ in each distribution) is the LGPL.
</para>
</answer>
</qandaentry>
<qandaentry>
<question id="Is-Wine-an-emulator">
- <para> Is Wine an emulator?</para>
+ <para>Does Wine emulate a full computer?</para>
</question>
<answer>
<para>
- Fortunately, no. Wine provides low-level binary compatibility,
- but currently only for OSes running on Intel-compatible chips.
+ No, as the name says, Wine Is Not a (CPU) Emulator. Wine just
+ provides the Windows API. This means that you will need an
+ 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
+ this is more due to the fact that Microsoft has heavily optimized parts of their
+ 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.
</para>
</answer>
- </qandaentry
+ </qandaentry>
<qandaentry>
<question id="Are-here-any-alternatives-to-Wine">
Note that, like Wine, they can only use the hardware platform that
the target programs were originally compiled for (see below).
</para>
+
</answer>
</qandaentry>
<answer>
<para>
There are two free x86 hardware emulators:
- <ulink url="http://bochs.sourceforge.net">bochs</ulink>, and
- <ulink url="http://savannah.nongnu.org/projects/plex86">plex86</ulink>.
+ <ulink url="http://bochs.sourceforge.net">Bochs</ulink>, and
+ <ulink url="http://savannah.nongnu.org/projects/plex86">Plex86</ulink>.
</para>
<para>
- Plex86 is the opensource free-software alternative for VMWare,
+ Plex86 is the open-source free-software alternative for VMWare,
VirtualPC, and other IA-32 on IA-32 "Virtual PC products." It
can only run on the IA-32 architecture.
</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,
- bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
+ Bochs can be compiled to emulate a 386, 486 or Pentium CPU. Bochs is capable
of running most Operating Systems inside the emulation including Linux,
Windows® 95, DOS, and recently Windows® NT 4.
</para>
<para>
- 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 real
- time binary compiler. The drawback of all emulators is that you need a version
- of Windows in order to run Windows.
+ 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
+ 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
+ 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
+ command line as well as menus. The clipboard also works seamlessly at this time.
+ </para>
+
+ </answer>
+ </qandaentry>
+
+ <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
+ data types they exchange. It is not uncommon for a Windows API to
+ 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
+ performance you lose due to Wine running inside the emulator
+ 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
+ <ulink url="http://www.transitives.com/">Transitives Technologies</>.
+ </para>
</answer>
</qandaentry>
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
- that application's window side by side with native application
- windows, copy/paste from one to the other, and run it all at full speed.
+ that application's window side by side with native applications,
+ copy/paste from one to the other, and run it all at full speed.
</para>
<para>
- It is also a pretty vital part of migrating a large organisation,
+ It is also a pretty vital part of migrating a large organization,
you can't change a 5000 desktop setup overnight without a lot of risk.
</para>
+
+ </answer>
+ </qandaentry>
+
+ <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
+ 3, drivers have to deal with specific memory management issues, and use
+ 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>
<variablelist>
<varlistentry>
- <term><ulink url="http://www.winehq.com">Wine</ulink></term>
+ <term><ulink url="http://www.winehq.org">Wine</ulink></term>
<listitem>
<para>
- This is the "standard" source distribution of Wine. Its license is
- LGPL, it can be downloaded for free.
+ 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.
</para>
</listitem>
</varlistentry>
-
- <varlistentry>
- <term><ulink url="http://rewind.sourceforge.net">ReWind</ulink></term>
- <listitem>
- <para>
- This is a forked Wine tree that got created when Wine changed its
- license from X11 to the more restrictive LGPL, in order to let
- people continue to maintain an X11 licensed Wine version. Its
- license is X11, it can be downloaded for free.
- </para>
- </listitem>
- </varlistentry>
-
+
<varlistentry>
- <term><ulink url="http://www.transgaming.com">Transgaming's WineX</ulink></term>
+ <term><ulink url="http://www.transgaming.com">TransGaming's Cedega</ulink></term>
<listitem>
<para>
- This is TransGaming's Wine version specially suited for games.
- It includes Direct3D support (thus its DirectX support is much
- more complete than Wine's) and copyprotection support. Its license
- is AFPL, the source distribution can be downloaded for free, but
- the binary pack ages that include copy protection support and good
- support are only for subscribed customers ($5/month).
+ This is TransGaming's Wine version specially suited for
+ games. It includes more mature Direct3D support than
+ WineHQ, although these days WineHQ has quite advanced
+ D3D support as well. Most of the code is under the AFPL
+ and can be downloaded for free.
</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><ulink url="http://wine.codeweavers.com">Codeweavers' Wine preview</ulink></term>
- <listitem>
<para>
- This is a specially packaged and more stable/older version of Wine
- which has a nice setup for easy installation. License X11, free
- download.
+ However TransGaming also distributes binaries that contain
+ improved copy protection support (needed for many
+ games), support, and other enhancements. These packages are
+ only available in binary form to subscribed customers
+ ($5/month, minimum three months).
</para>
</listitem>
</varlistentry>
-
- <varlistentry>
- <term><ulink url="http://www.codeweavers.com/products/crossover/">Codeweavers' Crossover Plugin</ulink></term>
- <listitem>
- <para>
- Special Wine installation to be used for running win32 browser
- plugins such as e.g. Quicktime in Linux browsers. Costs $24.95.
- Well worth it (very stable and useful packaging).
- </para>
- </listitem>
- </varlistentry>
<varlistentry>
- <term><ulink url="http://www.codeweavers.com/products/office/">Codeweavers' Crossover Office</ulink></term>
+ <term><ulink url="http://www.codeweavers.com/site/products/cxoffice/">CodeWeavers' CrossOver Office</ulink></term>
<listitem>
<para>
Wine version with special packaging to make sure almost all
- important Office type programs work pretty well. Costs $54.95.
+ important Office type programs work pretty well. Costs $74.95
+ for the Pro version and $39.95 for the Standard version.
Seems to be well worth it so far according to some comments.
- (note: you're supporting a company actively contributing to wine
- if you decide to buy either Plugin or Office.
+ (note: you're supporting a company actively contributing to Wine
+ if you decide to buy CrossOver.)
</para>
</listitem>
</varlistentry>
-
- <varlistentry>
- <term><ulink url="http://www.winehq.org/download/">Other packaged versions of Wine</ulink></term>
+
+ <varlistentry>
+ <term><ulink url="http://www.codeweavers.com/site/products/cxserver/">CodeWeavers' CrossOver Office Server Edition</ulink></term>
<listitem>
<para>
- Various wine packages can be downloaded for free, to be found at
- Wine HQ. They're not officially packaged by Wine HQ, and as such
- may have some configuration inconsistencies.
+ 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:
+ <ulink url="http://www.codeweavers.com/site/products/pricing/">CrossOver Office Server Edition Pricing</ulink>
</para>
</listitem>
- </varlistentry>
+ </varlistentry>
+
</variablelist>
</answer>
</qandaentry>
applications became popular.
</para>
<para>
- For more information, see <ulink url="http://www.winehq.com/about.shtml">
- http://www.winehq.com/about.shtml</ulink>
+ For more information, see <ulink url="http://www.winehq.com/site/history">
+ http://www.winehq.com/site/history</ulink>
</para>
</answer>
</qandaentry>
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
- <ulink url="http://www.winehq.com">Wine HQ homepage</ulink>. When
+ <ulink url="http://www.winehq.org">Wine HQ homepage</ulink>. When
downloading Wine from your FTP site of choice (see
- <ulink url="http://www.winehq.com/download.shtml">the Download page</ulink>
+ <ulink url="http://www.winehq.org/site/download">the Download page</ulink>
for some of these choices), you can make sure that you are getting
the latest version by watching the version numbers in the distribution
- filename. For instance, the distribution released on October 31, 2002
- was called Wine-20021031.tar.gz. Patch files are also available. If
+ file name. For instance, the distribution released on August 13, 2004
+ was called Wine-20040813.tar.gz. Patch files are also available. If
you are current to the previous version, you can download and apply
just the current patch file rather than the entire new distribution.
- The patch filenames follow the same conventions as the monthly
- distribution. <ulink url="http://www.winehq.com/dev.shtml">
+ The patch file names follow the same conventions as the monthly
+ distribution. <ulink url="http://www.winehq.org/site/cvs">
Read-only CVS</ulink> access is also available.
</para>
</answer>
</question>
<answer>
<para>
- As of mid 2002, Wine consists of over 1 million lines of C code,
- written by more than 300 developers from dozens of countries around
+ 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
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
- <ulink url="http://www.winehq.com/about/index.php?status">
+ <ulink url="http://www.winehq.org/site/status">
Status page</ulink> for a global view on Wine's implementation progress.
</para>
</answer>
<para>
Large software projects are never finished, only released. In any
case Wine is chasing a moving target since every new release of
- Windows contains new API calls or variations to the existing ones.
+ Windows contains new API calls or variations on the existing ones.
</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
- we are working on releasing Wine 0.9 during 2003
+ we are working on releasing Wine 0.9 Real Soon Now(tm).
</para>
</answer>
</qandaentry>
<qandaentry>
<question id="Who-is-responsible-for-Wine">
- <para>Who's responsible for Wine?</para>
+ <para>Who is responsible for Wine?</para>
</question>
<answer>
<para>
Wine is available thanks to the work of many people. Please see the
- <ulink url="http://www.winehq.com/source/AUTHORS">AUTHORS</ulink>
+ <ulink url="http://source.winehq.org/source/AUTHORS">AUTHORS</ulink>
file in the distribution for the complete list. Some companies that
- are or have been involved with Wine development are Codeweavers,
+ are or have been involved with Wine development are CodeWeavers,
TransGaming, Corel, and Macadamian.
</para>
</answer>
</qandaentry>
- <qandaentry>
- <question id="folks-who-contributed-money-or-equipment">
- <para>Who are the folks and organizations who have contributed money or equipment to the Wine project?</para>
- </question>
- <answer>
- <para>
- People and organizations who have given generous contributions of
- money, equipment, or licenses, include:
- </para>
- <itemizedlist spacing="compact">
- <listitem>
- <para>David L. Harper</para>
- </listitem>
- <listitem>
- <para>Bob Hepple</para>
- </listitem>
- <listitem>
- <para>Mark A. Horton</para>
- </listitem>
- <listitem>
- <para>Kevin P. Lawton</para>
- </listitem>
- <listitem>
- <para>The Syntropy Institute</para>
- </listitem>
- <listitem>
- <para>James Woulfe</para>
- </listitem>
- <listitem>
- <para>
- VMWare Inc. (<ulink url="http://www.vmware.com">
- http://www.vmware.com</ulink>)
- </para>
- </listitem>
- <listitem>
- <para>
- Corel (<ulink url="http://www.corel.com">
- http://www.corel.com</ulink>)
- </para>
- </listitem>
- </itemizedlist>
- </answer>
- </qandaentry>
-
<qandaentry>
<question id="What-undocumented-APIs-are-not-understood">
<para>What undocumented APIs / interfaces are not understood? Would
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
- engineering have been necessary, particularly in the shell (Explorer)
- interface.
+ engineering has been necessary, particularly in the shell (Explorer)
+ 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.
</para>
</answer>
</qandaentry>
No, it's not.
</para>
<para>
- TransGaming make money via a subscription service. Thus they
- submitted their DirectDraw and some DirectSound work, but they will
- not submit their OpenGL wrapper based Direct3D support.
+ TransGaming makes money via a subscription service and the license
+ of their Cedega tree is incompatible with the Wine license. Thus
+ Cedega patches cannot be integrated into the Wine tree without
+ express permission by TransGaming. They have submitted some
+ of their work for integration into Wine, most notably DirectDraw
+ and some DirectSound work, and such work has been integrated into
+ the Wine tree. However it seems highly unlikely they will ever submit their
+ Direct3D work.
</para>
</answer>
</qandaentry>
</question>
<answer>
<para>
- Some people are working on getting Wine code to compile on Windows.
+ Some people are working on getting Wine code to compile on Windows
+ using one of the following projects as a basis:
</para>
<itemizedlist spacing="compact">
<listitem>
<para>
- Cygwin (<ulink url="http:/www.cygwin.com">
- http://www.cygwin.com/</ulink>)
+ Cygwin
+ (<ulink url="http:/www.cygwin.com/">http://www.cygwin.com</ulink>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ MinGW
+ (<ulink url="http:/www.mingw.org/">http://www.mingw.org</ulink>)
</para>
</listitem>
<listitem>
<para>
- Reactos (<ulink url="http://www.reactos.com/">
- http://www.reactos.com/</ulink>)
+ ReactOS
+ (<ulink url="http://www.reactos.com/">http://www.reactos.com</ulink>)
</para>
</listitem>
</itemizedlist>
<para>
There's some progress, so a Wine version that's usable on Windows
- might be available at some time.
+ might be available at some time in the future.
+ </para>
+ <para>
+ Part of the rationale for these projects is to find out areas where
+ Wine portability is lacking. This is especially true of the
+ ReactOS project which is a reimplementation of the Windows kernel
+ 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>
</answer>
</qandaentry>
-
+
+ <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>
+
</qandadiv>
<qandadiv id="What-do-I-need-in-order-to-use-Wine">
<title>What do I need in order to use Wine?</title>
</question>
<answer>
<para>
- Wine is being developed specifically to run on the <emphasis>Intel x86</emphasis> class of CPUs under certain UNIXes that run on the x86 platform.
- Winelib however is capable of porting Windows program <emphasis>source code</emphasis> to other platforms also, not only x86.
+ 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 programs via Wine on other platforms (e.g. MacOS X) is <emphasis>not</emphasis> possible; the only way to run Windows code
- on MacOS X would be to take Windows program source code and recompile it for e.g. MacOS X using Winelib.
+ 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.
</para>
<para>
- The following will list the x86 operating systems supported by
- Wine; Winelib support for other platforms keeps evolving,
+ These are the platforms supported by Wine.
+ Winelib support for other platforms keeps evolving,
so it's not specifically listed here.
</para>
<para>
- NetBSD, OpenBSD, Unixware, and SCO OpenServer 5 worked at one time,
+ NetBSD, OpenBSD, UnixWare, and SCO OpenServer 5 worked at one time,
but Wine now requires kernel-level threads which are not currently
- available (or understood by the Wine team) in those platforms.
+ available (or understood by the Wine team) on those platforms.
</para>
<para>
The Wine development team hopes to attract the interest of other
commercial UNIX and UNIX clone vendors as well.
</para>
<para>
- BeOS: porting efforts used to be pretty strong, but BeOS has severe
- limitations in Unix call support, so a port will probably never
- happen.
+ 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.
</para>
<para>
- FreeBSD: Should work, with limitations in specific areas (mainly
- missing device/hardware support)
+ FreeBSD: This port is well maintained and should work with
+ limitations in specific areas (mainly missing device/hardware
+ support).
</para>
<para>
- Linux/x86: WORKS. If it doesn't, You may also want to see the
- <ulink url="http://www.winehq.org/fom-meta/cache/19.html">Wine
- Troubleshooting Guide</ulink>
+ Linux/x86: Works, and as the most popular platform for both
+ developers and users, it is the best supported platform of all.
</para>
</answer>
</qandaentry>
<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
- to the vast range of applications out there.
+ 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.
</para>
</answer>
</qandaentry>
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>
+ <para>
+ Binary packages, especially those not containing debug information,
+ have much lower disk space requirements, usually in the 20MB range.
+ </para>
</answer>
</qandaentry>
<qandaentry>
<question id="What-other-software-do-I-need-to-compile">
<para>
- What other software do I need to have installed to compile and run
+ What other software do I need to install, compile and run
Wine?
</para>
</question>
<answer>
<para>
- Many development tools need to be installed in order to compile Wine.
+ Many development tools are needed in order to compile Wine.
A list of required packages for several distributions is included in
- the README (<ulink url="http://www.winehq.com/source/README">
- http://www.winehq.com/source/README</ulink>).
+ the README (<ulink url="http://source.winehq.org/source/README">
+ http://source.winehq.org/source/README</ulink>).
</para>
<para>
To run Wine, you will need the following:
on how memory hungry the application is.
</para>
<para>
- A Wine workstation will work with 16 megabytes of RAM and a 16
- megabyte swap partition as long as you have a reasonable graphics
- card. Most applications will run reasonably with 64/64 Mb,
- interactive games are likely to need more. You can run Wine with 8/8,
- but it is going to be unusably slow and very constraining on the
- applications you can run. If you wish to be part of the development
- team and program Wine itself, be aware that the debugger is rather
- memory intensive. Some have suggested that 64 megabytes is the
- minimum RAM needed for Wine development, although some are able to
- work (albeit slowly) with 24 megabytes of physical RAM and lots of
- swap space.
+ 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.
</para>
</answer>
</qandaentry>
<answer>
<para>
Wine is getting to be quite large, and building from scratch takes a
- lot of processing. As of September 2002, compile times were around 20
- minutes on an Athlon 1200 with 640 Mb and 45-50 minutes on a Cyrix
- 300 with 64 Mb. If you have a CVS copy, you may not need to rebuild
- the whole thing every time you update.
+ 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.
</para>
</answer>
</qandaentry>
<answer>
<para>
Yes, but only if the operating system supports mounting those types
- of drives.There is a Linux file system driver called dmsdos that will
- allow read/write access through Doublespaced and Drivespace 1.0
+ of drives. There is a Linux file system driver called dmsdos that
+ will allow read/write access to Doublespaced and Drivespace 1.0
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/">
- ftp://metalab.unc.edu/pub/Linux/system/file systems/dosfs/</ulink>
+ ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink>
</para>
</answer>
</qandaentry>
</para>
</answer>
</qandaentry>
-
+
<qandaentry>
<question id="Does-MS-Windows-need-to-be-installed">
<para>
</question>
<answer>
<para>
- Many folks have successfully installed and run some small programs
- in their UNIX filesystem without having a DOS partition or MS
+ Many folks have successfully installed and run programs
+ in their UNIX file system without having a DOS partition or MS
Windows. However, in many cases you need a directory and file
infrastructure that is similar to an existing Windows installation.
Some applications' installation programs want to distribute some of
the package's files into the /windows and /windows/system
directories in order to run, and unless these exist on your UNIX
file system, those programs will not install correctly and probably
- will not run well, if at all.
+ will not run well, if at all. Most packages will set that up for you
+ as part of the install process.
</para>
<para>
If you have a DOS partition with MS Windows installed in it, make
[Drive C]
Path=/var/lib/wine
Type=hd
- Label=MS-DOS
- Filesystem=win95
[wine]
Windows=c:\windows
System=c:\windows\system
machine. If you have DOS/MS Windows installed on your system, you can
mount that partition at bootup by modifying the file
<filename>/etc/fstab</filename> in your UNIX partition (assuming that
- the UNIX kernel supports the DOS/MS Windows filesystem type).
+ the UNIX kernel supports the DOS/MS Windows file system type).
</para>
<para>
If you edit this file by hand, it should contain something similar
</para>
</answer>
</qandaentry>
-
+
<qandaentry>
<question id="If-Wine-completely-replaces-MS-Windows">
<para>
</question>
<answer>
<para>
- Most of them, yes. However, some applications and applets that come
- with MS Windows, such as File Manager and Calculator, can be
- considered by some to be redundant, since 32-bit UNIX programs that
- duplicate these applets' functions already exist.
+ 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
+ application (e.g. the Visual Basic run time). This also
+ 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
+ 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
+ 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
+ <ulink url="http://www.gnome.org/">Gnome</ulink> or
+ <ulink url="http://www.kde.org/">KDE</ulink> desktop environments. You
+ will get the added benefit that your contribution will then be
+ usable by everyone, not just by Wine users.
</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="Will-I-install-on-ony-UNIX-file-system">
+ <question id="Will-I-install-on-any-UNIX-file-system">
<para>
Will I be able to install MS Windows applications in any flavor of a
UNIX file system?
</para>
</answer>
</qandaentry>
-
+
<qandaentry>
<question id="Will-Wine-run-only-under-X">
- <para> Will Wine run only under X, or can it run in character mode?</para>
+ <para>Will Wine run only under X, or can it run in character mode?</para>
</question>
<answer>
<para>
- Most of Wine's development effort is geared against MS Windows' GUI,
+ Most of Wine's development effort is geared towards MS Windows' GUI,
but some limited support for character mode has appeared, by setting
<parameter>GraphicsDriver=ttydrv</parameter> in wine.conf's
<parameter>[wine]</parameter> section.
<para>
Wine's infrastructure is already somewhat prepared for supporting
other graphics drivers than x11drv, but no real "alternative"
- graphics driver has been used yet.
+ graphics driver has been developed yet.
</para>
</answer>
</qandaentry>
-
+
<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>
<qandaentry>
<question id="Will-32-bit-applications-run-under-Wine">
- <para>Will 32-bit Windows 95/98 applications run under Wine?</para>
+ <para>Will 32-bit Windows 95/98/ME/NT/2000/XP applications run under Wine?</para>
</question>
<answer>
<para>
- Yes, 32-bit programs are now about as well supported as 16-bit
- programs.
+ Yes, 32-bit programs are now well supported.
</para>
</answer>
</qandaentry>
-
+
</qandadiv>
<qandadiv id="FAQ-Getting-Wine">
<title>Getting Wine</title>
</question>
<answer>
<para>
- Because of lags created by using mirror, word of this newest release
+ Because of lags created by using a mirror, word of the latest release
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>
+ <listitem>
+ <para>
+ <ulink url="http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=77449">
+ http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=77449
+ </ulink>
+ </para>
+ </listitem>
<listitem>
<para>
<ulink url="http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/">
</itemizedlist>
<para>
It should also be available from any other site that mirrors
- ibiblio.org. For more download locations, see
- <ulink url="http://ftp search.lycos.com.">lycos</ulink> Some of
- these ftp sites may archive previous versions of Wine as well as the
+ 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
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
<para>
Wine binary packages are available for several OS'es and
distributions. See
- <ulink url="http://www.winehq.com/download.shtml">
+ <ulink url="http://www.winehq.org/site/download">
the download page</ulink> for the most recent list.
</para>
</answer>
To login to the CVS tree, do
</para>
<screen>
-export CVSROOT=:pserver:cvs@cvs.winehq.com/home/wine
+export CVSROOT=:pserver:cvs@cvs.winehq.org/home/wine
cvs login
</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
- <ulink url="http://www.winehq.com/dev.shtml">
- http://www.winehq.com/dev.shtml</ulink>
+ <ulink url="http://www.winehq.org/site/cvs#cvsservers">
+ http://www.winehq.org/site/cvs#cvsservers</ulink>
</para>
<para>
Patch files are also available, so that you don't have to download,
- install, and configure the entire distribution each week if you are
+ install, and configure the entire distribution each month if you are
current to the previous release. Patch file release names follow the
same numbering convention as do the general releases, and take the
form
does. Use a <filename>wine.sup</filename> file of:
</para>
<screen>
-*default host=cvs.winehq.com
+*default host=cvs.winehq.org
*default base=/cvs
*default prefix=/cvs/wine
*default release=wine
</qandadiv>
<qandadiv id="Installing-And-Configuring-Wine">
- <title>Installing And Configuring Wine</title>
+ <title>Installing and Configuring Wine</title>
<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>
- See the README (<ulink url="http://www.winehq.com/source/README">http://www.winehq.com/source/README</ulink>) for instructions.
+ See the README (<ulink url="http://source.winehq.org/source/README">http://source.winehq.org/source/README</ulink>) for instructions.
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).
hardware and cannot get it with Wine and UNIX in the way
</para>
<para>
- Wine is supposed to be used WITHOUT Windows primarily. If you want
+ Wine is supposed to be primarily used WITHOUT Windows. If you want
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
<filename>~/.wine/config</filename>. The format of this file is
explained in the <filename>wine.conf</filename> man page. The file
<filename>documentation/samples/config</filename>
- (<ulink url="http://www.winehq.com/source/documentation/samples/config">
- http://www.winehq.com/source/documentation/samples/config</ulink>)
+ (<ulink url="http://source.winehq.org/source/documentation/samples/config">
+ http://source.winehq.org/source/documentation/samples/config</ulink>)
contains a config file example. More explicit directions can be
found in the <filename>README</filename> file
- (<ulink url="http://www.winehq.com/source/README">
- http://www.winehq.com/source/README</ulink>) that will be located in
+ (<ulink url="http://source.winehq.org/source/README">
+ http://source.winehq.org/source/README</ulink>) that will be located in
the base Wine directory after you gunzip and untar the distribution
file.
</para>
</question>
<answer>
<para>
- Either use a classic no-windows install (Wine is getter better all
+ Either use a classic no-windows install (Wine is getting better all
the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T
- configure Wine to use an NT-based Windows install (NT, Win2K, WinXP).
+ configure Wine to use an NT-based Windows install (NT, Win2K, WinXP, Win2K3).
</para>
+ <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
+ install the programs you want into Wine's fake windows drive.
+ </para>
</answer>
</qandaentry>
</question>
<answer>
<para>
- Make sure you have all the VB runtime libraries installed. You may
- need to use the native DLL vbrun60.dll
+ Make sure you have all the VB run time libraries installed. You can
+ get the latest version from the Microsoft web site.
</para>
</answer>
</qandaentry>
<qandaentry>
<question id="When-I-click-on-exe-file-nothing-happens">
- <para>When I click on *.exe file in my file Manager, nothing happens</para>
+ <para>When I click on *.exe file in my file Manager, nothing happens.</para>
</question>
<answer>
<para>
cd /my/windows/program/directory
wine myprogram.exe
</screen>
- <para>
- Or alternatively you could download the CodeWeavers Wine preview
- which includes .exe extension registration for KDE/Gnome and a nice
- setup program.
- </para>
</answer>
</qandaentry>
<qandaentry>
<question id="bash-wine-Command-not-found-What-can-I-do">
- <para>bash "wine: Command not found" What can I do?</para>
+ <para>bash says "wine: Command not found" What can I do?</para>
</question>
<answer>
<para>
- Try to relogin into bash. That might fix it.
+ Try to logout and login again into bash. That might fix it.
</para>
<para>
If it doesn't, then make sure the wine binary is in your
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
- making a meaningfull config file, it DOES NOT install the wine
+ making a meaningful config file, it DOES NOT install the wine
package...
</para>
<para>
- For complete packages, use <ulink url="http://www.rpmfind.net/">
- www.rpmfind.net</ulink> or the <ulink url="http://www.winehq.org/download/">
+ For complete packages, use <ulink url="http://rpmseek.com/rpm-pl/wine.html?hl=com&cx=0::">
+ http://rpmseek.com/</ulink> or the <ulink url="http://www.winehq.org/site/download">
Download</ulink> section.
</para>
</answer>
</question>
<answer>
<para>
- All you have to do is to type:
- </para>
- <screen>
-rm -fR \[/path/\]Wine*
- </screen>
- <para>
- Make sure that you specify the exact path when using the powerful
- <command>rm -fR</command> command. If you are afraid that you might
- delete something important, or might otherwise delete other files
- within your filesystem, <command>cd</command> into each Wine
- subdirectory singly and delete the files found there manually,
- one file or directory at a time.
- </para>
- <para>
- Neither the Wine developers and programmers, nor the Wine FAQ
- author/maintainer, can be held responsible for your deleting any
- files in your own filesystem.
+ It depends on how you installed. If you used an RPM, the right command is this:
+ <command>rpm -e wine (as root)</command>
</para>
+ <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>
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="About-running-Wine">
<title>About running Wine</title>
- <para>
- In case of problems when running Wine, You may also want to see the
- <ulink url="http://www.winehq.org/fom-meta/cache/19.html">
- Wine Troubleshooting Guide</ulink>.
- </para>
<qandaentry>
<question id="How-do-I-run-an-MS-Windows-program">
<para>How do I run an MS Windows program under Wine?</para>
<answer>
<para>
When invoking Wine, you must specify the entire path to the
- executable, or by filename only. For example to run Windows'
+ executable, or by file name only. For example to run Windows'
solitaire, type any of the following:
</para>
<itemizedlist>
<listitem>
<para>
<command>wine c:\\windows\\sol.exe</command>
- (using a DOS filename).
+ (using a DOS file name).
</para>
</listitem>
<listitem>
<para>
<command>wine /usr/windows/sol.exe</command>
- (using a UNIX filename).
+ (using a UNIX file name).
</para>
</listitem>
<listitem>
<para>
<command>wine "c:\windows\sol.exe"</command>
- (using quoted DOS filename).
+ (using quoted DOS file name).
</para>
</listitem>
</itemizedlist>
</answer>
</qandaentry>
+ <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
+ 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.
+ </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
+ can some core system DLLs like gdi32, user, ntdll, kernel32 etc.
+ </para>
+ </answer>
+ </qandaentry>
+
<qandaentry>
<question id="Can-I-use-Wine-with-other-Linux-Distros">
- <para>Can I use Wine with SuSe, Peanut or other Linux Distro's?</para>
+ <para>Can I use Wine with SUSE, RedHat or other Linux Distro's?</para>
</question>
<answer>
<para>
You can use Wine on any sufficiently recent Linux installation. The
- amount of work getting Wine up and running depends on whether there
- are proper packages available or a source compile has to be done.
+ amount of work getting Wine up and running depends on whether you
+ install a binary packages or do a source install.
</para>
</answer>
</qandaentry>
</question>
<answer>
<para>
- Yes, it does.
+ Yes, it does. Wine should work on any processor compatible with
+ the Pentium or greater.
</para>
</answer>
</qandaentry>
<answer>
<para>
Sure, Wine supports that. Just enter the unix program name wherever
- a program has something that it's supposed to execute,and then it
+ a program has something that it's supposed to execute, and it
should just work.
</para>
</answer>
<question id="Error-with-installshield-6">
<para>
I get <quote>Error installing iKernel.exe: (0x1400)</quote>
- when running an Installshield 6 installer
+ when running an InstallShield 6 installer.
</para>
</question>
<answer>
point, it's probably because there are leftover processes from a
previous try. You can verify this with the command
</para>
- <para><command>$ ps augxw | grep wine</command></para>
+ <para><prompt>$ </><command>ps augxw | grep wine</command></para>
<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>
- <para><command>$ killall wine</command></para>
+ <para><prompt>$ </><command>killall wine</command></para>
<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
which doesn't exist yet).
</para>
<para>
- You should repeat the <command>ps</command> to make sure the old
- wines are gone.
+ You should repeat the <command>ps</command> to make sure all of the old
+ Wine processes are gone.
</para>
</answer>
</qandaentry>
</qandadiv>
-
+
<qandadiv id="Getting-help">
<title>Getting help</title>
<qandaentry>
</question>
<answer>
<para>
- Yes, see <ulink url="http://www.winehq.org/support.shtml">
- http://www.winehq.com/support.shtml.</ulink>
+ Yes, see <ulink url="http://www.winehq.org/site/documentation">
+ http://www.winehq.org/site/documentation.</ulink>
</para>
</answer>
</qandaentry>
<para>
Updates and additions to the Wine documentation directory should be
sent to the wine-patches mailing list at
- <ulink url="http://www.winehq.com/dev.shtml#ml">
- http://www.winehq.com/dev.shtml#ml</ulink>. Website and FAQ
- additions should be added to the appropriate Wine Knowledgebase
- directory.
+ <ulink url="http://www.winehq.org/site/forums">
+ http://www.winehq.org/site/forums</ulink>. Website and FAQ
+ additions should be added to the appropriate Wine Knowledge base directory.
</para>
</answer>
</qandaentry>
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
- crossposted to other appropriate newsgroups, such as the following:
+ cross posted to other appropriate newsgroups, such as the following:
</para>
<itemizedlist>
<listitem>
</question>
<answer>
<para>
- Wine HQ (<ulink url="http://www.winehq.com">http://www.winehq.com</ulink>) is the official site.
+ Wine HQ (<ulink url="http://www.winehq.org">http://www.winehq.org</ulink>) is the official site.
</para>
</answer>
</qandaentry>
<answer>
<para>
Bug reports should be submitted to our online Bugzilla system
- (<ulink url="http://bugs.winehq.com">http://bugs.winehq.com/</ulink>).
+ (<ulink url="http://bugs.winehq.org/">http://bugs.winehq.org/</ulink>).
You should include at least the following:
</para>
<itemizedlist>
</listitem>
<listitem>
<para>
- The MS Windows program name and, if possible, the version number
- of the software tested
+ The Windows application name, including the version, and, if
+ applicable, a URL the application can be downloaded from
</para>
</listitem>
<listitem>
<answer>
<para>
If you can program C, that's a good start. Download the sources via
- CVS, 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 url="http://www.winehq.com/dev.shtml#ml">http://www.winehq.com/dev.shtml#ml</ulink>). 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).
+ (<ulink url="http://www.winehq.org/site/cvs">CVS,</ulink>)
+ 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
+ url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>).
+ 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).
</para>
</answer>
</qandaentry>
</para>
<para>
For a list of ideas of how you can help, please consult the
- <ulink url="http://www.winehq.com/about/index.php?contrib">
+ <ulink url="http://www.winehq.org/site/contributing">
Wine contrib page</ulink>.
</para>
</answer>
</question>
<answer>
<para>
- Patches are greatly appreciated and should be submitted to the
+ Submitting a patch for inclusion in Wine is pretty simple.
+ Basically all you have to do is send the patch to the
wine-patches mailing list
- (<ulink url="http://www.winehq.com/dev.shtml#ml">http://www.winehq.com/dev.shtml#ml</ulink>). Also see this page for
- a description of what happens to submitted patches.
+ (<ulink url="http://www.winehq.org/mailman/listinfo/wine-patches">http://www.winehq.org/mailman/listinfo/wine-patches</>).
+ Still there are a couple of recommendations about the patch format
+ and all so it's best to read our page describing <ulink
+ url="http://www.winehq.org/site/sending_patches">how to submit
+ patches</>. This will also give you more details about the whole
+ process and in particular to what will happen to your patch once
+ submitted.
</para>
</answer>
</qandaentry>
</qandadiv>
-
+
<qandadiv id="Developing-programs-using-Wine-WineLib">
<title>Developing programs using Wine/WineLib</title>
<qandaentry>
</question>
<answer>
<para>
- A few examples of applications using Winelib:
+ Here are few examples of applications ported using Wine or Winelib:
</para>
<itemizedlist>
<listitem>
<para>
- Corel's WordPerfect Office Suite
+ 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>
+ MusicMatch Jukebox 5 has also been
+ <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.
</para>
</listitem>
<listitem>
<answer>
<para>
You really shouldn't want to do this. If there's a quirk in Wine
- you need to work around, it's much better to fix it in Wine (after
- all you're a developer, so you should be able to gather enough help
- and knowledge to fix it for real).
+ you need to work around, it's much better to fix it in Wine.
</para>
</answer>
</qandaentry>
-
+
</qandadiv>
<qandadiv id="Wine-HQ-issues">
<qandaentry>
<question id="Why-are-the-maillists-set-to-reply-to-author">
<para>
- Why are the maillists set to reply to author, not to mailing list?
+ Why are the mailing lists set to reply to author, not to mailing list?
</para>
</question>
<answer>
<para>
- There are very valid reasons for doing so.
+ There are some very valid reasons for doing so.
</para>
</answer>
</qandaentry>
</question>
<answer>
<para>
- Please see: <ulink url="http://www.winehq.org/development/#ml">http://www.winehq.org/development/#ml</ulink>
+ Please see: <ulink url="http://www.winehq.org/site/forums">http://www.winehq.org/site/forums</ulink>
+ And select [(Un-)Subscribe]
</para>
</answer>
</qandaentry>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
-sgml-parent-document:("wine-doc.sgml" "book" "part" "chapter" "")
+sgml-parent-document:("wine-devel.sgml" "book" "part" "chapter" "")
End:
-->