Talk:Resource Container (RCO): Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 88: | Line 88: | ||
all OFW 1.00-4.75 hashes: https://www.mirrorcreator.com/files/7KCMQKWQ/RCO-hashreport.7z_links | all OFW 1.00-4.75 hashes: https://www.mirrorcreator.com/files/7KCMQKWQ/RCO-hashreport.7z_links | ||
=RCO's containing images with non-gim formats | =RCO's containing images with non-gim formats= | ||
*campaign_plugin (png) | *campaign_plugin (png) | ||
*eula_net_plugin (png, jpg) | *eula_net_plugin (png, jpg) | ||
| Line 99: | Line 99: | ||
All the images in all the other rco's uses .gim format | All the images in all the other rco's uses .gim format | ||
=RCO's containing sounds (in .vag format) | =RCO's containing sounds (in .vag format)= | ||
*edy_plugin | *edy_plugin | ||
*eula_net_plugin | *eula_net_plugin | ||
Revision as of 03:00, 29 September 2015
RCO versioning
All RCO files contains a version number, the version increases with bigger firmwares but not for every firmware and is not directly associated with it. The same versioning sequence is used in PSP and PS3 RCO's
It seems all the RCO's of a specific firmware shares the same version (speculative, not verifyed in all firmwares). It seems to be the version of the "rco set", or the version of the "rco tool" used to compile the whole "rco set"
Is posible to create a correspondecy between the "rco set" version and the firmwares versions where a specific "rco set" version was used. RCOmage v1.1.1 (latest stable) identifyes the version with a list of hardcoded values associated with a "system firmware version"
Code Sample
After extracting the contents of the RCO with RCOmage, the "rco set" version is stored for rebuilding purposes in the RCOXML descriptor file as an attribute with the name minFirmwareVer
If the version is unknown is stored as unknownId0x%x using unknownId to specify the fact that is unknown + the real hex value 0x%x
Example... sysconf_plugin.rco from PS3 firmware 2.00 with "rco set" version 0x106
Code Sample
Speculation
There is no known formula to make a direct conversion from the hex value to the system firmware... speculative ideas post here
RCO versions
If there is no formula, the only thing we can do is to make a list with the versions used in the "rco set" from all PS3 firmwares. Probably this list will be included in the next version of rcomage to improve PS3 compatibility so please help completing the collection
| Console | System firmware version | "RCO set" version |
|---|---|---|
| PSP | 1.0 | 0x70 |
| PSP | 1.5 | 0x71 |
| PSP | 2.6 | 0x90 |
| PSP | 2.7 | 0x95 |
| PSP | 2.8 | 0x96 |
| PSP | 3.5 | 0x100 |
| PSP | 6.61 | ? |
| Console | System firmware version | "RCO set" version |
|---|---|---|
| PS3 | 1.00 | 0x97 |
| PS3 | 2.00 | 0x106 |
| PS3 | ? | 0x107 |
| PS3 | 3.41 | 0x110 |
| PS3 | 3.55 | 0x110 |
| PS3 | 4.21 | 0x120 |
| PS3 | 4.46 | 0x130 |
| PS3 | 4.76 | 0x130 |
RCO hashreport
all OFW 1.00-4.75 hashes: https://www.mirrorcreator.com/files/7KCMQKWQ/RCO-hashreport.7z_links
RCO's containing images with non-gim formats
- campaign_plugin (png)
- eula_net_plugin (png, jpg)
- game_ext_plugin (png)
- newstore_plugin (png, jpg)
- photoviewer_plugin (png)
- regcam_plugin (png, jpg)
- videoeditor_plugin (png, jpg)
All the images in all the other rco's uses .gim format
RCO's containing sounds (in .vag format)
- edy_plugin
- eula_net_plugin
- osk_plugin
- regcam_plugin
- system_plugin
- videoeditor_plugin