Our commitment to offer 100% resistance to 1:1 copy is more than ever confirmed. To make it definitely clear to everyone, an already implemented version of TAGESâ„¢, with a slight modification of one API, clearly repels copies right from the beginning, making the Spath method void whatever the improvement he may wish to add.
Wow… excellent assumption of Tages…
Let’s analyse this…
Our commitment to offer 100% resistance to 1:1 copy is more than ever confirmed.
Confirmed ? The only thing that’s confirmed is that the resistance boundary is NOT 100% anymore. It’s not perfect (and might never be perfect) , but it sure isn’t 100%.
Sure , 1:1 copies are not possible , but is that the goal here ? What if the goal is to make a 75% copy which removes all Tages checks ?
The Tages commitment is 100% true , but it’s a worthless commitment if Tages protected cd-roms are still copyable and running.
To make it definitely clear to everyone, an already implemented version of TAGESâ„¢, with a slight modification of one API, clearly repels copies right from the beginning,
So … despite the assumption there’s nothing to be worried about (since Tages already “confirmed” that there is still 100% resistance) , Tages actually DID modify an API to be “more 100% resistant”

Questions :
- What does this new API do ? Blacklist ? Circumvent ? Bypass ? Block ? Install weird drivers/tools/registry entries ?
- Why do Tages only points to the “Spath method” and not the no-cd cracks that have been flying around for almost a decade ?
- If there is nothing to worry about for Tages , why then still modify things (which were already implemented ?)
What’s next ? 150% resistance ?