PS2 Unified MemoryCard System/Setup/Structure (UMCS)

[TnA]

This is a small sub/side-project of the PS2 Application System project, which strives to unify some of the core elements of the structure of a MemoryCard setup, regardless if it is used for any exploit, or modchips.

The proposed ideas and changes are the following:

• Move apps to their own seperate folders, instead of having them collected in either BOOT or APPS.
• Have PS2BBL as BOOT.ELF and rename LaunchELF to BOOT2.ELF, including adapting links in the Exploit-configs including PS2BBL.
• etc.

This also allows to reset installations to default and update them with BDM Assault drivers.
Then people can simply download the APP PSUs they want.

Download: https://ps2wiki.github.io/sas-apps-archive/psu-categories/umcs.html

 

[R3Z3N]

To make things simple, @pcm720 helped with this for ps2homebrewstore.com

Introducing LoadBOOTer, an app that does 1 thing...chainloads mc?:/BOOT/BOOT.ELF

With this there it saves space as LoadBOOTer is 14KB UNPACKED, packing makes it 28KB ;-) Compared to ~84KB for minimal PS2BBL up to 150KB. Multiply this by however many is needed for cross/region/device and the benefit is clear. Nice for those 8MB memory cards...but also nice because PS2BBL as exploit does not need to be updated with BOOT.ELF PS2BBL when it is updated. Then I went ahead and unified PS2BBL/PSXBBL as well....

What's the downside? Boot takes ~1 second longer. Signed exploit no longer has rescue mode...but alas user isn't supposed to generally delete BOOT.ELF either... It aligns for purpose of the project and to save maintainers time signing or user signing.

For example lets say user downloads our KELFBinder and swaps out XLFs to sign PS2BBL with MX4SIO support..then they also need to change BOOT.ELF. Or the reverse? Users are generally confused...this way there is 1 unsigned app that is easy to swap out for their needs.

Working on more features now to align with things that make sense from OSDMenu now to have the ultimate NOOB+Advanced user setup.