CurseForge and Overwolf are joining forces!
Awesome More Information
  • 0

    posted a message on WowAceUpdater 1.9.44+ Official Thread
    Today my WAU auto-updated to version 1.9.46.747 and does not crash with a normal (un-edited) hosts file. It appears this problem has been solved.
    Posted in: Updaters
  • 0

    posted a message on WowAceUpdater stopped working
    Today my WAU auto-updated to version 1.9.46.747 and does not crash with a normal (un-edited) hosts file. It appears this problem has been solved.
    Posted in: Updaters
  • 0

    posted a message on WAU 1.9.46.746 CRASH FIX - Vista and XP Instructions
    Today my WAU auto-updated to version 1.9.46.747 and does not crash with a normal (un-edited) hosts file. It appears this problem has been solved.
    Posted in: Updaters
  • 0

    posted a message on WAU crashes
    Today my WAU auto-updated to version 1.9.46.747 and does not crash with a normal (un-edited) hosts file. It appears this problem has been solved.
    Posted in: Updaters
  • 0

    posted a message on WAU crashes
    Quote from Eldamar »

    unfortunately the posted fix does not seem to work in all cases. followed all the instructions in the post for vista and it seemed to make it crash faster then it was previous...

    Hoping for at least a fix on this even if they don't do any further development as trying some of the other addon downloaders nearly wiped my entirely custom ui


    Pleaes try the ping test shown below to check your work.
    Start: All Programs: Accessories: Command Prompt
    Type in "ping wdaddons.com" without the quotes, and press enter.
    If you receive an error message, then double check your changes to the hosts file.
    If you see the following, I don't know why it's not working for you.
    Please post your results if they are different.

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\Admin>ping wdnaddons.com

    Pinging wdnaddons.com [24.129.136.26] with 32 bytes of data:
    Reply from 24.129.136.26: bytes=32 time=98ms TTL=52
    Reply from 24.129.136.26: bytes=32 time=97ms TTL=52
    Reply from 24.129.136.26: bytes=32 time=96ms TTL=52
    Reply from 24.129.136.26: bytes=32 time=97ms TTL=52

    Ping statistics for 24.129.136.26:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 96ms, Maximum = 98ms, Average = 97ms
    Posted in: Updaters
  • 0

    posted a message on WAU 1.9.46.746 CRASH FIX - Vista and XP Instructions
    Quote from ozsmeg »

    The ultimate question is. Why does it craash why is the timeout/reponse not captured and ignored?


    From the posts in the thread referenced in my original post, it appears that WUA was written with the expectation that the domain name would always resolve, and therefore no error handling would be needed. It takes a lot of time to create handlers for every possible exception, so it is not uncommon for the less likely scenarios to go ignored. Some call this lazy, others call it efficient.

    To be specific, the website is not timing out. The domain name of the website is not resolving to an IP address.
    Posted in: Updaters
  • 0

    posted a message on WAU 1.9.46.746 CRASH FIX - Vista and XP Instructions
    Quote from Kyrros »

    LOL, That CPA Firm's hosting ISP is probably gonna be like

    "WTF?! How'd these guys get so popular all of the sudden?!" :-p



    A web server can serve multiple websites using the same IP address. When your web broswer requests a page, it provides the domain name in your address bar. The web server then uses that provided domain to determine where to find the rest of the address your browser requested.

    To demonstrate, first apply to change the hosts file as shown above. Browse to wdnaddons.com, and then browse to 24.129.136.26. You should see two totally different sites.

    Ultimately I believe it is the same server providing the adds. We are just bypassing the fact that wdnaddons.com no longer resolves to an IP. Since the wdnaddons.com site itself does not appear, I'm guessing their account on that server has been shut down.
    Posted in: Updaters
  • 0

    posted a message on wowaceupdater
    Please see my crash fix instructions here: http://www.wowace.com/forums/index.php?topic=14320.0
    Posted in: AddOn HELP!
  • 0

    posted a message on WAU 1.9.46.746 CRASH FIX - Vista and XP Instructions
    Temporary sticky please.
    Posted in: Updaters
  • 0

    posted a message on WowAceUpdater 1.9.44+ Official Thread
    Please read my crash fix instructions here: http://www.wowace.com/forums/index.php?topic=14320.0
    Posted in: Updaters
  • 0

    posted a message on WowAceUpdater stopped working
    Please read my crash fix instructions here: http://www.wowace.com/forums/index.php?topic=14320.0
    Posted in: Updaters
  • 0

    posted a message on WAU crashes
    Please read my crash fix instructions here: http://www.wowace.com/forums/index.php?topic=14320.0
    Posted in: Updaters
  • 0

    posted a message on WAU 1.9.46.746 CRASH FIX - Vista and XP Instructions
    As shown at http://www.wowace.com/forums/index.php?topic=13733.20 the crash is happening because WAU is trying to connect to an add server by a name which no longer resolves to an IP address. Until WAU can be updated to not use this server name or better handle the error, we must make that server name resolve into an IP addres. This is done by editing the "hosts" file on your computer.

    XP (simple)
    Launch WordPad from the Start Menu. File: Open, then paste in the following:

    %windir%\system32\drivers\etc\hosts

    Add this line to the end of the file, then click the Save button and close WordPad:

    24.129.136.26 wdnaddons.com

    WAU show stop crashing now. To double check your work, open a Command Prompt from the Start Menu (or Start: Run: CMD) and type "ping wdnaddons.com". If you get replies from 24.129.136.26 then it worked.

    Vista (less simple)
    The host file cannot be edited by a normal user. Instead you must run WordPad as Administrator (which is not the same as being logged in as an administrator).

    To do this, find WordPad on your Start Menu, then right-click it and choose "Run as administrator". Follow the XP instructions from there, the rest should be the same.
    Posted in: Updaters
  • To post a comment, please or register a new account.