CloneCD Settings

CloneCD Settings

Trouble with your Delta-V?

In General[list=A][li]Use an 80’ / 700 MB or 74’ / 650 MB disc for writing as required[]Ensure your writer is compatible[/list=A]Determine the Protection[ul][]Check your game title here or here for any copy protection[*]Use a tool listed here[/ul]Recommended Settings
[/li]
Plextors & RAW-DAO

SafeDisc1. This protection is based on binary errors that are physical in the early sectors (up to ~10.000) which can be very difficult to read but which are less difficult to write. There is no copy protection in the P-W subcode channels. [ul][li]Read:[list=1][]Max Speed[]DAO RAW[]Fast Error Skip (click “Settings…” & then “Default”)[]Note that the error skipping may take some time![/list=1][/ul] [ul][]Write (default):[list=1][]Max Speed[]DAO RAW[]Close last Session[]Buffer Underrun technology[/list=1][/ul]SafeDisc2. This protection is also based on binary errors that are physical in the early sectors which are very difficult to read but which are also very difficult to write. Writers must be capable of “correct EFM encoding of regular bit patterns”. There is no copy protection in the P-W subcode channels.[ul][]Read:[list=1][]Max Speed[]DAO RAW[]Fast Error Skip (click “Settings…” & then “Default”) []Note that the error skipping may take some time![/list=1][/ul] [ul][]Write:[list=1][]Max Speed[]DAO RAW[]Close last Session[]Buffer Underrun technology[]Amplify Weak Sectors, as required, up to v2.51.020[/list=1][/ul]Some points to note about SD2:
[/li]

[list=a][li]the errors are normal & can take some time depending on your reader - this is MOHAA during error skipping on a Toshiba SD-M1402 DVD-ROM
[/li]

after error skipping

[li]SD2 was a killer app introduced in Red Alert 2 (many writers still remained in contention)[]SD2.4 introduced the killer API version with an ATIP Check[]Tiger Woods Golf saw SD2.51.020 – the last revision where, all then recognised, SD2 writers had a chance[*]Medal of Honor Allied Assault introduced the giant killer v2.51.021; brands of capable writers can now be counted on one hand, models on your toes…[/list=a][/li]> Originally posted by sonny39

