webMAN Classics Maker

PS3 webMan Classics Maker: Launch ISOs straight from XMB 3.0.0-beta3

So I was testing this application for a ps1 title (Final Fantasy VII (Disc 1)) which was a bin/cue file and was on the Webman PSX folders; everything seemed fine like game id and the path was correct but when I clicked on the Build button, I get the error message that says the build has failed. Is there anything I'm doing wrong here?
 
So I was testing this application for a ps1 title (Final Fantasy VII (Disc 1)) which was a bin/cue file and was on the Webman PSX folders; everything seemed fine like game id and the path was correct but when I clicked on the Build button, I get the error message that says the build has failed. Is there anything I'm doing wrong here?

EDIT: On second thought, nevermind. I actually had to move the app into my OS Drive. Now it works! Sorry, about that!
 
I discovered one more bug ?!
I just made a forwarder for a PSX Iso. after starting the installed pkg the game is getting mounted but does not autostart like the other forwarders. I have to go all the way up and start the mounted disc manually. is this intentionally or is this a bug? how can I change that behavior to start the game automatically?
 
@matruka Hi. First of all, thank so much for those kind words. I almost forgot other people were using this tool besides me :)
I appreciate the investigation of cause for both issues, I must admit I good while since I spent time updating WCM!

So from what I understand regular ISO works fine but folder-games seems to get a bugged launch-command w/ duplicate name in path. I remember the other bug when PIC1 doesn't get its info showed on top, it's good to know it only affects folder games, makes life easier to debug.

I can't promise I'll have the time to update this week, but I will look into it as soon as I some time over.

However, I'll let you when an update is due, please have a great day.

EDIT: I added to check PSX ISO to the list. If you want to elaborate you can always increase the /wait.ps3?3 -command to something like /wait.ps3?4 or 5 (there are two in total)

EDIT2: @FantastixLive99 it's likely a bug that depends on C: for some reason; I'll add to my list, thank you :)
 
@jacobsson thanks for the tip with the wait time, I will try that.
the "bug" with the missing title wasn't caused by WCM, the PIC0.PNG of that game was just missing.

so it's just the bug with the path of folder games

and i love this app, it is the essential one for me :) you helped me to make my xmb look nice and tidy and i don't have to start a backup manager separately
 
Would be nice if we can build the PKG without needing to connect to the system, here i have over 3000 titles and it takes a lot of time to scan it
 
Last edited:
It always gives me error,

[4/5] Execution of 'resign_eboot.py': FAILED

Edit: It's related to my user name having Space on it, so i just moved the whole folder to C: and now it's working
lUpB5u1.png
 
Last edited:
It always gives me error,

[4/5] Execution of 'resign_eboot.py': FAILED

Edit: It's related to my user name having Space on it, so i just moved the whole folder to C: and now it's working
lUpB5u1.png
Disable DEP or install older Windows version on Virtual Machine(VirtualBox or WMware) try in VM.
 
Would be nice if we can build the PKG without needing to connect to the system, here i have over 3000 titles and it takes a lot of time to scan it

Absolutely! You can always just type in your info manually and using the predefined paths from the buttons
upload_2021-11-27_16-37-46.png


What error did you receive when having a space in your path?
I'm testing this right now from C and other drives using spaces, but I can't reproduce it unfortunately.
 
Unfortunately you need a backwards compatible model (stated in the first post) such as CECH-A/B/C/E in order to use USB peripherals such as the Buzzers.
Sorry I didn't notice. Don't I have any chance of getting the Buzzcontrol to work? I have FERROX 4.87 + COBRA 8.20 and the latest webman. I'm sorry for my bad english
 
Sorry I didn't notice. Don't I have any chance of getting the Buzzcontrol to work? I have FERROX 4.87 + COBRA 8.20 and the latest webman. I'm sorry for my bad english
The non-BC models (such as yours) is forced to use the full software emulator aka. PS2_netemu.
PS2_netemu has no USB implementation at all so unfortunately we can't get non-BC models to use stuff like Buzzers etc
 
The non-BC models (such as yours) is forced to use the full software emulator aka. PS2_netemu.
PS2_netemu has no USB implementation at all so unfortunately we can't get non-BC models to use stuff like Buzzers etc
One more question, is it possible with a cechk04 console because I would have that kind of cabinet. Thanks a lot for the help and replies to the posts
 
Hi everyone . I just installed this program but i cant get it to work . I Have Rebug system if that helps . keep getting the following error :


[1/5] Execution of 'write_json_to_param_sfo.py': DONE
-----------------------------------------------------
[2/5] Execution of 'content_id_elf_replace.py': DONE
-----------------------------------------------------
[3/5] Execution of 'edit_launch_txt.py': DONE
-----------------------------------------------------
DEBUG content_id: UP0001-WLUS00044_00-0000000000000000
'C:\Webman' is not recognized as an internal or external command,
operable program or batch file.

[4/5] Execution of 'resign_eboot.py': FAILED

-----------------------------------------------------
 
Hi everyone . I just installed this program but i cant get it to work . I Have Rebug system if that helps . keep getting the following error :


[1/5] Execution of 'write_json_to_param_sfo.py': DONE
-----------------------------------------------------
[2/5] Execution of 'content_id_elf_replace.py': DONE
-----------------------------------------------------
[3/5] Execution of 'edit_launch_txt.py': DONE
-----------------------------------------------------
DEBUG content_id: UP0001-WLUS00044_00-0000000000000000
'C:\Webman' is not recognized as an internal or external command,
operable program or batch file.

[4/5] Execution of 'resign_eboot.py': FAILED

-----------------------------------------------------
Hi! What install path do you use for the program? It seems like it might not like spaces in the path/folder name.
 
Hi! What install path do you use for the program? It seems like it might not like spaces in the path/folder name.

I have it in the main root of C drive . Could it be the icons n pics not been in the same drive? I'm totally lost . Any suggestions how I should have it install location wise?
 

Similar threads

Back
Top