Author: Jackal • Created: 2007-01-01 • Last updated: 2009-07-10
Please dump all tracks at least twice (if possible, using different drives) to be sure that they are correct!

Introduction

This guide will explain how to preserve CD-based games in the best possible way.

Software needed

Determining disc type

Before we dump the disc, we need to know if it contains any audio tracks.

Insert the disc into the drive and launch IsoBuster.


A disc with audio tracks will look as follows (notice how the audio track icon differs from the data track one):



A disc with audio tracks will unfortunately take a bit longer to dump, because audio tracks require a different treatment than data tracks.

Ripping the data track

Ripping the data track using IsoBuster


The data will now be extracted.

If you get 'Unreadable sector' errors at the end of the track (this is common for discs with audio tracks), pick the option 'Replace with User Data All zeroes' for all unreadable sectors.



Errors should only occur at the very end of the track (99%-100% extraction). If the error occurs earlier, make sure that the disc is free of scratches.

After extraction, if it asks if you want to delete the file, choose 'No'.



When the extraction is complete, you will have an image file of the data track.


If the disc contains audio tracks, go to the next part called 'Fixing the pregap'.


If the disc only contains a data track, head on to the 'Final steps' part.

Fixing the pregap

If the disc has audio tracks, we will have to do some more steps to get the data track down to the right size.

Because IsoBuster is unable to detect where the audio track starts, it will add a part from the first audio track to the end of the data track.

In order to remove the required amount of bytes from the end of the track, it is neccesary to determine the length of the Track02 pregap.
This can be done using Exact Audio Copy (this is also the tool that's we will use to extract the audio tracks).

Before we can determine the pregap length, EAC needs to be set up properly. Go to the next step called 'Setting up EAC the first time'.

Setting up EAC the first time


The above steps have to be done only once!

Determining pregap length



 

You can see that in this picture, EAC detected a Track02 pregap of 4 seconds. In most cases the pregap will be 2 seconds.
Each second of audio data equals 176400 bytes, so a pregap of 2 seconds is 2*176400 = 352800 bytes.

Each second also equals 75 sectors, so a pregap of 2 seconds is 150 sectors. A pregap of 1.74 seconds 149 sectors.

Now that you know the Track02 pregap length, go to the next step.

Removing the pregap using Resize

To remove the Track02 pregap from Track 01, we will use a tool called 'Resize'

To use this tool, download it and extract it in the same folder as the 'Track 01.bin' file. Resize.com requires you to work in Command Prompt.

If EAC reported a pregap of 2 seconds = 352800 bytes and the filename of the image is 'Track 01.bin', the command would be as follows:


RESIZE -r -352800 "Track 01.bin"



When the correct amount of bytes is removed from the end of the image, you can go to the next step. For PSX discs, this is 'Checking and repairing the postgap'. For other discs, it's 'Ripping the audio tracks'.

Checking and repairing the postgap (PSX only)

We now have an image of the data track that is ready for error checking and repairing. For this step we will use the 'psxt001z' tool by Dremora. This tool will only work with PSX images.

Psxt001z requires you to work in Command Prompt.

Make sure that the psxt001z.exe file is in the same folder as the Data track image, and use the following command:


psxt001z.exe --fix "Track 01.bin"


If the data track was ripped from a disc with audio tracks, you will receive a message similar to this (it is also possible that some sectors are fixed, this is normal for discs with audio tracks):



If the disc that you are trying to dump has no audio tracks, we are almost ready. You can go to the part 'Final Steps'.


If the disc contains audio tracks, you can start ripping the audio tracks. So if you are ready, continue to the next part 'Ripping the audio tracks'.

Ripping the audio tracks

Determining the (factory) write offset

Note: Plextor users can skip this section and use a different (faster, easier and more flexible) method instead: http://forum.redump.org/viewtopic.php?id=2468


To determine the factory write offset value we will use IsoBuster to browse to the relevant cd sector:


 


Now you should get a number of rows that show (scrambled) binary data, followed by rows of zeroes. It is also possible that the last row of data is not filled completely, but is partly zeroed.

 

Each row is 16 bytes, so if we have 8 full rows (like in the screenshot above) that are filled with data (and not just zeroes) this means we have 8*16 = 128 bytes.


The amount of data in bytes has to be divided by 4 to get the amount of samples, so in our screenshot it's 128 bytes of data /4 = 32 samples. This is the offset value that we will use in EAC for ripping the audio tracks.
 

Note 1: It can happen that the sector shows no data at all, but only zeroes. If you are 100% sure that you are reading the correct sector and it shows no scrambled data (and going forth and back one sector also doesn't help),  it's best to retry the audio ripping part using a different drive, but this time try using a drive with a bigger read offset (a list of read offsets for each drive can be viewed here: http://www.accuraterip.com/driveoffsets.htm). To be able to detect all offsets, most dumpers in our project bought a cheap CDRW drive with a large read offset, such as the Sony CRX-100E or 120E.
 

Note 2: It is also possible that the sector is full of data. A full sector contains 2352 bytes of data. If the first sector is full of data, browse on to the next sector(s) and make sure all data is counted until you reach the end of the data (start of zeroes).


Now we will change the offset value in EAC to the one that we just determined. Before we do that, we will first calculate the factory write offset.

The offset value that we just retreived from the sector and that is used in EAC to dump the audio tracks is the combined read+write offset. However, for documenting purposes we need you to supply us the write offset value alone, so the read offset value needs to be substracted from the combined offset value.

In order to do this we will need the Read offset value of your drive (detected in EAC or taken from the accuraterip drive list). Once you know this value, it's possible to calculate the factory write offset value:
For example, if reading the sector gives you +32 samples (or 128 bytes (=8 rows) of data) and the read from the Accuraterip database is +30, then the factory write offset is: +32 = (?? + 30) > ?? = +2.

Now we are finally ready to change the offset value in EAC and start dumping the audio tracks. Please make sure that you use the offset value that was calculated using the amount of data in the sector for EAC and not the factory write offset value!

Changing the offset in EAC

Start EAC and change the offset to the proper value:




Now we're finally ready to start ripping the audio tracks.

Ripping audio tracks with EAC


Now we are almost ready. Head on to the 'Final steps'.

Final steps

After dumping, you will end up with the following files:


You can now help our project by supplying us with the information about the dump.

The information that we need is specified in the next paragraph.


If you need any additional help, contact details can be found on this site in the 'Site' menu.

Feel free to idle or ask for any help in our IRC channel: ForeverChat #redump.

Mandatory information


Registered users online: 6 • Guests online: 22 • Feed readers online: 7
Online: amarok, iR0b0t, Jackal, RiMMER, romgod, xrusher