Hey Coldfreezer, I have a lite-on 24102B. The firmware is 5S54. Will these settings work for hitman (sd2)? Should I not check repair subchannel data?
“Subs” & “Don’t repair…” for SafeDisc v1 or v2[ul][li]OK, subs are required for subchannel protection. SafeDisc uses ‘main channel’ protection so subs are unnecessary, that is, not essential, but will not hurt 99.99% of burners or combinations of reader & writer.[]“Don’t repair…” ensures that a 96 byte subchannel write occurs - this means that the Q subchannel data is not corrected which is required to defeat PSX LibCrypt; that said, it has no effect on SafeDisc and cannot hurt (yet…)[/ul]LaserLock. This protection is also based on binary errors, that are physical, in the sectors which are very difficult to read but which are less difficult to write. Again, there is no copy protection in the P-W subcode channels. [ul][]Read:[list=1][]Max Speed[]DAO RAW[]Fast Error Skip (click “Settings…” & then “Default”) []Intelligent Bad Sector Scanner (up to 1000 is OK) []Note that the error skipping may take some time! (hours in some cases!)[/list=1][/ul] [ul][]Write (default):[list=1][]Max Speed[]DAO RAW[]Close last Session[]Buffer Underrun technology[/list=1][/ul]Some points to note about LaserLock:[list=a][]LaserLock2 requires an uncorrected subchannel write, like PSX Libcrypt[]Not all readers are capable, more so for LaserLock than any other common protection[]You just may not be able to do the read with your device[]BlindRead is known to suceed with LaserLock where CloneCD can’t, but this depends on your device[/list=a]
[/li]
SecuROM. This protection is subcode channel based which can be either simple or impossible to read, depending on your reader & which is also simple or impossible to write. The copy protection is in the Q subcode channel but the P channel must be read & written as well, requiring a 2x8 byte read/write across the sectors – this is what Olli terms DAO RAW + 16. SecuROM does not use error based copy protection. Recently, it seems, SecuROM has been strengthened. Lots of problems with Never Winter Nights disc #3, look here[ul][li]Read:[list=1][]Max Speed[]DAO RAW[]data sub[/list=1][/ul] [ul][]Write (default):[list=1][]Max Speed[]DAO RAW[]Close last Session[]Buffer Underrun technology[/list=1][/ul]Some points to note about SecuROM:[list=a][]Hide CD-R Media must be off when reading a SecuROM protected disc[]Early revisions of SecuROM are just a Q subcode channel protection[]Forsaken was one of the first titles published with SecuROM v1[]Brian Lara Cricket has v5 but the issue is one of SecuROM & SecuROM new[]SecuROM new was first discovered in V-Rally 2 and also has the killer API ATIP Check like SD2.4[]Publishers also include serialz & Daemon Tools ‘blacklisting’ code (among other :evil things) in the protection, rendering the game useless to key-gen junkies and legitimate users of Venom & Swenske’s masterpiece[/list=a]PlayStation PS1 consoles require a ‘mod-chip’ for the backup to play; one of the best mod-chips is Australian designed & made, they ship world-wide and it costs about USD$15. Most PS1 & PS2 titles, on CD-ROM, are protected by LibCrypt which is essentially incorrect CRC in the Q subcode channel. A ‘16 byte only’ burner cannot defeat LibCrypt as any [intentional] errors in the subcode will be corrected. The protection was first introduced in 1998 with the release of PoPoRogue & MediEvil. To be able to perfectly copy PSX CDs using an extra protection like Libcrypt your burner must have the ability to write the full 8x12 byte P-W subcode channel data (RAW DAO + 96) which disables CRC error correction. LibCrypt does not use physical error based copy protection. Check Olli’s compatibility list[ul][]Read:[list=1][]Max Speed[]DAO RAW[]data sub – 16 bytes only needed[/list=1][/ul] [ul][]Write (default):[list=1][]Max Speed[]DAO RAW[]Don’t repair subchannel data#[]Close last Session[]Buffer Underrun technology[/list=1][/ul]Some points to note about LibCrypt:[ul][]the R-W subcode data is not really needed, but[]nothing must be corrected in the subcodes to change the intentional errors[]PQ 16 byte writing corrects the CRC of the Q subcode, whereas[]in 96 byte mode the burner corrects nothing[]#The “Don’t repair subchannel data” is required to ensure that the burner writes only in 96 byte mode[]My “Don’t repair subchannel data” check box is greyed out! …your burner doesn’t support 96 bytes & cannot backup PSX, or Karaoke, or CD-Text or CD+G… :frowning: [/ul]ProtectCD. This protection is physical errors & subcode channel based which can be either difficult or impossible to backup. The copy protection seems to be in the Q subcode channel but the P channel must be read & written as well, requiring a 2x8 byte read/write across the sectors – this is what Olli terms DAO RAW + 16. CloneCD v3.3.4.1 (3 Jan 02), compared to previous versions, has slowed down the Toshiba range of DVD-ROM readers while improving the performance of the LITEON LTR-24102B, FW Rev. >= 5s07 (~ 40’ vs 8’). Backup CD performance varies & can be erratic; members have reported better results using “Don’t repair subchannel data” suggesting that disabling subcode CRC correction is required. My backup tests show that audio is missing at the main menu & that audio volume throughout is relatively diminished.[ul][]Read:[list=1][]Max Speed[]DAO RAW[]data & audio subs[]Fast Error Skip (click “Settings…” & then “Default”) []Intelligent Bad Sector Scanner (up to 1000 is OK) []Note that the error skipping may take some time! (hours in some cases!)[/list=1][/ul] [ul][]Write (default):[list=1][]Max Speed[]DAO RAW[]Close last Session[]Buffer Underrun technology[]Don’t repair subchannel data#[/list=1][/ul]Some points to note about ProtectCD:[list=a][]Not all readers are capable[]Not all writers are capable[]Don’t repair subchannel data# may help[/list=a]Tages. French developed & seems to be limited to Russian released titles at this stage and is not copyable with CloneCD
[/li]
LockBlocks. The LockBlocks protected CDs have 2 circles, one about 5 mm, the other 3 mm, which cause a CD-Reader/Writers to lockup when being read – try settings as per LaserLock – it’ll either read or ‘lock’ up your device :frowning:

Other Copy Protections. These protections are infrequently used and are generally found in countries there is a niche market or where professional piracy is out of control. Copying with CloneCD produces very mixed results & is really not possible at this stage. These titles tend not to run in a lot of devices & in many cases, the protection has been removed in later releases or by official patch.[ul][li]CD-Cops: found on the Italian Agostini series of CDs[]DiscGuard: found on Collin McRae Rally but quickly ‘patched’ out by the publisher[]Others – not popular & rarely encountered; tend to be found on data titles rather than game CDs[/ul][/li]> VeNoM386

DAEMON Tools Developer

Group: DAEMON Tools Staff
Posts: 2012
Joined: Nov. 2000
Posted: 21 Mar. 2002,16:46


