Note, I'm assuming you already have basic hex editing knowledge

The PBP file structure is quite simple really.  It's just 8 files concatenated (joined) together with a 40 byte header.  The header only contains DWord values.  Here's a breakdown:

Offset	Purpose
0x00	The PBP signature, always is 0x50425000 or the string "<null char>PBP"
0x04	Unknown purpose, possibily the version number.  Currently is always 0x00010000
0x08	Offset of the file PARAM.SFO (this value should always be 0x28)
0x0C	Offset of the file ICON0.PNG
0x10	Offset of the file ICON1.PMF
0x14	Offset of the file PIC0.PNG or UNKNOWN.PNG
0x18	Offset of the file PIC1.PNG
0x1C	Offset of the file SND0.AT3
0x20	Offset of the file DATA.PSP
0x24	Offset of the file DATA.PSAR

  
Then the file PARAM.SFO starts (at 0x28).

So there you go, if, for some reason you want to play around with PBP files.

Files
PARAM.SFO
Basically the information file for the PBP - has title, parental control level etc
ICON0.PNG
The little icon in 32bit colour PNG format.  Max resolution is 144x80.
ICON1.PMF
The little animated icon in PSMF format.
PIC0.PNG
"Information" image in PNG format.  Max resolution is 480x272.
PIC1.PNG
The background image in 32bit colour PNG format.  Max resolution is 480x272.
SND0.AT3
The sound which is played when the icon is highlighted, in ATRAC3 format.
DATA.PSP
More information, except more targetted at the executable portion (contains info such as ELF size)
DATA.PSAR
The bulk of the EBOOT, and the portion which contains the executable code.


PSP Brew is a useful tool for manipulating EBOOTs.

(This post was last modified: 20/01/2007 06:59 AM by ZiNgA BuRgA.)