Ubisoft dropped SF because of the bad press due to Christopher Spence's lawsuit against them (Ubisoft) (c
http://www.bluesnews.com/cgi-bin/board.pl?action=viewthread&threadid=66009).The lawsuit was for a vulnerability with older versions of StarForce that requires a user to be logged in locally to exploit (which makes it a low risk vulnerability).
The vulnerability was fixed and the lawsuit never saw a day in court (just as what would happen to a lawsuit by me against any software integrating IE because of it's multiple, better documented and more severe vulnerabilities) but bad press is bad press.
I imagine that the 'sick' computers you fixed also had all other redundant software removed, as I would expect from any half decent IT professional. As with others, you failed to document what the actual issue was and how it related to Starforce.
I can find only two 'real' issues specified by users while using StarForce (feel free to find more):
One is the lowering of the PIO mode of the disc drive when read errors occur, which is difficult to reverse by unexperienced users. However this is a known problem with Windows and occurs with any problematic disc (c
http://winhlp.com/WxDMA.htm) regardless of wether Starforce is used or not; something that the Boycott Starforce (
http://www.glop.org/starforce) website fails to mention.
The other issue was Starforce supposedly enforcing it's DRM by rebooting the machine. This was reported by cdfreaks to have been discovered by Futuremark; who later corrected them and pointed out that they had not uncovered anything related to Starforce - it was actually a post on their forums by a user (c
http://www.cdfreaks.com/news/13212).