How to get rid of SecuRom, NOW

<< < (30/191) > >>

JCSpencer:
I can only suggest checking page 2 of this thread. Some users with Vista discussed using this method with success, although a couple of things seemed different, such as where registries are located, and possibly requires you to download a DLL that Vista no longer maintains by default. Wish I could be more help.

miramis:
Quote from: jmtmom on 2007 October 15, 03:15:08

Has anyone had success using these steps on a VISTA machine?


Yes, it worked like a charm too.  In my own case a couple of steps weren't necessary because the files were apparently not installed, possibly because I have read-only dvd and cd drives.

Celesta:
Quote from: JCSpencer on 2007 October 14, 20:33:15

From what I've read, it's identified as a rootkit because it's behaviors are virtually identical to (and thus fit the definition of) rootkit. Such as the manner in which it installs itself, the manner in which it runs, the manner in which it attempts to mask both its presence and its functions, the location where it is installed, and the fact that it does provide administrative-level access (or the potential for other programs to have it) on systems (which was the original purpose of rootkits on Unix systems, I believe). The people screaming that SecuROM is malicious are not really on the right track. With the DRM fiasco, Sony's program was not malicious in and of itself; it was the fact that it allowed a nice hiding place for other malicious programs, which is what Sony got sued for. And according to FTC Chairwoman Deborah Platt Majoras: "Installations of secret software that create security risks are intrusive and unlawful." Yet this is exactly what SecuROM is doing - it is a secret program (or attempts to be) that creates a security risk. It certainly was secret in the manner in which it was distributed to us.

And still EA hasn't answered this question: If they claim and truly believe that since SecuROM is a copy protection program - meaning they didn't feel it was necessary to disclose which CP they were using - then why can't it be uninstalled with the game, especially when they claim that SecuROM is integral to Bon Voyage? If it is going to leave the software on our computers even after the game is installed, then it is not integral; instead BV is dependent on it. There's a huge difference, especially since the latter requires not only EA to inform us of the install, but to inform us that SecuROM is part of the software's operational requirements. They were allowed to say that SecuROM was included, but they broke the law by hiding everything from us and allowing the installation of software the FTC labels as illegal. And that's another important point to get across to all the naysayers on the EA BBS claiming that SecuROM isn't damaging systems: Whether or not systems have been damaged because of SecuROM is not the point - EA broke the damn law! That's all that matters, and THAT affected everyone who purchased and installed any of the SecuROM-inclusive titles.

As for what you said, morriganrant, I agree with you mostly, except the higher ups weren't the ones programming the game. You'd think at some point someone in the company would've said, "Um, sir? Is this really a good idea?" You'd think someone that actually mattered in that company would've heard about SecuROM's previous woes. PR, legal, marketing, programming... someone. I dunno. I still think EA is more to blame than Sony. Sure, they made the product, but EA made the choice to give it to us without warning, and now is unwilling to make a sincere effort to apologize and help us fix this. They must have mighty big rugs in EA headquarters, that's all I can say.


The main reason I say SecuROM is malicious is the fact that it shuts off firewalls without our knowledge.  This leaves machines vulnerable to malware. 

The rootkit in SecuROM fits the definition of an application level rootkit.  It's my contention that we have an IT professional's compiracy that seeks to change the definition or separate other types rootkits of what has been traditionally known as rootkits to take the teeth out of other forms of rootkits given that Sony's kernal level rootkit has a very bad reputation and has come to everyone's attention. They probably got together at some IT convention think tank meeting and decided to take this approach as many software companies desire to use DRM technology for copy protection and don't want the other types of rootkits associated with the very nasty kernal rootkit.

I expect some time in the future we will be receiving a little post card in the mail informing us of our eligibility in a class action suit against EA/Sony over this matter and whether or not we want to take part in it.   I am beginning to see the second wave of complaints at the bbs as so many had forgone installing BV until that patch was released.  And then there is all those offline customers who haven't even purchased it yet since it's only been released for a month.  The nerve of EA not to remove their defective game off the shelves, if not for the sake of it's customers, at the very least to save their own behinds.   So EA has more complaints coming down the pike.  It's not over until its over.

morriganrant:
It is EA though and not just The Sims 2 branch. SecuRom 7.x is on many EA games now, they've started to put it on all of them. Would The Sims 2 branch have been able to stop it from being put everywhere? I doubt it, this is a big financial deal for them. We may have a chance if enough of us complain, that does not mean that they'll switch back all EA games but they may just switch back to SafeDisc for The Sims to get us all to shut up, I don't see how it would be financially beneficial for them that way though, it would probably cost less to only pay one company for their piracy protection services. How many are in on the big deals before they happen? In most cases everyone else just has to flow with it after it happens. I'm not saying EA is not a fault, they most certainly are, if only for being completely blind when it came to Sonys past mishaps, I am saying that The Sims 2 branch may not have had that pull and maybe if they did, how many of these people still play games and visit gaming sites in their spare time? For some, the hobby dwindles, you don't spend the time on it that you once did. Someone is at fault, they did not use their heads and did not do sufficient research, otherwise they would have seen it for the horrible idea that it was, unless the focus on the money was just too much for them. They probably had a deal, EA already puts games on Sony systems, I'm thinking there was some sort of "let's make a deal" situation and all sense was lost in money grubbing. When you get that high up, you loose sight of what exactly is holding you up, in this case a whole lot of angry gamers, hopefully their tower is shuddering enough for them to take notice that their foundation is crumbling.

jolrei:
Quote from: morriganrant on 2007 October 15, 18:13:58

We may have a chance if enough of us complain, that does not mean that they'll switch back all EA games but they may just switch back to SafeDisc for The Sims to get us all to shut up, I don't see how it would be financially beneficial for them that way though, it would probably cost less to only pay one company for their piracy protection services.

Yeah, well, that would make sense if the solution they chose actually did what was intended - stop piracy of the games.  In the case of TS2, far from discouraging "arrr!" versions, it has positively encouraged even those of us who own legit CD/DVD copies to download torrent versions and no-CD cracks, just to avoid having screw-u-ROM on our systems.  It is therefore doing the opposite of what EA contracted Sony to provide.  It costs them more to have the privacy protection than not have it, because they are now paying Sony for the "benefit" of having their former customers arrrr! the program.

Conclusion: their entire policy/strategy regarding protection is counterintuitive and made of FAIL.

Navigation

[0] Message Index

[#] Next page

[*] Previous page