I'm not sure if this functionality already exists or not, I'm looking for support for Multi-game collections support, for things like the demo Jam Packs Sony made, and custom made game compilations.
Others have said they couldn't get mulit-game compilations to work in any version of OPL.:chinscrat
I've been trying to figure out what I'm supposed to use as the SLUS part of the game name for a Multi game compilation, for regular ISO use in the volca GUI rev 337.
There are multiple SLUS_xxx.xx files in the ISO, and I'm not sure which one I need to name the ISO to so that the proper one gets booted and all the games can be played chosen.
If this is not even supported in the GUI version or vanilla OPL .7 , just let me know and I won't worry about testing till it is. I'll also try by using the USB advance format and see if this works.
The regular ISO feature is just freaking cool :cool:though. I don't have to have the game taking up twice as much HDD space, or have to wait to install it via USButil.
Thanks again OPL team for the best homebrew since XBMC.:D
since hdl server is coming in, one feature would be nice
- auto start of the hdl server
- ability to start it via some button press anywhere from menu, or by holding some button as opl starts.
i suppose some people (like me) don't run hdl server when their ps2 is connected to tv. that would be a welcome improvement.
All proper PS2 discs should contain a SYSTEM.CNF file that defines to the console how to boot it. Such a file can be inspected in a normal text editor, including the one of uLE. The most significant entry in that file is the "BOOT2" directive which specifies the elf file to be launched. It's format is like this: "BOOT2 = cdrom0:\SCES_500.03;1"
Originally Posted by urbigbro
Here it is noteworthy that the separator between drive specifier and filename really is a backslash, rather than a forward slash as normally used for PS2 pathnames, and also that the ";1" appended after the filename is not part of the name proper, which for this case is only "SCES_500.03". (This example SYSTEM.CNF was taken from my SM3coder DVD disc.)
Best regards: dlanor
I am aware of the system.cnf having the elf file to be launched. Here is the problem, some of the custom compilations have a multiloader.elf file listed in the system.cnf. Whenever I have renamed the ISO to reference that e.lf it will not show in the network games list. Perhaps the ISO support was not designed to recognize file names that deviate from the SCUS_XXX.XX format.
Originally Posted by dlanor
I could try renaming the multiloader.elf to that format, but it may break the compilation, or require a rebuild of the compilation that may in turn cause the compilation to break.
Has anyone already successfully got any multigame demo disc, or custom compilation to work in any version of OPL yet?
Originally Posted by urbigbro
We check that the iso filename start with: 4 char underscore 3 chars dot 2 chars dot.
That is not really needed, it was only a quick way to ensure we could retrieve a valid startup elf name within the iso filename.
So what is the name of the elf in your case ?
If you want to make a test, you could do a little modification inside supportbase.c, comment everything into isValidIsoName method (line 41), and add the line below in place of:
Here is what is inside my system.cnf
BOOT2 = cdrom0:\5\MULTI.ELF;1
VER = 1.47
VMODE = NTSC
My ISO has the MULTI.ELF inside a folder named 5 on the root of the compilation.
In that self same directory there is a file named M.XML that list all the game names and game .ELF paths.
Let me know if there is any other infor you'd like from me. I have a few other custom game compilations, game demo discs.
If you happen to have UltraISO, you can try renaming the MULTI.ELF to SLUS_123.45 (or whatever number), then make a new SYSTEM.CNF with that number.
UltraISO allows you to "add" a file of the same name without messing up anything and then save it. I have edited a few like Scarface: the world is yours because it wouldnt install with USBUtil 2.0 unless i did. That works fine in OPL.
I dont know if it will work, but im going to try it with the Multi-disc ISO i have and hopefully it will work.
I just tried my multi that i used PS2Load to make them and they are now working with the above method. :) I tested it with Rev 300, i have 1 more multi, so i'll see if that one will work now too. :D
It also happens to be exactly the same requirement as used by USBUtil, which always fails to install an ISO using a BOOT2 elf that does not follow this pattern for its filename.
Originally Posted by izdubar
I haven't really checked the code yet, but it seems very clear to me that we can easily change this requirement to something else. For the names of real ISO files all we really care about is to have a certain indication of the point where the elf-name part of the string ends and the game-list-description part of the string begins.
The XXXX_YYY.ZZ format test does accomplish that, but is not really needed, as we get exactly the same result simply by looking for the second occurence of a period character, and using all string characters before it as elf-name and all those after it as game-list-description. This should work fine for all elf-names that contain exactly one period in the full filename of the elf.
The bug/limitation can also be eliminated from the routines using the USBAdvance format, since the problem is not inherent to it. USBAdvance itself does NOT have this limitation, which to my knowledge was introduced by USBUtil.
Best regards: dlanor
So why not try to parse the SYSTEM.CNF for the BOOT2 entry in this case?
For an installer like USBUtil, that is of course the obvious thing to do.
Originally Posted by jimmikaelkael
(And also avoiding the insane demand for "XXXX_YYY.ZZ" format which USBUtil imposes.)
But when OPL needs to handle a ton of ISO files (real ISO files I mean, not USBAdvance format), it could make the implementation very slow if it had to open each ISO file and extract its SYSTEM.CNF file, to find the BOOT2 value of every game to be added to the active game listing. This method simply isn't practical.
That is why (I guess) izdubar went with the method of prefixing the ELF name in front of the game description string (separated by a period) in how to construct each ISO filename.
This way there is almost no processing cost involved in extracting the elf name from the ISO filename, as needed for using it as prefix for accessing the _COV, _ICO and _BG graphics files from the ART folder.
I see no problem at all with how this is done by OPL at present, except that the parsing done to extract the elfname from the ISO filename should not require a strict string format, but should accept any valid filename characters up to the separator between the elfname and the start of the gamelist_string.
If that separator is to remain a '.' period character like now, then the separator test needs to look for the second such occurrence in the string, as the elfname normally contains one too. But that is the ONLY special character handling that the routine should do (except of course for the ".ISO"/".iso" recognition of the filename extension).
Best regards: dlanor