• Registered: 2011-02-20
  • Posts: 1,747

Detailed page says https://web.archive.org/web/20080911180 … cl:80/?p=8

donde ss.bin es un dump en bruto (2064 bytes) del PSN 0xFD021E

I googled '0xFD021E', and it seems this value is correct, not '0xFD21E'.
'0xFD021E' is the lead-out area of layer 1.

DiscImageCreator, UmdImageCreator, Conv2multiBin, bin2wav, PS3Auth (needs login), recompressTo7z_20150109.bat

sarami's Website

  • Registered: 2006-12-24
  • Posts: 3,847

sarami wrote:
F1ReB4LL wrote:

Still doesn't work.

Sorry, fixed. http://www.mediafire.com/file/eq80y20l9 … st.7z/file

Forgot to show you the logs back then. It works (though, the SS ranges are unstable), but for some reason the dump itself always has different sizes, why?

Post's attachments

xboxlogs.7z 25.48 kb, 16 downloads since 2019-07-28 

You don't have the permssions to download the attachments of this post.
  • Registered: 2011-02-20
  • Posts: 1,747

F1ReB4LL wrote:

but for some reason the dump itself always has different sizes, why?

Because reading error occurred out of the ss range.

DiscImageCreator, UmdImageCreator, Conv2multiBin, bin2wav, PS3Auth (needs login), recompressTo7z_20150109.bat

sarami's Website

  • Registered: 2006-12-24
  • Posts: 3,847

But shouldn't DIC keep the total image size? Padding the bad blocks with zeroes or with 0x55 or something else?