Raven Shield 1.51 no cd

[dracklackner]

I patched today using the 1.0 to 1.51 and then I applied the 1.51 no-cd.exe into the games system director where the original .exe eas but it didn't ask to replace the .exe. I also went to replace the Core.dll and it also didn't ask to replace the existing one. I don't get it. When I went to start the game with the no-cd 151 it then asked me to put disk 2 in.

[dracklackner]

OK, I got it figured out. I had to manually delete the Core.dll and the original RS.exe out of the system file in the directory. For some reason it didn't give me the option to replace it as every other time I've done this with nocdexe files.

[null]

Can you explain that better please?
If I delete the core.dll and original .exe I get an error if I use the cracked .exe.

What do you replace the core.dll with? It won't start without it.

Thanks

null

[ash2dust2]

I'm assuming with the core.dll in the crack.

[krondike]

A theory, original .exe and core.dll file is write protected. If you extract and take replace the file with out asking, a option thing in winrar, think it automatic skip the write protectin files! that mean you must rename the file, and you might got a question if you wanna rename a write protected file!

Funny thing that Raven Shield 1.50 had SafeDisc 3.10 or 3.15 and Raven Shield 1.51 have SafeDisc 2.8 according to Protection ID! the first protection of them all.

:confused:

[Eagle]

yes. patch 1.51 was _ONLY_ released to downgrade to SD2.80 because all people were pissed off as version 1.50 (with SD3.1x) blacklisted their virtual drives.

[dracklackner]

Originally posted by null
Can you explain that better please?
If I delete the core.dll and original .exe I get an error if I use the cracked .exe.

What do you replace the core.dll with? It won't start without it.

Thanks

null

Exactly. Just replace your core.dll and .exe in the crack with the ones in the directory. (Save a copy of your originals in a seperate folder somewhere). That it!

[Eagle]

btw you shouldn't delete the original files. rename them because you'll need them again for the next patch.

[krondike]

Originally posted by Eagle
yes. patch 1.51 was _ONLY_ released to downgrade to SD2.80 because all people were pissed off as version 1.50 (with SD3.1x) blacklisted their virtual drives.
What I'm seen and heard so far. Latest Alcohol have fix the blacklist problem and SecuROM can be emulated.....