Curse

Chaos Theory Pvp · Feb 23, 2012, 08:16 PM // 20:16

Ok I thought I would change the thread to advice now I have the problem sorted to possibly help anyone with the same or future issues...

Fault:-
Basically since the 22nd/23rd Feb 2012 update (I have no idea if there is a connection there or not this was inconclusive and could be a coincidence) my guild wars would not load fully, it connected to arenanet hit 100% then closed itself down without reaching the login screen.
My game has always been loaded onto my secondary drive E: for years without any problems whatsever nothing was altered on my computer for this to happen.
The problem eventually was found to be the guildwars server was looking for the DAT file on my C: drive which was obviously not there, even after a new install with all the targets and registry at > E: drive.
The issue was resolved by completely uninstalling the game downloading the NCsoft launcher and installing the game using that.The default target is the primary drive (C: ) when installing so you have to create a folder name it Guild Wars into the NCsoft folder target it then to
E:\Program Files\NCSoft\Guild Wars.

So now the server loads DAT into E:

Simples.. not :P

http://us.ncsoft.com/en/launcher/ncsoft-launcher.html

Wika Sham · Feb 23, 2012, 10:14 PM // 22:14

Same thing happening to me currently and a couple others it seems. I sent in a ticket to Anet...

Showtime · Feb 23, 2012, 10:20 PM // 22:20

update happened. if running windows 7 need admin rights to make changes. go to update thread for details.

Chaos Theory Pvp · Feb 25, 2012, 08:24 PM // 20:24

Updated................................

Chaos Theory Pvp · Mar 01, 2012, 03:38 PM // 15:38

Updated any ideas folks?

Calista Blackblood · Mar 01, 2012, 05:34 PM // 17:34

Copy the .dat?

Chaos Theory Pvp · Mar 01, 2012, 05:51 PM // 17:51

Hi there is a copy of everything on E: drive, the only way it will work if there is a DAT file on C: drive... surely Anet do not only run GW from C: only and only C: drive... it has always worked before from E: maybe the 22 feb update done something to this..