Editing Talk:PARAM.SFO

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 1: Line 1:
=Unknown or new parameters=
This page is an index/worklog/notepad with sections referred to the front page. All the sections in this page are things related with PARAM.SFO that are not completely documented, and the final purpose is to move the info when completed to the front page. This also will help to keep the front page free of speculation.


==CATEGORY (new content formats)==
----
*CATEGORY '''VF''' - (HDD content, NOT in game column) ---> '''unknown name''', used as a valid category filter in the XML configuration file for [[XMB-Game | XMB game column]] in path: dev_flash/vsh/resource/explore/xmb/category_game.xml in key="gameDir"
**key="gameDir" is an XMB item that allows to order the contents by "rating" or "timeCreated" the command used contains a list of categories that are excluded using the [[XMBML Functions#Operators| operator "An" = An not equal]] (VF is at the end of the list excluded with '''An+Game:Game.category VF''')
**Similar than MN, 1P?


*CATEGORY '''XI''' - '''Confirmed''' ---> '''System File for Extra Content Item''' (or '''eXtra Item''' in short form) Used on blu ray structure?
==Unknown==
This is the first attempt to create an "index" for this page with sections refered to the "front" page that doesnt needs to have the same names but needs to be grouped in some way. All the sections in this page are things related with PARAM.SFO that are not completly documented, and the final purpose is to move the info when completed to the "front" page. This also will help to keep the "front" page free of speculation


*'''Indie games''' New category on PSvita and PSN http://blog.us.playstation.com/2013/06/25/ps-vita-indie-games-category-now-live-on-psn/
===TITLE_ID===
Indi games has a specific license, if XMB differences it it will be using ATTRIBUTE flags (similar identification than neogeo and pcengine because has a special license)
See [[PARAM.SFO#TITLE_ID]], everything that "breaks" the standards explained in this link can be added here in this table as an example to understand better how the ID's are assigned to each type of content


*'''PlayStation Mobile''' Implemented around 4.21 firmware, asociated with a text string in explore_plugin_full\Text\English.xml (inside explore_plugin_full.rco). See [PS3 and PSVita Cross Functions]
{| class="wikitable"
<Text name="msg_applications_psm">Applications (PlayStation®Mobile)</Text>
|-
! Content ID (.PKG) !! TITLE_ID (.SFO) !! TITLE (.SFO) !! CATEGORY (.SFO) !! Notes
|-
! colspan="5" | NPIA0****
|-
| IP9100-NPIA00001_00-PS2HDDSYSDAT0001 || NPIA00001 || PS2 System Data || 2D ||
|-
| IP9100-NPIA00002_00-0000111122223333 || NPIA00002 || Folding@home & Life with Playstation || CB ||
|-
| EP9000-NPIA00005_00-HOME000000000001 || NPIA00005 || Playstation home || HM ||
|-
| IP9100-NPIA00006_00-VSHMODULE0000029 || {{No}} || {{No}} || {{No}} || Photo Gallery (doesnt have an .SFO)
|-
| IP9100-NPIA00007_00-0000111122223333 || NPIA00007 || Folding@home & Life with Playstation || CB ||
|-
| || NPIA00009 || ? || ? || <!-- seen in vsh.self -->
|-
| || NPIA00010 || Playstation home || HG || Debug Version (shipped with HDK)
|-
| || NPIA00011 || ? || ? || <!-- seen in vsh.self -->
|-
| || NPIA00012 || DigitalComics || ? || PSP App
|-
| || NPIA00013 || SenseMe || ? || PSP App
|-
| IP9100-NPIA00016_00-VSHMODULE0000001 || {{No}} || {{No}} || {{No}} || Video Editor and Uploader (doesnt have an .SFO)
|-
| IP9100-NPIA00025_00-SFPROD0000000000 || NPIA00025 || Playstation Store || SF || new Playstation Store, not via webbrowser anymore
|-
| IP9100-NPIA09002_00-0000111122223333 || NPIA09002 || Music Unlimited || AM || Qriocity
|-
! colspan="5" | NPIA9****
|-
| IP9101-NPIA9100[5-9]_00-PLUS???????????? || {{No}} || {{No}} || {{No}} || Playstation Plus <!-- seen in vsh.self -->
|-
! colspan="5" | NP*A0****
|-
| EP9000-NPEA00008_00-AQUAVITAPS300000 || NPEA00008 || Aqua Vita || HG || interactive aquarium [http://www.theaveragegamer.com/2007/08/28/aqua-vita-the-ps3-gets-all-fishy/ info link]
|-
| EP9000-NPEA00013_00-HOME000000000001 || NPEA00013 || Playstation Home Beta || HG ||
|-
| EP9000-NPEA00022_00-EYECREATE0000000 || NPEA00022 || Eye Create || HG || Playstation Eye cam utility (create photos, videos, etc...)
|-
| EP9000-NPEA00030_00-MESMERIZEPACK001 || NPEA00030 || Mesmerize || HG || (is a move controller tech demo)
|-
| JP9002-NPJA00040_00-ADHOCPARTY000000 || NPJA00040 || Ad-Hoc Party || HG || (used by "PSP remasters" games to play online in PSP network)
|-
! colspan="5" | NP*B0****
|-
| EP4183-NPEB00344_00-LOVEFILMFULL0100 || NPEB00034 || LOVEFiLM || AV ||
|-
| EP2058-NPEB00894_00-HDDBOOTPINBALL01 || NPEB00894 || Pinball Arcade || HG || "game purchase" enabled in ATTRIBUTE (C00 folder), TROPDIR included
|-
| EP4381-NPEB01229_00-YOUTUBE000000001 || NPEB01229 || Youtube || AT || NPUP10028 for usa region
|-
! colspan="5" | NP*D0****
|-
| EP4061-NPED00026_00-GSKYSCRAPE000ENG || SLES55152 || Skyscraper || 2P || Is a "PS2 Classic" note the TITLE_ID inside SFO is the original of the PS2 game and is different than the CONTENT_ID of the .pkg
|-
! colspan="5" | NPHA*****
|-
| || NPHA0**** || First Party PSP PSN/SEN Games || ? ||
|-
| HP9009-NPHA80082_00-0000000000000100 || NPHA80082 || now TV || AT ||
|-
| HP9000-NPHA70006_00-0000000000000100 || NPHA70006 || QOOK TV || AT ||
|-
! colspan="5" | NPHB*****
|-
| || NPHB0**** || Licensed PSP PSN/SEN Games || ? ||
|-
! colspan="5" | NPXS0[!0]*** (FW Components) <!-- seen in vsh.self -->
|-
| IV0001-NPXS01001_00 || NPXS01001 || {{No}} || {{No}} ||
|-
| || NPXS01002 || {{No}} || {{No}} ||
|-
| || NPXS01003 || {{No}} || {{No}} ||
|-
| || NPXS01005 || {{No}} || {{No}} ||
|-
| || NPXS03003 || {{No}} || {{No}} ||
|-
| || NPXS03029 || {{No}} || {{No}} ||
|-
| || NPXS03043 || {{No}} || {{No}} ||
|-
| || NPXS04004 || {{No}} || {{No}} ||
|-
| || NPXS09386 || {{No}} || {{No}} ||
|-
! colspan="5" | NPXS00*** (SDK Samples)
|-
| IV0002-NPXS00006_00-SAMPLE0000000001 || NPXS00006 || NP GAME || HG ||
|-
| IV0002-NPXS00008_00-GAMEUPDATEPATCH[1/2] || NPXS00008 || GameUpdate Utility Sample || DG ||
|-
| IV0002-NPXS00009_00-GAMEUPDATEPATCH[1/2] || NPXS00009 || GameUpdate Sample (By System) || DG ||
|-
| IV0002-NPXS00018_00-SAMPLE0000000001 || NPXS00018 || Matching2 Invitation Sample || HG ||
|-
| IV0002-NPXS00020_00-HDDBOOTSAMPLE001 || NPXS00020 || HDD Game Sample || HG ||
|-
| IV0002-NPXS00021_00-SAMPLE0000000001 || NPXS00021 || Game Data Sample || HG ||
|-
| IV0002-NPXS00022_00-GAMEPURCHASE000[1/2] || NPXS00022 || Game Purchase Sample || HG ||
|-
| IV0002-NPXS00024_00-SAMPLE0000000001 || NPXS00024 || NP Basic Sample || HG ||
|-
| IV0002-NPXS00031_00-SAMPLE0000000001 || NPXS00031 || NP SNS || HG ||
|-
! colspan="5" | ULES*****
|-
| EP1004-ULES00151_00-GPCGRANDTH000001 || ULES00151 || Grand Theft Auto: Liberty City Stories || PP ||
|-
! colspan="5" | Others
|-
| UP0001-FSYN00001_00-0000111122223333 || FSYN00001 || FaceSync || HG ||
|-
| XXYYYY-MCPD12345_00-XXXXXXXXXXXXXXXX || MCPD12345 || Motion Controller Playground Demo || HG ||
|-
| UP9000-NPUO00007_00-AVAPS15ANVSYCOLR || {{No}} || {{No}} || {{No}} || Avatar 15 anyversary (doesnt have an .SFO)
|-
| UT0007-NPUP00030_00-NETFLIXRIGEL01NA || NPUP00030 || Netflix || AV ||
|-
| {{No}} || PBPX95208 || DVD Player Version 2.10 || {{No}} || PS2 DVD Player Update 2.10 <br/> ps2emu refuses to load this CD
|-
| {{No}} || PBXC0020[1-4] || PSX-Update 1.10/1.20/1.31/2.11 || {{No}} || PSX Updates <br/> ps2emu refuses to load this CD
|-
| {{No}} || SLED01340 || NET YAROZE COLLECTION || {{No}} || PS1 NET YAROZE demo disc <br/> ps1emu + ps3 crashes <!-- main loader is encrypted for [http://en.wikipedia.org/wiki/Net_Yaroze NET YAROZE] -->
|-
| UP0001-TEST00000_00-0000111122223333 || TEST00000 || Debugging Station Launcher || HG ||
|-
| ? || SCEAPPS01 || ? || ? || Related with "shop/kiosk" PS3 models (only visible in "unlocked mode" ?)
|-
| ? || SCEAPPS02 || ? || ? || Related with "shop/kiosk" PS3 models (only visible in "unlocked mode" ?)
|-
| ? || SCEAPPS03 || ? || ? || Related with "shop/kiosk" PS3 models (only visible in "unlocked mode" ?)
|-
|}
 
----
'''Other TITLE_ID's (speculation or as exotic)'''
 
*Playview see: [[Talk:Eboot.PBP#PlayView]]
For PS3: NPJB60*** & NPJA60***
 
For PSP: NPJH60***
 
*NPEO12345 & NPUO12345 : for Others items such theme, digital manual....?
 
*PS3 DISC with PS3_VPRM (Blue-Ray movie structure described as hybrid disc) : BLJM-9300* for Japan.
 
*Cross buy(?) : US: XCUS-0000* UE: XCES-0000*  JP: XCJS-0000*
 
*PSP remaster: BLJM-8500*
 
*1.5 HD remix or converted edition don t seems to have specific title id.
 
*ps2emu refuses to load CD's, that would crash, but ps1emu does this not
 
*Candidates to NPEA000** (more sony experiments) "Operation Creature Feature", "Trials of Topoq", "tori-emaki", "flower"
 
*SCEAPPS01, SCEAPPS02, SCEAPPS03
**blocked in [[XMB-Game | category_game.xml]] specifically in shop firmwares using tag [[XMB#XMB_Configuration_Files | <View id="shop_guest_root">]] (not allowed for "guest" users in shop PS3's)
 
===LINK.XML===
Used in category '''WT''' (and probably all others) to create a link in XMB to a webpage (and probably to a direct download link, if the mimetype of the file is recognized by the PS3 as valid... note the download paths are hardcoded in the firmware and are dependant of the file minetype)
 
The file LINK.XML must be placed in the same folder of the PARAM.SFO (root of the .pkg)... this kind of .pkg's doesnt contains an USRDIR subfolder neither an EBOOT.BIN... but the PARAM.SFO is marked as "BOOTABLE"
 
In a standard .pkg the item that "boots" is the EBOOT.BIN... but in this kind of .pkg's the item that "boots" is the LINK.XML (or more specifically his contents, in this case a link that needs to be managed by the browser)
 
This presents a problem when a .pkg contains 2 items that can "boot" (EBOOT.BIN, and LINK.XML in this priority order)... this behavior has not been tested yet (a frankenstein idea that probably needs to be erased from here, heheh) = "this service has ended" message on xmb (probably also when other none valid structure are used)
 
When the LINK.XML is not valid (as other than url), the XMB still try to launch an internet website but with adress as "about: blank"
 
LINK.XML Example:
{{Boxcode|content=<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<link ver="1.0">
<url>http://www.ps3devwiki.com</url>
</link>
</syntaxhighlight>}}
*Notes
Found in "animax" app (EP4452-NPEB00691_00-DE000000FULL0100)
 
Other: NPEB00701, NPEB00702...
 
Little difference with other way to launch internet web site ("what's news") :Not message "You are launching an internet website"


==ATTRIBUTE (flags brainstorming)==
===ATTRIBUTE===
'''XMB In-Game System Chat Voice Disable''' (Flag Nº7)　： Value and name description are related to this flag but need to be confirmed from PS3 side / not used on bootable but as patches?.
'''XMB In-Game System Chat Voice Disable''' (Flag Nº7)　： Value and name description are related to this flag but need to be confirmed from PS3 side / not used on bootable but as patches?.


Line 24: Line 209:
Boot logo Disable ? <-- <span style="text-decoration: line-through;">this is the "license text hidden" flag</span> ? FW max: 2.80 for ps3 fat? on patches?
Boot logo Disable ? <-- <span style="text-decoration: line-through;">this is the "license text hidden" flag</span> ? FW max: 2.80 for ps3 fat? on patches?


Some flags may only be effective with some hardwares (PSP/PSVITA/[[Torne| Torne ]]/[[Nasne |Nasne]]...), FW, Games, or Category and/or in a cumulative way and others conditions.   
Some flags may only be effective with some hardwares (PSP/PSVITA/[[Torne| Torne ]]/[[Nasne |Nasne]]...), FW, Games, or Category and/or in a cumulative way and others conditions.
 
Please report test/investigation here or on the link forum at the end of this page.   
 
*Examples
{| class="wikitable"
|-
!  Little Endian !! Big Endian !! Decimal !! Flags (Binary) !! Description || Flag Nº || Notes
|-
| colspan="7" style="text-align:center; background-color:#DDDDDD;" | '''Discs'''
|-
| 05 17 80 00 || 00 80 17 05 || 8394501 || 00000000 10000000 00010111 00000101 || killzone 3 || 01+03+09+10+11+13+24 || all flags identifyed
|-
| 20 00 02 00 || 00 02 00 20 || 131104 || 00000000 00000010 00000000 00100000 || Dead Space 2 || 06+18 || all flags identifyed
|-
| colspan="7" style="text-align:center; background-color:#DDDDDD;" | '''Patches'''
|-
| 85 00 00 00 || 00 00 00 85 || 133 || 00000000 00000000 00000000 10000101 || Torne v3.52 || 01+03+08 || all flags identifyed (doesnt use any "overwrite" flag)
|}
 
====XMB In-game background music compatibility====
'''Attempt to create compatiblity list with XMB In-Game (v2) Background Music feature.'''
 
XMB In-Game Background Music was implemented in firmware 2.40
 
Infos on limitations are mostly speculations (and from SFO point of view)
 
To activate it from SFO, see [[PARAM.SFO#ATTRIBUTE_In_Bootable_content]]
 
{| class="wikitable sortable"
|-
! Title !! compatibility!! Note
|-
| Atelier Meruru || {{No}}  || (Signed as 3.60)
|-
| Child of Eden  || {{Yes}} || PSN game, SFO edited and updated from PKG.
|-
| Uncharted 1    || {{No}}  || System FW version required 1.94
|-
|}
 
For better list see:[http://community.us.playstation.com/t5/PlayStation-3/Custom-Soundtrack-Compatible-PS3-PSN-Video-Games/m-p/31099592#U31099592  Custom Soundtrack Compatible list] (without SFO edited?)
 
Thread related: [http://www.ps3hax.net/showthread.php?t=41220 Here]
 
For [[PARAM.SFO#Replacing_a_PARAM.SFO_manually |replacing PARAM.SFO manullay]]
 
*Limitations:
 
After editing the SFO, you should not have anymore the XMB message saying "Music content cannot be played during use of this game" but instead "music will start in a while ( please insert exact xmb message). However, the feature might not work correctly (for easy display, the table report it as NO)
 
*Reasons (speculation):
Conflict with others system utility (E.G.:system chat voice, recording utility), music files or eboot compiled with old SDK or others restrictions (?)
 
*[[QA_Flagging#Debug_Menu_settings_not_in_Retail.2FCEX_QA | Debug Menu]]:
 


'''Unkown flag nº21''' (not tested by myself btw, this is my understanding after decrypting ada hints :P --[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 22:01, 4 February 2014 (EST))
'''Other:''' On PS Vita PKG:
*Previously proposed to be named "XMB In-Game for Software"... but "About This Game Disabled" looks a more intuitive name (note some of the other flags in the third byte of ATTRIBUTE like "Game Purchase Enabled" and "License Logo Disabled" enables/disables an option in side menu). This 3 flags could be grouped together because "About This Game" is another option in side menu, are under the third byte, and there is another unknown flag at his side that could work in a similar way (changing options in side menu)
*When activated, inside the game, and inside XMB In-Game, then trying to boot other content the warning text message is different (it mentions "software" and the variable %1 instead of "game"). In the next examples (copyed from a RCO) the first line is the normal error message and the second one is what appears with this flag enabled
<Text name="msg_need_quit_game_to_operate_ask">To perform this operation, you must quit the game. Do you want to quit the game now?</Text>
<Text name="msg_need_quit_to_operate_ask">To perform this operation, you must quit [%1]. Do you want to quit the software now?</Text>


'''ATTRIBUTE for other CATEGORY's'''
Facebook (gdc):
*ATRIBUTE is listed in this table: [[PARAM.SFO#SFO_Requirements_for_HDD_contents]] as valid for CATEGORY '''PP''', added by me here: http://www.psdevwiki.com/ps3/index.php?title=PARAM.SFO&diff=11171&oldid=11166 i guess it was filled with zeroes because i didnt taked note of special values. But the fact that was used there means is posible that exists specific flags for it, is also posible ATTRIBUTE is used in other CATEGORY's i missed of was added later--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 18:06, 4 February 2014 (EST)
00 80 00 00
LiveTweet (gdc):
00 80 00 00
Skype (gdc):
00 80 '''04''' 00
Musicunlimited (gdc):
88 '''90''' '''0E''' 00
Torne (gdc)
00 00 80 '''81'''
For Torne: http://www.vitadevwiki.com/index.php?title=System_File_Object_(SFO)_(PSF)


===subcategories from X0 to X7===
{{Boxframe0|content='''Subcategories'''<BR />
X category appear (listed on game_ext_plugin.prx) as HG (sub cat)but with different parameters and need cumulative flag (n22 at least+ 4th byte: half byte)
The 4th byte is not used as binary (only?) but as Hex value for half byte (right nibble, left nibble is ignored?) to set X category. If the value is 0 or end up with 0, and the X maker flag is set under right SFO X parameters, X0 (PCEngine) is read by the system.


SFO TEST Tool from Deroad can boot and return to XMB even under X category (when MINIS don t and are stuck after being X categorized, error occurred during the start operation (80010006))
====subcategories from X0 to X7====


'''Folder position in XMB ordered by format (in fw 3.55 with hand-made PARAM.SFO's):'''
X category appear as HG (sub cat)but with different parameters and need cumulative flag (n22 at least+ 4th byte: half byte)
The 4th byte is not used as binary (only?) but as Hexa value for half byte (right nibble, left nibble is ignored?) to set X category. If the value is 0 or end up with 0, and the X maker flag is set under right SFO X parameters, X0 (PCEngine) is read by the system.


Bootable contents installed in game column: [triangle]>[group by]: (works with square too in any item of game column)
SFO TEST Tool from Deroad can boot and return to XMB even under X category (when MINIS don t and are stuck after being X categorized)
*from dev_flash/vsh/resource/explore/xmb/registory.xml


-format <------------- GameList:GameList.type %xCB_LIST_TYPE_GAME_FORMAT
'''Folder position in XMB (in fw 3.55 with hand-made PARAM.SFO's):'''
-tag/album <--------- GameList:GameList.type %xCB_LIST_TYPE_GAME_TAGS
-all <---------------- long list of "conditionals" excluding CATEGORY's that doesnt belongs to XMB game column in the format: '''An+Game:Game.category **'''


By pressing square, group content format position (the 8 X category folders can be displayed at the same time in XMB):
By pressing square, group content format position (the 8 X category folders can be displayed at the same time in XMB):
Line 55: Line 294:
*Mini icon: {{icon content ps3}} Playstation 3
*Mini icon: {{icon content ps3}} Playstation 3


*Mini icon: {{icon content pspremaster}} PSP Remaster, on 3.55, Mini icon: not present (-) ,not accessible (with titles inside).
*Mini icon: {{icon content pspminis}} minis
*Mini icon: {{icon content pspminis}} minis
*mini icon: {{icon content psp}}PSP (Playstation portable): category PP


*Mini icon: {{icon content ps2}} Playstation 2
*Mini icon: {{icon content ps2}} Playstation 2
Line 72: Line 308:


Jul 15, 2009
Jul 15, 2009
Works alone and can be used with any "HG" category content, its not clear what does this flag other than the content has his own "tiny grey icon" with a "PCE" logo and are placed inside his own sub-folder when ordering contents (with square button) in the XMB (3.55, 3.41?).
Works alone and can be used with any "HG" category content, its not clear what does this flag other than the content has his own "tiny grey icon" with a "PCE" logo and are placed inside his own subfolder when ordering contents (with square button) in the XMB (3.55, 3.41?).
Same attributes on PSP
Same attributes on PSP


*'''X3''' Mini icon: not present (-) ?
*'''X3''' Mini icon: not present (-)


*'''X4''' Mini icon:{{icon content neogeo}} '''NEOGEO'''
*'''X4''' Mini icon:{{icon content neogeo}} '''NEOGEO'''
Line 88: Line 324:
Group content order is similar on PSP for the available icons (PS3 folder being PSP and no "PS2"). See [[Talk:Eboot.PBP#Others:_PARAM.SFO_attribut_.28PSP.29]]
Group content order is similar on PSP for the available icons (PS3 folder being PSP and no "PS2"). See [[Talk:Eboot.PBP#Others:_PARAM.SFO_attribut_.28PSP.29]]


Other app with category not implemented yet on 3.55 FW such WT or unknown as VF on 4.21 can also just not "appear" on XMB and not being on the "Unknown" folder as Corrupted/Unsupported data. To access/delete from 3.55 XMB your PSP remaster folder s titles, group content it (not by format).
}}


*The existence of the weird flags X0 (for PCEngine) and X4 (for NeoGeo) and we called them "subcategories" (refered to the fact that are an extension of HG category) seems to be related with the fact that those emulators are running under the PSP emulator. PC Engine and NeoGeo are part of the PSP firmware
===CATEGORY===
 
*{{icon content psvita}} - '''Speculation''', refered as "VT" in one his related PS3 packages: NP0001-NPXS10002_00-VTSTORELIVEAREA0.pkg


==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
----


*VF - '''Confirmed''' ---> '''unknown name''', used as a valid category filter in the XML configuration file for [[XMB-Game | XMB game column]] in path: dev_flash/vsh/resource/explore/xmb/category_game.xml in key="gameDir"
**key="gameDir" is an XMB item that allows to order the contents by "rating" or "timeCreated" the command used contains a list of categories that are excluded using the [[XMB_modding#Operators| operator "An" = An not equal]] (VF is at the end of the list excluded with '''An+Game:Game.category VF''')


*XI - '''Confirmed''' ---> '''System File for Extra Content Item''' , related to another disc structure/subfolders: http://www.ps3devwiki.com/wiki/PS3_DISC.SFB  ?


When a patch for a game (e.g: a disc game) is installed, the game boots from the "patch installation" folder, XMB loads from this folder his [[Content Information Files]], a new [[PARAM.SFO]], and a new EBOOT.BIN
*Folders EX_GAME & EX_VIDEO belongs to PS3_CONTENT disc substructure (same than THEMEDIR & VIDEODIR) :)
**StorageMedia:Common.fileName EX_GAME <--- Mounted by XMB in game column using key="seg_add_content_device" see: http://www.ps3devwiki.com/wiki/XMB-Game
**StorageMedia:Common.fileName EX_VIDEO <--- Mounted by XMB in video column using key="seg_add_content_device" see: http://www.ps3devwiki.com/wiki/XMB-Video


After one of this installations PS3 loads both PARAM.SFO's (the "original.sfo" one from disc + the new from the "patch.sfo" folder)... some values are taken from the "original.sfo" (e.g: BOOTABLE, RESOLUTION, SOUND_FORMAT... are not present in patches)... and others are taken from the "patch.sfo" (e.g: APP_VER increases in every patch)
* [[Move_Motion_Controller#Move.Me]] : regular category and title id?


Patches uses a system of "overwrite flag/param_key" that makes the PS3 ignore the "original.sfo" value and use the value from the "patch.sfo"... this can be used in combination with the "standard flags" (one flag indicates the value must be taken from the patch... and the other flag enables the feature)
===Subfolders structures and others Parameters===


'''PS3_GAME/'''


*C00, HTMLDIR, <span style="text-decoration: line-through;">DRMDIR</span>, INSDIR, <span style="text-decoration: line-through;">LICDIR</span>, PKGDIR, SHOPDIR, TRPDIR, USRDIR, Lxx


----
*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
***Is because the first and second byte of ATTRIBUTE for patches (16 flags) was used before ? (so are reserved and never was used, or used but unknown, or used but only internally) ?
***Is because the overwrite flags for patches needed to be placed in the third byte because every byte is managed by different process ? (third byte is marked in frontpage as "flags for game & software features").
***Is posible every byte is managed in a different level ? (e.g: one for vsh, other for lv2, etc...)
***Other theories ?... This is a good hint of how ATTRIBUTE flags are managed, wich part of the firmware is responsible of managing them, and if are managed as separated bytes
**When a game is booted from a disc and there is a game patch installed for this game in internall hdd, there are 2 SFO's readed (one in the disc, and another in internall hdd)... some areas from the SFO in the disc are ignored and taken from the SFO in internall hdd
***Who is the responsible of loading parts sellectivelly from each of them ?, is just by the presence of the same param_key's in the internall SFO ?. In this case the third byte of ATRIBUTE should be an exception of this rule because the ATTRIBUTE flags in the patch (overwrite flags) uses the third byte, but ATTRIBUTE flags in the disc in third byte are readed too because contains features that are not overwrited (as game purchase enabled, install packages, etc...)
***XMB database stores a copy of all PARAM.SFO's. Is posible the 2 files (SFO from disc, and SFO from his patch) are merged before indexed in database ? (or some of his values, more specifically the resulting of applying the overwrite flags from the patch)
**The process of adding or removing a flag from a previous value of ATTRIBUTE is simply a math operation with numberic values, some of the flags for patches overwrites ATTRIBUTE, but there is one that allows to overwrite Remote Play (an ATTRIBUTE flag) and RESOLUTION, SOUND_FORMAT (param_key's)... The overwriting of param_key's is a different process (not a math calculation) where the new value replaces the old value. What all them has in common is all overwrited data types (math calculations with ATTRIBUTE values or overwriting of RESOLUTION and SOUND_FORMAT) are "integer 4 bytes"
**Why overwrite Remote Play (an ATTRIBUTE flag) and RESOLUTION, SOUND_FORMAT (param_key's) are grouped together ?... This is a bit weird


==CONTENT_ID, NP_COMMUNICATION_ID, NPCOMMID (Network and purchase features)==
===='''Lxx: License Area'''====
Needs to be explained in another page
 
*Path:


==ACCOUNT_ID, PARAMS, PARAMS2, SAVEDATA_FILE_LIST, SAVEDATA_PARAMS, PADDING (security, integer special data type)==
/dev_bdvd/PS3_GAME/PARAM.SFO
/setting/system/licenseArea
/dev_bdvd/PS3_GAME/L00/PARAM.SFO
/dev_bdvd/PS3_GAME/L01/PARAM.SFO
/dev_bdvd/PS3_GAME/L02/PARAM.SFO
/dev_bdvd/PS3_GAME/L03/PARAM.SFO
/dev_bdvd/PS3_GAME/L04/PARAM.SFO
/dev_bdvd/PS3_GAME/L05/PARAM.SFO


All this parameters uses the data type = '''0400''' (in the SFO) named "utf8 Special Mode" in the wiki page (not used in SFX so we dont have an accurate name, consequently this "special mode" is an invented name)... seems to have the particularity of returning a "right" or "wrong" when comparing the value, so it can be said that the difference between the simple "utf8" and "utf8 Special Mode" is only from the point of view of how the system manipulate this data. There is no real explain yet why this data is marked differently and who is the responsible of processing it.
*Or:
/dev_bdvd/PS3_GAME/C00/L00/PARAM.SFO
/dev_bdvd/PS3_GAME/C00/L01/PARAM.SFO
/dev_bdvd/PS3_GAME/C00/L02/PARAM.SFO
/dev_bdvd/PS3_GAME/C00/L03/PARAM.SFO
/dev_bdvd/PS3_GAME/C00/L04/PARAM.SFO
/dev_bdvd/PS3_GAME/C00/L05/PARAM.SFO


*If the "scale" used for the second byte follows the proportion of 2^X (e.g. 1, 2, 4, 8, 16, 32, etc...) then we are missing a "04 01" valid data type in the list
*From HDD0:


===PARAMS===
/dev_hdd0/game/ABCD12345/Lxx/PARAM.SFO
This table is a collection of examples of some "rare" savedatas, probably will be needed to erase this section (replaced by a resume in front page) when all areas are identifyed, but by now is usefull to have an overview of how this process works and to find good candidates for tests, feel free to add any other examples you consider interesting ;)


The examples in the table are considered rare because most of the other games uses the values: 1,5,1,2,2 (2 last pointers pointing to the same counter slot 2 at 0x0C) or 1,5,1,3,3 (2 last pointers pointing to the same counter slot 3 at 0x10), so dont add this kind of games to the table because are pointless (by now the only identifyed pointers are the values at ffset 0x03 and 0x04 and the interesting examples are when this pointers are different, or when they changes his values to different numbers like 2,3 or 3,2, or any other combination of 2 different numbers, this means the SFO has several counters enabled), also the table doesnt includes the "user/console" areas that starts at offset 0x18 because are identifyed and explained in front page
*Speculation : Path used to restrict the content to a specific License Area (Parental_Level_x was created around FW 2.00? and them Region_Deny later (around FW 3.30 or less) making theses Lxx path archaic ( and so if have been used, only in early titles).


The table differences 2 types of savedata, one for "profile" and other for standard "savedata", the reason is because are treated different by the system, after the first analysis it looks the profile support more features, it can evolve by changing his type, and it can store the counters from the other savedatas when SFO's are merged (this happens after completing the game)
Title_xx was early implemented but it is not up to the region.


*Notes
You can quickly check your region area with this sub folder (other than checking debug menu, parental level, original Time Zone settting, ...) by using this sub folder and inserting content file informations such ICON0 etc... (will load directly on XMB instead of regular path) and param.sfo (will load if not shadow copy).
**Iris manager (and all his forks) has an hexeditor inside his archive manager, just navigate to the SFO press "X" and scroll down to offset 0x558 (where PARAMS area usually starts), is easy to recognize because always starts with this 1,5,1,2,2 bytes, at the next line are the 4 counters, 4 bytes length each
**To know exactly wich files has been updated inside the savedata folder is needed to look at his timestamps, iris manager doesnt displays timestamps, but you can use the FTP feature to see then from a FTP client running in a PC connected to the PS3, be sure the FTP client doesnt fool you with the timestamps, usually after a disconection/conection the old timestamps are displayed, is needed to "refresh" the files (with F5 in filezilla) or close/open the FTP client again to force it to refresh timestamps
**The system considers the savedata has been updated when the timestamp of the SFO is updated (and consequently the PFD has been updated too). But sometimes the PFD is the only file updated in the folder, in this cases the system doesnt considers the savedata has been updated. The number of times the SFO has been updated is stored in one of the counters inside PARAMS, most games loads and updates the SFO when the game boots (to be able to update his timestamp in XMB and display the last time the game was booted)


{| class="wikitable"
{| class="wikitable"
|+ reorder rows when completed in numberical order based in folder names
! Folder name !! License Area !! Regions
|-
|-
! rowspan=2 | Game Title !! rowspan=2 | Savedata type !! colspan=12 | PARAMS areas (by offset) !! rowspan=2 | Notes
| L01 ||SCEA || US, Canada (North America), Mexico, Central America, South America
|-
|-
! 0x0 !! 0x01 !! 0x02 !! 0x03 !! 0x04 !! 0x05 !! 0x06 !! 0x07 !! 0x08 !! 0x0C !! 0x10 !! 0x14
| ??? || SCH || China
|-
|-
| untold legends || || 1 || 1 || 1 || 2 || 2 || 0 || 0 || 0 || 00000000 || 40000000 || 00000000 || 01000000 || old game, after completing the game
| L02 || SCEE || Europe/Middle East/Africa, U.K./Ireland, Australia/New Zealand (Oceania), Russia, Ukraine, India, Central Asia
|-
|-
| venetica || profile || 1 || 1 || 1 || 2 || 3 || 0 || 0 || 0 || 00000000 || 01000000 || 02000000 || 01000000 || old game, after completing the game
| L03 || SCEH || Singapore/Malaysia (Southeast Asia)?, Taiwan (L03), Hong Kong (L03)
|-
|-
| yakuza 4 || SYSTEM || 1 || 3 || 1 || 2 || 2 || 0 || 0 || 0 || 00000000 || E1010000 || 00000000 || 01000000 ||
| L00 || SCEJ || Japan
|-
| yakuza 4 || CLEAR || 1 || 1 || 1 || 2 || 2 || 0 || 0 || 0 || 00000000 || 01000000 || 00000000 || 01000000 || after completing the game, needed to start a game+
|-
| need for speed most wanted ||  || 1 || 5 || 1 || 2 || 3 || 0 || 0 || 0 || 00000000 || 7A010000 || 64000000 || 01000000 ||
|-
| motogp 13 || || 1 || 5 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 16000000 || 01000000 ||  
|-
|-
| tintin || || 1 || 5 || 2 || 2 || 2 || 0 || 0 || 0 || 00000000 || AC010000 || 00000000 || 01000000 ||
| L04 || SCEK || Korea (South Korea)
|-
|-
| prince of persia sands of time || || 1 || 5 || 1 || 2 || 2 || 0 || 0 || 0 || 00000000 || FF000000 || 00000000 || 01000000 ||
|-
| prince of persia sands of time || || 1 || 5 || 2 || 2 || 2 || 0 || 0 || 0 || 00000000 || E6000000 || 00000000 || 01000000 ||
|-
| the last of us || profile || 1 || 7 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 01000000 || 01000000 || new profile savedata, no previous savedatas
|-
| the last of us || profile || 1 || 8 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 02000000 || 01000000 || boot game, quit game (see examples below)
|-
| the last of us || profile || 1 || 7 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 97000000 || 01000000 || after completing the game
|-
| the last of us || save || 1 || 2 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 21000000 || 01000000 || after completing the game
|-
| tomb raider || profile || 1 || 5 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 01000000 || 01000000 || new profile savedata, no previous savedatas
|-
| tomb raider || save || 1 || 5 || 1 || 3 || 3 || 0 || 0 || 0 || 00000000 || 00000000 || 01000000 || 01000000 || new game savedata, no previous savedatas
|-
| tomb raider || profile || 1 || 5 || 1 || 2 || 3 || 0 || 0 || 0 || 00000000 || 91000000 || 14000000 || 01000000 || after completing the game
|}
|}


*Tests examples
You can compare the result with this table:
**The last of us ---> http://pastebin.com/raw.php?i=SAiDzjLN (overall save behaviour with the profile, identifying update counter)
[[Regions |Regions ]] and report which Lxx is loaded on your Region and if this speculation is wrong.
***the game loads and updates the profile in every boot (by only updating the SFO timestamp and consequently the PFD), and changes the value at offset 0x01 to 8
You can load different Lxx folder by using [[QA_Flagging#Debug_Menu_settings_not_in_Retail.2FCEX_QA | Debug Menu Setting Region]] but be alert about your TV setting display video (NTSC/PAL).
***when the user changes some option or forces the save the value at offset 0x01 is changed to 7
***the profile is updated 1 time for every submenu inside "options" (there are 5 submenues under options)
***every time the SFO is updated, the counter at 0x10  increases 1 unit
**tomb raider ------> http://pastebin.com/raw.php?i=S13yrq9R (overall save behaviour with profile and save, update counter, timestamps, failed attempt to increase the game completion counter at offset 0x564)
***every time the game boots, only the PFD is updated (no other file is updated)
***When the savedata is updated all the files inside the folder are updated (included ICON0.PNG timestamp)
***the profile is updated 1 time for every submenu under options, and another time when exiting options (3 submenues + 1 when exiting options for a total of 4 updates)
***the profile is updated 1 time when exiting extras
***every time the SFO is updated, the counter at 0x10  increases 1 unit
***when the game is completed a new counter is added to the profile savedata, and the pointer at offset 0x03 changes to a new counter slot (from slot 3 to slot 2), the new value stored in counter slot 2 is partially unknown but seems to be another counter taken from the SFO of the save used to finish the game


==SAVEDATA_LIST_PARAM==
Here is a collection of folders (from L00 to L10) with icons displaying the different numbers, this way is easy to know wich one is used by XMB, to make the test just copy the folders next to USRDIR folder inside the installation folder of any app: '''region subfolders tests.zip (430.22KB)''' http://www.sendspace.com/file/ikvult
'''Example of SAVEDATA_LIST_PARAM containing the "folder size in sectors" in the gamesaves generated by the game "The Orange Box: BLES00153, BLES00171, BLES00172, BLUS30055"'''
{{Boxframe1|content='''Game Selector Boot Process'''
When the disc boots, the EBOOT.BIN loads APP_CHOOSER.SELF, is a "game selector" and contains 5 games: half life 2, half life 2ep1, half life 2ep2, Portal, and Team fortress 2


Each of this games has his own .SELF and his own SAVECONTENTPS3 folder (each game uses different [[Content_Information_Files#Saved_Data_Utility_.28PS3.29 | Content Information Files]] when generating his savedata). There is another savedata folder generated/loaded by the selector that is common. In some games (e.g: portal 1) there are several savedata folders to store: the "game settings", "autosave", and "manual save"
See also: "license area" restrictions used in combination with "parental level" http://www.ps3devwiki.com/wiki/Talk:PARAM.SFO#Lxx:_License_Area


All the PARAM.SFO's generated in this savedata folders contains SAVEDATA_LIST_PARAM with a '''param_len''' of 7 bytes, and his values are strings of 6 numbers + a zero (NULL terminated)
===='''Parameters'''====
}}


The value stored by this game in SAVEDATA_LIST_PARAM is the "size of the folder on disk". This size is dependant of the filesystem (512 bytes cluster size in UFS2), and how many clusters are taken as the "minimun chunk" (that seems to be 2 clusters)
*GAMEDATA_ID : length max should be 32 (0x20)?


Because the writing process standards (and from the point of view of available clusters for the next writing operation) when a single byte is used in a cluster, this whole cluster is considered "not available for next writing process of a new file". This means e.g: that a file with a size 513 bytes uses 2 complete clusters (512 bytes in the first cluster and 1 byte in the second cluster, both clusters are reserved for this file)
*FOLDER_NAME and FOLDERNAME_00 : ?


To calculate the number of clusters used by a folder... is needed to calculate the number of clusters used by each file inside the folder, this includes the files that uses a number of clusters that is not even and needs to be "rounded-up". e.g: a file with size 1 byte (that is supposed to fit in 1 cluster) uses 2 clusters because the number "1" is not even. In few words, the number of clusters used by a file needs to be "rounded-up to next even number"
===Special characters availables in text strings===
This simbols can be used in TITLE, SUBTITLE, DETAIL, etc...


*This save game is a good example because always contains the same values in SAVEDATA_LIST_PARAM (the second one from euro region): BLES00153-PORCONF-0 [[http://www.gamefaqs.com/ps3/934385-the-orange-box/saves Link 1]] [[http://db.gamefaqs.com/console/ps3/save/the_orange_box_eu.zip Link 2]]
{| class="wikitable sortable"
{| class="wikitable"
|-
|-
! File name !! real file size (in bytes) !! theorical disk size (in clusters) !! cluster round-up to even number !! real disk size (in bytes)
! hexadecimal !! simbol !! description
|-
|-
| ICON0.PNG || 12.461 || 12461/512=24,3... = 25 || 25+1= 26 || 26*512= 13.312
| E2 98 85 || ☆ || same star used in "install packages" icon
|-
|-
| PARAM.PFD || 32.768 || 32768/512= 64 || || 64*512= 32.768
|}
 
===DATA types===
 
{| class="wikitable"
|-
|-
| PARAM.SFO || 2.736 || 2736/512=5,3... = 6 || || 6*512= 3.072
! Data_Type !! Description !! Used in
|-
|-
| PIC1.PNG || 89.268 || 89268/512=174,3... = 175 || 175+1= 176 || 176*512= 90.112
| 04 00 || style="background-color:#00DDDD;" | utf-8 Special Mode || Data generated by the system: '''Game Saves''' (ACCOUNT_ID, PARAMS, PARAMS2, SAVEDATA_FILE_LIST, SAVEDATA_PARAMS)... and '''Trophies''' (PADDING)
|-
| POR-0.CFG || 893 || 893/512=1,7... = 2 || || 2*512= 1.024
|-
| POR-0.CHK || 16 || 16/512=0,03... = 1 || 1+1= 2 || 2*512= 1.024
|-
!! colspan="5" | Folder contents total
|-
| || 138.142 || 273 clusters || 276 clusters || '''141312''' (SAVEDATA_LIST_PARAM)
|-
|-
|}
|}
*The process is:
**1.- Divide by the cluster size
**2.- Round-up cluster number (if needed)
**3.- Multiply by the same cluster size (to know the amount of bytes reserved for this clusters)


This can be simplifyed by using 1024 (2 clusters)... because this way there is no need of step 2 (the "round-up")... but i have no idea if naming this "chunk" of 2 clusters a "page"... or why UFS2 filesystem takes them 2 by 2... i prefer to left this example as is, feel free to correct me
The '''Data_Type''' = '''0400''' marked as "utf-8 Special Mode" has the particularity of return a "right" or "wrong" when comparing the string with a reference value, so it can be said that the difference between the simple "utf-8" and "utf-8 Special Mode" is only from the point of view of how the system manipulate this data. For more info read the section [[#ACCOUNT_ID|ACCOUNT_ID]].


Also, there is a simple "trick" that can be used to display the files divided in clusters of the size you want (maybe are others but this is the faster way i found). By formatting a usb pendrive in advanced mode, using the cluster size your need, then moving the folder there (by using FAT32 with 1024 bytes cluster the value reported by your operative system is the same one stored inside SAVE_DATA_LIST)
If the "scale" used for the second byte follows the proportion of 2^X (e.g. 1, 2, 4, 8, 16, 32, etc...) then we are missing a "04 01" valid data type in the list


*PARAM.PFD relationship ?
====Cryptography in "user files" (game saves & trophies)====
ACCOUNT_ID, PADDING, PARAMS, PARAMS2, SAVEDATA_FILE_LIST, SAVEDATA_PARAMS


=Other parameters not used in PS3 (only used in other sony consoles)=
====PARAM.PFD relationship====
The only purpose of this table is to keep a record of them to not confuse with the ones used in PS3


{| class="wikitable" style="font-size:x-small"
===Firmware 3.56+ new features and contents===
|-
 
! rowspan=2 | Parameter !! colspan=3 | Console !! rowspan=2 | Notes
*PSVita Remote play: Specific remote play. See main page (similar than PSP remote play).
|-
 
! PSP !! [http://www.psdevwiki.com/vita/index.php?title=Talk:System_File_Object_%28SFO%29_%28PSF%29 PSV] !! [http://www.psdevwiki.com/ps4/Param.sfo PS4]
*PSVita Cross play : Specific game play with PS VITA used as controller.
|-
PS3 FW min 4.20 with PS VITA FW min 1.80:
| DISC_ID || {{Yes}} || || ||
 
|-
PS3_GAME/CROSSDIR/DATA000.SIG (Encrypted Certificate, magic "CER") speculation: see [[SIG_File_Format#CERTIFICATE|Certificate Signature Format]]
| DISC_NUMBER || {{Yes}} || || {{Yes}} ||
PS3_GAME/CROSSDIR/DATA000.PKG (PS Vita PKG, DRM type: "free")
|-
PS3_GAME/CROSSDIR/DATA000.PNG
| DISC_TOTAL || {{Yes}} || || {{Yes}} ||
 
|-
*PSVitA Cross buy : Get PS3 version to have PSViTA version for free, and reverse case.
| DISC_VERSION || {{Yes}} || || ||
 
|-
See above for title id and [[PS3_DISC.SFB |PS3_DISC.SFB]] (New Flag "S" related is speculation)
| DRIVER_PATH || {{Yes}} || || ||
 
|-
*PlayStation Mobile (implemented around 4.21 firmware)
| GAMEDATA_ID || {{Yes}} || || || Used in some PSP UMD games, found in [[game_ext_plugin]].sprx
'''explore_plugin_full\Text\English.xml''' (inside explore_plugin_full.rco)
|-
| HRKGMP_VER || {{Yes}} || || ||
<Text name="msg_applications_psm">Applications (PlayStation®Mobile)</Text>
|-
 
| REGION || {{Yes}} || || ||
PS3 internal hdd path: '''dev_hdd0/home/0000000x/psp2_backup/psm'''. Displayed in: XMB/Game/'''PS VITA System Application Utility'''. (Generated folder and displayed :e.g. with PS vita pkg)
|-
 
| USE_USB || {{Yes}} || || ||
'''psp2_backup''' subfolders: ps1, psm, psp, psp2, system (psp2 is the codename of PSvita, this contents are "shared/exported/imported" between PS3 and PSvita)
|-{{cellcolors|red}}
 
| ACCOUNT_ID ||  || {{Yes}} || || Not the same ACCOUNT_ID than PS3... this one for vita has  (fmt:utf8-S, len:0x8, max_len:0x8)
Note: "psp" folder display "psp/other", "system" folder don t seems to expect .pkg.  
|-
Note2: Trophy PS3-PS vita for possible similar user path.
| ATTRIBUTE2 ||  || {{Yes}} || ||
 
|-
 
| ATTRIBUTE_MINOR ||  || {{Yes}} || ||
*keyboard/mouse support (in one of the patches of game "DUST 514")
|-
http://gamescatalyst.com/2012/08/ps3-users-to-make-contact-with-their-pc-neighbours-as-dust-514-migrates-to-eve-onlines-servers/
| GC_RO_SIZE || || {{Yes}} || || GameCache ReadOnly Size ?
previous old game UNreal III has keyboard support, but not from SFO.
|-
| GC_RW_SIZE || || {{Yes}} || || GameCache ReadWrite Size ?
|-
| INSTALL_DIR_ADDCONT ||  || {{Yes}} || || Shared Additional Content, fmt:utf-8, max_len:12
|-
| INSTALL_DIR_SAVEDATA ||  || {{Yes}} || || Shared Save Data, fmt:utf-8, max_len:12
|-
| PARENT_DIRECTORY ||  || {{Yes}} || || used in PSvita savedata (fmt:utf8, len:0xB, max_len:0x40)
|-
| PSP2_DISP_VER ||  || {{Yes}} || || utf-8, max_len:8, example: "00.000"
|-
| PSP2_SYSTEM_VER ||  || {{Yes}} || || int32
|-
| PUBTOOLINFO ||  || {{Yes}} || {{Yes}} ||
|-
| SAVEDATA_MAX_SIZE || || {{Yes}} || || int32
|-
| SAVEDATA_VER ||  || {{Yes}} || || used in PSvita savedata (fmt:utf8, len:0x6, max_len:0x8)
|-
| STITLE ||  || {{Yes}} || || App Short Title, utf-8, len:52
|-
| STITLE_xx ||  || {{Yes}} || ||
|-
| SUPPORT_URI ||  || {{Yes}} || ||
|-
| APP_TYPE ||  ||  || {{Yes}} ||
|-
| CONTENT_VER ||  ||  || {{Yes}} ||
|-
| DISP_LOCATION_x ||  ||  || {{Yes}} ||
|-
| DOWNLOAD_DATA_SIZE ||  ||  || {{Yes}} ||
|-
| FORMAT ||  ||  || {{Yes}} ||
|-
| INSTALL_DIR_SAVEDATA ||  ||  || {{Yes}} ||
|-
| IRO_TAG ||  ||  || {{Yes}} ||
|-
| PROVIDER ||  ||  || {{Yes}} ||
|-
| PROVIDER_xx ||  ||  || {{Yes}} ||
|-
| PUBTOOL_VERSION ||  ||  || {{Yes}} ||
|-
| REMOTE_PLAY_KEY_ASSIGN ||  ||  || {{Yes}} ||
|-
| SERVICE_ID_ADDCONT_ADD_x ||  ||  || {{Yes}} ||
|-
| SYSTEM_ROOT_VER ||  ||  || {{Yes}} ||
|-
| SYSTEM_VER ||  ||  || {{Yes}} ||
|-
| USER_DEFINED_PARAM_x ||  ||  || {{Yes}} ||
|-
| SUB_TITLE_ID || || || ||
|-
| CONTENT_URL ||  || || || URL of content (not parameter but related to link.xml?)
|-
| _PARAM.SFO || ? || || || found in [[game_ext_plugin]].sprx (anti exploit/bug prevention ?)
|-
| __PARAM.SFO || ? || || || found in [[game_ext_plugin]].sprx (anti exploit/bug prevention ?)
|-
| /PARAM.SFO || ? || || || found in [[game_ext_plugin]].sprx (anti exploit/bug prevention ?)
|-
| FOLDER_NAME || || || || found in [[game_ext_plugin]].sprx
|-
| FOLDER_NAME_00 || || || || found in [[game_ext_plugin]].sprx
|-
|}


=DISC contents temporal installations (in dev_hdd0/tmp)=
'''/dev_hdd0/tmp/disc_install/'''


=Reserved Folder Names used in HDD or disc contents=
*new youtube app
youtube remote control from a paired smartphone -- http://www.ps3news.com/playstation-3-psn-news/sony-announces-the-new-youtube-app-hits-playstation-3-today/


==L00 up to L05 (License Area subfolders with restricted .SFO's)==
*7.1 virtual surround (in SOUND_FORMAT) sound mode has been announced officially, it will be implemented in the next firmware (aparently version 4.20). This sound mode will need one (or two) new flags for being activated in games


*From dev_bdvd: ?
===Emulators specific parameters/flags===
/dev_bdvd/PS3_GAME/L00/PARAM.SFO (up to L05)
ANALOG_MODE & specific values for RESOLUTION
/dev_bdvd/PS3_GAME/C00/L00/PARAM.SFO (up to L05)


*From dev_hdd0:
====RESOLUTION====
  /dev_hdd0/game/ABCD12345/Lxx/PARAM.SFO
Data_Type: uint32_t
  /dev_hdd0/game/ABCD12345/C01/Lxx/PARAM.SFO ---only working if region setting is L03 country (only other tested: L00 not working)
Data_Size_Total: 4 bytes
  Data_Size_Used: 4 bytes
  Used by: HDD Game, PS1 Classics Game, Minis Game, PSP Remasters Game


Speculation: Path used to restrict/use different License in the same region (L03?).
TV video modes supported by the content.


You can quickly check your region area with this sub folder (and inserting content file informations such ICON0). L** path can avoid error some code related to param.sfo/disc.sfo.
When there are several flags activated the PS3 will use the one with higher quality supported by the TV.


{| class="wikitable"
{| class="wikitable"
! Folder name !! License Area !! Regions
|-
|-
| L00 || SCEJ || Japan
!  Little Endian !! Big Endian !! Decimal !! Binary (Flags) !! Description
|-
| 01 00 00 00 || 00 00 00 01 || 1 || 00000000 00000000 00000000 00000001 || 480  (4:3)
|-
| 02 00 00 00 || 00 00 00 02 || 2 || 00000000 00000000 00000000 00000010 || 576  (4:3)
|-
| 04 00 00 00 || 00 00 00 04 || 4 || 00000000 00000000 00000000 00000100 || 720  (16:9)
|-
|-
| L01 || SCEA || US (L01), Canada (North America), Mexico (L01), Central America, South America
| 08 00 00 00 || 00 00 00 08 || 8 || 00000000 00000000 00000000 00001000 || 1080 (16:9)
|-
|-
| L02 || SCEE || Europe/Middle East/Africa, U.K./Ireland, Australia/New Zealand (Oceania: L02), Russia, Ukraine, India, Central Asia ,
| 10 00 00 00 || 00 00 00 10 || 16 || 00000000 00000000 00000000 00010000 || 480  (16:9)
|-
|-
| L03 || SCEH || Singapore/Malaysia (Southeast Asia)?, Taiwan (L03), Hong Kong (L03)
| 20 00 00 00 || 00 00 00 20 || 32 || 00000000 00000000 00000000 00100000 || 576  (16:9)
|-
|-
| L04 || SCEK || Korea (South Korea)
| colspan="5" style="text-align:center; background-color:#DDDDDD;" | Examples
|-
|-
| L05 || SCH  || China
| 3F 00 00 00 || 00 00 00 3F || 63 || 00000000 00000000 00000000 00111111 || All video modes supported
|-
|-
|}
|}


(Unlinked Note: Button Behavior: for L05 is also O , Oceania is X. Path Pioneer with significant idea about it: Deroad)
*Note the resolution for originall PS1 disc games can vary (See: [[Emulation#Resolution|Emulation Resolution]]). The RESOLUTION flags used in PARAM.SFO's of "PS1 Classics Game" from PSN seems to be specific and not fixed sizes (e.g: 01 00 00 00). This will need another table if more are found
 
===Patches===
APP_VER, TARGET_APP_VER, PS3_SYSTEM_VER, VERSION
lot of things to add here, maybe needs another page, but im not the best one to document them


You can load different Lxx folder by using [[QA_Flagging#Debug_Menu_settings_not_in_Retail.2FCEX_QA | Debug Menu Setting Region]] but be alert about your TV setting display video (NTSC/PAL).
==== PS3_SYSTEM_VER ====


Here is a collection of folders (from L00 to L10) with icons displaying the different numbers, this way is easy to know which one is used by XMB, to make the test just copy the folders next to USRDIR folder inside the installation folder of any app: '''region subfolders tests.zip (430.22KB)''' http://www.sendspace.com/file/ikvult
This is the flag for what's the minimum firmware a game will run on. It is 0x8 bytes and is only found it Gamedata SFO files, not gamesaves (most of them atleast).  


See also: "license area" restrictions used in combination with "parental level" http://www.ps3devwiki.com/wiki/Talk:PARAM.SFO#Lxx:_License_Area
[[File:PS3_SYSTEM_VER.png]]


==EX_GAME and EX_VIDEO==
This can be changed to run on other firmwares.


*Theory 1:
===Purchase content===
**Belongs to PS3_CONTENT disc substructure (same than THEMEDIR & VIDEODIR)
CONTENT_ID, NP_COMMUNICATION_ID, NPCOMMID
**StorageMedia:Common.fileName EX_GAME <--- Mounted by XMB in game column using key="seg_add_content_device" see: http://www.ps3devwiki.com/wiki/XMB-Game
**StorageMedia:Common.fileName EX_VIDEO <--- Mounted by XMB in video column using key="seg_add_content_device" see: http://www.ps3devwiki.com/wiki/XMB-Video


*Theory 2:
**EX_GAME & EX_VIDEO requires SFO Category 'XR' and are emerged into PS3_EXTRA! (EX_GAME/EX_VIDEO are actually leftovers?)


==Others==
==To Do==
There are lot of "yes" in the parameters table that in fact are optional "opt". The "yes" means the value is mandatory, so the table is not fully correct, it needs to add a lot more "opt" in the paces of the "yes"


-GE
Also... this table represents the values needed for each content ordered by CATEGORY, but there are different contents that shares the same CATEGORY (like the different types of patches, DLC's, and game installations... alll them uses "'''GD'''"
PS3 DVD / PS2 CD
/dev_bdvd/NORMAL
/dev_bdvd/HYBRID


-GP
The "parameter table" cant contain all this different variations, by now i dont see a way to do it
/dev_bdvd/PHOTODIR
/dev_bdvd/PS3_CONTENT/PHOTODIR
/dev_bdvd/PS3_CONTENT/PHOTODIR/PARAM.SFO


-GM
----
/dev_bdvd/MUSICDIR
/dev_bdvd/PS3_CONTENT/MUSICDIR
/dev_bdvd/PS3_CONTENT/MUSICDIR/PARAM.SFO


-GV
==Suggestions==
/dev_bdvd/VIDEODIR
/dev_bdvd/PS3_CONTENT/VIDEODIR
/dev_bdvd/PS3_CONTENT/VIDEODIR/PARAM.SFO


-GT
* Link each ID to a subpage, so they can be centrally managed (some are also listed here : http://www.ps3devwiki.com/wiki/Productcode )
/dev_bdvd/THEMEDIR
/dev_bdvd/PS3_CONTENT/THEMEDIR
/dev_bdvd/PS3_CONTENT/THEMEDIR/PARAM.SFO


=Todo and Suggestions=
* Sure NP Communication refers to '''Network Platform''' and not '''Playstation Network'''(sdk) ?
*'''Parameters requirements table''' has lot of "yes" that should be "opt" (optional). The "yes" means the value is mandatory, so the table is not fully correct.Also... this table represents the values needed for each content ordered by CATEGORY, but there are different contents that shares the same CATEGORY (like the different types of patches, DLC's, and game installations... alll them uses "'''GD'''". The "parameter table" cant contain all this different variations, by now i dont see a way to do it--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 12:25, 29 January 2014 (EST)
** The name comes from: '''NPMT''' (Network Platform Management Tools) --[[User:Sandungas|Sandungas]] 06:06, 18 January 2013 (MSK)
*The internal structure example for SFO needs to be replaced by a new one with at least 2 parameters, this will make more obvious how are meassured the relative offsets displacements
*Is needed an explain of how the file is loaded in stages by the system, how is indexed, and the method to access single areas to update single values, the rebuilding process, etc... this is complex and i ignore (but i imagine) how is made by the PS3, but the source codes i saw that manages SFO files uses different methods and styles (and probably some others i ignore), by now im not skilled enought to discuss this in the page but an open talk about all this could be interesting --[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 23:41, 15 February 2014 (EST)
*'''Overall page cleanup''' of obsolete or wrong info, grammar corrections, etc...
*'''Link each ID to a subpage''', so they can be centrally managed (some are also listed here: [[IDs_%2B_labels | ID's and labels]]
**The affected sections in front page are: [[PARAM.SFO#CONTENT_ID|CONTENT_ID]], [[PARAM.SFO#NP_COMMUNICATION_ID|NP_COMMUNICATION_ID]], [[PARAM.SFO#NPCOMMID|NPCOMMID]], and [[PARAM.SFO#TITLE_ID|TITLE_ID]], explaining them in the .SFO page (as i did initially) doesnt looks the best solution, but is needed at least a short description of each, now there are specific pages for them (without much descriptions) and the decission of separating all the IDs in pages makes hard to have a overall view of them... the best solution i see is to use the [[IDs_%2B_labels | ID's and labels]] converted to a template an use it repeatedly in SFO page, but the names are not the same used in SFO, also this doesnt solves the short description needed in SFO page (that should be duplicated, and expanded in his specific pages)--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 12:25, 29 January 2014 (EST)
Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://www.psdevwiki.com/ps3/Talk:PARAM.SFO"