These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page12
 

Launcher stuck again (just like every time)
Author
Previous Topic Next Topic
Eleeyah Myrha
Federal Navy Academy
Gallente Federation
#21 - 2014-07-24 16:13:15 UTC
Lucas Kell wrote:
Eleeyah Myrha wrote:
Lucas Kell wrote:
I'm with McCandless on this one. If you take a step back and look at the situation, you'd see that the common variable in your problems is you. I don;t have you in my setup and it works fine. Ramona has no you and can patch and launch fine every time. You on the other hand have you, and problems occur. User error, plain and simple.

I'd go with my usual response of "When you first think it's frozen, it's probably not. Stop touching it and wait". If you think "oh it's frozen, I better close this down and try again", it's likely to lead to badness, kinda like if I switch off my PS4 at the wall because a system update is taking to long.
If you'd actually read what I wrote, you wouldn't be typing that.
Wrong, since I read what you wrote, and yet still typed that. I take it you mean because you wrong about you "waiting for a few hours", right? Well First off, I've had the pleasure of working in a support position in a large business, and I know that "a few hours" differs greatly person to person.

I also know that if it gets stuck, then a few hours later "may show a 100% completion, but it never actually is completed" then it wasn't stuck, hence it's progressing in %. 100% may in fact be "nearly done", so leaving it a further "few hours" may result in magical completion.

I also know that 9 times out of 10, when people complain about their launcher issues, when talking to them you find out that they shut down their launcher after what is a pretty short amount of time for a large patch to be installed. Remember that it's not just your internet connection, but how fast their server can respond, then however long it takes for the actual patch process to run (which can vary a lot).

I'm talking about 7 hours sleep + 10 hours not being home. So no, I'm not wrong about "a few hours".
Frostys Virpio
State War Academy
Caldari State
#22 - 2014-07-24 17:00:22 UTC
Eleeyah Myrha wrote:
Sara Tosa wrote:
Eleeyah Myrha wrote:
Jake Warbird wrote:

[quote=Sara Tosa]memtest/chd.

Care to elaborate?

did you check if your pc is ok? if this happens everytime it could be a faulty ram stick or hd

My computer is fine, I've run the launcher on 3 different setups (XP, Vista, 7) with different modules, with different security softwares, etc. over the years and it always froze since the moment they implemented it. When I reinstall the game using the offline launcher and the 2 payloads, the first patch will usually install fine, the second might or might not freeze visually but still finish (the progress suddenly jump to 100% then, but the launcher won't start the game, but you can still do so using the exefile.exe in \bin\) and the 3rd patch almost always breaks the launcher for good. Sometimes it's the second already.

This has happened regardless of where I live, regardless of the computer I use, regardless of whether or not I do anything with the PC during that time and regardless of whether I have a firewall/Anti-Virus/whatever installed or not. The traceroutes have always been fine.


Then it sure as hell is a code 18 error because it's the only thing you didn't try changing.
CompleteFailure
DAWGS Corp.
#23 - 2014-07-24 20:17:03 UTC  |  Edited by: CompleteFailure
I used to get this same thing on my SISI install. The only way I was able to fix it was by deleting my SISI install folder, and recopying my TQ folder. At the same time, I also deleted the cache folder in my AppData folder. The problem isn't with the launcher, or with the patch, or with your computer, or with you. It's something in either the install or cache folders. My guess is you're going to have to run a clean install from scratch to fix this.

E: At a minimum, start with clearing your cache folders as was suggested earlier. If that doesn't work, nuke and pave.
Previous page12