Editing Talk:PARAM.SFO
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 95: | Line 95: | ||
==APP_VER, TARGET_APP_VER, PATCH_FILE, PS3_SYSTEM_VER, VERSION (Patches)== | ==APP_VER, TARGET_APP_VER, PATCH_FILE, PS3_SYSTEM_VER, VERSION (Patches)== | ||
Lot of things to add here, maybe needs another page, but im not the best one to document how patches works | Lot of things to add here, maybe needs another page, but im not the best one to document how patches works | ||
*Million dollars questions in relationship with ATTRIBUTE: | *Million dollars questions in relationship with ATTRIBUTE: | ||
**Why ATTRIBUTE flags for patches (used to overwrite other ATTRIBUTE flags or param_key's) are placed at the third byte of ATTRIBUTE instead of first byte ?. Being an special group under CATEGORY '''GD''' they could be placed anywhere, all the other groups of flags are placed starting from top of the table represented in wiki (matching chronologicall usage/implementation of them), this is the only group of flags that doesnt starts with his first (or oldest) flag with a value of 00000000000000000000000000000001 | **Why ATTRIBUTE flags for patches (used to overwrite other ATTRIBUTE flags or param_key's) are placed at the third byte of ATTRIBUTE instead of first byte ?. Being an special group under CATEGORY '''GD''' they could be placed anywhere, all the other groups of flags are placed starting from top of the table represented in wiki (matching chronologicall usage/implementation of them), this is the only group of flags that doesnt starts with his first (or oldest) flag with a value of 00000000000000000000000000000001 |