Tijl Coosemans <[EMAIL PROTECTED]> writes:
> It appears that the only solution is to locate wine somewhere after
> 0x8000 instead of at 0x7bf0 and to allow mmap to allocate
> memory there. Then the data segment size limit can be set to 256Mb or
> something instead of 32Mb. The problem is t
Hi all!
I had a user running FreeBSD 6.2, Xorg 7.3, ATI r200 DRI driver report
a problem where running Warcraft3 crashed because it ran out of malloc
heap space. The error was:
Assertion failed: (texObj->DriverData != NULL), function
r200BindTexture, file r200_tex.c, line 1098.
fixme:ntdll:FILE_
Mike Hearn wrote:
> Well if you can get the email address of a WoW developer then maybe we
> can track down where the problem in WoW is and work with them to fix
> it.
You might have some luck contacting Sam Lantinga. He is the creator and
current maintainer of the SDL library and works for Blizza
et the email address of a WoW developer then maybe we
> can track down where the problem in WoW is and work with them to fix
> it. I don't think Wine-specific workarounds make any sense: the
> address space layout when not requesting a specific address is not
> guaranteed. Vista alrea
WoW Has a all chain of checks that go up all the way to rootkit reveler
to make sure the user is not aided by an automatic system, Given the
player an advantage other players do not have. The Memory layout checks
is for making sure the program is not loaded by a Debugger of sorts. Or
that core Dl
On 5/30/06, Mike Hearn <[EMAIL PROTECTED]> wrote:
This has been discussed previously. It looks likely that to fix this so
WoW works out of the box requires extensive and intricate changes to the
core of either Wine or the kernel to provide a more accurate match to the
NT memory layout model.
I
Mike Hearn wrote:
It's a bug in WoW itself, it relies upon the exact way NT maps memory
which is different to how Linux does it. I guess they are storing
information in the high bits of a pointer somewhere or some similar
trick.
One can never be sure, but I suspect this is not do to a bug but to
n WoW is and work with them to fix
it. I don't think Wine-specific workarounds make any sense: the
address space layout when not requesting a specific address is not
guaranteed. Vista already includes ASLR which is likely to break such
software. It will need to be fixed sooner or later, might
On Tue, 30 May 2006 16:08:42 +0200, Tomas Carnecky wrote:
> Since WoW also runs on MacOSX, how does the memory layout on MacOSX
> differ from NT and Linux?
I have no idea, but the MacOS and Windows versions of WoW will be
different; probably the bug is only in the Windows specific parts of the
co
[EMAIL PROTECTED] wrote:
> No, they have added this regressions after a little patch-set.
> So they can fix it.
> And as we can't download a playable demo ...
>
Interesting.. if MacOSX has a similar memory layout as linux, maybe we
could get Blizzard to include a workaround that is only active w
Message d'origine
>Date: Tue, 30 May 2006 16:08:42 +0200
>De: Tomas Carnecky <[EMAIL PROTECTED]>
>A: Mike Hearn <[EMAIL PROTECTED]>
>Copie à: wine-devel@winehq.com, n0dalus <[EMAIL PROTECTED]>
>Sujet: Re: World of Warcraft (WoW) patch/more address
Mike Hearn wrote:
> It's a bug in WoW itself, it relies upon the exact way NT maps memory
> which is different to how Linux does it. I guess they are storing
> information in the high bits of a pointer somewhere or some similar
> trick.
>
Since WoW also runs on MacOSX, how does the memory layout
On 5/30/06, n0dalus <[EMAIL PROTECTED]> wrote:
It would be really great if someone could document the patch and
explain what exactly is stopping WoW from working (as well as which
changes would cause problems for other programs).
It's a bug in WoW itself, it relies upon the exact way NT maps me
On Mon, 22 May 2006 19:18:07 +0100, Nick Law wrote:
> Below is an email regarding this partiicular problem, I would be
> grateful for any comments that I can pass back to Jan Riewe. Thanks
Hi Nick,
This has been discussed previously. It looks likely that to fix this so
WoW works out of the box r
Opening up the debate again on the World of Warcraft ( WoW ) memory
patch.
Some facts about WoW that may explain why the AppDB page is pretty
active and the wow patch for wine 0.9.12 was downloaded over 1000 times
from the Appdb page during a 4 week period Wow has approximately 6
million p
Well ever since me, Mike and Alexandre did the preloader work a few
years ago Wine itself has been execshield resistant, but the apps
themselves may not be (my guess is that this is why Microsoft have not
implemented it themselves ... that and they appear to be scared of
their own dynamic linker c
On 5/1/06, Mike Hearn <[EMAIL PROTECTED]> wrote:
Seems the WoW appdb page (apart from being a great example of what an
appdb entry should be like!) recommends users patch their Wine to run WoW
properly.
The patch mentioned particularly causes problems on systems like
Fedora with randomized pr
On Monday 01 May 2006 20:59, Mike Hearn wrote:
> * Is this working around a bug in WoW? (my guess - almost certainly yes)
Perhaps, but there are other problems with the Linux kernel not using the
entire address space.
> * What exactly is it doing?! No comments! It seems to be forcing the
>
Mike Hearn wrote:
> (yeah i'm bored :/)
>
> Seems the WoW appdb page (apart from being a great example of what an
> appdb entry should be like!) recommends users patch their Wine to run WoW
> properly.
>
> The patch is this one, which I am SURE we discussed before but I can't
> find the thread! S
(yeah i'm bored :/)
Seems the WoW appdb page (apart from being a great example of what an
appdb entry should be like!) recommends users patch their Wine to run WoW
properly.
The patch is this one, which I am SURE we discussed before but I can't
find the thread! So my questions are:
* Is this wo
Mike Hearn a écrit :
On Fri, 28 May 2004 09:10:22 +0200, Pouech Eric DMI AEI CAEN wrote:
Hi Mike
I've started to revisit the architecture.sgml file, and started to write
also about this matters (and a few others). For coherency reasons, if
you don't mind, I'll reintegrate your bits in the architect
On Fri, 28 May 2004 09:10:22 +0200, Pouech Eric DMI AEI CAEN wrote:
> Hi Mike
> I've started to revisit the architecture.sgml file, and started to write
> also about this matters (and a few others). For coherency reasons, if
> you don't mind, I'll reintegrate your bits in the architecture.sgml file
> Message du 28/05/04 01:35> De : "Mike Hearn" <[EMAIL PROTECTED]>> A : [EMAIL PROTECTED]> Copie à : > Objet : Add documentation on the address space layout in Wine> Mike Hearn <[EMAIL PROTECTED]>> Add documentation on the address space layout in Wine&g
23 matches
Mail list logo
