ManaGunZ

PS3 ManaGunZ - PS3 Backup Manager by Zar v1.41

I never used it that's why I didn't include it, yet. I'm not sure to know how it works. I can include it if it's like I think it's working.
Just to be sure, can you tell me if the path "/netX" (net0, net1, etc) are visible on the filemanager of ManaGunZ ? if yes then i'll I add it when I'll update for next update. If no then I'll need time to see how it works.
 
I never used it that's why I didn't include it, yet. I'm not sure to know how it works. I can include it if it's like I think it's working.
Just to be sure, can you tell me if the path "/netX" (net0, net1, etc) are visible on the filemanager of ManaGunZ ? if yes then i'll I add it when I'll update for next update. If no then I'll need time to see how it works.

"/net" path is not visible on the standard file system.

The path is emulated. To list the remote files, the PS3 application must have the configuration settings (IP address and port of ps3netsrv) and connect to the server using the "netiso" protocol. The communication is always started by the PS3. Once connected, a request is sent to the ps3netsrv with an opcode command (list files, open file, read file, etc.) Each opcode has a response structure.

The code for connecting and remote directory listing can be found from line 588 and below:
https://github.com/aldostools/webMAN-MOD/blob/master/include/netclient.h#L588

The file listing for a remote folder is returned in an array which you can list in a file manager, like webMAN does.

To mount a netiso is relatively easy, since all the hard work is done by the netiso plugin.
All you have to do is load the netiso.sprx with the following netiso_args:

Code:
typedef struct
{
char server[0x40]; // IP address of ps3netsrv (PC or remote PS3)
char path[0x420]; // Remote path of the ISO (e.g. /PS3ISO/my_game.iso)
u32 emu_mode;  // Cobra emulation mode: EMU_PS3, EMU_PSX, EMU_BD, EMU_DVD
u32 num_tracks; // EMU_PSX = number of CD tracks. Other mode num_tracks = 0
u16 port; // Default: 38008
u8 pad[6]; // unused
ScsiTrackDescriptor tracks[MAX_TRACKS]; // array with initial LBA for each audio track (EMU_PSX only)
} __attribute__((packed)) _netiso_args;

To mount a remote folder as a virtual ISO (viso) use "path" with one of the following prefixes:
/***PS3***/GAMES/my_game
/***DVD***/My_Folder

Once the netiso plugin is loaded, it starts the communication between the remote server and Cobra (sys_storage_ext_mount_discfile_proxy).
The netiso plugin receives from Cobra the read requests from SCSI port, pass the request to ps3netsrv and return the response from ps3netsrv to Cobra.

NOTE: The VSH plugin slot 0 is reserved to load netiso or rawseciso.

In IRISMAN I didn't include the code for scanning remote files.
Instead I use mygames.xml that has the remote files already scanned by webMAN MOD.
I mount the remote games via webMAN MOD. It's wMM who decides if use the internal netiso plugin (coded in netclient.h) or the external netiso.sprx
 
Last edited:
So, if I understood correctly all I need from the user is the address IP of the server ?

In a simplistic way: Yes. But you need to pass all these parameters to mount a game:

1. Server IP address
2. Port (default is 38008, but the server can be started listening on any other port)
3. Remote path of the game (/PS3ISO/My_Game.iso or /***PS3***/GAMES/My_Game_Folder)
4. Emulation Mode based on the game type (EMU_PS3, EMU_PSX, EMU_BD, etc.)
5. For PSX only:
- The number of tracks
- Array of initial LBA for tracks (obtained from the CUE file)
 
Last edited:
Can someone help me out here?In the compatibility list it claims the game shadow hearts needs a config,but when I run the game trough managunz it didn't ask me to apply any config I am doing something wrong?
 
Last edited:
  • Like
Reactions: Zar
Doubt here,but why some games that according to the compatibility list doesn't need a config still have a config?

All the games need a CONFIG. Some games don't need an external CONFIG file because the ps2 emulator has one hard coded internally.
The database just makes a copy of the internal CONFIG.
 
So, if I understood correctly all I need from the user is the adress IP of the server ?
Incase you was wondering about how to integrate that settings into managunz interface...
I guess (by default) the IP address (and/or proxy) can be loaded from the xRegistry.sys
First try to load the proxy, and incase it doesnt exists load the base IP
And for the port make it use the default mentioned by aldo

I guess this auto-setup is going to work for lot of users, the ones that have the PS3 directly connected to the PC as a proxy and runs ps3netserv on PC, and some more than have the PS3 connected to a router and runs ps3netserv on the router/NAS

Im just talking about using this auto-setup as the default settings (on first managunz boot, inmediatlly after a fresh managunz install)
Of course... is needed to allow the user to change them :D

Btw, additionally, i guess ps3netserv have some kind of "ping" response that you could use as a check to display a notification message on managunz screen with something like... "Network game server active"
 
Incase you was wondering about how to integrate that settings into managunz interface...
I guess (by default) the IP address (and/or proxy) can be loaded from the xRegistry.sys
First try to load the proxy, and incase it doesnt exists load the base IP
And for the port make it use the default mentioned by aldo

I guess this auto-setup is going to work for lot of users, the ones that have the PS3 directly connected to the PC as a proxy and runs ps3netserv on PC, and some more than have the PS3 connected to a router and runs ps3netserv on the router/NAS

Im just talking about using this auto-setup as the default settings (on first managunz boot, inmediatlly after a fresh managunz install)
Of course... is needed to allow the user to change them :D

Btw, additionally, i guess ps3netserv have some kind of "ping" response that you could use as a check to display a notification message on managunz screen with something like... "Network game server active"

The "auto-setup" is a good idea, but not very practical. IMHO The ps3netsrv should be configured manually (a suggested IP address is ok). The ps3netsrv can be a SAN, another PS3 or a PC. There could be many ps3netsrv servers too. So it's better to let the user configure them using a GUI or a config file.

webMAN MOD lets the user configure the IP in /setup.ps3. IRISMAN doesn't require any configuration because it uses the XML generated by webMAN MOD.
 
Moreover, the IP address on registry is the IP of the PS3, not the server.
I meant the IP that appears in the official XMB network settings field "Default Router"
In my PS3 that IP is my PC :) (because i have the PS3 directly connected by ethernet cable to the PC)
 
Doubt here,many games have a soft,gx,custom config,how the hell I am supposed to know which one to use?
By trying them :rolleyes:

If you are wondering why there is not a single "winner" config for every game... well... thats a bit long and technical story, but it can be resumed as... "because nobody filtered them"
The configs from category soft, gx and net are official
Gx and soft has been extracted from the emus itself (are old versions of the ps2 emus that contains the configs embedded inside them), and net configs has been extracted from PSN

The next logic step would be to compare them to identify the duplicated ones (probably there are many duplicates in between soft and gx), and incase some configs differs a bit is needed to test them doing a playthrough to have a confirmation which config is "the good one"
This is the kind of thing that only can be made with the feedback of the community
 
Back
Top