[BUG] webMan MOD mounts the ROM folder rather than the game on remote ROMS

[kadai]

When trying to load a ROM file from a machine with ps3netsrv, webMan mod mounts the folder instead of the actual ROM. This happens either when trying to load the ROM from the XMB menu or from the web menu.

Expected behavior:
To have the game be mounted like if it was being mounted from /dev_hdd0/ROMS and have it be shown as a "disc" game... instead, I got a message telling me that "NES", "SNES", "GBA" or alike is ready and no "disc" is shown in the XMB menu.

When you examine /dev_bdvd, you can see the contents of the mounted folder there (a list of roms):

Setup:
Machine with ps3netsrv (version: ps3netsrv build 20250803 (mod by aldostools))
PS3 with webMAN 1.47.48p MOD (PS3HEN)

Thanks in advance!

[aldostools]

In the case of /dev_hdd0/ROMS it is not necessary to mount anything, because the HDD is already mounted and all the content can be accessed directly.

For remote ROMs, the story is different. The remote folder containing the ROMs is mounted as /dev_bdvd, and then you can load the ROMs from the mounted "disk" using RetroArch or the webMAN MOD integration.

Honestly, I haven't been very active lately. However, I do remember that the webMAN integration with RetroArch was working the last time I tested it. It should still be working unless some recent change has broken it.

[kadai]

In the case of /dev_hdd0/ROMS it is not necessary to mount anything, because the HDD is already mounted and all the content can be accessed directly.

For remote ROMs, the story is different. The remote folder containing the ROMs is mounted as /dev_bdvd, and then you can load the ROMs from the mounted "disk" using RetroArch or the webMAN MOD integration.

Honestly, I haven't been very active lately. However, I do remember that the webMAN integration with RetroArch was working the last time I tested it. It should still be working unless some recent change has broken it.

The webMan integration works well, but only for ROMs locally!

I mean, when you "mount" a local ROM, I have seen that the contents of "/dev_hdd0/game/PKGLAUNCH/" are mounted into "/dev_bdvd", then a file "launch.txt" has the ROM you wanted to launch.

Was reporting this because I expected to see something similar happening but with the remote ROM being populated into "launch.txt".

Now, I can still load the roms mounted into /dev_bdvd with retroarch, is just that if this is the way it was implemented, is ok! Is just me that did not expected this to happen!

[aldostools]

Thank you for your feedback. As I commented earlier, I haven't been very active lately and I don't remember if I implemented it that way intentionally. If I recall correctly at some point the remote ROMS were being mounted in PKGLAUNCH like it does with local ROMS.

I will try to reproduce this issue and fix it if I can, but first I need to find some free time to do it.

[sequc82]

@aldostools does #312 mean it was intentional?

[aldostools]

@aldostools does #312 mean it was intentional?

That response is from 2020. There were changes in the way the ROMS are scanned after the date of that post.

The ROMS stored in ps3netsrv are handle in a different way because there is direct access to the remote files.

The remote folder containing the ROMs is mounted as /dev_bdvd. To handle this difference, PKGLAUNCH use one retroarch.cfg for local content and retroarch.cce (renamed to retroarch.cfg) for the remote ROMS stored in ps3netsrv.