Quote Originally Posted by Lax View Post
To be fair it would take more information to say what's happening, but it's highly unlikely that ISBoxer would *cause* a #132 error (especially considering nobody else is making similar reports). #132 just identifies a type of error that can happen, specifically a memory error. The other information in the error message would specify why it is actually getting the error (mostly useful for Blizzard to be able to analyze and identify the line of code for example that is causing the problem).

With that said, no I couldn't possibly guess right off hand why you get the error. In my experience I've gotten this error if the WoW install was corrupt, in which case I would suggest using the WoW repair tool. I've gotten this error if there's bad RAM, in which case I would suggest replacing RAM. I've gotten this error if the PC is overheating, in which case I would suggest checking all of the fans in your PC, especially the video card fan.

I know you'd rather it just be a bug in ISBoxer that I could fix for you, but ... sorry.
No lax reason I think it might be innerspace to clarify not isboxer. I use one folder on my second pc to launch 4 instances of the game. When i use keyclone to launch those game instances it works fine. I have never gotten a #132 memory access violation. I am using 8 gigs of ocz reaper in a fairly new machine under a year old which I put together in April of '09. When I run my team with innerspace it will load the one copy of wow on my main machine then load the other 4 copies on my slave computer but once they are all loaded every instance closes even on my main computer but I only get the #132 memory access violations on my slave computer that tried to run the 4 instances of wow not on my main computer. The reason I think its innerspace is because it is shutting down the one instance of wow on my main computer also. As far as corrupted files go I don't think its that because keyclone will launch 4 instances on the computer fine and I never have a problem. If the game does crash from a fatal error during game play, which is not very often, only one instance of the game will close on the computer running my 4 slave copies not all of them. I'd really like to get innerspace working right using two computers because I want to use the mouse broadcasting feature which keyclone doesnt have. Its driving me crazy that it won't work!