Hi all. While this is currently a very hot topic on the forums, I have been looking for a thread that has an easy how to guide for making backups of games with the new versions of Securom. After looking extensively I was unable to. I tried various methods, including using just Blindwrite and the BWA Builder, using Alcohol MDS files and converting them to BWA files and burning through blindrite, etc. In the end only 1 method seemed to work. This is for bacing up the Thing (Securom v4.77..00 0029).

While I can't guarentee this will work for all, it worked for me. Here is teh software required:

- Alcohol 120%
- Blindwrite Suite
- Blackcheck's Twinpeak

1. Create an image with Alcohol using the Securom New(ver 4.x) Setting, using the MDS file format.

2. Create a second image using Alcohol using the Securom New setting using the Clone CD (.CCD) image format, placing it in the same folder as the first image.

3. Convert the MDS file created to a BWA file using BWA Builder and save the BWA file, placing it in the same folder as the first image. Once this BWA file is created, you can delete the original MDS image you created.

4. Using TwinPeak v0.2, merge the CCD image file and the BWA file together. This will create a new image called patched.ccd. I used a twin sector step of 15, though I have read that 50 and other numbers work too, with disc recognition times decreasing as this number has increased. Once this new image is created, you can delete the original Clone CD image you created (DO NOT DELETE THE CLONE CD IMAGE THAT YOU JUST MADE THOUGH (patched.ccd)!!).

5. Using Alcohol, burn this 3rd image (Patched.ccd). Make sure that Bypass EFM error is unticked and rectify Sub channel data is unticked. Also, I'm not sure if this will make a difference, but I had Close last session unticked. Note you get a message saying that image size NOT match to Lead Out specified in TOC! Choose the first (recommended) option.

6. You should now have a working backup!

While this method may not work for all, it worked for me. It not be the fastest method, but this is the only way it has worked for me thus far.

Weshy.

What burner did u use?

Sorry I used a Lite-on 48125W. I used a Lite-on LTD-165H to read.

Weshy.

Thanx for your instructions, only one thing I don´t quite understand (i´m bad at english)


What do you mean with using the "securom new (ver 4.x) settings"?

If you use twinpeak to patch a ccd image (whether made with clonecd or alcohol), it makes no difference whether or not the bwa file is in the same folder as the ccd image.

It also doesn't matter if the ccd image and the bwa file have totally different names.

The bwa file only has to have the same name and be in the same folder as the image file if you use blindwrite for reading and writing the image.

Actually, you don't need BlindWrite. All you need is the BWA Builder from the install directory, and pcouffin.sys. Just put pcouffin.sys in your C:\Windows\System32\drivers directory and BWA Builder wherever you want, and you are all set. This way you can eliminate the need for unneccessary additional burning software.

Simply use new alcohol 1.3.6.1223 datatype: Securom 4.8x
It works!!!!!!!!!!!!!!!!!!!!!!!!!

but you emulate
so you need alcohol (or any other rmps emulate software) to be running in the background in order to let it work.

you just cant make a 1:1 back-up of an securom 4.8 protected cd.
all programs (ccd, BW and alcohol) use some form of emulation wich means you have to have the emulation software running in the background.

Please stop posting misinformation.

If a twinpeak copy works (whether made with blindwrite or with ccd or alcohol together with a bwa file and blackcheck's twinpeak tool), emulation is not required. The fact that a twinpeak copy is not a 1:1 copy is irrelevant.

luciano was NOT talking about the twin peaks method (as far as i understand from his message) but the alcohol 120% securom 4.8 new setting, wich uses emulation.

Quite so but you stated in this thread and others that a working copy wasn't possible without emulation and that is not so.

Yes. That is very normal. The Thing is protected by SecuROM 4.77.00.0029 which doesn't need a BWA file or MDS with DPM. A backup is relatively easy to achieve by just using default SecuROM procedure.