First post, by DosFreak
- Rank
- l33t++
http://www.gamesetwatch.com/2009/06/gamesetin … arforce_and.php
To reach this goal we had to penetrate into the system pretty deep, as hackers and emulating tools do exactly the same to circumvent protection. It was fighting fire with fire. It is always weird for me to see users hate protection drivers when the Daemon Tools one also operates in Ring 0, but it is highly appreciated. The difference is that the StarForce driver is fully certified for Windows XP and Vista, passed through numerous tests inside Microsoft testlabs. Our company has gained Microsoft Certified Partner and Technological Partner levels. And I can’t say something similar about DT.
It's sad that Microsoft certified this crap. Users hate DRM jackass, because it more often that not screws up their system I can mabye remember once or twice where Daemon Tools caused me issues and it was easily solved (BSOD caused by Daemon Tools driver). Not so with StarForce.
Today, most publishers implement protection during the final stages of game development. This means that the resulting protection solution is pretty weak and uncomfortable to the user. For instance, one possible way is to plan protection methods in the early stages of game development. I’d say it is better to start during the program architecture’s development stage. Only then will the final solution be highly compatible and extremely complicated to circumvent.
Looks like any new game using StarForce may take longer to crack.....guess I won't be buying those games.
We do not intend to repeat our past mistakes.
You already are.
