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 Blizzard
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
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
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 space layout stuff
Mike Hearn wrote:
It's a bug
[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 when
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
Interesting.. if MacOSX has a similar memory layout as linux, maybe we
could get Blizzard to include a workaround that is only active when it
sees that it's running under wine/cedega.
Well if you can get the email address of a WoW developer then maybe we
can track down where the problem in WoW
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
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
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
On Tuesday 30 May 2006 16:37, Mike Hearn wrote:
Interesting.. if MacOSX has a similar memory layout as linux, maybe we
could get Blizzard to include a workaround that is only active when it
sees that it's running under wine/cedega.
Well if you can get the email address of a WoW developer
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
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
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
(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
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! So my
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
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
18 matches
Mail list logo
