A real solution to the StarF**k virus for everyone.

[DABhand]

hehehe I guess my lost post was long winded a bit :P

Nahh there is no point boycotting, help the SF makers by giving them your PC specs and error msg's etc that occur, im sure by helping them they will help you.

Also as I said ive not had any problems in shape or form with Starforce. Im just one of the many lucky ones I guess.

[Eagle]

Originally Posted by DABhand

Nahh there is no point boycotting, help the SF makers by giving them your PC specs and error msg's etc that occur, im sure by helping them they will help you.

I did. I asked SF support why SF wouldn't accept a game cd from any of my 3 SCSI CD/DVD drives. They answered: It's intended because virtual drives are also using/faking SCSI techniques.

I asked them when they got that brain-fart and returned the game for a full refund.
Still waiting for an answer though...

[DABhand]

Hopefully you asked them in nicer words :P

[Tony22]

Starforce3 is trash . Safedisc and Securom i can respect cause they won't load the protection drivers constant . only when the game is running the protection drivers are running.., with starforce you have to reboot after installing and the protection driver is running always after that..so this spoils youre memory .

[Morglum007]

Originally Posted by DABhand

hehehe I guess my lost post was long winded a bit :P

Nahh there is no point boycotting, help the SF makers by giving them your PC specs and error msg's etc that occur, im sure by helping them they will help you.

Also as I said ive not had any problems in shape or form with Starforce. Im just one of the many lucky ones I guess.

DABhand, unfortunately, SF guys will not HELP u anymore with problems with its prot. The way SF is turning is by eliminating any thread that could get its protection system compromised. This way, SF will not stop even if many systems get crashed.

I have no problems with SecuROM or Safedisc, and i hadn't too with SF before SCCT arrived. The problem now isn't a cracking/not cracking/copying/not copying/emulating issue. SF is becoming a very interesting system, and it is close to be FULLy cracked.

What i'm trying to say is that SCCT implemented its new SF system to intercept IDE calls "on the flY", checking or not original CD, and this CRASH FOREVER some DVD drives, such LG, Toshiba, or some SONY. When i say crash, i'm saying to buy a new one, cause older does not burn anymore.

Drives without a very stable writing system, like "Just Link", at the end will be ****ed by the intrussion of SF in IDE calls. SF, as someone stated earlier isn't a passive driver anymore, it is fully active ALWAYS, even when extracting DPM or burning DVDs. This way, Just link overloads and then, drive motor spins up an down without any ritmic control. Finally, drive DIES. This is not a foolish warn, thats what spanish people from almost everywhere reports, and we know why. I simply recommend not to use SF to protect their drives, but at ur own ( as said in english).

PS: I have a lot of ORIGINAL games, even with SF, but not for playing the standart way( some of then DOESN'T work on my MACHINE due specs, but i don't care). I use cracks to play them ( to PLAY), even having original, cause i know how SF works, and don't like how it runs.

Null warns are most times useless, thats what i recomend.

Morg

[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.

[Morglum007]

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

[CrossWire]

I’m sorry DABhand but you really do need to wake up and smell the coffee.

[DABhand]

As ive said ive not had any problems with any SF protected games like others are having.

[Pangster]

I will boycott SF as well!
If the problems or 'intrusions' Starforce where made public then lots more people will know about it and SF will get a bad reputaion because of it.
A bad reputaion is alomst as bad a gaining no profit because those two are connected. Think about it!