#132 error being caused by isboxer

[KAC]

I recently purchased a 3 month license to try out this software after using keyclone for over a year without any issues. Now when trying to launch my 5 toons on two different computers with up to date drivers and everything else I get a #132 fatal error and all five instances close. I'd like to try and give this solution a fair shake but as far as multiple computers goes its been a total fail for me. I can load all my toons with keyclone fine but this gives the #132 error. Anyone have any ideas why this happens?

[Svpernova09]

I recently purchased a 3 month license to try out this software after using keyclone for over a year without any issues. Now when trying to launch my 5 toons on two different computers with up to date drivers and everything else I get a #132 fatal error and all five instances close. I'd like to try and give this solution a fair shake but as far as multiple computers goes its been a total fail for me. I can load all my toons with keyclone fine but this gives the #132 error. Anyone have any ideas why this happens?

#132 is a general wow error, you need to read the error and see what it says is going wrong.

[Lax]

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.

[KAC]

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!

[Ualaa]

Just to be clear, you launch the same number of instances and on the same computers.
The only difference is having IS or KC launch them?

You could try removing IS from the system.
And then re-downloading, which would help if your copy was somehow corrupt.
A couple of other people have had issues, which were fixed with a clean install.

Honestly, I'm not really sure.
I'm better at modifying a configuration then in troubleshooting the program.

[Fizzler]

I use to get this error nearly every shutdown but it stopped a few weeks ago.. no idea what was causing it or what fixed it.

[Lax]

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!

It would help to see your configuration, then. (This post http://isboxer.com/forum/viewtopic.php?f=18&t=13 explains how to do this, and note that your account names are censored)

If you made a Mapped Key that recurses in every window, I could see this happening. I can't really imagine what else you could have configured through ISBoxer to make all of your WoW windows close/crash at once. 2 people talked to me yesterday in the ISBoxer chat room who both managed to create a recursive Mapped Key that would crash the game when they hit it. I may need to make ISBoxer detect recursive Mapped Keys.

In plain English, in order to produce a crash like this, they had to create a Mapped Key that had a Do Mapped Key Action which ended up doing the same Mapped Key (this is the definition of recursion). It might be a Do Mapped Key Action set to do itself, or set to do a different Mapped Key that, in turn, does the original Mapped Key with a Do Mapped Key Action. This creates an infinite loop, crashing the game. (Note that no delays are possible, so it is not possible to use this "loop" functionality for anything but crashing the game)

There is no way, with the default configuration and no changes, for this crash to happen.

[KAC]

I recently converged all my subs into one bnet account. I run my slaves out of one wow folder and keyclone doesnt have virtual config files like isbox does so I used the wizard to configure the virtual wtf files so I wouldn't have to keep using the drop down menu to select each account when I launched the game. After I did this this is when I started to get the crashing error. I stopped using isboxer and innerspace and went back to keyclone. To eliminate the need to select the accounts I copied the wow folder and made it into 4 one for each account. Today I had one instance crashing with #134 error which was a failure to load map data. I recalled you sayiong that the wow instal could be corrupt so I decided to go in and check the files in that folder. I'll be dammed but that installation was fuxored as were the other 2 copies I made but not the original that I made the copies from. I fired them back up with keyclone and have not had a problem since. I don't know how the hell the folders got corrupted or why when using the virtual config files in isboxer for launching 4 games from one folder would have caused the problem.

As for runnign the game is it better to run each instance from its own folder or to run all instances form a single folder? I don't recall being able to actually pick the folder in which to run the wow.exe when setting up isboxer is this possible or is it better to just run all instances form one folder?

[Lax]

As for runnign the game is it better to run each instance from its own folder or to run all instances form a single folder? I don't recall being able to actually pick the folder in which to run the wow.exe when setting up isboxer is this possible or is it better to just run all instances form one folder?

The only benefit you get from multiple folders is having multiple configurations.

Performance-wise and cost-wise you are better off having a single folder, and with ISBoxer virtual files you get the multiple configurations while maintaining the single folder benefits.

Without virtual files, people generally use symlinks to regain most of the performance of a single folder. However, there is still extra work to do on patch day to make sure all of your WoW folders are patched even if using symlinks. (Also not a problem with virtual files)

This sort of corruption is typically caused by... WoW crashing at just the "right" time, normal wear on your hard drive, or even bad drivers used by your hard drive. When SATA drives were the new thing, I remember having lots of driver issues with the drivers that were default in windows as well as shipped with the motherboards. Then now with the new SSDs, particularly of the Intel variety (or maybe only on Intel motherboards, I don't recall right off hand but google would probably turn it up), there's also a data corruption bug. There's probably other scenarios but these are probably the most common.

To be on the safe side, I would recommend checking for drivers for whatever sort of drive it is your data is on. Other than that, running the repair tool should have solved the immediate problem, so you're probably in good shape for now