Thanks for the swift reply Andrew :D.
I couldn't write the code, personally, so I tend to just hit the brick wall, /cry a lot -.-, and spend hours searching through shit I don't understand trying to understand XP.
At least you have the complexity to at least see a future in which the client and its code make some kind of long term sense to you...
Thankyou for explaining it was complicated :).
So what about this:
So the patch fix seems to be "An alternative would be to compile the current WoW.exe with IMAGE_FILE_LARGE_ADDRESS_AWARE set, making the VA space 4GB on 64-bit Windows"... with http://www.ntcore.com/4gb_patch.php.
*has no idea how to do this*...
The blue post, on the forum about it. I believe from what i read on one of the middle posts in response by him, is that he uses this patch at home. If its going to make it more stable... any idea of how to make it work.
I does happen only once a day really, and it does just log straight back on so its not big deal. Its just, in the heat of the moment, wiping a raid might be a bad way to go. But, ill be flushing out my addons [which i have been trying to do over the last year anyway, getting a fine tuned list for effective fps]. I cleaned out the cache < and ill keep doing this regularly.
So hopefully that fixes some of the issue. But yeah... did u try the patch?
It gives me a program, wine, crossover and etc just look at it like "wtf is this weird program" -.-. So I'm a little lost on where to put it in the backend files :P.
You are allowed to say, "its too complicated to teach you," because I got the impression on the forums that it was semi innate. Like people knew because it was a part of what they did within their comps, hence why it wasnt explained I think somewhat. He does have an interesting blog on that site... interesting indeed :). But i couldnt really find a step-by-step install guide, because its usable for a wide range of programs /sigh...
except that. Thats a readme, but I have no history with injecting code to a portable executable file, rofl.