08-22-2010,08:24 AM

Originally Posted by
SP193
PS: Finding the size of a disc's TOC isn't accurate if you try finding it based on the size of the disc! You must see how many files there are on the disc. The more files/folders there are, the bigger the TOC is.
Heh Bro, all good with your post except the last sentence (and I think I stated it correctly before).
So bigger the Data-Track on a disc is, so bigger is the TOC (or atleast "the thingy", which is what matters here).
By searching for the files, the chance that you'll get the wrong size is pretty high for PS1&PS2-Games.
Just look at the FinalFantasy-Games, which often had their files hidden and the actual Game-Executable contained the LBAs, instead of the original TOC.
Then there are the games with dummy-space. One example, which I find very good even thought it is a PS2-Game (the TOC-Example just applies to it in the same way), is "EyeToy: Play".
The Game-Files are only around 700MB, maybe 698MB or so...and it's actuall TOC is ~4,38GB (so full SingleLayer-DVD).
Anyway,... The big-TOC-thingy only matters for the mechacon, that it knows which sectors are actually accessible (which contain data), so if a CD with a shorter data-track is inserted, software can't simply access the sectors "behind" that biggest sector-value, which is pre-defined by the actually used original.
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony BBA
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
MAX/Datel 32MB&64MB
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux