[ISSUE]: OPL Launcher doesn't work, redirects to PS2 OSD

[jdev15]

Checks

• I have checked existing issues for duplicates and found none

Describe the issue

Context

I have an Official PS2 Network adapter modified to support SATA drives. I have a Crucial BX500 250Gb SSD setup with krHACKen's SUDC4 utility disk in order to enable the OSD 2.0. I have a partition dedicated to Homebrew apps that launches wLaunchELF_isr named PP.WLE with the minimum supported size of 128MB. This partition appears on the OSD. The other partition I have setup is the +OPL partition with OPL and all of its config files. Aside from that, there's also the OPL folder inside the __common partition with the file conf_hdd.cfg that specifies the location of the main OPL executable, supposedly so OPL Launcher knows where to launch it. I add games to the HDD with HDL Batch Installer by connecting the SSD to my PC with a SATA to USB adaptor.

Issue

The supplied OPL Launcher ELF file on this repository is dated from 2022 and does not work with my setup. Whenever I launch a game from the OSD with this executable in its header, the console freezes for a minute or two before returning to the OSD. This seems similar to an issue I've previously opened on the main OPL repo, that was fixed in the meantime. From my understanding, this was mainly a PS2 SDK issue with drive detection that was fixed and trickled down to OPL.

With this in mind, I thought that maybe by re-compiling OPL Launcher with the latest PS2 SDK would fix my issue and allow game booting in the OSD. The repo as is does not compile with the provided Makefile. I forked the project and modified the Makefile so it would compile. Turns out removing the -G8192 flag from the compilation fixes the error:

Error: -G may not be used with abicalls

I have here an up to date compile of OPL Launcher, but it still does not boot games from the OSD. This time, whenever I try to launch a game the screen flashes for a bit but then returns to the OSD, as it previously happened.

Now, I'm not sure if removing the flag from the compilation might have affected OPL Launcher's behaviour, or if there's a fault with the OPL Launcher codebase, or even if it's a fault with OPL itself.

Console model

SCPH-30004 (C'-Chassis)

[jdev15]

Upon further research on the issue, I've tried an old 80GB IDE HDD that I've tested in the past as working with the HDD OSD and OPL Launcher combo, and it also isn't able to boot into a game. Considering I'm using the same OPL Launcher Kelf, I'm starting to believe that this is an issue with the latest 1.2.0 releases of OPL. I'll try release 1.1.0 to see if the issue still manifests.