World.myp strikes again.

[schild]

I'm not reinstalling for a 3rd time. If anyone has a solution, please do tell. The only thing I hate more than stupid is patching issues.

And before some wiseass takes this as me quitting, not in the least, I just don't want another (read: 3rd) corrupt install and desire a solution.

[kildorn]

Man, what's going on with it, exactly?

[schild]

I don't fucking know, but it's angering.

[schild]

Got it working, apparently an instance of WAR keeps running in the background, keeping any new instances from patching. /stupid

[Arrrgh]

Done a disk surface scan lately?

[schild]

That's assuredly not the problem. What would lead you to believe it was?

[Arrrgh]

Because bad sectors cause file corruption. Looks like I replied to the first post. Odd, I normally am able to master the art of scrolling down.

[schild]

It's not file corruption.

[squirrel]

No it's not. Basically there are cases where war.exe doesn't actually quit. So when you go to patch a new instance of war.exe is launched and it can't patch because the original instance has the file locked. Et voila.

[raydeen]

Speaking of patching war.exe, I've noticed more than a few times that war.exe will patch before the game starts up, then at some random point, I'll crash out and when I restart, war.exe patches again. Is the game not actually writing the patched file to the disk until the game is successfully shut down? That just seems weird.

[Zetor]

My ISP is wonky.. sometimes I drop connection for a minute or two.

The awesome part is, if I try to start up the patcher while I'm not connected, it just sits there without even giving me a username/password screen, and I have to kill the patcher via the task manager... if I don't, trying to start the patcher again will give me the "can't access warpatch.bin (or something)" error. 


-- Z.