During start of every StarForce game you see a small dialog
‘Please wait while checking CD…’ with star icon to the left. Nothing more. In case of failure standard error box is displayed ‘No valid CD found’.
Protection is inside one of game DLLs - you can always find typical string inside it with hex viewer:’ Starforce’ etc…

VeNoM386

DAEMON Tools Developer

Group: DAEMON Tools Staff
Posts: 1985
Joined: Nov. 2000
Posted: 13 Mar. 2002,21:28


What concerns StarForce it is not possible to burn even theoretically with any program or writer, unless you get special media which can be different for each title or even party of CDs of same title. So forget it. It can be only emulated.
Support for emulation from image will be included soon.

VeNoM386

DAEMON Tools Developer

Group: DAEMON Tools Staff
Posts: 2014
Joined: Nov. 2000
Posted: 22 Mar. 2002,11:36


…meaning that the code that checks for a valid CD is inside one of DLLs and is easy to find. There is also another symptom that can help identify starforce protection: if after the game is run, a new file appears in your system directory (prodrv03.vxd in 9x or prodrv03.sys in 2000) then this is StarForce. You can delete it if it is present - it will be recreated by StarForce loader.

VeNoM386
DAEMON Tools Developer

Group: DAEMON Tools Staff
Posts: 2098
Joined: Nov. 2000
Posted: 04 April 2002,02:54


I have also analyzed TAGES protection in Motoracer3. It WILL be possible to copy this protection relatively easy on any RAW capable writer. I have successfully made 1:1 copy for test purposes. No further details until work is completely finished.


A Word on Error Correction
Originally posted by Slussh

One thing i forgot to mention when taking the image off with CloneCD is that the Log file says that my hardware does not support current Fast Error skip settings and it changes the Fast Error Skip settings automatically to Hardware Control with 0 Retries.
Originally posted by Truman

CloneCD does not automatically change the setting back. The setting couldn’t be set in the first place. The description in the log about changing back to hardware error correction setting is wrong. It should really say something like this:“Cannot change drive to software error correction mode, drive is still set in hardware error correction mode.”

Anyway, this doesn’t affect SD2 backups - because CloneCD will replace unreadable sector with another made up unreadable sector - you can see these by using a hex editor on the CD image. The unreadable sectors are filled with hex values 55h. SD2 can read them so it doesn’t know they are different.

If you really want to know the difference here it is:

The difference is that if your drive supports setting to software error correction and the none setting the drive can actually read corrupted sectors with C2 or EDC/ECC errors and therefore be able to copy those corrupted sectors. Currently it seems only Plextor drives can support this.

DAEMON Tools’ “fastdump” feature is used to speed up the image creation of SafeDisc 1 & 2 protected CDs and is also the first step to create a backup of a SafeDisc 2 protected CD. To use this feature you will first have to make sure the DAEMON Manager is running with ENABLED SafeDisc emulation (that’s very important!!)! Now install the CD you want to copy. Run the CD setup and select the desired install size and options. Afterwards start the application from the original CD, make sure the SafeDisc CD verification is over and then exit the application. Do NOT remove the original CD from the CDROM/DVDROM drive you installed from.

Now run your burning program and use the general settings for extracting a SafeDisc protected CD (get the correct settings for CloneCD here or for other programs here). Now start the image creation in your burning program. You will notice the errors at the beginning of the CD (usual for SafeDisc protection) are counted up in about 10 seconds and then the extraction continues like normal. The resulting image will work the same as if you extracted it without the help of DAEMON Tools’ Fastdump feature. You can use this image to mount it with DAEMON Tools’ virtual STEALTH DVDROM or burn it to a CD.
Please note that this feature ONLY WORKS WITH SAFEDISC PROTECTED CDs!!! Other CDs using “unreadable sectors” can’t be extracted faster!!
A word on subchannel codes…
Originally posted by Olli
[B]

The reason was simple: Subchannel reading was broken in CloneCD3, if the device didn’t get it right on the first try.
This has been fixed in CloneCD4, so reading of subchannel data is more “relaxed”. Only thing that could happen is, that you get a warning in your logbook, subchannel reading gets switched off and reading continues.

Exceptions from the rule:

1.) Some readers are very slow when reading subchannel data (Plextor Writers, for example), so you might want to switch it off to save some minutes read time.

2.) Some devices must be “kludged” into reading subchannel data (older SONY Writers, e.g. CRX-140 or Plextor 40x CD-ROM) with an “alternate read method”. On these devices reading subchannel data from data tracks should be avoided, if not absolutely necessary. [/B]