The above video goes away if you are a member and logged in, so log in now!
Don't quite understand what select+x does in multiman??
Don't quite understand what select+x does in multiman?? –
So I came across a game today that would not load up in multiman (Silent Hill: Homecoming, in case that matters). Normally when this happens, I go running around looking for an unmodified eboot.bin (I'm on 3.55 kmeaw)...but this time, I wasn't able to find one. As I kept looking for a solution, I saw a few mentions of this 'select+x' method of loading a game in multiman. I tried it, said 'yes' on the following screen, and voila....I was now able to start the game from the xmb.
An odd bit of aftermath....I later took the USB external I'd been booting the game from and attached it back to my PC, only to find that I could no longer see the Silent Hill game folder on the drive. Worried it had been deleted, I quickly re-attached the external to the PS3 and loaded up multiman, only to find that it's still there and loadable using the 'select+x' method.
So with all that said....what exactly does this 'select+x' method do? And, why can I no longer see the game folder when I attach the external to my PC (all the rest of the games are still visible), yet it does seem to actually still be there (according to multiman and the fact it can load the game)???
Select + X resolves the black screen games (showing only black screen after selecting the game from XMB) via an external HDD.
For me it fixed my Prince of Persia The Forgotten Sands game and finally being capable of playing again.
It creates a shadow copy of the game on the root of the external usb device, and launches the eboot directly from there, removing the need for a payload in the memory sectors that the particular game is trying to use.
The Reason why you cannot see the game on youre pc (and why some people believe sony is using some sort of rrotkit to delete their games) on the external is because most ps3 tools are programmed in c++. c++ being the language of choice these days, it is mainly used by linux devs becausse the entire linux system is built around the unix system and the c++ language was developed for unix development. c++ programming can be done under windows but most of the free source comes from unix. Now! the reason you can't see the games under windows is because it uses the same fat (file allocation table) but a different version (that is not a m$ version). windows recognises that these files are there, but cannot read the specific file structure used, so you will see the hdd space as reserved for used but not the folders/files under windows because it is unrecognised. If you want to fix this: use a version of linux (like ubuntu that uses both file structures) to copy and replace the existing folders with themselves (the files will then be readable under windows). These file managers use these file structures only because of the open source code (freeware code) with library indexes (pre-programmed commands for them) available for them (which saves alot of time and effort) even if they are programmed under windows (yes, the best c/c++ libraries come from linux, but are not restricted to linux!!!). Which does not restrict hacking to linux but does include linux code for legal (misused) code. Sorry for the technical reply but im drunk! (IF YOU CANNOT UNDERSTAND WHAT IS WRITTEN HERE: THIS ONLY EXPLAINS WHY THE GAMES ARE NO LONGER VIEWABLE UNDER WINDOWS AND NOT WHY [SELECT + X] IS USED FOR GAME BOOTING!)