.*.* I whant to know how to backup Silent Hill 1 *.*.

[ch3bastian]

hi i new on this of backuping cds so i have Silent Hill 1 and i whant to backup it (it have too much scraches) still working but i dont wanna brake it so any body have a full (noob) guide of backup CDs of PSX to use in my PSX and emulator and in not so far future in a PS3


tnx

[Sidney]

Download Goldenhawk's CDRWin.
Install with default settings.
Select Backup Disc from menu.
Do not change any settings, they are the correct ones for copying PSX games.
Read and write at slowest speed settings.
I do not think you will create a good copy though as the dumping process will abort if it cannot read the disc due to the scratches.
If it does then you cannot make a true backup.

[SimpleSnake]

I don't remeber what the default value is but set your read retry setting around like 50 or more. Also, clean the disc, scratches don't matter as much as the dirt and dust that will settle in them, that is if they're not too deep. luke warm water will work, just dry with one of those clothes people use to clean their glasses with.

[Sidney]

By default Read Retries are set at 0 for a very good reason.
Any read errors at all means the source cd is damaged.
Some people may even suggest to set Error Recovery to either Ignore or Replace instead of the default which is Abort.
Once again the Default is Abort for very good reasons.
PSX cds do not have any deliberate bad sectors, they only exist due to damage to the source cd.
Setting Read Retries to other than 0 will invariably mean that, if either of the other two Read Recovery options is selected, you will end up with an image that can not possibly contain the same data as the original should have.
This will lead to simple things like glitches in the videos or even more severe problems such as game crashing because data in the executable is not what it should be.
Once again, Goldenhawks CDRWin was originally created for the purpose of backing up PSX games and the defaults as installed are the correct settings.
One other usefull utility to use, once the .bin/.cue files are created, is CDMage, from

http://cdmage.orcon.net.nz/frames.html

.
This has a function with which you can scan .bin files for corruption.
Any corruption means a bad image.

[SimpleSnake]

eh, fine values i used
raw
abort
auto
auto
read retry 50+

make image, use fireburner, check file for corruption, then burn.
Or message me and maybe I'll come over and hold your hand while you do it.

Maybe we should just use the disk, as it is scratched, and just burn it on the fly, if it works buy a lotto ticket, if not you have a new coaster.

[Warlock]

Originally Posted by Sidney

By default Read Retries are set at 0 for a very good reason.
Any read errors at all means the source cd is damaged.
Some people may even suggest to set Error Recovery to either Ignore or Replace instead of the default which is Abort.
Once again the Default is Abort for very good reasons.
PSX cds do not have any deliberate bad sectors, they only exist due to damage to the source cd.
Setting Read Retries to other than 0 will invariably mean that, if either of the other two Read Recovery options is selected, you will end up with an image that can not possibly contain the same data as the original should have.
This will lead to simple things like glitches in the videos or even more severe problems such as game crashing because data in the executable is not what it should be.
Once again, Goldenhawks CDRWin was originally created for the purpose of backing up PSX games and the defaults as installed are the correct settings.
One other usefull utility to use, once the .bin/.cue files are created, is CDMage, from

http://cdmage.orcon.net.nz/frames.html

.
This has a function with which you can scan .bin files for corruption.
Any corruption means a bad image.

I agree 100%

[SimpleSnake]

if you set the error correction to abort it will abort. I remember backing up parasite eve that I bought used from some store bin. The disk was bad, very bad. It was a pain to tell it to retry every time myself as it would get to 76% then bail the first time it hit an error. So I set the read-retry above 50, it took that many to get the data off the disk. When I had it set to 0 to 15 it would abort, meaning stop... not abort fill in the blanks.
About half the good programs have corruption scans, that's nothing special.

Don't get me wrong I love the attention I get here,
but as long as you two are breathing down my neck use a mint eh?