Page 5 of 7
Re: Offset detection using the D8 read command - Discussion
Posted: Fri Feb 08, 2008 1:04 pm
by pnkiller78
gigadeath wrote:Isn't the drive offset subtraction only necessary to get the absolute write offset of the disc? He should dump with +702 in EAC / -702 PerfectRip
Yeah, you are right, it was a typo. I corrected my redaction.
Re: Offset detection using the D8 read command - Discussion
Posted: Fri Feb 08, 2008 1:12 pm
by xenogears
Thanks but I need the confirmation that +702 EAC / -702 Perfectrip (the one I used) is correct.
I know that the disc factory write offset would be +672 (I did the calculations with the px-760a, drive offset +30).
From the previous posts I assume that 702 is correct, I'll submit dump data tomorrow in the morning!
Thanks for the collaboration!
Re: Offset detection using the D8 read command - Discussion
Posted: Fri Feb 08, 2008 1:54 pm
by themabus
it's ok
018174:
01 xor 01 = 00
81 xor 80 = 01
74 xor 00 = 74
MSF=00:01:74
when you requested LBA 0 (MSF 00:02:00), previous sector with 28,5*16 bytes offset was returned, so it's as if data was shifted to the outside of cd by more than a sector, and you now see it's scrambled header, so +1 sector
(2352+(28*16)+8)/4=702 samples
ok
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 1:25 am
by pepsidrinker
Ok, I did the d8 command there is 8 rows of data so 32, accurate rip says my offset is 30, so write is +2, I wonder why my other drive and ISObuster wouldn't show that info? In the header or whatever it's 200, so I don't have to do anything extra correct?
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 2:26 am
by pepsidrinker
Just to make sure I did this right... This is for Shining Force CD for the Sega-CD
Code: Select all
F6A986FEE2C0499036EC16CDCED5945F -1
2F781C2289D9A6DAFADB031B41CB7057 -2
643EAB507F7C2021D8185A8ABB27335A -3
95FB2F035C01F9C042D0319C1469CF6E -4
D42C5F5DF8398292E1AD887DA6A1BAF8 -5
7302A5C1BB10734C25F5DB071B428B71 -6
A7647AAB633F69D02EDC1C59C9FAD6C3 -7
1ED1C85C56B9FEF2C04590332C15DDCF -8
19940AEF470C3285D5A31F39C812D68D -9
9EE5A84B3EB75076BC26F1DAC45B137B -10
4DE37589E726CA9AD72B1E9F486836AE -11
96FC6EC1EC504DFC3581D7205E98386A -12
92AF2DBC1DB1C9B456F77EC6A052F83D -13
8291A1AC787DE2A189B866F2AAC5BF13 -14
300DD4059F432831DE94586F7AAC233D -15
D9D19ADC6B19EF4ACC3715D68F1EE408 -16
4B46B772F6A586FB22C35991FAEC430D -17
F1C58453237DD9E19AC86B16AF4EFC34 -18
41D7705EA4387B52A37DB9E1B2C87596 -19
A72EFA9C4329F1DEC458537ABDE33189 -20
D466DF6AD82F1A9C0B29C75ED2B85DB2 -21
B9B5B2F735869722EE998C6AE5EF0B0C -22
0745C2B311B5CC7715E68F0AE4070B42 -23
8771A2A479BB62F36985EEE30C49C5F6 -24
D306DDC2D9919AEC6B0DEF458C3325D5 -25
DB1F1B480B768766E2AAC9BF16F00EC4 -26
0453437DF1E184486376A9E6FECAC057 -27
103E8C1065CC2B15DF4F18340A97472E -28
B29C75A9E73ECA90572C3E9DD0699C2E -29
E9DC4ED9F45AC77B12A34DB9F5B2C735 -30
92972DAE9DBC69B1EEF44C4775F2A705 -31
BA833321D5D85F1AB80B328755A2BF39 -32
B012F40D8745A2B339B5D2F71D8689A2 -33
E6F98AC2E7118A8C6725EA9B0F2B441F -34
734825F69B06EB42CF7194246F5B6C3B -35
6DD36D9DEDA98DBEE5B04B34375756BE -36
BEF0704424335B55FB7F036001E8004E -37
80346017680EAE847C6361E9E84ECEB4 -38
54777F66A02AF81F028801A6807AE023 -39
0819C68AD2E71D8A89A726FA9AC32B11 -40
DF4C5835FA97032E81DC6059E83ACE93 -41
146DCF6D942DAF5DBC39B1D2F45D8779 -42
A2A2F9B982F2E185886326A9DAFEDB00 -43
5B403B7013640DEB458F732425DB5B1B -44
7B4B637769E6AECAFC5701FE80406030 -45
571D1AEF486436AB56FF7EC020A540C9 -46
0A91C72C529DFDA981BEE0704824369B -47
56EB7ECF6054283F5E90386C12ADCDBD -48
95B1AF347C1761CEA8547EBF60702824 -49
1E9B486B76AF66FC2AC1DF10580C3A85 -50
D3231DD9C99A57F0126F485436BF56F0 -51
3EC410A760C9F5D1871C6289E9A6CEFA -52
D4431F71C824569B7EEB604F68342E97 -53
5C6EB9EC72CDE5958B2F275C1AB9CB32 -54
D7559EBF28701EA4087B46A372F9E582 -55
CB2197586EBAAC733DE5D18BE275412A -56
B6CF36D416DF4ED834F4977B2EA35C79 -57
F9E2C2C99196EC6ECDEC558DFF257CD3 -58
C8EEB37785DFA321B9D872DAA59B3B2B -59
535F7DF821824B044D2B4B76A0BF780C -60
2285D9A31AF9CB02D7419EB068742EA7 -61
5C7A414BA985B73DDE61D81C5A89FB26 -62
C35AD1FB1C4349F1F6C4CD43B95FA524 -63
00FFFFFFFFFFFFFFFFFFFF0001820061
There is 63 * 16 = 1008 /4 = 252(Fixed Read) - 30 = 222(Write Offset)
Is that correct?
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 2:26 am
by themabus
what is the read offset for 2nd drive? if it is larger negative than -1, then it won't show in IsoBuster.
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 2:28 am
by pepsidrinker
My other drive was +102 offset. Is my post above correct?
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 2:31 am
by themabus
it's correct,
but about +102 - i don't know... does it show junk for other cds? maybe it just won't...
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 2:34 am
by pepsidrinker
Yeah, it showed junk for other cds, with the new plextor when I tried to dump it I got read errors so maybe that is why it didn't show before for the +102 drive I have to try and get it resurfaced.
I have another question, for the shining force cd at the 99% point I got read errors in the guide it says to fill with user data does that go for sega-cd games also?
EAC gives a gap of 1.74 for track 2, when I try sector view with ISO buster 150 sector has ff ff on top and 149 sector back gives a device read error, do you happen to have perfectrip so i can try that gap detection?
Re: Offset detection using the D8 read command - Discussion
Posted: Thu Feb 14, 2008 2:46 am
by themabus
i'm sorry, i don't have a perfectrip, i hope somebody can answer that