RETROLauncher

PS2 RETROLauncher (Launcher created on Enceladus for Retroarch, POPStarter, Neutrino, wLE_ISR and OPL) 1.0 - rev 2

Go to download
Overview Extra info Updates (2) Reviews (2) History Discussion
I would like to run everythings from HDD. Can you give some details where do I need to modify the code? Another question what kind of filesystem do I need to use on HDD (uLE 48Bit format wit +OPL partition or exFAT)?
 
dukejp said:
Piensas agregar soporte a HDD pronto?
Click to expand...
Lamentablemente no tengo como realizar pruebas, si algún día consigo una PS2 Fat con disco le agregare soporte a RETROLauncher, en teoría debe ejecutarse sin problemas, es mas viable que alguien edite el código y le agregue soporte.

Unfortunately I don't have a way to carry out tests, if one day I get a PS2 Fat with a disk I will add support to RETROLauncher, in theory it should run without problems, it is more feasible for someone to edit the code and add support.

BeLANzO said:
I would like to run everythings from HDD. Can you give some details where do I need to modify the code? Another question what kind of filesystem do I need to use on HDD (uLE 48Bit format wit +OPL partition or exFAT)?
Click to expand...
Simply change all references to "mass:/" to that of the hard drive, both in the ".lua" files and in the Retroarch configurations "retroarch.cfg" and it should work.
In fact, almost all "RETRO Launcher" settings refer to its launch location automatically, except for some searches where the address "mass:/" is expressed.
In theory, you should be able to run it from any Enceladus-compatible device.
 
Last edited by a moderator:
adannan said:
Hello
I will be testing the models SCPH-70012, SCPH-77001, SCPH-79010

I also have some 90,000 saved
Click to expand...
Thank you very much, it would be very helpful to me.
So far I have received some error reports in "90xxx" but since they are not detailed I don't know if they are errors in the code or in the installation of the program.
On the PS2 FAT models I am interested in knowing if the shortcut system works with the HDD, that would also be important.
Thank you very much again.

ZjemCiKolege said:
Its possible to emulate ata0 with file in neutrino?
Click to expand...
From what I saw it is possible (it says so in the neutrino documentation), however I did not apply any of that to RETROLauncher because I have no way to test it, just add a system for direct access to games on HDD (ata - experimental).
 
Last edited by a moderator:
Boon Tobias said:
Thank you very much, it would be very helpful to me.
So far I have received some error reports in "90xxx" but since they are not detailed I don't know if they are errors in the code or in the installation of the program.
On the PS2 FAT models I am interested in knowing if the shortcut system works with the HDD, that would also be important.
Thank you very much again.


From what I saw it is possible (it says so in the neutrino documentation), however I did not apply any of that to RETROLauncher because I have no way to test it, just add a system for direct access to games on HDD (ata - experimental).
Click to expand...
Okey works but its possible to implement game id support for sd2psx/memcard pro2?
 
Boon Tobias said:
Lamentablemente no tengo como realizar pruebas, si algún día consigo una PS2 Fat con disco le agregare soporte a RETROLauncher, en teoría debe ejecutarse sin problemas, es mas viable que alguien edite el código y le agregue soporte.
Click to expand...
I can make it if you move the project to github. where everything will be easier to handle. since supporting APA HDD requires modifications to the enceladus executable itself.

if it is EXFAT hdd then just loading the corresponding IRX will suffice

TnA said:
The app needs to write to history for PS1 & PS2.
Click to expand...
nah. waste of time and bloating the ELF.

Better wait for the IRX driver that will be shared by sd2psx and memcardpro2 project
 
Last edited:
How should the IRX be "smaller"?
I would very much argue, that this would bloat it MUCH more.
 
TnA said:
How should the IRX be "smaller"?
I would very much argue, that this would bloat it MUCH more.
Click to expand...
we dropped the rpc approach and went with the fileio device route.

the IRX is less than 10kb and already offers a much wider set of utilities without even needing rpc...
 
Interesting, but but how big is the overall project again? IMO, that "bloating" argument is moot right from the start AND third, history-writes update the towers on ANY card and is not SOLELY made for MemoryCard-Emulators, which the protocol&IRX are...!
 
El_isra said:
I can make it if you move the project to github. where everything will be easier to handle. since supporting APA HDD requires modifications to the enceladus executable itself.

if it is EXFAT hdd then just loading the corresponding IRX will suffice


nah. waste of time and bloating the ELF.

Better wait for the IRX driver that will be shared by sd2psx and memcardpro2 project
Click to expand...
Thanks for the information, there are things that are beyond my knowledge, I will try to take it to github so that whoever wants can improve it.
I tried to load IRX from Enceladus but couldn't, I thought it was easier to compile it with the IRX already integrated.
But as soon as I can I will see it. Thank you.
 
Boon Tobias said:
Thanks for the information, there are things that are beyond my knowledge, I will try to take it to github so that whoever wants can improve it.
I tried to load IRX from Enceladus but couldn't, I thought it was easier to compile it with the IRX already integrated.
But as soon as I can I will see it. Thank you.
Click to expand...
assuming youre using latest enceladus the usage is pretty simple

Code: 
result, id = Sif.loadModule(path, argc, argv)
argc and argv are optional

most of the modules will be successfully loaded if result is not equal to 1 and id is not a negative number
 
El_isra said:
assuming youre using latest enceladus the usage is pretty simple

Code: 
result, id = Sif.loadModule(path, argc, argv)
argc and argv are optional

most of the modules will be successfully loaded if result is not equal to 1 and id is not a negative number
Click to expand...
I am using the build from 02/10/2024 which is on github, if I remember correctly it was a version compiled by you.
Great, as soon as I can I'll put it into practice.
I was calling it like this: "System.loadModule(path)" but now I'll see how it goes with that code you gave me.
Thank you so much.
 
@Boon Tobias Update/Upgrade/Port This AWESOME Tool to use them on ps3/ps4 because the ps3/ps4 use the games of ps2,psx,and all emulators only one by one! and this awesome tool ported and upgraded to ps3/ps4 is the retro homebrew need to load retrogames on actually systems!

Thanks for this toll and upgrade them captain!!
 
oleguer said:
@Boon Tobias Update/Upgrade/Port This AWESOME Tool to use them on ps3/ps4 because the ps3/ps4 use the games of ps2,psx,and all emulators only one by one! and this awesome tool ported and upgraded to ps3/ps4 is the retro homebrew need to load retrogames on actually systems!

Thanks for this toll and upgrade them captain!!
Click to expand...
Hello, thank you very much.
Unfortunately I don't have a PS3/PS4 to try it and if I did I would have to see if there is a tool according to my limited knowledge.
But I understand that Retroarch is available for both consoles without the limitations of PS2, so by supporting GUI themes and covers can be applied.
So something like RETROLauncher doesn't make much sense on PS3/PS4 since Retroarch is much more comprehensive for collections of multiple retro systems in one place.
 
I copied the elf + title.cfg to the MC1 for Retrolauncher. I need to copy more files to the MC1 in case there are problems with my USB Flash Drive and I lose the files and folders. I don't know how to create new folders and the path to recognize the games in the emulators.

To use POPStarter with games on the HDD, MX4SIO, network and USB, is it necessary to create it again separately from the Retrolauncher?
 
You must log in or register to reply here.

Similar threads

Back
Top