Well, lets clarify something about Starforce.
First, since 3.4.65.09 version of starforce engine, it have been turned into a very restrictive way.
To "prevent" (with so minor success) Starfucker tool to work, Starforce have tried to get control of internal windows OS routines, i say, IDE control, as example. Starfucker just deactivated some IDE drives to windows, and in consecuence, any good mini-image (complete images doesn't work with this tool) could be launched from virtual devices ( Daemon, Alcohol).
Prior to above version, this "trick" worked so fine ( for MOST users (not all)).
Then, Starforce have modified its drivers to avoid that, and in consecuence, tries to reset IDE bus prior to checking disc.
This have some important variants when launching mini-images or equivalent:
1.- If manual IDE unplugging happens ( to launch with Alcohol for example) (first known method) then Starforce will be near 2 minutes reseting bus to check if everything is OK. This way, any Alcohol image/mini-image will always last 2 minutes or more to be launched.
2.- The same happens by BIOS IDE deactivation
3.- Tha same happens when deactivating IDE channel in newest starfucker version ( starforce nightmare 1.01).
To prevent this, only starforce nightmare option to disable just ONE drive, will launch inmediatly.
Well, what can i say. Not a lot, just that with time, Starforce will be as incompatible as laserlock star were time ago ( there are very few titles with such protection cause compatibility). Starforce doesn't keep in mind compatibility, and just tries to prevent "external" launching by getting Windows control. This will have important consecuences in game specs, cause game box requirements will not be the real ones. Could be the case, a original game would be natively perfectly launched onto a windows XP SP2 system with newest PCI-E graphic card, but with SF present, such game will always refuse to be launched due copy-protection. Why?, well, cause native mode controllers for PCI-E. Starforce will not allow that to avoid mini-image launching. In a near future, everything should have the native controller mode to support the windows hardware logo, and what will happen then?...supose yourselves.
Till now, i always believed SF were a miniOS inside Windows. Now things have changed, and SF, when running, is the main OS, and windows just a program.
Unless starforce changes policy, will be forgotten in a very near future due incompatibilities, like laserlock star.
This is extensive to USB controllers ( CD/DVD writers connected by), RAID, SCSI, PCI-E, ATA, S-ATA and any other connecting "protocol" u could say.
Starforce is getting mad, and even with its actual policy, it is not getting success to avoid tools such Starforce nightmare (cause works like Starforce does).
Again, war between freak world, and copy-protection.
Many users will not be able to launch its original games cause copy protection, and a lot ones will permanently crash their systems just with Starforce execution.
I do not recommend to use Starforce Nyghtmare, even with a deeper knowledge of what it makes (:-)), but i do not recommend too to buy a Starforce protected game. Starforce nightmare will work, will partially work, or will not work. Now everything is hardware/software-dependant.
If u still thinks u want to use a starforce protected game, then do it at ur own. It is dangerous.....