Editing 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 783: | Line 783: | ||
*Intended to store: | *Intended to store: | ||
**Counters (number of times the .SFO was updated, etc...) | **Counters (number of times the .SFO was updated, etc...) | ||
**User/console | **User/console data | ||
**Some more unknown and reserved areas. See {{Talk}} page | **Some more unknown and reserved areas. See {{Talk}} page | ||
Line 829: | Line 829: | ||
**When the SFO is generated the user/console data is taken from [[XRegistry.sys]] | **When the SFO is generated the user/console data is taken from [[XRegistry.sys]] | ||
**The system displays the time when the savedata was updated by reading the timestamp of PARAM.SFO | **The system displays the time when the savedata was updated by reading the timestamp of PARAM.SFO | ||
**In the case one of the first bytes at the begining is used to store flags (second byte mostly because is the one that changes most in the samples found) there is a limited number of firmware features related with savegames that needs to work in a different mode based on a flag (this flags should be using as settings of the gamesave), some posible features enabled/disabled by this flags could be: | **In the case one of the first bytes at the begining is used to store flags (second byte mostly because is the one that changes most in the samples found) there is a limited number of firmware features related with savegames that needs to work in a different mode based on a flag (this flags should be using as settings of the gamesave), some posible features enabled/disabled by this flags could be: | ||
***Times the savedata was exported/imported to a external device (counters) | ***Times the savedata was exported/imported to a external device (counters) |