Close
Page 2 of 2 FirstFirst 1 2
Showing results 11 to 16 of 16

Thread: Change it back!

  1. #11
    Rated Arena Member Shabu42's Avatar
    Join Date
    May 2009
    Location
    Lakeland, FL
    Posts
    133

    Default

    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
    Fxv Fxz Fxy Fxw
    Shaman, High 5s of 1828 (S8)

  2. #12

    Default

    Quote Originally Posted by Shabu42 View Post
    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 it
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

  3. #13

    Default

    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.

  4. #14

    Default

    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
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

  5. #15

    Default

    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
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

  6. #16

    Default

    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.
    80 Blood Elf Paladin, 80 Blood Elf Priest,80 Troll Mage, 80 Undead Warlock, 80 Tauren Druid, 80 Undead Rogue
    80 x4 Shaman (Orc x3, Troll)

    Madoran - Horde - PvE

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •