Multiman vanished. Any ideas?

(On 4.88.2 Evilnat)
Turned on the PS3 last night to notice that Multiman had vanished. I have both Multiman and Webman installed. Latest versions for both. Reinstalled Multiman, and it came back. The settings were even saved from before.

Any idea what might have caused this? Any idea if it'll happen again?
I've done some searching on this, but haven't found concrete answers.

Thanks in advance!
 
(On 4.88.2 Evilnat)
Turned on the PS3 last night to notice that Multiman had vanished. I have both Multiman and Webman installed. Latest versions for both. Reinstalled Multiman, and it came back. The settings were even saved from before.

Any idea what might have caused this? Any idea if it'll happen again?
I've done some searching on this, but haven't found concrete answers.

Thanks in advance!
if you got kids, i bet it was them.
 
I am wondering if this still work on latest CFW's
https://www.psx-place.com/resources/ps3lock.10/

Not sure if it needed an update for support or not or works as is..
Assuming only thing that would not work is detection of later firmware then 4.82
I was hoping for something that would just hide all that stuff. But thank you, I'll look into it. :)
EDIT: Just realized this was in the multiman thread, it really could apply to my other thread about making a clean profile that hides settings for CFW and such. lol
 
Nope! It's a pretty barren setup right now. I'm running Evilnat 4.88.2. Have Multiman, Webman installed. Movian (video player), and 2 sets of covers packs from multiman. That's pretty much it.

PARAM.SFO in cover packs is replacing the original PARAM.SFO in multiMAN.

I will fix this issue. Thank you for report it.
 
PARAM.SFO in cover packs is replacing the original PARAM.SFO in multiMAN.

I will fix this issue. Thank you for report it.
My Multiman also disappeared after I installed cover packs. I didn't understand why so I just re-installed multiMAN. Must have been that issue.
 
My Multiman also disappeared after I installed cover packs. I didn't understand why so I just re-installed multiMAN. Must have been that issue.

Yes. The problem was that the pack was created using pkg_custom.exe
That tool replaces the PARAM.SFO installed by the package.

I rebuilt the cover packs with psn_package_npdrm.exe
This tools updates the PARAM.SFO when the category is GD (Game Data).

The new cover packs were uploaded and replaced in my github repository.

It is not necessary to download or reinstall the cover packs again if you already reinstalled multiMAN.
 
Yes. The problem was that the pack was created using pkg_custom.exe
That tool replaces the PARAM.SFO installed by the package.

I rebuilt the cover packs with psn_package_npdrm.exe
This tools updates the PARAM.SFO when the category is GD (Game Data).

The new cover packs were uploaded and replaced in my github repository.

It is not necessary to download or reinstall the cover packs again if you already reinstalled multiMAN.
Since we're taking about unexpected un installs

It happens at random times when I boot a iso game (externa hdd) from webman and it black screems me and gives me the "PRESS PS buttom to restart or select and start to install new system update"

When I boot up webman is gone.
 
Since we're taking about unexpected un installs

It happens at random times when I boot a iso game (externa hdd) from webman and it black screems me and gives me the "PRESS PS buttom to restart or select and start to install new system update"

When I boot up webman is gone.

Thank you for your report. The unexpacted black screen is a completely different issue.

It could be caused by a crash of LV2 kernel process or by a corrupted system file in dev_flash (or less probable in core_os).

If you're on Evilnat 4.88 or 4.89, webMAN is gone because stage2 is disabled if the system fails to load properly.
This is a new failsafe feature of Cobra 8.3 to prevent potential bricks if stage2 cannot be loaded.

When stage2 (Cobra payload) is disabled, the plugins cannot load on boot. Therefore webMAN is gone until Cobra is re-enabled.

I suggest that update webMAN MOD using the online updater, just in case you have an older build with bugs.

If the issue still happens after update, it would be helpful to get a socat capture when the error happens.
For this, it would be required to enable Cobra debug and keep socat running until the bug is produced.

The problem is that running Cobra debug permanently could cause other bugs too.
For instance, VshFpsCounter crashes when Cobra debug is enabled. To minimize this issue, an older version of the FPS plugin is loaded if Cobra debug is detected.
 
PARAM.SFO in cover packs is replacing the original PARAM.SFO in multiMAN.

I will fix this issue. Thank you for report it.
Ohhhhh ok! Happy to help! :D

I have another question you might be able to answer.

What do I have to name my PS1 ISOs to get the game covers to work?
(Either with the cover packs, or to get MultiMan to auto-download them).

Let's use "Final Fantasy Chronicles - Chrono Trigger (USA)" as an example.

