redump.info Forum

gigadeath wrote:Actually I don't think it's always true...

The replaced sectors warning in the log is a sure sign of something wasn't right.

xenogears wrote:I really don't know. There are not corrupt C2 pointers but in the end perfectrip sends out a message similar to "sorry, the dump was not perfect"
On the other hand the data track is the same I got with the traditional method. Soon we'll see for the audio track.

xenogears wrote:I really don't know. There are not corrupt C2 pointers but in the end perfectrip sends out a message similar to "sorry, the dump was not perfect"
On the other hand the data track is the same I got with the traditional method. Soon we'll see for the audio track.

Including Track 02 pregap
In the step 'fixing the pregap' we removed the track02 pregap from the end of the data track.

We already determined length of the pregap. For instance, 2 seconds pregap was 352800 bytes. The amount of bytes that was determined now has to be added to the beginning of Track02.

We can do this by inserting the required amount of (empty) bytes with a hex editor or by using the psxt001z tool:

Open up command prompt, go to the folder of the track images. Make sure a recent version of psxt001z.exe (see the beginning of this guide for a link) is in the same folder. Use the following command:

psxt001z --gen pregap.bin SIZE

'SIZE' has to be replaced with the amount of bytes that was determined in the step 'fixing the pregap'. In most cases this amount will be 352800 (for a 2 sec gap), so this would give us the following command:

psxt001z --gen pregap.bin 352800


To add the pregap to Track02, use the following command:

copy /b pregap.bin+track02.bin newtrack02.bin



The file newtrack02.bin should now consist of pregap and audio track.

This is the Track02 file that we want to use for preservation.

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

gigadeath wrote:Vigi, the dump is not good, PerfectRip itself says it. And the log says clearly that some sectors were replaced because they couldn't be read. I don't think having 0 corrupt C2 pointers is the only indication of a good dump.