[sandungas]

Originally Posted by Ada Love Lace ...if it s possible to do more patching (about sys version to avoid the game to don t boot being block by the required sys...

There are needed 2 patches to solve all this problems:
-The one multiman does by patching the APP_VER in the main PARAM.SFO in the main folder of the disc (or hdd installation folder)
-Another patch in the APP_VER in the main PARAM.SFO in the main folder of the update installation (this is a problem as explained before if you pretend to patch this file after his installation XMB will ignore it and will try to boot from the original one from the XMB database)

I think this patching cant be standarized because there are several different ways to boot a game.. but from the point of view of multiman maybe this 2 patches can be reduced to 1... by only patching the "returned value" for APP_VER (in ram, not in the PARAM.SFO's) when the game boots
This solves the problem of the XMB database (the value of APP_VER from the XMB database is ignored)
And another benefit... the game folder doesnt needs to be modifyed (no need to modify the PARAM.SFO's files)

*Yeah, this is a suggestion, i understand is more complicated than patching a file but here is the idea

[BGMaxie]

Basically what is this talk about? What effects does it bring/hint?

[KDSBest]

The funny thing is I own the bicycle deck that is shown on the picture.

Pretty awesome deck of cards

[sandungas]

More brainstorming
Something documented few time ago used in game updates that can add some eye candy to your "fixes"...
The PARAM.HIS format ---> http://www.ps3devwiki.com/wiki/PARAM.HIS

With this you can add some texts (like what files has been fixed, who did the fix, credits, etc...)
After the update is installed... by pressing triangle over his icon, in the side menu you can see this kind of display that takes the info from PARAM.HIS

Also, with a bit of work it can be done a logo in ASCII art for a more "proffesional" look :P