Thank you!
 
Ohhhhh ok! Happy to help! :D

I have another question you might be able to answer.

What do I have to name my PS1 ISOs to get the game covers to work?
(Either with the cover packs, or to get MultiMan to auto-download them).

Let's use "Final Fantasy Chronicles - Chrono Trigger (USA)" as an example.

Thank you!

Include the game id as part of the name or name the cover file with the same name of the ISO (in the same folder).

In multiMAN, If I recall correctly, it's like:
SLES_123.45-[FFC - CT (USA)].bin
SLES_123.45-[FFC - CT (USA)].cue

In webMAN MOD, it can be included also between brackets or parenthesis:

FFC - CT (USA) [SLES_123.45].bin
FFC - CT (USA) [SLES_123.45].cue
or
FFC - CT (USA) (SLES-12345).bin
FFC - CT (USA) (SLES-12345).cue
 
Include the game id as part of the name or name the cover file with the same name of the ISO (in the same folder).

In multiMAN, If I recall correctly, it's like:
SLES_123.45-[FFC - CT (USA)].bin
SLES_123.45-[FFC - CT (USA)].cue

In webMAN MOD, it can be included also between brackets or parenthesis:

FFC - CT (USA) [SLES_123.45].bin
FFC - CT (USA) [SLES_123.45].cue
or
FFC - CT (USA) (SLES-12345).bin
FFC - CT (USA) (SLES-12345).cue
Ok, sounds good. Thanks.
I'll mess with it more tonight and report back if it gives me issues!
 
Thank you for your report. The unexpacted black screen is a completely different issue.

It could be caused by a crash of LV2 kernel process or by a corrupted system file in dev_flash (or less probable in core_os).

If you're on Evilnat 4.88 or 4.89, webMAN is gone because stage2 is disabled if the system fails to load properly.
This is a new failsafe feature of Cobra 8.3 to prevent potential bricks if stage2 cannot be loaded.

When stage2 (Cobra payload) is disabled, the plugins cannot load on boot. Therefore webMAN is gone until Cobra is re-enabled.

I suggest that update webMAN MOD using the online updater, just in case you have an older build with bugs.

If the issue still happens after update, it would be helpful to get a socat capture when the error happens.
For this, it would be required to enable Cobra debug and keep socat running until the bug is produced.

The problem is that running Cobra debug permanently could cause other bugs too.
For instance, VshFpsCounter crashes when Cobra debug is enabled. To minimize this issue, an older version of the FPS plugin is loaded if Cobra debug is detected.
It happend often when I disable syscalls and enable ir by the system update in XMB(enable syscalls and boot another game and then black screen) or if I load a good ammount of games

Right now im on Evilnat 4.89 RSX OC un oficial, but happend more often in 4.88.2, and webman is updated to the latest vía the intégrated updater

My first thought was that there was not sufficient ammount of memlry and just crashes and It deleites webman since that was the cause of the crash
 
It happend often when I disable syscalls and enable ir by the system update in XMB(enable syscalls and boot another game and then black screen) or if I load a good ammount of games

Right now im on Evilnat 4.89 RSX OC un oficial, but happend more often in 4.88.2, and webman is updated to the latest vía the intégrated updater

My first thought was that there was not sufficient ammount of memlry and just crashes and It deleites webman since that was the cause of the crash

Without a way to reproduce the bug consistently or without a log trace it will be really hard to fix.

VshFpsCounter is one of the possible causes, if you have it loaded at the moment of the crash.
Recent versions seem to be more unstable due the extra memory scanning needed to display the clock speed and other information.

Check if the issue is less frequent not using VshFpsCounter.
 
Without a way to reproduce the bug consistently or without a log trace it will be really hard to fix.

VshFpsCounter is one of the possible causes, if you have it loaded at the moment of the crash.
Recent versions seem to be more unstable due the extra memory scanning needed to display the clock speed and other information.

Check if the issue is less frequent not using VshFpsCounter.
I will thanks

The problem seems to be there, I remember when I updated webman from 1.47. 37 to 1.47.38 when fps counr was added, I couldnt even launch isos, and when o could boom, black screen.

Your sugestión is just use it when need it or I don't display the cloack speeds? Right now im using intégrated webman fos clunter displaying FPS, TEMPS and CLOACKs
 
Your sugestión is just use it when need it or I don't display the cloack speeds? Right now im using intégrated webman fos clunter displaying FPS, TEMPS and CLOACKs

The FPS plugin is very useful and has many neat features.
But it is still buggy. I'm not sure if it is more stable removing the clocks.

My suggestion is use it just when need it & unload it after use.
 
Back
Top