Backing up some CD-Roms with SafeDisc

[Ryanrs]

Heres the files that you have requested, there is 7 CDs in there, there was a few more but i dont want to take the pi** too much! I have included the SD version in the name of each folder. Im guessing that if you suss how to patch one, the rest will be practically the same?

Heres a link to the Rar. -If there is a password on the archive, its ' spain '.

http://www.megaupload.com/?d=ICR6LBDK

Thanks.

[Ryanrs]

Heres the link to the files you requested, there is 7 CDs in different folders, i have added the SD version of each one to the folder names.I i guess that if you can suss how to patch one, then the rest will all be the same?

I did post this earlier but it seems to have been deleted off the forum? perhaps links are not allowed to be posted??

well here it is again, but not as a link ;D password if needed is ' spain '

megaupload DOT com/?d=ICR6LBDK

[Cowsheep]

I downloaded the files and will take a look at it later.

[Cowsheep]

Hi,

here is a tool for unpacking the SD 4.60 ones, orginal disc or working clone must be mounted.
Will look at 4.81 ones later.

[TippeX]

Is that the arteam one? the sd3 ones i think ryanrs got the cracked exes for... Didn't he msg you?

[Cowsheep]

Yes, this is the Arteam unwrapper for the Sd 4.60 and yes, he msged me, but about the files with Sd 3.

[Ryanrs]

Thanks Cowsheep, ill give that a try.

[Ryanrs]

Ok, i gave that program a go and its still not working! Heres what i did. I copied to MDS image using Alcohol 120% with 'Safedisc 2/3/4' datatype profile and mounted it to Virtual H drive. I then ran Unsafedisc which then prompts me to select an executable to load. I select the program EXE from the H drive (the same one that you have a copy of) to which a DOS window opens displaying the following :

SafeDisc 4.6 unwrapper Beta Internal Release

Process started...
Setting Breakpoint on DLL entry...
DLL reached...
Setting Breakpoint for IAT rebuilding...

Then i get a windows error window displaying " Fatal error! , CreateProcess Error!" which is immediately followed up with the usual 'Please insert the correct CD-Rom ...bla bla'

Any ideas whats going wrong!! :/

[Cowsheep]

Safedisc detecteds that the discs are not valid...

That files are Sd clean, but dont work because there is some overlay stuff inside SD crypted area that gets lost.

(For Sd 4.81 this tool dont work as it fails to set a BP and app starts through.)

[TippeX]

Thats why i asked if it was the arteam tool....its a piece of crap and done very badly..said this years ago too..0day theyre geed at.. Safedisc (1 tool..and sloppy reversing) and securom ("total ownage".. more like total bollocks) they should have left to those who have an intricate knowledge of iso protections..hell most of the tuts are olly + imprec (or variations)...
Just my 2 cents tho

[Cowsheep]

Yes, its not a very good tool i know... but iam not aware of a better one available in public. That what RLD released is only a loader. At least it unpacks Sd 4.60, but the reason for the files not working is the macromedia flash projector overlay thingy.
I still didnt figure out how to unpack SD with Olly, a SYSENTER is always the end.

[Ryanrs]

Well, i gave them files a go and it crashes at the macromedia flash loader, i guess this is what your talking about above?

Any ideas on a fix? im guessing these are proving quite challenging! Btw, i did notice how the file size of the two exe's in the zip above are tiny in size compared to the originals! is all the missing filesize all crypt data that you have removed?!

[Cowsheep]

Safediscs dll files take about 2MB, so a size loss of 2MB is normal if SD was removed. But the size difference is bigger, so there must be some other data that was lost...

Here is the generic loader from RLD, that should work with all version.
Read the .txt file for instructions.

[Joe Forster/STA]

(Any ideas on the password for the source archive? )

[TippeX]

Is the appended data stripped out? if so then i'm sure its easily put back..then flash should pick it up... As for loaders, i found a problem with some exes..the loader faked the cdcheck and code got to the oep but some ccc's (what r!sc, me and yates called them.. Others call it sdapi) could silenty call the cdcheck again (which the loader won't handle again) and...boom.. and loaders are weak nehows..and the rld one is stolen... Which explains how they know little on newer sd versions