docs/en wine-faq.sgml

[Dimi Paun]

ChangeSet ID:	1127130386237366325062798
CVSROOT:	/cvsroot/wine
Module name:	docs
Changes by:	[e-mail]	2005/09/19 04:46:26

Modified files:
    en             : wine-faq.sgml

Log message:
    Tom Wickline 
    Spelling fixes, typo fixes.
    Remove info about history as we now have a history page.
    Link to BricsCad as their product runs on Wine.

Old revision  New revision  Changes     Path
 1.5           1.6           +56 -115    docs/en/wine-faq.sgml

Index: docs/en/wine-faq.sgml
diff -u -p docs/en/wine-faq.sgml:1.5 docs/en/wine-faq.sgml:1.6
--- docs/en/wine-faq.sgml	19 Sep 2005 11:46:26 -0000
+++ /dev/null	19 Sep 2005 11:46:26 -0000
@@ -141,7 +141,7 @@ cvs -z3 -d:pserver:[e-mail]
           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
           of running most Operating Systems inside the emulation including Linux, 
-          <trademark class="registered">Windows</> 95, DOS, and recently <trademark class="registered">Windows</> NT 4.
+          <trademark class="registered">Windows</> 95, DOS, and recently <trademark class="registered">Windows</> NT/2000.
        </para>

<para>
@@ -303,64 +303,6 @@ cvs -z3 -d:pserver:[e-mail]
       </qandaentry>

<qandaentry>
-      <question id="What-software-is-based-on-Wine">
-        <para>What software projects are based on Wine and how are they
- related?</para>
-      </question>
-      <answer>
-        <para>If you trace Wine's roots back, you'll find quite a few 
- different projects have emerged.  For complete details, look at
- the <ulink url="http://www.winehq.com/site/history">Wine history</ulink>
- page to learn how these diverged.
-        </para>
- <para>
- In the beginning, the only version of Wine that existed was managed
- by Alexandre.  This eventually became to be known as the WineHQ
- tree.  From there, all other branches diverged.  One of the first
- ones to be developed outside of WineHQ was done by Corel in 1998 in 
- support of their Wine efforts.  Even though Wine was developed under 
- the X11 (BSD-like) license, Corel resubmitted most of their changes 
- back to WineHQ.  Corel eventually moved on as well as their development
- team.  Many changes from Corel made their way back into the WineHQ
- tree.
- </para>
- <para>
- In 2002 the main WineHQ tree changed licenses to LGPL and caused
- Wine to fork.  The original X11 code is available on SourceForge as 
- the <ulink url="http://rewine.sourceforge.net">ReWind</ulink> project.
- For all intents and purposes, this is a dead project.  The code
- has diverged drastically from WineHQ's and any updates that do
- appear are infrequent.  Anyone wishing to utilize the old Wine code
- under the old X11 license should strongly consider otherwise.
- </para>
- <para>
- As Corel was ending their efforts, two new companies emerged with
- their own versions of Wine.  CodeWeavers' developed their CrossOver
- line of products and TransGaming developed WineX (now called Cedega.)
- CodeWeavers continues to develop their products based on Wine and
- actively supports the community.  Their development model consists
- of contributing directly to the WineHQ tree and branching periodically
- for releases.  TransGaming's WineX/Cedega product followed the
- X11 split.  Much of their code has been relicensed under 
- the Aladdin Free Public License limiting the distribution.
- TransGaming has since adopted some of the libraries from the WineHQ 
- tree and they remain under the LGPL license.  TransGaming maintains
- informal contact with the Wine community but has not contributed 
- anything to Wine in a number of years.
- </para>
- <para>
- If your primary concern is to use a free version of Wine (as in beer 
- as well as right-to-use), then you're probably most interested in 
- utilizing the WineHQ tree.  If you want a commercial product (including 
- all the features like support) developed by a company that actively 
- contributes to Wine, then you should check out the CodeWeavers' 
- products described below.  If you simply want to run games, 
- TransGaming's Cedega might be a solution.
- </para>
-      </answer>
-      </qandaentry>
-
-      <qandaentry>
       <question id="Which-one-of-the-different-Wine-packages">
         <para>Which one of the different Wine packages out there is good for me?</para>
       </question>
@@ -376,7 +318,7 @@ cvs -z3 -d:pserver:[e-mail]
            <para>
               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.
+              are available in the <ulink url="http://www.winehq.org/site/download">download</ulink> section of the site.
             </para>
            </listitem>
           </varlistentry>
@@ -449,8 +391,8 @@ cvs -z3 -d:pserver:[e-mail]
           <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
