Well having to deal with this style of copy protection is just about as bad as rootkits from Sony. And BS like this pisses me right off: http://www.onlinesecurity-on.com/protect.phtml?c=55 (http://www.onlinesecurity-on.com/protect.phtml?c=55). In no way should I have to un-install something that I didn't tell it to install in the first place. Pricks!
Quote
Besides StarForce software drivers at ring 0 are installed by many different programs such as emulators, anti-viruses, firewalls and etc. Here is how StarForce drivers work:
Driver sfsync02 serves the purpose of CD validity check and identification of different emulators.
Driver sfhlp02 + sfdrv01 ? is in charge of functioning of the core, including anti-debugger tools.
Driver sfvfs02 ? is essential for data protection and StarForce virtual file system.
The matter is that all of known emulators install ring 0 drivers. Obviously, the only way to prevent emulation is to work on the same level and that is the reason our copy protection installs drivers.
:gag: "The reason we are violating your liberties is to protect you" So now we all know what company John Ashcroft is working for now that he's not the Head Lawmaker Of "The You Ess of Kissasseh" >:(
http://www.extremetech.com/article2/0,1697,1968997,00.asp
Vista warns you about ring 0 aka kernel level drivers, and according to the MS chalk talk I went to MS doesn't want any future applications running in this space, so I suspect programs with this type of copy protection will not be able to get a Windows Vista logo certification in the future. MS also sites ring 0 drivers as the number one cause for BSOD, which seems to be true from my experience.
http://www.extremetech.com/article2/0,1697,1931914,00.asp
OK maybe they can still use them if they sign their drivers... :(