Talk:Eboot.PBP

From PS3 Developer wiki
Revision as of 08:20, 25 May 2012 by Ada L0ve Lace (talk | contribs) (Links and cosmetic)
Jump to navigation Jump to search

Structure folder/files around EBOOT.PBP

Structure folder/files around EBOOT.PBP

Dev_HDD0/game/NPXX.12345/

|-ICON0.PNG (ICON On PS3 XMB)
|
|-PARAM.SFO (this SFO is used by PS3 for classify the game: CATEGORY_For_HDD_contents in normal case, among others things)
|
|-PIC0.PNG
|
|-PIC1.PNG
|
|-PIC2.PNG
|
|-PS3LOGO.DAT 
|
|- USRDIR:
      |
      |-CONTENT (dir): (this folder is sent when using export)
      |     |
      |     |-DOCUMENT.DAT (software manual)
      |     |-EBOOT.PBP (more infos on main page)---the SFO inside will be sent when using export and used by PSP
      |     |-KEYS.BIN (see above)
      |    
      |- SAVEDATA (dir): More infos :about minis/ ps1 classic save  and Memory card adapter
      |     | 
      |     |-ICON0.PNG   (used for PSP save data)
      |     |-PARAM.SFO   (Category: MS, used for PSP save data)
      |     |-SCEVMC0.VMP (memory card save in PSP format for slot 1)
      |     |-SCEVMC1.VMP (memory card save in PSP format for slot 2)
      |     |-CONFIG.BIN  (probably generated by the PSP)
      |
      |-CONFIG (generated after first boot)
      |
      |-ISO.BIN.EDAT: Iso.bin.edat and EDAT files
      |    
      |-MINIS.EDAT (when it s a MINIS game)
      |
      |-load_tmp: (dir only on MINIS after first boot?) 
      |      | 
      |      |-ICON0.PNG
      |      |-PARAM.SFO (Category: MS)
      |      |-PIC1.PNG
      |      |-SECURE.BIN
      |      |-SND0.AT3
      |
      |-save.tmp (empty dir only on MINIS after first save?)


(Might not be complete structure tree)

About NPDRM and PSP

Files related to EBOOT.PBP

DOCUMENT.DAT

Software manual of games (minis and ps1 classic) using a kind of the PS3 PNG viewer.

Same folder as EBOOT.PBP. This folder is copied straight to PSP when using psp export function .

By pressing home button during the game, ICON of software manual will appear near the game icon to display within ".png viewer" of the ps3 (as option when it s PS1 classic)

Can be replaced by other (similar type) DOCUMENT.DAT of other game. It s the SFO (the first, not the SFO inside EBOOT.PBP) to summon this icon and name but it s the EBOOT.PBP giving the path(can be changed)to load it (?)

Not related but more infos about files around the game CONTENT INFORMATION FILES

DOCUMENT.DAT on PS3

(goal: have it on PS3 games/ homebrews, not only to MINIS/PS1 games)

Limitations and workaround

  • From PARAM.SFO:
 for DG game:  The icon of software game can appear on PS3 game
(edited SFO category as MN under DG game with MultiMan, didn t try others backup manager and may not be really important
 but  MultiMan has somes functions related to fix weirdos SFO, but not working from HG) 

Other topic (and to activate folder) can be interesting to have a look even it s not suppose to be directly related: PS3 DISC.SFB

 For HG game (and so for homebrew) : the trick with edited SFO don t work here 
 but there are fews possibles others tricks so should not be the first problem. 
 (XI as memo but probably nothing related)


  • From EBOOT:

To identify from .PBP to incorporate it on .BIN (if possible). Not every eboot.PBP / .SFO has this XMB option (software manual after pressing triangle) on psp XMB but not only used for minis/ps1 classic (PSP game such EG category can have it also).

  • Others:

To identify if it was use on different category as MINIS (MN) /PS1 classic (1P) (on ps3 or psp side) and the difference betwen DOCUMENT.DAT format (MINIS/PS1)