-          file name. For instance, the distribution released on August 13, 2004
-          was called Wine-20040813.tar.gz. Patch files are also available. If
+          file name. For instance, the distribution released on July 25, 2005
+          was called Wine-20050725.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 file names follow the same conventions as the monthly 
@@ -466,9 +408,9 @@ cvs -z3 -d:pserver:[e-mail]
       </question>
       <answer>
         <para>
-          As of mid 2004, Wine consists of about 1.6 million lines of code,
+          As of mid 2005, Wine consists of about 1.4 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
+          the world. Wine is in active use by an estimated 200K people. Wine
           implements more than 90% of the calls in popular Windows 
           specifications such as ECMA-234 and Open32.
         </para>
@@ -491,11 +433,11 @@ cvs -z3 -d:pserver:[e-mail]
           Windows contains new API calls or variations on the existing ones.
         </para>
         <para>
-          Because Wine is being developed by volunteers, it is difficult to
+          Because Wine is being developed mainly by a single company (CodeWeavers) and 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
+          much increased interest by other 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 Real Soon Now(tm).
+          we are working on releasing Wine 0.9 our schedule has this release around September 30th 2005.
         </para>
       </answer>
       </qandaentry>
@@ -523,7 +465,7 @@ cvs -z3 -d:pserver:[e-mail]
       </question>
       <answer>
         <para>
-          The best would be if the Windows API was fully documented, so Wine
+          The best solution would be if the Windows API were fully documented, so Wine
           could be a perfect "clean-room" implementation. Seeing the source
           code might make it harder to prove that no copyright violations have
           taken place. That said, the documentation is often bad, nonexistent,
@@ -532,7 +474,7 @@ cvs -z3 -d:pserver:[e-mail]
           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
+	  parts needed to make Windows programs work), that's still nearly 8 times
      more people working simply on one release than have <emphasis>ever</emphasis>
      worked on Wine, in the history of the project.
         </para>
@@ -649,7 +591,7 @@ cvs -z3 -d:pserver:[e-mail]
         </para>
         <para>
           Mac OS X / Darwin: The <ulink
-          url="http://darwine.sourceforge.net/project.html%22%3EDarwine</ulink> is
+          url="http://darwine.sourceforge.net/project.html%22%3EDarwine</ulink> project 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.
@@ -710,13 +652,13 @@ cvs -z3 -d:pserver:[e-mail]
       </question>
       <answer>
         <para>
-          You need approximately 250 megabytes of free hard drive space to
+          You need approximately 750 megabytes of free hard drive space to
           store and compile the source code. Wine also needs about 18 megs in
           your /tmp directory. And about 50 MB are needed to do a make install.
         </para>
         <para>
           Binary packages, especially those not containing debug information,
-          have much lower disk space requirements, usually in the 20MB range.
+          have much lower disk space requirements, usually in the 30MB range.
         </para>
       </answer>
       </qandaentry>
@@ -751,9 +693,9 @@ cvs -z3 -d:pserver:[e-mail]
       <answer>
         <para>
           Wine is getting to be quite large, and building from scratch takes a
-          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
+          lot of processing. As of July 2005, compile times were around 15
+          minutes on a Intel 3.8GHz Laptop with 1 GB of RAM and 20 minutes on a Athlon 
+          2000 with 512 MB of RAM. If you have a CVS copy of wine, you may not need
           to rebuild every thing each update.
         </para>
       </answer>
@@ -787,7 +729,7 @@ cvs -z3 -d:pserver:[e-mail]
       <answer>
         <para>
           You do not need a licensed and installed copy of DOS or MS Windows to
-          install, configure and run Wine. However, Wine has to be able to 
+          install, configure or run Wine. However, Wine has to be able to 
           'see' an MS Windows binary (i.e. application) if it is to run it.
         </para>
       </answer>
@@ -884,8 +826,7 @@ cvs -z3 -d:pserver:[e-mail]
           Windows programs under Wine. Wine uses standard X libraries, so no
           additional ones are needed. Wine has its own window management,
           which acts like MS Windows. It can be turned off to use the native
-          window manager by modifying Managed or Desktop settings as described
-          in <command>man wine.conf</command>.
+          window manager by modifying Managed or Desktop settings in winecfg.
         </para>
       </answer>
       </qandaentry>
@@ -1116,18 +1057,11 @@ wine 
       </question>
       <answer>
         <para>
