Old style copylocks
 

Hi all. I've come across an old copylock on 3D Pool. It is an AmigaDOS executable which has been crypted using Rob Northens 'protect' tool. It seems to be different from other (newer) copylocks I've seen before and I'd like to ask you guys what is the best way of tackling it??

I know Codetapper cracked it for WHDLoad - so if he (or anyone else - Galahad?) could give me some help I'd appreciate it... :bowdown

Which version are you talking about? There are at least 2 copylock versions of 3D Pool and to crack them requires different techniques.

I'm reffering to CAPS 3DPool (#621), it's a normal DOS executable with no loading screen. The EXE is encrypted by RNC and does a disk check before decrypting the game...

Using AR I can find where the copylock code starts - but that's about all so far :) I saved it out and fed it to copylockdecoder 1.67 with the original disk, but it said it "wasnt copylock".

You must have made a mistake, CopylockDecoder can decode that one with the CAPS disk inserted no problem. The instructions are identical to Dark Side:

http://action.reversers.net/copylock_darkside.html

Incidentally, the game only has one hunk, and you don't need to relocate it since it copies itself to $1000 anyway. And since you're using the original, choose sync $8914.

Offset $d24 in 3D-Pool.dec is where the decrypted code appears at.

I'll start working again with a fresh perspective :D

Thanks Codetapper... :bowdown

Series One Copylocks aren't too tricky too crack. The key is knowing what they do so that you can crack it.

Obviously the old skool way would have been to single file it (i.e. wait until its loaded and decrypted and then save the contents of memory), but I would 'assume' that 3D Pool works in a similar way to Stunt Car Racer in that once its passed its protection check, the routine that decrypts the game is then revealed which you can then grab and use to externally decrypt the game.

Exactly, I'd never seen a series one before - only the later ones. So I wasn't too sure about it... as I knew it was different. So I asked the experts :)

And respect to you both for your great work with WHDLoad