StarForce protection

Thank you deroko for clarifying this. Yes, I am planning to bind the game to the hardware of the computer and not to the disk.

As far as I know most of the disk bound StarForce protections use the hardware bound protection as well. And when you call customer support saying your disk is damaged, they can send you an activation code in response to the hardware code the program generates.

Can you circumnavigate the hardware binding protection by a general way as the disk protections can be tricked many times?

Thanks for tall the answers!

[Maximus]

As always, it depends the way the hardware code are collected. Being StarForce a r0 protection, probably hardware codes are directly fetched from IDE interface, thus making it harder to 'fake' (I've read *F initially was harder to fuck, requiring to disconnect IDE CD to force it to use 'compatibility' drivers, Mostly the DT one I think). r3 protections are, on this side, easier to attack since they often rely on DeviceIOControl API for evaluating the serial (at least, the 'HW_ID' routines I examined does do).