Would be very strange if this commit went through without testing the basic feature. Maybe something in the config naming changed or maybe now it must be a specific partition if it's HDD? Where exactly is your config file located on the HDD?@Grahf I know, that is why i mention about it:
It's a homebrew stuff, anything can happens, including bugs\problems, etc.Would be very strange if this commit went through without testing the basic feature.
Config on HDD always was stored in:Maybe something in the config naming changed or maybe now it must be a specific partition if it's HDD?
Where exactly is your config file located on the HDD?
Does it also not search for the config on the internal HDD, when it is started from there?
...does it happen when you start OPL from USB or internal HDD or in both cases?
Changed how devices are selected for loading/storing config files.
When loading:
1. Check memory cards.
2. If config could be loaded, try the device that OPL was booted from (supported devices only).
3. If config could not be loaded, try all supported devices.
4. Default to memory card, if no config file could be loaded.
When saving:
1. Try the device that the config file was loaded from.
2. If config could not be saved, try the device that OPL was booted from (supported devices only).
3. If config could not be saved, try all supported devices.
4. Give up.
Almost the same "mechanism" was previously.
The only downside is that currently when "conf_opl.cfg", "conf_network.cfg" are not on HDD, settings will not be saved,
when there is no another device (MC o USB).
OPL 1206 or higher will not creates these files and user will get "Error writing settings...".
Currently no matter from what device OPL was launched, if there are settings on MC, this device has the highest priorytety, not the device that OPL was launched from.
To be add, there is also no way to load translation from other device that MC:
http://www.psx-place.com/threads/op...leases-language-pack.20547/page-2#post-149522.
Previously, it would never consider where it booted from and will always fail to save anything if you:
Connecting a USB disk or memory card later on, would not fix this. The only solution at that point, was to reboot OPL.
- Do not have a HDD unit installed.
- Did not connect a memory card nor USB disk to the PS2, when OPL was booted.
This is now styled similarly to how FMCB locates USBD and USBHDFSD, as discussed previously. There cannot be an option for selecting the save device because you need to load that file before OPL can load the setting from it.
Now, you can choose what device you wish to save on, by putting OPL on the device that you want to save on. If you saved on the memory card before, then it will continue to use the settings there, for backward and forward compatibilty. If you no longer wish to keep your settings there, either move the files to the desired device (memory card, USB disk or the HDD unit) or delete the OPL saves directory (and OPL will start over).
I'm not sure what you mean. It sounds like something is not working, but it will fail if there is no device available to save to.
Is this before or after the fix was made (commit c8c4205)? Other than because of that bug, you should never get that error, unless you either have no usable devices connected or your hardware has some problem.
Yes, but having the settings there also means that the user saved there before. If the user saved to a device before, we shall not move it on behalf of the user.
This is a different problem, not related to configuration loading. Support for languages and fonts will load their files independently of the main OPL configuration files. I added support for USB disks and the HDD unit for font-loading, quite a long time ago.
But okay, we can do something about loading the language files from other devices as well.
One other thing is that OPL is creating OPL folder in mc? (e.g. mc?:/OPL), with icons, even if it won't be using it (settings are on HDD).
When there are no settings ("conf_opl.cfg", "conf_network.cfg) on HDD (hdd0:/+OPL/):
OPL will not save settings, giving an error:
When I have these settings in (hdd0:/+OPL/):
I can save settings:
Until OPL 1200 I can save setting even without "conf_opl.cfg", "conf_network.cfg on HDD.
So if these files will not exist, OPL will create them and the settings will be saved.
I'm not entirely sure with what rev this problem has started 1206, 1214 or 1218.
BTW I have also notice that when I want to power off PS2 with a button combination on PAD (L1+L2+L3+R1+R2+R3),
additional red debug color has been added.
Please wait for https://github.com/ifcaro/Open-PS2-Loader/pull/162.
I originally wanted to also change theme and language support to allow files to be loaded from other devices as well, but there might be a possibility that the rest of the UI depends on these two to be initialized first... and I cannot prove/disprove that within the time I have now.
For at least now, you still have to keep your themes and language files there. OPL was clearly originally designed to only support the memory card for settings.
Right now, there's no code that will tell OPL to not create that save, as it cannot tell whether it needs it or not. It will always create the folder when it checks the memory card.
That part was added to stop the device before the PS2 is shut down: https://github.com/ifcaro/Open-PS2-Loader/commit/f661fe286895a3f0ef6ebe8ba3188433d06d0157 and https://github.com/ifcaro/Open-PS2-Loader/commit/07b6677e6a4a45f2b8f448b4549865132ce6ca6f.
Both are related to this discussion: https://github.com/ps2dev/ps2sdk/issues/85
I can confirm this, I've got themes on both USB and internal HDD and they load fine. I think it's just language files and fonts related to them that only load from MC?From what I remembered, themes can be loaded from USB, however I never tried it from HDD.
It's only a problem on HDD, that OPL fails to create new configuration files.
There shouldn't be any troubles with that on USB or MC.
Soon we will have Christmas, so there is no hurry, we can continue later.
Theoretically it is only few KB on MC, but on 8 MB MC, every KB counts.
Maybe soon we won't be needing to have any config on MC,
so we also will not need empty OPL folder with only icons for PS2 MC Browser.
From what I remembered, themes can be loaded from USB, however I never tried it from HDD.
I can confirm this, I've got themes on both USB and internal HDD and they load fine. I think it's just language files and fonts related to them that only load from MC.
It looks that way in the code but nope it doesn't.The theme config file has to be stored on the memory card as well, doesn't it?
I'm not sure why it does not fail for you, but it was a fact that the same mistake also affected USB devices.
Indeed. Merry Christmas!
The theme config file has to be stored on the memory card as well, doesn't it?
The same limitation applies to languages.