XMBoot– Create XMB ‘QuickBoot’ Containers

Post Reply
User avatar
sas67
Possible Ally of Robinhood
Possible Ally of Robinhood
Posts: 319
Joined: Wed Feb 18, 2009 2:29 pm
Location: sunny scunny,uk

XMBoot– Create XMB ‘QuickBoot’ Containers

Post by sas67 »

Jurai2 has release an app for the PS3 today that allows you to create the equivalent of a 360 QuickBoot container. In laymans terms it allows you to create a shortcut in your PS3 XMB to your game backup, allowing you to boot directly to it. Image
To quote via ReadMe:

XMBoot is a stripped down backup app which will allow you
to create the equivalent of a 360 QuickBoot container.

This allows you to create a custom entry on your XMB with
the original audio/video from your backup with which you
can either boot DIRECTLY into your game (if supported),
or mount it for launching via XMB.

To load the original XMB video/icon/sound/etc you will need
to copy that content out of the /PS3_GAME/ directory
of your backup and place it in the subdir of this package
prior to compiling.

NOTE: If using the backups original .SFO file you will need
to edit it to report itself as HG (Harddisk Game)
rather than DG (Disc Game).

If not using the original SFO from a backup, be sure to edit
the included SFO to specify your game title.

Also be sure to edit the package.conf and SFO
so that your new package has a unique Title ID.

You will need to set three options in the main.ccp file
prior to compiling your package:

game_path is the path to the backup you wish to use

ex: /dev_usb000/GAMEZ/BLUS-12345/

The app does NOT scan for usb device #’s, so you
will have to hardcode it to the usb slot you use.

direct_boot is the option to attempt launching the EBOOT
without booting back into XMB. Does not work with
all games, but will let you direct boot games on
which it does!

use_hermes is an option to apply the Hermes F1/SFIV/etc
fix at runtime, doesn’t work with every game.

Because these options are stored in main.cpp you MUST
recompile in order to change your container setup.

These options ‘could’ be moved to be stored in the
SFO file instead, which would allow you to simply
edit the SFO instead, bypassing any need for an SDK
setup.
You do not have the required permissions to view the files attached to this post.
flash all phat's and slim drives upto 1175fw.awaiting delivery of cr3lite

Image
Post Reply

Return to “General information”