• Visit Rebornbuddy

    • About 112 error

    Discussion in 'Honorbuddy Support' started by RoloTomasi, Oct 30, 2013.

    Thread Status:
    Not open for further replies.
    1. RoloTomasi

      RoloTomasi New Member

      Joined:
      Jun 8, 2011
      Messages:
      85
      Likes Received:
      1
      Trophy Points:
      0
      This error occur after you rename Wow-64.exe.
      I think hb launcher do this(rename Wow-64).
      After last wow update wow 32 client check for Wow-64.exe and if have a problem with it(not exixt another size) throw this error.

      But when we rename Wow-64 to normal we can't lauch hb.... but wow luached right.

      If you have this error just check the name Wow-64.exe in your game folder. But hb cant start now.
       
      RoloTomasi, Oct 30, 2013
      #1
    2. RoloTomasi

      RoloTomasi New Member

      Joined:
      Jun 8, 2011
      Messages:
      85
      Likes Received:
      1
      Trophy Points:
      0
      And

      from http://www.thebuddyforum.com/honorb...uddy-test-release-660-possible-solutions.html

      not have the status FIX. Status changed to NotWORKed.
       
      RoloTomasi, Oct 30, 2013
      #2
    3. meingb

      meingb New Member

      Joined:
      Jan 15, 2010
      Messages:
      92
      Likes Received:
      0
      Trophy Points:
      0
      i have the same problem as soon i staart 64 bit it works again but others dont :( i think blizzard is really goin to stop these bots soon doing all this and that
      its time for64bit client from honorbuddy :p
       
      meingb, Oct 30, 2013
      #3
    4. gen0m

      gen0m Member

      Joined:
      Feb 8, 2013
      Messages:
      78
      Likes Received:
      1
      Trophy Points:
      6
      this happend for all who uses x32 wow client

      blue post from EU forums
      link: Error #112 - Unable to validate game version - Forums - World of Warcraft

      and..
      battle.net error #112 - Forums - World of Warcraft you can still read this thread ( old US thread )
       
      gen0m, Oct 30, 2013
      #4
    5. webhond

      webhond TEMPORARILY MUTED

      Joined:
      May 23, 2011
      Messages:
      2,471
      Likes Received:
      19
      Trophy Points:
      0
      webhond, Oct 30, 2013
      #5
    6. IksDeh

      IksDeh New Member

      Joined:
      Sep 22, 2013
      Messages:
      35
      Likes Received:
      0
      Trophy Points:
      0
      IksDeh, Oct 30, 2013
      #6
    7. IksDeh

      IksDeh New Member

      Joined:
      Sep 22, 2013
      Messages:
      35
      Likes Received:
      0
      Trophy Points:
      0
      The issue is resolved as blizzard fixed it a few minutes ago.
       
      IksDeh, Oct 30, 2013
      #7
    8. Fenol1

      Fenol1 New Member

      Joined:
      Oct 15, 2013
      Messages:
      83
      Likes Received:
      0
      Trophy Points:
      0
      Anyway if you guys get this error in the future , start game , -> options change it so it doesnt launch in 32 bit and it will automaticly launch in 64 bit wich usually works when the 32 bit is down :) GL in future
       
      Fenol1, Oct 30, 2013
      #8
    9. Unimight

      Unimight New Member

      Joined:
      May 24, 2012
      Messages:
      30
      Likes Received:
      0
      Trophy Points:
      0
      I still feel like the bot should have 64bit support, incase this doesn't happen again.
       
      Unimight, Oct 30, 2013
      #9
    10. ryftobuddy

      ryftobuddy Banned

      Joined:
      Aug 19, 2011
      Messages:
      2,291
      Likes Received:
      34
      Trophy Points:
      0
      The 112 error has absolutely nothing to do with 32 bit, nor does it have anything to do with Honorbuddy in any way.

      I had the same error yesterday, but as soon as the servers came back up, it was resolved.

      Sometimes a little patience goes a long way...

      And next time, maybe check the actual wow forums before you assume this has anything to do with the bot.
       
      ryftobuddy, Oct 30, 2013
      #10
    Thread Status:
    Not open for further replies.

    Share This Page