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.
The dump is good.. it should be added.. It's just strange that it's supposedly the same version, but with different data+audio tracks.. maybe p_star can supply some more info about his dump (disc scans, whatever)
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.
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.
Last edited by gigadeath on Fri Feb 01, 2008 3:14 pm, edited 1 time in total.
The disc 2 is perfectly dumped by perfectrip and both data and audio tracks are different than the dump submitted by p_star.
Data track of disc 1 is also different from the data track submitted by p_star and furthermore perfectrip result match the result of the traditional Isobuster method.
For the audio track of disc 1 I don't know, I'll try to dump it with the traditional method and verify if it match.
I'm still waiting for a tip on how I can generate the correct pregap of 2 second and manually attach it to the audio track extracted with EAC (there is a well known bug that prevents 2 tracks discs to be correctly dumped in EAC with the automated procedure)
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.
Those messages only meant that 5 sectors in the pregap, which were empty to begin with, were replaced with empty contents..
I've had this error plenty of times before and my dumps always matched EAC's checksums and other dump's checksums.. the log says 'completed succesfully' and there are no C2 errors, so everything should be ok. And I agree with xenogear's latest post.. the disc is clearly different and there are no dumping issues.
Themabus, you are GREAT!!
I followed your guide step by step and the result is the same as perfectrip!!
The dump was good after all!!
I got the same result with every drive I have here at home (yes, it was a great amount of work!)
Here are the details of the new track02 created with EAC:
To recap, the dump is surely good; I dumped 3 times (with different drives too) the discs with the traditional method and 1 time with perfectrip with the PX-760A. Everytime the size/CRC32/MD5/SHA1 of the tracks are always the same!
I still have to figure out how to check the EXE date and why p_star dump is so different.
both SKUs have 3 discs, I don't know why p_star did not dump Disc 3.
Furthermore yesterday I swapped disc 2 with 3 and I discovered that disc 2 matches with the dump of p_star.
The mystery remains for disc 1 which is different.
I'll submit dumps info in the Dumps forum.
SORRY but it seems that I was wrong...
My dumps of disc 1 and disc 2 match with the dumps of p_star
I simply did the wrong comparisons with the hash info...
Give me a few time, I shall lay out results...