Page 2 of 2
Re: Problem finding out combined read+write offset
Posted: Fri Sep 11, 2009 2:38 am
by hydr0x
themabus wrote:additionally, to be certain, you could try to descramble this garbage data
and would it match to last few data track sectors, it's pretty sure to be just usual offset manifestation then
(though from fragment you provided in 1st post it's already apperant it comes from empty Mode1 sector with LBA:128015
which is expected last data track sector)
No idea how to do this
If I understand you right though I just shouldn't worry too much about the message and try to go with +1356
Re: Problem finding out combined read+write offset
Posted: Fri Sep 11, 2009 10:21 am
by F1ReB4LL
hydr0x wrote:I see. My LG 4167B is supposed to support D8, at least some versions but I had no success with it. I don't think swapping is possible either.
LGs aren't swappable, IIRC. Try to insert some CD, then insert a pin into the eject hole -- all the LG drives I've seen eject the tray automatically.
About D8 -- what does px_d8 write? Also try to run this cachex tool: "cachex -i -p d:" (use a letter of your drive instead of d:), if you have SPTD drivers installed on your system - uninstall them (otherwise, info will be incorrect).
Re: Problem finding out combined read+write offset
Posted: Fri Sep 11, 2009 2:42 pm
by Rocknroms
Without a CloneCD (hydr0x, google it and you'll find it) sub I don't know if we can determine real gaps. Then if there's some data sectors in audio they can be easily converted with the tool for descrambling ** in old dctools package, I'll upload if needed. The only thing to find out is real offset, if D8 command will work after the above clue, you will have no problem.
** It matched all dumps here with those sectors I need to convert.