View Single Post
Old 01-20-2013   #6
CaptainCPS-X
Homebrew Developer
 
CaptainCPS-X's Avatar
 
Join Date: Sep 2010
Location: Puerto Rico, U.S.
Posts: 906
Likes: 1,066
Liked 2,021 Times in 512 Posts
Mentioned: 347 Post(s)
Tagged: 0 Thread(s)
Hiyas guys, I posted some research technical information here that you might find useful

http://www.ps3hax.net/showthread.php...369#post524369

I'll quote myself just in case xD...

Size difference between old ISOs and new ISOs

From my experience coding my personal (unreleased) disc reading library for Windows, from what I understand, I will assume that the size difference its because the ISO is not really created following the ISO9660/MODE1/2048 (+UDF/Joliet/...) standard, but probably created as ISO9660/MODE1/2352 (+UDF/Joliet/...) or BIN (binary). So each sector will have 'synchronization data', and 'Error Check Data', found on Discs to allow recovery / re-creation of sector data in case of Disc Surface damages and such.

Such 'extra' data located on ISO/MODE1/2352 BIN (binary) disc images is not so evident on regular old school CD (700mb) images, size of the ISO/MODE1/2048 version of it will always be less.

I bet they didn't even include a .CUE file as well, since they are "probably" not following any standard.

Anyway, ISO9660 disc images in binary form should always be named .BIN and include a .CUE file.

There is a probability that I am wrong, maybe it is some kind of new ISO that doesn't follow any Standards (I really doubt it xD), but I will try to acquire the released "ISO" to verify it myself.

I hope that if my theory is right, these release groups choose to release future disc images as BIN/CUE, just to avoid any confusion with already circulating ISOs.

Reason to Release new "ISO"s

I doubt that the reason of releasing such "ISO"s is because Sony could detect regular ISO/MODE1/2048 (LOL ). The Cobra Optic Drive Emulator, was probably designed to read data as the real BD-Drive reads it, so when it cannot find the original 'synchronization data', 'header', 'error check data', etc...it will most probably give read error.

EDIT: Just to confirm my point, I made a custom disc image following ISO9660/MODE1/2352 standard of "BCES01435-[PlayStation All-Stars Battle Royale]", and the resulting size is 6.75 GB, very similar indeed to the one released by "TL" group. If I made the custom disc image as ISO9660/MODE1/2048 then the resulting size would be approx. 5.84 GB.

I just need to acquire one piece of the release made by "TL" and I will be able to confirm if the ISO is a BIN named and published incorrectly without proper CUE.

Edited my original post:

EDIT2: The difference between their size is approx. 13.48% [ ((6.75 - 5.84) / 6.75) * 100 ]. So if this difference rate is same in all PS3 disc images ripped as ISO/MODE1/2352, then a 40 GB game would have approx. 5.39 GB more when saved as BIN/CUE.
SeeYa!
__________________
gamePKG / FB Alpha RL - [ https://github.com/CaptainCPS ]
FB ALPHA DEV TEAM - [ http://neosource.1emu.net ] [ http://www.barryharris.me.uk/ ]
PS3 - [CECH-2501A][NOR][160GB HDD][REBUG CFW 4.41.2 LITE]

Last edited by CaptainCPS-X; 01-20-2013 at 03:43 AM.
CaptainCPS-X is offline   Reply With Quote
Likes: (1)