Lionel Debroux wrote:With reliable code execution, you can change the contents of the virtual memory translation table to map the boot1, if it's not mapped at the suitable place (0 or A4000000, back in the day) when the boot1.5 executes.
That is the problem. Nothing is mapped there.
How do I map it? I looked at some code in ControlX to map the second 32MB of RAM, but I don't understand how it works.