Blizzard's Christmas Present = TFT 1.13? Think first!

dosnt matter, bliz fixed it anyway with 1.13b

Wow... no idea people were so stupi... er paranoid. If you are seriously not going to be a blizzard customer anymore because blizzard did something that was within their legal rights then I for one am glad I wont see you people playing starcraft 2 (which I am betting is next on their list). Furthermore, if you have not installed the 1.13 patch or the 1.13b patch then just connect to bnet and get it. I have XP and a burner and none of the crap they are complaining about has happened to me.

everyone stare at the red bit of this picture. This problem is solved, thread is over.

kazaa sucks, so many fakies, use bt
(not telling what it is because wc3c does not support warez)

caps warning, if you dont like posts in all caps, press Page Down. (no i seldom post in all caps)



PATCH 1.13B IS OUT, IT DOWNGRADES WARCRAFT III'S SECUROM PROTECTION TO THE OLD VERSION, IF YOU WANT TO BE SAFE, UNINSTALL WARCRAFT III, INSTALL WARCRAFT III, PATCH TO 1.13B. PROBLEM SOLVED.

NOW CLOSE THIS THREAD.

If there is suchs problems get the no cd version of war3, also i found out by deleting the reg keys of Securecom and renaming your war3.exe to war3_1.13.exe etc removes the problem, it doesnt generate the file any more.

Really? they fixed it in 1.13b? :D

The file (Given it's on your computer) must be deleted by you, but no longer will it have a 'sharing voilation' You can look on what registry keys to get rid of (Or go into Regedit and find>securom) and delete the 29 kb sys file.

Yea you Can go to Start->Run then type regedit you can delete it from there. But I have no clue where it is and you can do serious damage to you computer I WARN YOU.

BIT TORRENT ROCKS i mean i didn't say that.
anywayz close this thread