Hopefully this will help:
Correction: 14:56 should say "sector" instead of "track".
Include the disc write offset in your post (Garbage data (combined) offset - your drive's offset)
I hope that covers about anything you'll need to know. I went over dumping Playstation games with audio tracks, including some special situations and troubles you might run into. Because of that, it is very long, but hopefully it covers any potential troubles you might run into.
If you're dumping data-only, just right-click extract raw the track in ISOBuster on a couple drives and make sure the checksums match (with a tool like DAMN HashCalc).
Things I didn't make clear, though should be done:
Be sure to dump the data track multiple times, in multiple drives, and make sure all the checksums match after the psxt001z fix (with a tool like DAMN HashCalc).
Always use the combined offset (the one you find by counting lines of garbage) in EAC offset correction. To find the factory offset from the combined offset, do: combined offset - drive offset (look up your drive in this list). So a combined +669 in a +667 drive would be 669-667 = +2 factory write offset. You can only do this for data+audio discs without a Plextor.
Use psxt001z to check for anomalies. When running it with plain "psxt001z.exe track01.bin", it will tell you the expected total filesize of the image. If the sum of your data+audio track bin files don't match up, something is wrong.
Last edited by velocity37 (2010-04-21 05:16:05)