PS3 How to boot psn iso off exfat usb - without installing game to internal hdd ?

harmjabo2 said:
Does this work if I am using wifi connection ?
Click to expand...
Yes, it might be a little slow but as long as both PC and PS3 are on the same LAN subnet, it should work. Although generally speaking I would advise using a cable (or LPC) between the PS3 and the router for PS3-PC communication.

Check your network settings.
You should be able to ping your PS3 IP from your PC command prompt to make sure it's reachable.
 
@aldostools
when i copy over folder for psn title to usb, it does not show on xmb.
But when I install the pkg to GAMEI drive then it shows up.
Is a away way to get the psn folders that I mabnually copied over to the GAMEI drive ?

Also, when boot ps3 into debug mode and execute your cmd command it throws the following error (attached pic)

GADPD2F
 
Last edited:
harmjabo2 said:
@bguerville
I was successfully ping my ps3 ip from pc, but I cant get the socat commands to execute on pc.
Click to expand...
I cannot say.
Maybe the debug cobra build is not enabled or you omitted a step.

I don't have evilnat's 4.89 installed to test the Cobra debug build that should be included with it so I cannot confirm anything. Maybe someone else can..
 
Apologies to hijack, but I'm getting similar issues trying to use GAMEI, which I posted on a thread over here - https://www.psx-place.com/threads/p...ng-in-webman-mod-from-both-usb-and-net.37313/

Following along on this one however, thanks for letting me know how to disable debug output so I can try and diagnose my issues further.

Here's my socat output of an extracted PKG mounted in /net_host0/GAMEI/ being mounted via webMAN mod, then being kicked back to XMB on launch with error 80010009:

https://pastebin.com/C1FAZLEm
 
As far as I can tell from these logs (and I'm no expert), it's mapping one extra directory down than it should be?

Code: 
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002

Shouldn't this be mapping /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002 instead? In order to mirror the structure expected in /game (containing subfolders matching Title IDs).
 
Looking into the logs more, and going back through to bisect previous versions versions, the 80010009 error only started occurring with GAMEI folders on 1.47.40 onwards. Looking at Cobra debug, it may be missing the Title ID on the hdd0 side of the mapping.

1.47.38:
Code: 
map_path_user, called by process 01000300_main_vsh.self: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
Map path: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0//game/PKGLAUNCH
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0/game/NPUA30002 -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0/game/NPUA30002 -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0/game/NPUA30002/USRDIR/EBOOT.BIN

1.47.40:
Code: 
map_path_user, called by process 01000300_main_vsh.self: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
Map path: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0//game/PKGLAUNCH
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0/game//USRDIR/EBOOT.BIN

I will say that the particular title I'm testing does still seem to end up on a black screen (or an 'update available' system menu) on these older versions, but that could be a compatibility issue with the package itself. At least it seems to be mounting correctly, though.
 
retroNUC said:
Looking into the logs more, and going back through to bisect previous versions versions, the 80010009 error only started occurring with GAMEI folders on 1.47.40 onwards. Looking at Cobra debug, it may be missing the Title ID on the hdd0 side of the mapping.

1.47.38:
Code: 
map_path_user, called by process 01000300_main_vsh.self: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
Map path: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0//game/PKGLAUNCH
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0/game/NPUA30002 -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0/game/NPUA30002 -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0/game/NPUA30002/USRDIR/EBOOT.BIN

1.47.40:
Code: 
map_path_user, called by process 01000300_main_vsh.self: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
Map path: /app_home/PS3_GAME -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0//game/PKGLAUNCH
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0//game/PKGLAUNCH -> /dev_usb000/GAMEI/NPUA30002
map_path_user, called by process 01000300_main_vsh.self: /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002
Map path: /dev_hdd0/game/ -> /dev_usb000/GAMEI/NPUA30002
open_path /dev_hdd0/game//USRDIR/EBOOT.BIN

I will say that the particular title I'm testing does still seem to end up on a black screen (or an 'update available' system menu) on these older versions, but that could be a compatibility issue with the package itself. At least it seems to be mounting correctly, though.
Click to expand...

Try updating to the latest build currently online using the online updater or re-download the installer.
Today I uploaded a commit for the fix of remote GAMEI that probably also fixes your issue too.
 
Thanks for the quick turnaround - Fixes the mounting issue and no longer encountering the 80010009 error, but still seeing black screens when trying to launch content from GAMES and GAMEI via USB.

Mounting and running a folder in from /dev_usb000/GAMES:
Code: 
map_path_user, called by process 01000300_main_vsh.self: /dev_bdvd -> /dev_usb000/GAMES/BLUS30537
map_path_user, called by process 01000300_main_vsh.self: //dev_bdvd -> /dev_usb000/GAMES/BLUS30537
map_path_user, called by process 01000300_main_vsh.self: /app_home -> /dev_usb000/GAMES/BLUS30537
...
PROCESS /dev_bdvd/PS3_GAME/USRDIR/EBOOT.BIN (01030200_main_EBOOT.BIN) (01030200) created from parent process: 01000300_main_vsh.self
...
open_path /app_home/DataPS3.forge

Exec then gets stuck trying to load data files that don't exist - The correct location of this data file at time of black screen, given the mappings I can see via FTP, would be "/app_home/PS3_GAME/USRDIR/DataPS3.forge"

Full cobra logs of mounting and running on pastebin. I can take this to GitHub if you prefer, avoid the wait time of my newbie user status :)
 