-          Wine requires that you have a config file as 
-          <filename>~/.wine/config</filename>. The format of this file is
-          explained in the <filename>wine.conf</filename> man page. The file
-          <filename>documentation/samples/config</filename>
-          (<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://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.
+          As of Wine release 20050725 the config file has been disabled and
+          the values are now stored instead in registry files in your .wine directory.
+          The  preferred method to configure Wine is with winecfg, winefcg is a
+          tool to make it easy for new users to edit some of the contents of there
+          registry files.
         </para>
       </answer>
       </qandaentry>
@@ -1139,8 +1073,8 @@ wine 
       <answer>
         <para>
           Upgrading the wine installation does not affect the existing wine
-          configuration. So after upgrading wine you still have the old (working )
-          wine configuration.
+          registry settings. So after upgrading wine you still have the old (working )
+          wine registry configuration.
         </para>
       </answer>
       </qandaentry>
@@ -1169,7 +1103,7 @@ wine 
       </question>
       <answer>
         <para>
-          As of 02/2002:
+          As of 08/2005:
         </para>
         <para>
           I'd say Win98SE is the best version to use with Wine, as it's fairly
@@ -1248,13 +1182,6 @@ export PATH=$PATH:/path/to/wine/binary 
           That should help.
         </para>
         <para>
-           If you used a package manager (<command>rpm</command> or 
-           <command>apt</command>) - Verify your packages. The package 
-           <filename>winesetuptk.rpm</filename> is only a front-end for 
-           making a meaningful config file, it DOES NOT install the wine
-           package...
-        </para>
-        <para>
            For complete packages, use <ulink url="http://rpmseek.com/rpm-pl/wine.html?hl=com&amp;cx=0::">
            http://rpmseek.com/</ulink> or the <ulink url="http://www.winehq.org/site/download">
            Download</ulink> section.
@@ -1380,9 +1307,10 @@ export PATH=$PATH:/path/to/wine/binary 
       </question>
       <answer>
         <para>
-          Kill the xterm shell window that you called up to run your MS 
-          Windows program, and the X window that appeared with the program 
-          will be killed too.
+          Menus should be working correctly, if for some reason your applications menus stops responding.
+          You can kill the xterm shell window that you called up to run your MS Windows program, and the X 
+          window that appeared with the program will be killed too. If you started the application from a 
+          shortcut you can open a terminal and start <command>xkill</command> and just click on the application to kill it.
         </para>
       </answer>
       </qandaentry>
@@ -1409,12 +1337,15 @@ export PATH=$PATH:/path/to/wine/binary 
             <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>
+          We recommend that you try builtin dlls first and report any errors that you may run across to wine-devel 
+          or to our Bugzilla. If you report problems they can be verified and fixed by the development team 
+          and this helps everyone over the long run by not covering up bugs with the use of native dlls.
+          </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.
+	    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 with winecgf). 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>
@@ -1583,7 +1514,7 @@ export PATH=$PATH:/path/to/wine/binary 
           Sure. It's channel <filename>#WineHQ</filename> on 
           <filename>irc.freenode.net</filename> see 
           (<ulink url="http://freenode.net">http://freenode.net</ulink>).
-          Usually several Wine developers hang out there just to help YOU ;-)
+          Usually several knowledgeable Wine users hang out there.
         </para>
       </answer>
       </qandaentry>
@@ -1666,10 +1597,18 @@ export PATH=$PATH:/path/to/wine/binary 
       <answer>
         <para>
           You can contribute programming or documentation skills, or monetary
-          or equipment donations, to aid the Wine developers in reaching their 
-          goals.
+          or equipment donations, to aid the Wine developers in reaching their goals.
         </para>
         <para>
+          One area where every Wine user user can contribute to this project is by sending high quality 
+          bug reports to our Bugzilla and helping the developers with any follow up questions that they
+          may have about a bug that you have come across. It is not only impossible but also impractical 
+          for a developers to have a copy of every program on the market. This is why we need your 
+          help even after you have sent in the initial bug report. If a developer has a good idea what 
+          might be causing the bug he or she may ask if you can try a patch and see if it fixes the problem. 
+          After this patch makes its way into our main development tree the bug report will be closed 
+          and your help will be appreciated by everyone.
+        <para>
           For a list of ideas of how you can help, please consult the 
           <ulink url="http://www.winehq.org/site/contributing">
           Wine contrib page</ulink>.
@@ -1793,11 +1732,13 @@ export PATH=$PATH:/path/to/wine/binary 
             (<ulink url="http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p">http://www7b.boulder.ibm.com/dl/swws/swwsgddb-p</ulink>)
           </para>
           </listitem>
+          <listitem>
+          <para>
+            BricsCad™
+            (<ulink url="ftp://ftp.bricscad.com/pub/Eng-Us/B4L/Readme.htm">BricsCad™ V6 for Linux</ulink>)
+          </para>
+          </listitem>
         </itemizedlist>
-        <para>
-          Many other important applications have already been ported. (we are
-          speaking of several top 500 applications here)
-        </para>
       </answer>
       </qandaentry>