Close
Page 2 of 3 FirstFirst 1 2 3 LastLast
Showing results 11 to 20 of 24

Hybrid View

  1. #1

    Default

    I don't see what the issue is - am I the only one who runs all his copies of wow from the wow.exe as opposed to the launcher?
    Resto Shaman + 4 DK's, work in progress...
    ------------------
    Teezy/Jaqblaq @ Stormrage
    Emeritus Guardian and Keeper of the no focus manifesto.

  2. #2

    Default

    Quote Originally Posted by Zzyzxx71 View Post
    I don't see what the issue is - am I the only one who runs all his copies of wow from the wow.exe as opposed to the launcher?
    No, I stopped symlinking for this very reason. I run all 5 from one wow.exe and it works just as well.
    "My dogs could roll heroics with how a lot of you play."
    - Fursphere 2010




  3. #3

    Default

    If you guys have symlinked folders you only need to patch the main folder. Then go in and copy the Repair.exe, Launcher.exe and there is one more item just look at the modified date to find out what it is. Copy those 3 files to each of your folders and profit as you normally do.

    Edit: This is only for this tools update patch last night only. Okay need to learn to string words better. Normally after a patch you copy the WoW.exe and the Wowerror.exe. Last nights update messed with the launcher and the repair and something else.. Sorry not at home so can't tell you.

  4. #4

    Default

    Launcher what's a launcher?

    Seriously though the only time I see that stupid box is on patch nights, I just launch the wow.exe directly

  5. #5

    Default

    Yeah I start all my wow's via their .exe. However when the patch hit I found that when I patched up my main as normal.. then copied the wow.exe and wowerror.exe as I normally do on patch day.. only 1 of my screens worked. the others errored out or would go to the download screen. Since this was a tools patch, the wow.exe didn't change.
    So I looked at what did change and saw that the launcher, repair and I still can't remember what the third item is in the main folder, but those 3 things changed. so I then just copied and pasted those 3 items to my other folders and I was back in business. I relaunched my games and none of them tried to patch anymore or gave me errors.

  6. #6

    Default

    So it is the launcher that prevents more wows running. So there should be no problem then cause I don't use the launcher. whew!
    Dana Pain
    Legion of Boom
    Kil'Jaeden



  7. #7

    Default

    Launcher?

    But for some reason, I'm having trouble logging in more than one account at a time. They stay logged in fine, but only one auth at a time will succeed. WTF? I don't want to spend five minutes just logging in to do any little thing...

  8. #8

    Default

    Yaki do you have an authenticator? If that is what you are talking about it, that is a totally different story that has been talked about for a while now regarding the battle.net accts only allowing you to log in once now accross multiple accts single authenticator. A current workaround for that is to have multiple b.net accts so you can still use 1 authenticator code. If that is not what you are talking about ignore this whole post.. lol.

  9. #9

    Default

    Wild, all my accounts log in just fine following my usual patch one/copy files procedure. On the other hand, when I log in I cannot interact with anything or anyone. Seems Blizz wants me to do a bunch of stuff I don't want to do.

    Can anyone with a bit more programming or computer understanding explain to me how every time a patch comes out (that does not allow a significant player base game access) Blizz tells everyone, "Yes we know everything was fine yesterday, but we patched the game and now YOUR computer is screwed up, you need to fix it."?

  10. #10

    Default

    Quote Originally Posted by Jubber View Post
    Yaki do you have an authenticator? If that is what you are talking about it, that is a totally different story that has been talked about for a while now regarding the battle.net accts only allowing you to log in once now accross multiple accts single authenticator. A current workaround for that is to have multiple b.net accts so you can still use 1 authenticator code. If that is not what you are talking about ignore this whole post.. lol.
    Aww, crap. I don't really want to take the authenticator off, but since I already merged the accounts it sounds like the only way to get sane logins back.

Posting Rules

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