Quote:
|
Originally Posted by DABhand
As burning you mean with Alcohol I guess, I have blindwrite and nero and ive yet to have the same problem as you said.
Perhaps its the virtual drive api's conflicting with SF, cause I dont think the programmers at SF would make something that would intentionally screw up drives, they would be liable to cost if that was indeed the case.
Im not saying they are all good, but nothing is perfect, even protections some will have conflicts while others who use the same dont have the same problems.
Thats why I was saying to help them find out why, by giving them details. At least they can work towards this not happening.
|
DABHand really??????????, heheheheh it is the newest and nasty second effect they WILL NOT fix cause it is PART of COPYPROTECTION. It is NOT a BUG, it is INTENDED to BE. Or this, or RPMS could be authenticated, and of course it wont like that.
I didn't thought u were so innocent
, and u are facing problems like others, When u had to BUY a new recorder, lets see what face u put and what oppinion u have on Starforce.
TIP: I do not mean burning with Alcohol, i mean drive DEATH, so no more burning with Alcohol, BlindWrite, Nero neither any burning APP u could find. When i say dead, i say a new drive. U said, virtual APIs conflict, well, u are mixing IDE commands, from real IDE drives or virtual ones. The effect is bidirectional, and optical devices gets compromised. Remember that the idea is to make SF to think a virtual drive is a real one, so if u "****" one, will "****" the other too. It is part of SF policy.
CdSTeam