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

Blizzard Made a post on the subject, Yet it's nothing that important.

If you read Kharmas post(s) you'll see that it's only a updated version of Securom, Meaning that you probaly wont suffer any big problems that wouldn't of existed prior to 1.13.

Annoying, Yes. But no, not evil.

Is it possible that this was done by some rogue programmer or something? Because I haven't known companies to intentionally install things on your computer that could get them sued.

Actullay, Blizzard probaly can given the liscense agreement Giving them the right to install programs on your computer, Excluding that of malicous intent (Viruses, Trojans, and such) , I believe.

Well, whatever it is, I'm glad I have a Mac.

In that case, they're still breaking the law. If they won't even talk to us about it, how can anyone except the people who made it know that it isn't a virus or trojan?

and what's this? For Some odd reason, while I was playing my game, it comes up and crashes saying: "FILE DATA CORRUPT: Human2.mp3"

that is nothing to do with copy protection. that is simply a corrupt mp3 file in your war3.mpq

It only happened after 1.13.

I don't see anything yet but I havent really checked. I noticed a slowdown in My comp though.

Wheres our archmage? Why? I need him to blizzard BLIZZARD. Well not until we really need him too... but what blizzard is doing is wrong or atleast from what I hear.

Great discussion and all but what are we suppose to do?
Do we not download 1.13?

No wonder!!! my WE doesnt work when i import files now it worked fine intill this new patch came god damn u blizz

Alright, I now know how the protection works.

Using event viewer and reading the englishish portion of the random sys file.

When you launch war3x 1.13 it creates a virtual drive using a generic interface, and tries to burn a 0kb cd image. (When war3 starts check your event viewer it goes Imapi Burn Process start mode enabled, then goes Imapi burn process run mode start (when your animated icon spins), and then finally goes Impai burn process stop mode.
If it doesn't burn the image (because there is an emulator using the interface), it reports that their is an emulator interfering.

My guess is that the latest version of Dtools uses a different interface, which is why it works just fine. Also the regular ROC disc works in place of the TFT disc if your having troubles. In conclusion, this file is a system driver as it installs virtual hardware. As for the memory leak and footprint it takes up my guess is sloppy programming. (Maybe blizzards fault).


^^ ACCORDING TO WEAADDAR ^^

Kharma its a shittly written driver which conflicts with your regular cd burner.

My super duper analysis (direct Copy and Paste from my blizzard forum post)
Alright, I now know how the protection works.

Using event viewer and reading the englishish portion of the random sys file.

When you launch war3x 1.13 it creates a virtual drive using a generic interface, and tries to burn a 0kb cd image. (When war3 starts check your event viewer it goes Imapi Burn Process start mode enabled, then goes Imapi burn process run mode start (when your animated icon spins), and then finally goes Impai burn process stop mode.
If it doesn't burn the image (because there is an emulator using the interface), it reports that their is an emulator interfering.

My guess is that the latest version of Dtools uses a different interface, which is why it works just fine. Also the regular ROC disc works in place of the TFT disc if your having troubles. In conclusion, this file is a system driver as it installs virtual hardware. As for the memory leak and footprint it takes up my guess is sloppy programming. (Maybe blizzards fault). Now I also know why you can't burn cds after you play war3x 1.13

When you normally burn a cd after the stop event it does a close event. This [crappy driver] merely does a stop event, meaning that the Imapi burning rom can not be used by others burners until you manually call a close event. But you can't as the drive was removed, and the letter its given is random (or one of the drives already registered by windows!) The only way to fix this is to restart windows. Delete this file, when your not using war3 and use a No-cd crack for worldedit just for safety sake.

My CD Rewriter (using Nero) hasn't been working since I applied the patch - consequently f**king up 3 CD's when I've tried to burn something. Several other people have reported similar, CD-rom related problems.

"This is bullsh*t."-Jim Raynor.

Oh hell, Now im pissed, I finnaly get a good Cd-Burner just to have it not work?!?!?!

It better still work...

After Testing.....

I'll be passing out the grenades....