ChangeSet ID: 22807
CVSROOT: /opt/cvs-commit
Module name: lostwages
Changes by: jnewman(a)winehq.org 2006/02/06 12:56:45
Modified files:
wwn : wn20060122_303.xml
Log message:
fix some malformatted XML
Patch: http://cvs.winehq.org/patch.py?id=22807
Old revision New revision Changes Path
1.2 1.3 +2 -2 lostwages/wwn/wn20060122_303.xml
Index: lostwages/wwn/wn20060122_303.xml
diff -u -p lostwages/wwn/wn20060122_303.xml:1.2 lostwages/wwn/wn20060122_303.xml:1.3
--- lostwages/wwn/wn20060122_303.xml:1.2 6 Feb 2006 18:56:45 -0000
+++ lostwages/wwn/wn20060122_303.xml 6 Feb 2006 18:56:45 -0000
@@ -591,14 +591,14 @@ there is interested here's how it is set
</p><p>
In regedit:
-<ul><li> disabled auto winedbg by renaming AeDebug<br>
+<ul><li> disabled auto winedbg by renaming AeDebug<br />
I changed HKEY_LOCAL_MACHINE/Software/Microsoft/Windows
NT/Current Version/AeDebug to AeDebug-DISABLED. Without this gdb
doesn't seem to be able to get a hold of SEGFAULTs.</li></ul>
</p><p>
In eclipse's Run/Debug dialog box:
-<ul><li> set the c/c++ application to WINE_SRC/loader/wine-pthread<br>
+<ul><li> set the c/c++ application to WINE_SRC/loader/wine-pthread<br />
WINE_SRC points to a compiled version of wine. For me, I got the
wine src rpm and ran rpmbuild -bb. This is where main() is,
which eclipse looks for at start up.</li>
ChangeSet ID: 22804
CVSROOT: /opt/cvs-commit
Module name: lostwages
Changes by: jnewman(a)winehq.org 2006/02/06 10:41:38
Modified files:
templates/en : download-deb.template
Log message:
Scott Ritchie <scott(a)open-vote.org>
Improve download-deb page to link to old packages, make things clearer
Patch: http://cvs.winehq.org/patch.py?id=22804
Old revision New revision Changes Path
1.7 1.8 +18 -7 lostwages/templates/en/download-deb.template
Index: lostwages/templates/en/download-deb.template
diff -u -p lostwages/templates/en/download-deb.template:1.7 lostwages/templates/en/download-deb.template:1.8
--- lostwages/templates/en/download-deb.template:1.7 6 Feb 2006 16:41:38 -0000
+++ lostwages/templates/en/download-deb.template 6 Feb 2006 16:41:38 -0000
@@ -1,18 +1,17 @@
<!--TITLE:[Wine for Debian based distributions]-->
<h1><a name="debian"></a><img src="{$root}/images/distro/debian.png" width="50" height="50" alt="Debian Linux" border="0">
-Wine for Debian based distributions</h1>
+Wine for Ubuntu, Debian, and Debian-based distributions</h1>
-<p>Debian and Debian based distributions, such as Ubuntu, utilize a special tool
+<p>Debian and Debian-based distributions, such as Ubuntu, utilize a special tool
for managing packages known as APT. APT is able to automagically install all of
the needed dependencies for a software package, as well as keep the package
-up to date, by scanning what are known as APT repositories. Debian based
+up to date, by scanning what are known as APT repositories. Debian-based
distributions have their own repositories of software, many of which include
Wine, however we keep the latest available packages here for download.</p>
-<p>Packages here are designed to function on Debian unstable, and are meant to
-replace the older Debian-provided ones. Like most packages for Debian unstable,
-these packages also work in Ubuntu Linux, where they are tested regularly. </p>
+<p>Packages here are designed to function on Debian unstable and the latest stable
+Ubuntu, and they should replace the older Debian-provided ones.</p>
<h2>Installing from the WineHQ APT Repository with Synaptic:</h2>
@@ -31,6 +30,8 @@ If you already have a 'wine' package ins
opting for the "smart upgrade" option should update Wine to the newest version.
</p>
+<h2>Getting source packages from the repository</h2>
+
<p>Currently, we only have i386 binary packages available. If you do not use an
i386 architecture, or wish to compile the package in an optimized way, you can
build the wine package using the source repository instead. To do this, add a
@@ -38,7 +39,8 @@ source repository with the the following
<i><p>deb-src http://wine.sourceforge.net/apt/ source/</p></i>
-<p>Then, see the instructions below for building the package in the console.</p>
+<p>Then, see the instructions below for building the package in the console.
+Most users, however, will neither need nor want to do this.</p>
<img src="{$root}/images/distro/synaptic-repository-source2.png" alt="Synaptic Package Repository Screenshot" border="0">
@@ -83,3 +85,12 @@ compiling to finish.</p>
<p>To install your newly created package (which should be in whatever directory
you were in when you ran apt-get --build source), run '<b>dpkg -i wine*.deb</b>'
as root.</p>
+
+<h2>Older .deb packages</h2>
+
+<p>Since the APT repository can only hold the latest packages, older versions of
+packages are available here:
+<a href=http://sourceforge.net/project/showfiles.php?group_id=6241&package_id=…>Ubuntu/Debian Unstable Packages</a></p>
+
+<p>If you wish to use these packages, you'll have to install them by hand
+using dpkg -i</p>
ChangeSet ID: 22803
CVSROOT: /opt/cvs-commit
Module name: lostwages
Changes by: jnewman(a)winehq.org 2006/02/06 10:40:54
Modified files:
templates/en : myths.template
Log message:
Juan Lang <juan_lang(a)yahoo.com>
Win32 has been the default for Wine for years, so say so
Patch: http://cvs.winehq.org/patch.py?id=22803
Old revision New revision Changes Path
1.12 1.13 +15 -18 lostwages/templates/en/myths.template
Index: lostwages/templates/en/myths.template
diff -u -p lostwages/templates/en/myths.template:1.12 lostwages/templates/en/myths.template:1.13
--- lostwages/templates/en/myths.template:1.12 6 Feb 2006 16:40:54 -0000
+++ lostwages/templates/en/myths.template 6 Feb 2006 16:40:54 -0000
@@ -163,24 +163,21 @@ although Windows NT (and thus the Win32
supported Windows 3.1 applications. Anyway, almost no-one used Windows
NT in that time anyway.
<p>
-But these days are long gone. The Windows 3.1 support may still be more
-complete than that of the Win32 API but most of the development nowadays
-happens for the Win32 API. Furthermore I should point out two more
-things. First, it seems people complaining about Wine supporting only
-Windows 3.1 usually do not realize that Wine also includes some support
-for the DOS API. That's because a non negligible percentage of Windows
-3.1 and even Windows 9x applications still make calls to the DOS
-interrupts! Second, Winelib only supports the Win32 API. The Win16 header
-files (necessary for compiling a Win16 application) have been moved out
-of the way to simplify development. So in some way the Win32 API is
-better supported than the Win16 one.
-<p>
-So currently Wine does not support the Win64 API at all. But the Wine
-team does take Win64 into account when making architectural decisions.
-In fact we'll probably see history repeating itself: the Win64 API has
-not been released in a commercial product yet, so no-one is using it
-anyway. So I can predict that when it becomes widespread we'll see Wine
-developers starting to work on supporting it.
+But these days are long gone. Since August 2005, Wine advertises its version
+as Windows 2000, and for several years before this it was Windows 98, so really
+Win32 is the primary thing Wine supports. Support for Windows 3.1 applications
+is still around, of course, as is some support for DOS applications.
+<p>
+Win64 support would allow Wine to run native Windows 64-bit executables, and
+as of February 2006, Wine does not yet have this support. That's okay, since
+there are very few commercially available Win64 applications. One exception,
+Unreal Tournament 2004, is available in a native Linux 64-bit version, so
+nobody (except maybe a Wine hacker) should want to run the Windows version
+anyway.
+<p>
+This doesn't mean that Wine will not work on 64-bit systems. It does. See
+<a href="http://wiki.winehq.org/WineOn64bit">this entry</a> in the
+<a href="http://wiki.winehq.org/">Wine Wiki</a> for more info.
<a name="only_linux"></a>
<h2>Myth 9: "Wine is for Linux only"</h2>