203w ago - First of all, Happy July 4th to our American viewers! As we all know, Folding At Home on the PS3 is really a beast - it knows how to use the hardware efficiently, making the PS3 one of the top clients in the entire project.
The PS3 Debug / Test version has the included files, sprx's, and the Eboot.bin all decrypted. You can now peel apart the files to see how the Folding@Home client utilizes the power of the PS3.
An interesting note: the configuration file outlines that 6 SPU's are in use, as well as one Raw SPU.
It begs the question, is it 6 SPU's in total, or 6+1 = 7 ?
It becomes much more interesting if its 6+1, beckoning rumors of the 8th "disabled" SPU not being disabled at all, but actually, secretly being used for security, while the 7th SPU, that we all thought was for security, was just a front.
It is a bit of a stretch, but it is something to keep in mind while you dig through the Folding@Home client, looking for goodies.
Since this is an old version, when updating on a Development unit from this file, it gets stuck in an "update loop" essentially, and eventually fails to run, so it's not very useful on the PS3, but in a disassembler is another story!
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Just a guess: AFAIK good encryption algorithm hides any pattern from original source - even though the un-encrypted source would be having patterns or repeating sequences, encrypted result hides all of it. Well encrypted data has (almost) the same distribution of every character thus making it very hard to compress. See http://en.wikipedia.org/wiki/Entropy_(Information_theory)#Data_compression