retroNUC said:
Thanks for the quick turnaround - Fixes the mounting issue and no longer encountering the 80010009 error, but still seeing black screens when trying to launch content from GAMES and GAMEI via USB.

Mounting and running a folder in from /dev_usb000/GAMES:
Code: 
map_path_user, called by process 01000300_main_vsh.self: /dev_bdvd -> /dev_usb000/GAMES/BLUS30537
map_path_user, called by process 01000300_main_vsh.self: //dev_bdvd -> /dev_usb000/GAMES/BLUS30537
map_path_user, called by process 01000300_main_vsh.self: /app_home -> /dev_usb000/GAMES/BLUS30537
...
PROCESS /dev_bdvd/PS3_GAME/USRDIR/EBOOT.BIN (01030200_main_EBOOT.BIN) (01030200) created from parent process: 01000300_main_vsh.self
...
open_path /app_home/DataPS3.forge

Exec then gets stuck trying to load data files that don't exist - The correct location of this data file at time of black screen, given the mappings I can see via FTP, would be "/app_home/PS3_GAME/USRDIR/DataPS3.forge"

Full cobra logs of mounting and running on pastebin. I can take this to GitHub if you prefer, avoid the wait time of my newbie user status :)
Click to expand...

For this kind of report it is better to open an issue in github. I try to answer most of them.

I uploaded a new fix for this issue. You can use the online updater on XMB or the releases page to download the new installer.

Take in count that not all games are compatible with app_home (or GAMEI).
For instance, CoD Black Ops III works fine, but CoD Black Ops causes a black screen from app_home icon.

Your feedback is appreciated.
 
Again, thanks for the quick update, as well as an example of a title that worked. I think that I just suffered from incredibly bad luck, and the three titles that I chose at random were all incompatible with extracted data in GAMES/GAMEI. Backed up BO3 and tested it along with a few more random titles, and they worked perfectly.

Do you have any more information about the /app_home compatibility issues? I suppose it's because the executable sees the existence of /app_home or detects being ran from a non-standard place, and assumes it's been run in a development-like environment so can use alternate paths.

Developer kits do have the option of blocking some access to these, essentially trying to coerce an /app_home title into behaving more like a retail disc. I may try switching to REBUG DEX instead of Evilnat, see if I can then toggle these flags and see if that helps with some of the more incompatible games.

From DevWiki page:
Code: 
Release Check Mode:
    - Check if /app_home is used in the application.
        - "Development Mode" : the application can used /app_home.
        - "Release Mode" : the application can't use /app_home.

- GameContentUtil Boot Path (/app_home/PS3_GAME/):
    - Change the game content boot path when an application is started from /app_home/PS3_GAME/.
        - "For Development" : return the real path where the application is started.
        - "For Release" : return the path from the PARAM.SFO settings.
 
retroNUC said:
Again, thanks for the quick update, as well as an example of a title that worked. I think that I just suffered from incredibly bad luck, and the three titles that I chose at random were all incompatible with extracted data in GAMES/GAMEI. Backed up BO3 and tested it along with a few more random titles, and they worked perfectly.

Do you have any more information about the /app_home compatibility issues? I suppose it's because the executable sees the existence of /app_home or detects being ran from a non-standard place, and assumes it's been run in a development-like environment so can use alternate paths.

Developer kits do have the option of blocking some access to these, essentially trying to coerce an /app_home title into behaving more like a retail disc. I may try switching to REBUG DEX instead of Evilnat, see if I can then toggle these flags and see if that helps with some of the more incompatible games.

From DevWiki page:
Code: 
Release Check Mode:
    - Check if /app_home is used in the application.
        - "Development Mode" : the application can used /app_home.
        - "Release Mode" : the application can't use /app_home.

- GameContentUtil Boot Path (/app_home/PS3_GAME/):
    - Change the game content boot path when an application is started from /app_home/PS3_GAME/.
        - "For Development" : return the real path where the application is started.
        - "For Release" : return the path from the PARAM.SFO settings.
Click to expand...

As far as I know to mount a folder game through /app_home basically these paths need to be mapped:
/app_home => <path>/USRDIR
/app_home/PS3_GAME => <path>/PS3_GAME or /dev_hdd0/game/<title_id>

The order of the mapping is important, because /app_home/PS3_GAME is inside /app_home and Cobra can think that PS3_GAME is a folder of /app_home.

Also the slash is very important. It is not the same to map /app_home/PS3_GAME to /path/PS3_GAME than /app_home/PS3_GAME/ to /path/PS3_GAME or /app_home/PS3_GAME to /path/PS3_GAME/. Indeed /app_home/PS3_GAME and /app_home/PS3_GAME/ are treated by Cobra as different paths.

Maybe there are other considerations, but I don't recall them.

If you want to experiment yourself, you can play using the /mappath.ps3mapi interface to create your own remaps.

Or use similar web commands like:
/app_home.ps3<path>
/remap.ps3<path>&to=<new-path>
/unmap.ps3<path>
/remap.ps3 <= unmap all mapped paths

So far, the games that I tested worked fine, except the ones that as you mention could be blocking /app_home on purpose.
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top