Redump Forum

ssjkakaroto wrote:Using the offset +1176 I was able to get the same hashes for tracks 2 and 3 as pnkiller78 (probably all the other tracks will match too now).
I'll redump this game tomorrow.
Does this change affect track 1 too? If so, how much do I need to remove?

Just dump it in perfectrip with the plextor.. if that will give you matching checksums with +1176 and 1.73 gap then it should be ok..

@pnkiller, what's the offset difference between the 2 Hexen II dumps? are you sure there isn't a sector offset caused by the bug?

I dumped with perfectrip, it gave me a 1.73 pregap but none of the tracks matched
The pcm format it uses is the same as the MS PCM Converter?

Yes. There's some option you have to adjust, did you read the guide?

For example combined read/write offset has to be inserted with +/- inverted

So if you dump with +56 in EAC you have to put -56 in PerfectRip

pnkiller78 were you able to overread into the Lead out with your LG drives? I always get a sync error at ~99.9% of track 11 with my NEC and my LG, the Plextor and Pioneer read without a problem but the CRC doesnt match yours. If I turn off overread they work ok.

Yes, I inverted the offset.

So what are you saying ssjkakaroto, does the checksum match if you invert in perfectrip or not? or is there anyway you can trigger a 1.73 gap in EAC?

No, perfectrip never matches any checksum (not for this game or any other that I have tested) and I use the same offset that I use in EAC but with the - sign.

And yes, I can get a 1.73 pregap in EAC using my plextor.

As I said before, I can match tracks 2-10 with pnkiller78's. But when ripping track 11 I have 2 different results:
1) I can overread into the leadout with my Plextor and Pioneer and get the same CRC but it's different from pnkiller78's
2) I can't overread into the leadout with my LG and NEC, both always give me a sync error

Finally I want to know how much do I have to remove from the data track, is it just the 1.73 pregap or the fact that there's a 2 sector correction has some influence?

sorry for the delay.. the last track I dumped with my LiteOn LTN323 -1164 Drive offset... since the disc had a big positive offset, i give it a try with this drive and in fact it got info after the position were my other drives was throwing just zeros, dumped 3 times, so since the drive didn't show errors on EAC I decided to post the info for the last track dumped with the liteon drive.

EDIT 1
Yes, my LG and plextor drive do overread in the lead-out, but I'm presuming that since these game has huge positives offset, the overread is not enough, with both drives the hashes matched, but comparing against the dump obtained with the LiteOn drive they star showing zeros in the last portion of the dump were the liteon dump showed data.

I'm not sure how many sectors need to be removed.. I hope someone else knows this.. And I hope you can compare the last track to pnkiller's.. maybe one of them is cut off.

edit: pnkiller, can't you install the plextor into your pc?

Vigi wrote:edit: pnkiller, can't you install the plextor into your pc?

Sorry, it's a notebook

Vigi wrote:@pnkiller, what's the offset difference between the 2 Hexen II dumps? are you sure there isn't a sector offset caused by the bug?

I don't know right now, I will dump the entire disk into a bin file and apply the psxt001z track method to obtain your checksums, then will compare against mines and tell you the offset difference.. I post them later