Command and Conquer 3: Kanes Wrath Problem.

[Blazkowicz]

You should tell us the error SecuROM is telling.

Also you replaced your original file with which exact file?

What about trying that repair file

[cpthk]

I replaced the cnc3ep1.dat file from EA to fix the explorer crash problem. But just right after I replace it, I can't not go into the game anymore. I even tried turn on yasu, but still.

Any solution?

BTW, EA Support updated into a repair file. Anyone tried it? What's the difference? So If I use that repair file, do I replace back the original cnc3ep1.dat file?

[Blazkowicz]

You are right, vSCSI is blacklisted, vIDE not.

[Bollo]

Aggg...this new versions of Securom blacklist Daemon Tools...so WE the "Lite" users cannot even dream of playing a game with a mini-maxi image...so let's stick with the original ones until they get scratched.

I don't even know if the PRO ADVANCED version can bypass this new versions...

[lagglad]

Hotfix blacklists 4.30.1

EA published some Securom Fix for Kanes Wrath Patch 1.01.

Sources:
Support EA

Maybe this helps in some other ways too, i cant test it myself because it works flawless.

Old SecuROM Version:
[!] SecuROM Detected - Version 07.37.0010
[!] Possible CD/DVD-Key or Serial Check -> cdkey

New SecuROM Version:
[!] SecuROM Detected - Version 07.37.0012
[!] Possible CD/DVD-Key or Serial Check -> cdkey

Yea the "hotfix" version blacklists 4.30.1, however, the 1.01 patch without the hotfix works flawlessly :P

So i'm sure there will be a 4.30.2 soon enough to get around this.

[Mystique]

EA published some Securom Fix for Kanes Wrath Patch 1.01.

QUESTION
I've updated with the latest patch and my explorer crashes when I right click on program icons, what can I do?
spacer

Answer
If you have downloaded and installed the 1.01 update you may have an issue when you right click on a .exe file or program icon.

To resolve this:

1. Download and open the SecuROM Command and Conquer file.
2. Drag and drop the cnc3ep1.dat file to your desktop.
3. Double-click on My Computer.
4. Double-click on Program Files.
5. Double-click on Electronic Arts.
6. Double-click on Command & Conquer 3 Kane's Wrath.
7. Double-click on RetailExe.
8. Double-click on 1.1.
9. Right-click on the cnc3ep1.dat file and click rename.
10. Rename this file to cnc3ep1.dat.OLD.
11. Right-click on the cnc3ep1.dat file on your desktop and click copy.
12. Right-click anywhere in the 1.1 folder not on a file and click paste.

Once this is done explorer will no longer crash.

Die C&C-Fans sind von rigorosen Kopierschutzmaßnahmen a la StarForce bisher verschont geblieben und somit kam es wohl bisher relativ selten vor, dass es Probleme, wie ein nicht erkanntes Originalspiel gab. Doch jetzt hat es auch uns erwischt. Offenbar verursacht SecuROM seit Patch 1.01 für Kanes Rache einen Fehler, der bewirkt, dass wenn man mit der rechten Maustaste auf ein Desktopsymbol oder eine Exe-Datei klickt, der ganze Computer einfriert.


EA hat nun eine Hilfestellung veröffentlicht, die wir euch natürlich umgehend auch bei uns anbieten.

1. Ladet das C&C SecuROM Update herunter
2. Öffnet euren Kanes Rache Ordner
3. Geht hier in den Ordner RetailExe und öffnet dann das Verzeichnis 1.1
4. Benennt die Datei cnc3ep1.dat in cnc3ep1.dat.ALT um
5. Extrahiert das heruntergeladene Update in dieses Verzeichnis

Jetzt sollte euer Computer nicht mehr beim Rechtsklick auf Desktop-Symbole und Exe-Dateien einfrieren.

Sources:
Support EA

Maybe this helps in some other ways too, i cant test it myself because it works flawless.

Old SecuROM Version:
[!] SecuROM Detected - Version 07.37.0010
[!] Possible CD/DVD-Key or Serial Check -> cdkey

New SecuROM Version:
[!] SecuROM Detected - Version 07.37.0012
[!] Possible CD/DVD-Key or Serial Check -> cdkey

[Dethklok]

The new version of DTools fixed everything. But yeah you're right: with the new version I have to turn off YASU, in the old one i used to have to run it. Glad everything is fixed now - thanks for all your help everyone. ^_^

[Blazkowicz]

Dont use yasu.

[Dethklok]

Despite your warnings I tried the trick. Doesn't work, still gives me the security module error. >.< Pity no one knows how to fix this >.<

[Reef]

The trick is about changing some value in the registry, but I don't think it's a good idea to mess in your registry if you don't know what you're doing. The registry is like the heart of Windows, so if something goes wrong in it, there's a chance your PC needs to be reformatted.

[Dethklok]

For me it only runs if I change the name of the first CDROM device in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Cdrom\Enum

I have heard of this "trick" before. how do I do it? can anyone give me a detailed step by step guide or something? (Don't start with go to HKEY_LOCAL_MACHINE... because thats the first problem I have: I don't know where that is) >.< sorry to be such a noob and SO persistent >.<

[Terramex]

I've got the grid patched to 1,2,
it have been securom 7,37 0010 too,that's work with dt 4,124 and dt pro.

Please have a look at the new blacklist of securom-Thread in Customer section.
Seems like GRID uses some alleviated version of new SecuROM which doesn't utilise all options of the API.
So i guess GRID's blacklist isn't the best criterion.

[angelsdecay]

it seems that dt pro is blacklistet(i've got dt pro adv)
anyway securom 7,37 0010 did not the reason,that must been a part of the update from c&c tb wrath.
I've got the grid patched to 1,2,
it have been securom 7,37 0010 too,that's work with dt 4,124 and dt pro.
I've tried with dt lite and yasu.does not work.

[Terramex]

...but i still have to try how it behaves when i uninstall Alc 120% + DT 3 so there are no SCSI controllers at all.

No change after that.

[Reef]

For me it only runs if I change the name of the first CDROM device in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Cdrom\Enum