how-to block ads
|
|
Share Topic
 |
 |
|
|
|
davePremium,MVM
join:2000-05-04
not in ohio
kudos:7 Reviews:
 ·Verizon FiOS
 ·Verizon Online DSL
| reply to StanRad
Re: hidden? but you can see it ;) said by StanRad:
Secondly, I don't care if it's just a node in Device Manager - the publisher should always return the computer to the same state they found it in after uninstall is done. I'm a software developer myself, so don't try your BS on me. Sure, a lot of programs leave orphaned Registry entries behind anyway, and that is bad too. This is beyond bad.
OK, please point to the procedure for doing this. It is Beyond Bad to write application code that goes screwing around with registry keys that do not belong to the application - that's the fastest way to system screwups there is.
--
If the driver stays behind, then I agree it's bad.
But no-one actually really said that they found the drivers remaining - they just pointed at some Device Manager node, which is only somewhat related. And they also read bad intent into the word 'hidden', which is just a Device Manager classification of the driver beyond the driver-writer's control. These two things suggested a lot of fuss about the wrong symptoms.
I repeat, failure to remove the driver is bad. | |
| Of course I am not suggesting uninstallers go around removing other people's registry keys; I am specifically talking about applications that after uninstalling leave their own keys present in the registry. But that's just a nuisance compared to what StarForce does.
And yes, leaving the driver behind is bad, and it is confirmed that this is the situation in at least one of the games (see second post on this page by StarForce):
»www.adventurecompanygames.com/ta···t=2&vc=1
Finally, I really don't care about how well they clean up after themselves - the fact remains that people have lost data and time just to play a game they were legally licensed to do, and the only reason for the loss of data and time is that the company wanted to prevent that same user from stealing their product. If the customer did steal the product, they wouldn't have had any of these problems since the crack would have taken care of it. And of course, I'm sure StarForce has ensured the same publishers that their protection software, for the first time in the history of computing, is uncrackable. Brilliant!
This is the problem with using device drivers for protection, every programmer always likes to believe that their code is foolproof and it's a piece of cake to implement. But then reality bites them on the arse and they realize that in the real world their driver will have to deal with hundreds of other drivers that are often buggy themselves. This is why this type of practice is plain unwise. Read the thread above to see some of the annoyances people had to put up with StarForce. | | |
|
|