Difference between DOCUMENT.DAT from MINIS and PS1 classic (not only a question of ID type?)

MINIS game and DOCUMENT.DAT from them are the most flexible for tests.

best will be to be able to generate custom eboot.pbp/patched eboot.bin

For the same purpose of having easy custom text or pictures, getting pictures (or PARAM.HIP) in games can provide the solution or the line "comment" (within informations) on music or picture as possible solution (but not great) available in game ( more chars available than sub_title?).

DOCUMENT.DAT on PSP

Can be loaded from psp XMB (if it is from MINIS, not from PS1 classic) without having to boot the game or even a working game.

It's possible to create your own DOCUMENT.DAT such as homebrew manual or walktrough by using PSP DocMaker GUI but not yet used in PS3 homebrew (limited to EBOOT.PBP type?)?

( http://forums.qj.net/psp-development-forum/88463-release-update-psp-docmaker-gui.html / http://www.mediafire.com/?d2mobmwlrlw )

Others: Max 100 pages as display?

DOCUMENT.DAT on PSVITA

On PSVITA, it seems the document.dat is not used anymore (?) and instead, directly as .png format (also when transfer MINIS games ps3 to psvita?) [1]

CONFIG

Infos about PS1 Emulation

Size:60 bytes, string in ASCII: PS1EmuConfigFile, disc_no

"Auto" generated and overwrite at each boot of the game, configure the PS1 emulator for : ?

KEYS.BIN

16 bytes, unique per game (at least).

PS1 game fixed with "NPDRM tool" don t have this file, so it s not clear for me if this file is generated on PS3 side (and the tools can be missing this part and same for MINIS or it s not suppose to be create from free content?) or by the PSP side (and in this case, it s not generated because of the game is considered as free???). So...it s a bit trivial question since there are a lot of solutions for playing PS1 games on PSP but still.

If you have the appropriate file, you can put it into the folder CONTENT to make the game working also in PSP (required at least LCFW)

On PSP scene: for the purpose of making ps1 cd format to eboot.pbp and using the PS1 emulator, it seems the need of this file was patched to an unique game (attached to "PSP.base").

For MINIS and export?

Others: PARAM.SFO in different console

General infos:

By pressing square, PS3 (or PSP) classify the games into different folder according (in general) to the SFO category (HG, 1P, MN mostly for HDD games).

Most of the game on HDD will go on Playstation 3, Playstation 1 or MINIS (there are others but you need one game and less or more specific SFO installed to have it visible)

SFO inside EBOOT.PBP is not what is used by PS3 for folder classification (or may be only one specific case) but the SFO just after the game folder ID.

When on PSP, this is the SFO used for classification (by format) on folder.

On PSP (from FW 6.39) there are 4 visible folder (even with 0 title inside) when you classify by format under square:

PSP™ (most of the game), Playstation® (for ps1 classic game) , PCENGINE and NEOGEO (same as PS3).

By loading on PSP specific SFO (with X2 attribut inside the eboot.pbp, but not from export) it s going to NEOGEO folder when it was supposed to be X4.

(i did fews tests with others category, from export or not, X0 as PCEngine seems fine, X4 NEOGEO from export not)

with Attribut as on PS3 FW 3.55 (not the one inside EBOOT.PBP) on PSP after export on PSP with edited SFO inside EBOOT.PBP
X0 PCENGINE PCENGINE
X1, X3, X4, X5, X6, X7 X4 is NEOGEO, others are - ) PSP™ (X1 don t have name on PS3 but it used on official MINIS SFO (inside EBOOT.PBP)
X2 - NEOGEO

I did fews test also with PSP export, games go to PSP™ (as supposed, SFO sent was X1, when SFO loaded by PS3 were different) but need to make more test (with the 2 SFO edited) to see if the column is really required (or also on PS3 with the 2 SFO edited) Most of theses informations can be resumed in fews words (can explain the different positions folders of X category or at least X2 as NEOGEO for PSP, need to check real examples and if NEOGEO can be officially exported) when it s become more clear.