Fast error skipping settings for Safedisc 2
 

I'm trying to make a copy with my Plex 16x of MOH:AA. After using the search I found out the best settings for Clonecd. Everybody agrees I've to set the readingspeed to 4x and enable fast error skip for making the image. Than I've to use (latest) Betablocker to filter the weak sectors (writer doesn't support correct EFM), write the image at 4x using 'RAW DAO', 'BURN-Proof' and 'Always close last session'.

But it is not totally clear to me which settings to use for Fast error skip. Some say I have to set correction to none and retries to 5, others correction to software and retries to 0. Can anybody help me out on the best settings??

well mate, just try it out :D

use an cd-rw and if the copy doesnt work erase it and try a different setting!

i would recommend the ine with no corretcions and 5 retries...


that's what i do and it works....

if you are going to use betablocker on it, rip it as fast as you want, and fast error skip. you dont want to pause and hear about every little bad sector that betablocker is going to patch for you.

welll,but it's better having no errors(less time)and using betablocker than just using betablocker...

really? how long does it take betablocker to fix the errors? 4x read speed is about 17 minutes for an image of a full cd, and max (40ish) is about 3 minutes.

BetaBlocker does not fix any errors... it simple corrects so called weak sectors. And this should last about 20 seconds (depending on your CPU speed).

BTW: error correction: none, retries: zero and read speed: max

I wondering why there are still people unable to copy SD2... for me its a miracle!

maybe because you have a cd-writer miracle...

Well i'm using Betablocker (Plex 16x no EFM support), so i could just set it to none and 0 in the fast error skip settings. But what if there are some real errors -not weak sectors- that can be corrected? Don't these settings fuck up your cd if there are errors that need to be corrected ??

these are "destroyed "sectors...

for semantics sake, a weak sector is a section of coding that writers dont deal well with. commercial recording softwares such as nero and easy piece of crap both, when encountering this sector, replace it with a section of null code. null code is a specific string that indicates an error.......hence, a 'weak sector' is an error that is placed on purpose......and betablocker fixes it.

Thanks for the explanation, but this isn't really new nor what i asked for...
With fast error skip set to retry 0 en correction none, it skips every readerror it encouters right? But what if there's a real error on the disc that needs to be corrected?? Than the cd could get fucked up right?? Or am i overlooking something?

are retries just not that the reader reads an error and then re reads it again until hte read retries are finished>?

right!!!!:o

yes, and if you set it to 0 it won't do that.., my question is it possible you skip an error that could be corrected that way

what do you mean what if theres a real error on the disk that needs to be corrected? a real error would mean a loss of data, and the disk you tried to back up would probably crash every time that bit of data was called, but was missing. if there is an error on the disk.......(nonsafedisk)........how can software know what to put in its place besides the null string?

tha'ts what i told too