Error #132 Wow crashes when launched through pwnboxer

[ignatius937]

I cannot seem to overcome a problem I am having. When wow is launched using pwnboxer the dreaded Error #132 displays immediately. When I launch wow normally from the shortcut wow runs fine and I have never had this error during normal play. Pwnboxer was working fine about 3 patches ago.





I just installed wow fresh with no addons but the error continues. If I point pwnboxer to launch wow via Launchpad.exe instead of wow.exe the error does not happen, but pwnboxer does not control the size/position of windows nor remove the window frames...and key broadcasting does not work. If I launch wow without pwnboxer via either the launchpad or wow.exe directly wow works fine. Aside from wow updates I do not know of anything which has changed on my pc. I upgraded my nvidia video drivers, even though they used to work fine with pwnboxer, but that also had no effect.

Any ideas?

[Tim]

Very weird, I've never heard of this before.

Try this: Run each of your WoW accounts via wow.exe not using Pwnboxer. Go into the options, set widescreen mode in video, whichever one looks right. Also, set windowed mode and make sure maximized is NOT selected.

Do that for each account, then log out of WoW normally. Then try to start them up with Pwnboxer.

If it crashes still, at what point does it crash, after you log in, before it shows up, on the first game or second, and any other useful info.

Thanks

[ignatius937]

Thanks for your prompt responses. I have googled the problem but cannot find anyone using pwnboxer with this problem. Those experiencing it in wow are many, fixes range from updated video drivers to new memory to changing memory voltages in bios to we don't know because this has never been a repeatable error just a random one. (I've got that one beat as this happens every time I try to start games through pwnboxer) Blizzards official stance seems to be "we don't know, nor care".

I tried your suggestions, and many other configurations in my own tinkering. Same error. It crashes at the exact same point it crashes every time, when trying to load the wow window. In the above screenshot the wow game window is actually shown, the thick blue bar near the top of the picture is wows title bar, and the grey transparent frame is actually wows window border. Its contents are transparent, the error pops up before it can display any picture/login screen.

As mentioned pwnboxer used to work fine, I ran 4 toons without problem, all 4 on one monitor, and television shows/video full screen on the second monitor. Pc is a quad core 2.6, 4gb ram, nvidia 8600gt video, few terabytes, win xp pro sp3. I have tried disabling the second monitor and obviously took it down to only trying to run 2 wows at the same time.

I think I'm going to have to try a reformat:-/

[EaTCarbS]

132 errors can often be related to cooling issues.

How are your temps?

[ebony]

or bad ram

[ignatius937]

Temps and memory perfectly fine. Only happens when wow is started through pwnboxer.

[ignatius937]

A fresh xp install and everything works fine again. Not sure what changed with my old setup, but something must have:-/

[Tim]

My only guess is that the window sizes of WoW was conflicting with some cached WoW settings, either in the game, or with game addons/mods. I've seen it happen before, but in a different error than you described, but all were fixed in generally the same way.

Glad its working for ya

[Bubba]

I have had this error on occasion, IRC it was when I clicked all WOW windows to close from Pwnboxer. I was also trying to do some other things when these occured like open a browser. I think it happened once just because when I was playing but Im old and decrepit so my memory is failing.