11-04-2012,03:24 AM

Originally Posted by
Ceedlorenzo
Hello SP192, I am just wondering,...
What does unhook system calls and forced sync does actually with the game during runtime? I mean technically speaking... ^,^ Im just really curious... Maybe an in-depth knowledge about these options could help many people what to activate incase something goes wrong.. ^.^
It basically does what it's name suggests: Unhook all hooked syscalls on the EE kernel. I don't know why, but some games just get broken when the SifSetDma() syscall is hooked on. It's actually HDLoader and OPL compatibility mode 3.
The force synchronization mode is actually a half-complete attempt to make PS2ESDL run like OPL does - just block execution until the read operation completes (Even though all I/O operations should be asynchronous).
But that compatibility mode doesn't actually achieve that since it causes PS2ESDL to only block when either sceCdSync() or sceCdDiskReady() is called with any mode, which is why it's only a partially-completed attempt at doing that (But seems to be good enough anyway....). If the game needs OPL's design to run well, you're better off with using OPL (And I will not support the game because it's not too well written).
I just chose to not go with the old naming convention as I think that it's not very intuitive to most people. What does mode 3 do? Unless you tinker with the compatibility modes on a regular basis, you'll probably forget.
Unmodified SCPH-77006 with SM 3.6
SCPH-39006 with M-chip modchip, SCPH-10281 NA and refurb Seagate 80GB HDD
SCPH-10000 v1.00 with SCPH-10190 PCMCIA NA and SCPH-20400 HDD unit

PS2ESDL v0.823B
やっほー 汗がひかる♪