Printable View
Please revert your changes to IS =(
Since the patch I have only been able to successfully start up all 5 clients once and now all the windows are unable to become the main window. I tried reloading and they just stay minimized. I cant do anything. :(
Quote:
Originally Posted by Multibocks
were there changes to IS today? up to last night i've been able to play without problems (cept for the bex issue).. haven't tested today as i'm @ work .
yes it was patched and now that I can get in game I can't switch to other windows unless I open any other program and then minimize it, only then will the main window maximize. Makes it really hard to switch to alts windows.
I've just got the updates and switching windows works fine for me. Have you tired re-exporting your ISBoxer setup? The previous update gave me FTL 1-9 keys which I had disabled. Re-exporting my ISBoxer setup fixed that.
Actually, got a bug too: the mouse over the secondary windows does not work - it turns back to a regular windows cursor (not the blizzard one) and I can't interact with anything using it.
I've reverted the patch and I'm working on getting some issues fixed before re-patching. Restart Inner Space and it'll patch back down.
I was just about to make a post about this as well. Cant get all 5 windows up. The 5th one locks up, and I cannot switch windows by clicking.
Thanks Lax!
Now if we can only get Blizzard to revert THEIR latest patch -.-
If only they were that helpful.Quote:
Originally Posted by Svpernova09
Lax, I can confirm the mouseover 2ndary windows not working. Thanks for working on it.
I downloaded the first patch, didnt run into too many problems, every now and then wow would just crash. Then I had to DL the 2nd patch, now I can barely start up without one crashing. Even had it crash during arena 3 times :(. I dont know if its IS, but thats the only thing thats changed and Ive never had wow crashes before. Also have the issue of restarting instances, not going to their appropiate window allotment space
If it had anything to do with the IS update, then the revert to IS 1.09 build 5039 would change it back to exactly the way it was before the 1.10 update. If it still crashes with 5039, and it didn't yesterday, then I don't think that's itQuote:
Originally Posted by Shabu42
Not sure this will help, but I received C++ run-time error R6034 after downloading today's WoW update. I was able to click past it, but might be related.
R6034 is a different issue entirely ;) If that keeps coming up, come by the ISBoxer Chat Room and I'll see if I can find out what's causing it. I fixed R6034 issues several months back
Okay the new R6034 from the WoW update -- which apparently happens when you log in with an authenticator -- is fixed in IS build 5150 which is now live. If you get that error, just update IS and you should be good to go :)
Thanks Jafula for testing the fix for me in the ISBoxer chat room
So for people like Lax and Jafula, this makes me wonder about my experiences with a corporate IT organization.
It takes literally hundreds of thousands of "dollars" to get even the simpliest IT project done. I put quotes around dollars as its really simply an allocation of the IT staff that is decked against a particular project.
I know its apples and oranges, but here a customer identifies an issue with ISBoxer and the provider has at least provided a temporary solution in less than a business day.
Man, if I could get Lax to work with me in my business...... domination. ;)