Right after the recent findings that Starforce will reboot your computer when it find "suspicious" activity, it has now been found it also travels across networks - to be more exact, they describe a disturbing worm-like behavior from StarForce drivers using "multidropper type techniques" to spread across network drives. The update then relates the ugly back and forth over the treatment discussion of the topic in the StarForce forums, with the opposing sides accusing each other of lies and libel. (thanks Digg)

The data mentioned in my post was obtained by running standard and also thorough bench tests on several systems. Before I even start I think both you and I know that the SATA/SCSI primary drive incompatibility with SF is well documented. Its just the nature of using a Virtual IDE emulation.

SATA/SCSI and IDE are not compliant with each other protocols at the best of times, but when you add an emulation which is not 100% compliant with the IDE subsystem, it does not take a genius to realise that this will have errattic side effects to system stability. FOr one thing SF struggles to isolate which is the primary partition on a SATA/SCSI system. Also if network drive have full read/write permission it will install its drivers there as well (Basically because of this not being able to isolate where its supposed to be).

At no time did I ever state that this reaction to the conflicts was an intentional issue created by Security Technologies, thus I am extremely concerned that rather than addressing the issue you chose to present the challenge to the finding in such a libelous manner. I am quite sure the authorities will carry a similar view point on this since I am a reputable tech Engineer/Developer with over 25 years in the business under my belt.

The article is talking about SATA/SCSI drives where Windows uses a virtual IDE driver, my understanding from the article is that Starforce's software is installing its driver in front or in place of the virtual IDE driver, because it doesn't understand SATA/SCSI very well it can't locate the correct place to install the software and as a result not only is it incorrectly writing to the MBR of the drive as well as all the partitions, but it's also causing the software to panic and try and install it in any place it thinks might be right, including mapped network drives. Well, it would be nice to see the technical proof ( reproduce the experiment while recording with a digital camera), but what is suggested is possible.