On Fri, 21 May 2004 12:58 am, Francois Gouget wrote:
On Thu, 20 May 2004, Mike Hearn wrote:
[...]
This is no longer true. According to a Red Hat kernel engineer, you can
use setarch i386 wine to switch it back to the 3/1 split while we
fix it in the Wine code.
Don't we have the
On Wed, 19 May 2004 09:46:50 +0100, Mike Hearn wrote:
There is currently no known workaround for this problem short of
recompiling your kernel.
This is no longer true. According to a Red Hat kernel engineer, you can
use setarch i386 wine to switch it back to the 3/1 split while we
fix it
On Thu, 20 May 2004, Mike Hearn wrote:
[...]
This is no longer true. According to a Red Hat kernel engineer, you can
use setarch i386 wine to switch it back to the 3/1 split while we
fix it in the Wine code.
Don't we have the same problem with the 3/1 split?
If I remember correctly we can
Hi,
On Fedora Core 2, the kernel is compiled with the 4G/4G VM split option
enabled, which can prevent us from performing a correct emulation.
Win32 apps are apparently built with the assumption that they will not
be allocated addresses beyond the 3G boundary. The solution therefore is
to
On Wed, May 19, 2004 at 09:46:50AM +0100, Mike Hearn wrote:
Hi,
On Fedora Core 2, the kernel is compiled with the 4G/4G VM split option
enabled, which can prevent us from performing a correct emulation.
Win32 apps are apparently built with the assumption that they will not
be allocated
On Wed, 2004-05-19 at 11:46 +0200, Marcus Meissner wrote:
Could it be that Redhat is trying to deliberate break WINE every half year ;)
Heh, you have to wonder don't you? :)
The annoying thing about this one is that the 4G/4G layout is actually
harmful to desktop users (ie anybody who doesn't
