Ticket #595 (Open)Mon May 15 13:40:57 UTC 2023
Boot choices from the ROM resident OS may not work with the softloaded OS
| Reported by: | Cameron Cawley (3514) | Severity: | Normal |
| Part: | RISC OS: Boot sequence | Release: | |
| Milestone: | Status | Open |
Details by Cameron Cawley (3514):
When softloading RISC OS 5.29 over RISC OS 5.28, !Configure adds additional flags to the ThemeSetup file. This will cause a “Parameters not recognised” error when booting RISC OS 5.28, before the softload menu can be reached.
Changelog:
Modified by Sprow (202) Sun, October 22 2023 - 07:34:48 GMT
- Summary changed from New WimpVisualFlags parameters cause issues with softloading to Boot choices from the ROM resident OS may not work with the softloaded OS
Renaming this to describe the more general case, to avoid a rash of tickets all describing basically the same thing.
(Item 1)
New WimpVisualFlags parameters cause issues with softloading. Since the ThemeDefs are in PreDesk, and PreDesk is run before the SoftLoad tool, it may in general encounter Wimp theme settings which were written out by the more recent OS which were not recognised on the ROM OS.
Modified by Sprow (202) Sun, October 22 2023 - 07:39:20 GMT
(Item 2)
Because !Boot.RO*Hook.Res is added to BootResources$Path in PreDesktop, which is set up differently depending on what version of RISC OS you first boot from, double clicking on !Boot will start the RISC OS 3.x !Configure application regardless of which version of RISC OS is actually running. This leaves a number of configuration options inaccessible in a softload environment.
Moved here from Ticket #597 as this is just a different manifestation of the issue I explain in detail in
https://gitlab.riscosopen.org/RiscOS/Sources/Sy…
whereby the Choices copied in for 3.70 are being used with 5.xx which is not expected to work.
Modified by Sprow (202) Sun, October 22 2023 - 07:43:21 GMT
(Item 3)
RISC OS 3.x !Configure writes most if not all non-CMOS settings to !Boot.Choices.Boot.Tasks.Configure, while RISC OS 5 !Configure uses separate files for different plugins.
Moved here from Ticket #598 as this is just a different manifestation of the same thing; there isn’t an issue with the old combined !Configure writing its settings out to a different place than the plug-in based Configure, because the Choices.Boot is tailored to the OS on which is was first run and isn’t expected to span multiple OS versions.
