The above video goes away if you are a member and logged in, so log in now!
Problem with the language file.
Problem with the language file. –
Excuse me if my english fail!
Ok, i'm trying to use an pt-BR language file with my uLaunchELF 4.38. I don't whant to select the language file, i want to launch the program already with the language file applied. But it is not working. To test it i just toke the original lang.h file from the sourcecode and modified the line LANG_FILE = from the LAUNCHELF.CNF to LANG_FILE = lang.h.
Then i put the following files in my pendrive:
I did the procedures to run the boot.elf file from my pendrive and the following message appears:
If i press OK or CANCEL the uLaunchELF will run normally in english.
LNG loading failed with error_id==2 and test==0
The latest string index (possibly invalid) was 0
This was a failure to open the file:
Use either OK or CANCEL to continue (no diff)
First what i did wrong? How i can make it work? And what is the use of the OK or CANCEL choice if they do the same as it says (no diff)
You have two methods.
First: just replace your english lang.h by yours, and compile the program.
Second: place i.e pt-BR.lng on your pendrive, choose this file in configurator and save changes.
You specified an incomplete path string for the language file.
Originally Posted by deadoverlord
Such a path string must include a device/drive specifier as well as the normal folder names and path/folder separators, in addition to the file name itself. Additionally, you can also choose to use the pseudo-drive specifier "uLE:" to signify a search in three standard locations, these being:
1: The same folder that the uLE elf was launched from.
Here is a practical example of how this may be used:
I sometimes use a swedish language file made by 'taonaut' and named 'Svenska_taonaut.lng', and this is stored inside the same folder as the uLE elf which is to use it. So for this case I use the following variable definition:
LANG_FILE = uLE:/Svenska_taonaut.lng
The main benefit of using the pseudo-drive designation "uLE:/" is that the CNF does not need to be modified if moving the folder containing this instance of uLE to some other medium or subfolder, as the path will automatically relate to the current elf location.
That is probably what you intended when you used no drive specifier at all, but such relative path strings are not valid in any PS2 file operations (unlike those of a PC).
Several different error messages requiring a user response to continue use a common subfunction (int ynDialog(const char *message)) so as to save code space. It would be wasteful to add yet another similar function just because this particular case does not need to react differently depending on what the user response is. (This is needed for other cases where this subfunction is used.)
And what is the use of the OK or CANCEL choice if they do the same as it says (no diff)
Best regards: dlanor