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