|
To get back on topic and answer the original post, Starforce has always been notoriously difficult to bypass because it uses drivers, virtual devices and other nasty things to thwart pirates.. though I believe they have only succeeded in being a minor nuisance at best while destroying many peoples computers or killing performance (a story of SF drivers corrupting a guys hard drive comes to mind).
Older versions of SF are well documented and numerous ways to bypass it with no-cd exes have been found. Recently released programs though are coming with a brand new completely redesigned version of SF in them though.
As I said before it is notoriously hard to reverse engineer the SF software to find ways to bypass it.. I have a fairly decent knowledge of assembly language and Im at a loss as to where to even begin.. it even manages to hide the read/write requests for every address within the games memory space making it impossible to even create a trainer for the game.
Someone will figure it out eventually but in the meantime we're stuck having to use a combination of SFCure and SFNightmare to trick starforce into believing there are no IDE optical drives connected so it will look at the scsi drives created by deamon tools and alchohol 120 (which it cant tell is virtual).
|