IAmVery(0x400|0x139)
Forum Noob
I am currently writing a Lua PS3MAPI wrapper, but I got stuck at the SYSCALL command. Whatever I do, it seems to return 0xFFFFFFFF8001000d. From the source codes I've been grepping through, that means CFW syscalls are disabled. However, all syscalls are enabled, and the webMAN-MOD /syscall.ps3 endpoint actually does work.
I tested it with a few different syscalls, mainly non-CFW (eg; sys_process_getpid(), sys_sm_ring_buzzer()) but also CFW syscalls (lv1 peek & poke). None of them worked via PS3MAPI, but did work via webMAN-MOD's /syscall.ps3.
I am using Evilnat D-PEX 4.92, Cobra 8.5, on a CECH2004. webMAN-MOD is v1.47.48n. LV2 protections are disabled, QA flag is enabled, and everything else works fine.
I sent AldosTools an email about it, and I got told to make an account and ask here
Also, with PS3MAPI I mean the server running on port 7887, which comes with webMAN-MOD.
Figured it out. I assume there is a bug in the way the server reads the parameters, as it reads from the second parameter and not the first, causing it to skip it.
The fix for me was just to add a second space after "SYSCALL", but before the parameters, so they are read (in)correctly.
@aldostools you might want to look into this, as it is a gnarly little bug lol.
I tested it with a few different syscalls, mainly non-CFW (eg; sys_process_getpid(), sys_sm_ring_buzzer()) but also CFW syscalls (lv1 peek & poke). None of them worked via PS3MAPI, but did work via webMAN-MOD's /syscall.ps3.
I am using Evilnat D-PEX 4.92, Cobra 8.5, on a CECH2004. webMAN-MOD is v1.47.48n. LV2 protections are disabled, QA flag is enabled, and everything else works fine.
I sent AldosTools an email about it, and I got told to make an account and ask here
Also, with PS3MAPI I mean the server running on port 7887, which comes with webMAN-MOD.
Figured it out. I assume there is a bug in the way the server reads the parameters, as it reads from the second parameter and not the first, causing it to skip it.
The fix for me was just to add a second space after "SYSCALL", but before the parameters, so they are read (in)correctly.
@aldostools you might want to look into this, as it is a gnarly little bug lol.
Last edited by a moderator:
