Starforce 3 - The gravestone?

[dyn!o]

"Then the crack is not as interesting (even though it is still impressive) protect.dll changes from game to game - the same effort that was put into this particular game will have to be repeated on others.��

With all respect, Doug:

In some previous post I suggested that maybe we should avoid so brave statements . Let��s assume some ExeTools member, who really want to learn Starforce internals, will read that protect.dll ��changes from game to game�� and it��s not interesting. Let��s try to become himself for a while: I would like to learn how to crack Starforce (this is just an example), I also see some team did it without modifying protected game files. I am pretty interested because if it works then, maybe, I will be able to learn the same trick and gain additional knowledge (invaluable if I want to know how the protections works and how they can be defeated). Unfortunately I read the following sentence: ��the crack is not as interesting�� ��protect.dll changes from game to game�� and think: ��damn, I just thought it could be what I am searching for, but this guy proved it is not��. What��s next? Ehh, you know. Are we here to learn or get discouraged? I will tell you something: when I was beginning my experience with PC software protections, I was totally out of help. I have been trying to contact some teams and even single crackers with the same kind request: ��please help me and tell me where should I begin, what should I read, what should I try to crack at first����. I have sent tens of emails. Guess how many answered? None. That made me wonder if the scene is really worth such an effect-less effort and if crackers do want to help each other, at least a little. I started to learn myself by completely partisan-like way, without knowing even trivial things like executable compressors (I didn��t know they exists and was wondering long weeks why process memory differs from executable content! He he�� good old times).

But let��s go into the details and render some logic estimations.
We have a problem called ��protect.dll��. Also we have a sentence: "A driver crack, if it existed, would activate all other games too...��. I will try to prove it was a too brave statement too . Protect.dll �C you have written that it ��changes from game to game�� - have you wondered why? Tell me. ��A driver crack�� ��would activate all other games���� �C I am sorry to say you are wrong. Have you wondered why Starforce drivers do not have to change on each game? If you don��t know then think about their purposes. Problems? I will help you: tell me which file is the only critical for Starforce security? If you know then tell me if a driver based Starforce crack, in your opinion, really would be able to defeat other games? And now, after those inferences, please tell me if ��the crack is not as interesting��? Really?

"It would be great of Ultima release some info about their method but I think they won't cause it should help the developers to improve SF3��
Well said, but Starforce developers are skilled enough to discover this trick by downloading discussed relase.

Regards.