To quote, roughly translated, on SmallLoader: "TheTool offers a loader used shortcuts in the XMB to rip up a game in the drive without going through virtual BR open the backup manager or manager.
• Edit file game.ini located in the folder PS3_GAME/USRDIR:
• In the path variable, specify the path of your games (Ex: path = / dev_usb000/gamez/BLES12345). You can also delete the line path, smallLoader use the GAME folder which is in USRDIR (just copy your games in that folder).
• In variable autolaunch, enter 1 if you want smallLoader start the game automatically switches to "No AB" and 0 if you want to go back to XMB after the game is installed.
• In the folder PS3_GAME, copy the file ICON0.PNG, PIC1.PNG .....
• Using PS3SFOEdit , edit the file located in PARAM.SFO PS3_GAME
• In "Basic Setting", change the value by that title id you want
• In alt-(default) specify the name of your game
• Click on save and overwrite the old file PARAM.SFO
• Open the file has smallloader.conf using notepad for example.
• In line Product_ID, replace BLES12345 by title id values you have filled in the file PARAM.SFO
• You can save and close this file.
• Now you can generate the PKG file using the command "make_package_npdrm smallloader.conf PS3_GAME /" (without the quotes and the command prompt windows).
• Added fix for the problem of controller.. to enable or disable it, change the line 'fix =' in file game.ini (untested, with no games involved in this problem)
• Added a function to restore the normal functioning of BR player, just run the shortcut by pressing the button .
Note: Sources are also included in the archive.
Finally, from the XMBoot ReadMe file, to quote:
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
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.
Greetings to PS3News. Do not support piracy, purchase the games you love. Winners don't use drugs.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Hello Guys! I also tried to get this beautiful thing working, but still have a few questions.
I use a tool named PKG-Maker, so i don't need the SDK to be installed. But do i need to edit the PARAM.SFO to a higher version than the installed game? Because, if i put my USB-Stick in my PS3, It says that a higher version is already installed, and that there is no need to install this version.
I'm afraid that something goes wrong and i can't play my beloved Black Ops anymore. Does anyone know an answer on my question?? BTW, Nice tool, although i don't understand much of it!
Edit: I installed my fantastic pkg, and my black ops was downgraded to 1.00 again. XMBoot shortcut didn't work.
My question: how do you make a 'forwarder' of the EBOOT.BIN? I didn't get it working with the game.ini (?) or package.conf.
I'm sure it will work if i have the correct EBOOT.BIN! Maybe you can tell me howto, or give me one of Call of Duty: Black Ops BLES01031 version 1.09? I'd be pleased if someone could do that!
The eboot.bin for xmboot/smallloader is the bare code necessary to mount a game. That's why they're termed "containers", because all they do is run syscall35/36 on a hardcoded path (the path to your backup), and then simply exit.
The majority of the work is with the payload, but xmboot/smallLoader/OBM (whichever you're using) and the payload have a role to play. The payload implements the functions necessary for running unsigned code (as well as use dev functions like peek/poke), and it is homebrew developers who use those functions in their apps enabling them to do a number of things.
syscall 35/36 is an entirely separate issue that has no real bearing on the end user other than what payload they should use. For backup manager devs, they either choose between syscall 35 or 36 (NZHawk's awesome mount point manager explicitly uses syscall 35), or support both (drizzt84's OBM derivative Gaia manager supports both). In terms of backup booting, both syscalls do the same thing, but syscall 35 is more robust and, most importantly, free of liability for those who work on PL3.
If you want enhanced stability/compatibility/functionality you'd have to improve the payload. PL3 is a huge step toward this from a developer standpoint.