From 10227610905dd65076fadae31128ec369742f6f8 Mon Sep 17 00:00:00 2001 From: Tom Wickline Date: Fri, 14 May 2004 21:35:32 +0000 Subject: [PATCH] Some updates to the faq. --- documentation/faq.sgml | 91 +++++++++++++++++++----------------------- 1 file changed, 42 insertions(+), 49 deletions(-) diff --git a/documentation/faq.sgml b/documentation/faq.sgml index 18d23a4ffda..7d7d1c73fcf 100644 --- a/documentation/faq.sgml +++ b/documentation/faq.sgml @@ -291,7 +291,7 @@ - + ReWind @@ -303,7 +303,7 @@ - + TransGaming's WineX @@ -615,7 +615,6 @@ - What do I need in order to use Wine? @@ -784,17 +783,11 @@ on how memory hungry the application is. - 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. @@ -806,10 +799,10 @@ 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. @@ -847,7 +840,7 @@ - + @@ -917,7 +910,7 @@ - + @@ -978,7 +971,7 @@ - + Will Wine run only under X, or can it run in character mode? @@ -997,7 +990,7 @@ - + Will Wine run under any X window manager? Does it require a window manager at all? @@ -1017,16 +1010,15 @@ - Will 32-bit Windows 95/98 applications run under Wine? + Will 32-bit Windows 95/98/ME/NT/2000/XP applications run under Wine? - Yes, 32-bit programs are now about as well supported as 16-bit - programs. + Yes, 32-bit programs are now well supported. - + Getting Wine @@ -1036,7 +1028,7 @@ - Because of lags created by using mirror, word of the latest 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: @@ -1083,8 +1075,8 @@ It should also be available from any other site that mirrors - ibiblio.org, see http://www.ibiblio.org/pub/Linux/MIRRORS.html. Some of - these sites may archive previous versions of Wine as well as the + ibiblio.org, see 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 @@ -1143,7 +1135,7 @@ cvs -z 3 checkout wine/ANNOUNCE 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 @@ -1336,11 +1328,6 @@ wine cd /my/windows/program/directory wine myprogram.exe - - Or alternatively you could download the CodeWeavers Wine preview - which includes .exe extension registration for KDE/Gnome and a nice - setup program. - @@ -1529,30 +1516,36 @@ export PATH=$PATH:/path/to/wine/binary 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), or hire somebody to do it for you. If this application - is an internal corporate application, you may be able to hire a - Wine developer to do consulting work for you on the matter. + program work (there must be a downloadable version or demo for that). + + + You can submit your application to the + Wine Application DB and gather tips on ways to get your app to work its best. + + + You can also submit your application to the CodeWeavers CrossOver + Compatibility Center. + Where you can pledge/vote toward future support of your favorite application. 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 user, ntdll, kernel32 etc + can some core system DLLs like gdi32, user, ntdll, kernel32 etc. - + - Can I use Wine with SUSE, Peanut or other Linux Distro's? + Can I use Wine with SUSE, RedHat or other Linux Distro's? 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. @@ -1609,13 +1602,13 @@ export PATH=$PATH:/path/to/wine/binary which doesn't exist yet). - You should repeat the ps to make sure the old + You should repeat the ps to make sure all of the old Wine processes are gone. - + Getting help @@ -1838,7 +1831,7 @@ export PATH=$PATH:/path/to/wine/binary - + Developing programs using Wine/WineLib @@ -1938,7 +1931,7 @@ export PATH=$PATH:/path/to/wine/binary - + @@ -1951,7 +1944,7 @@ export PATH=$PATH:/path/to/wine/binary - There are very valid reasons for doing so. + There are some very valid reasons for doing so.