Curse

ShadowsRequiem · May 22, 2009, 07:20 PM // 19:20

Well I have no idea wtf is wrong with this damn game. Ever since I came back to GW i've been having the "repairing the data archives" almost every day(sometimes twice a day). It does this automatically when I try to start the GW program.
Now today it has deleted every RED ENGINE GORED ENGINE GORED ENGINE GORED ENGINE GOing file and now I have to data archive > then download 5k files and now when I got a chance to finally login I now have to download 21k more files(Now its 25k files gg).

Forgot to say that the data archive repair doesnt happen everytime I try to start the game, but still 1-2 a day.

Wtf is wrong with this thing.

Kattar · May 22, 2009, 07:33 PM // 19:33

Did you add the -image tag onto the program shortcut and forget to take it off?

If not, there's probably a damaged sector on your hard drive.

ShadowsRequiem · May 22, 2009, 07:35 PM // 19:35

Quote:

Originally Posted by Katsumi

Did you add the -image tag onto the program shortcut and forget to take it off?

If not, there's probably a damaged sector on your hard drive.

nope i've never done or even tried to do that : /

Kattar · May 22, 2009, 07:42 PM // 19:42

Ok, you might want to run checkdisk. You can do it from the command line or Windows Explorer. Instructions can be found here: http://support.microsoft.com/kb/315265

Run it once. Post here if it finds any bad sectors.

MisterB · May 22, 2009, 08:22 PM // 20:22

I had this before, and faulty RAM was the problem. Run memtest overnight if your hard drive checks out.

Chthon · May 23, 2009, 02:39 AM // 02:39

Top three suspects are:
1. Bad internet connection
2. Bad HD. Use chkdsk.
3. Bad RAM. Use memtest.

Quaker · May 24, 2009, 06:42 PM // 18:42

Agree with 2 & 3 above.

GranDeWun · May 27, 2009, 05:57 PM // 17:57

I just went thru this; ultimately the problem was bad RAM.

GW is actually a pretty good way to test memory: it loads a ton of files into memory, then saves it to disk at the end. If the checksum is bad on next start, it runs the repair. So a bad memory address almost always causes the repairing archive error.

New Buddha · May 27, 2009, 06:07 PM // 18:07

I too just started to have this problem. Could overclocking the cpu and/or video cause this? I had no problems in the past even with the OCs.

will check the suggested when I get home tonite.