OS5.25

I expect there is a really obvious reason why OS5.25 does not start on either the RPi3B+ or Titanium. The last OS5.23’s were OK, without ZeroPain.

What a good start!!

I expect there is a really obvious reason why OS5.25 does not start on either the RPi3B+ or Titanium.

You don’t say at what point in the boot sequence it stops which might be useful info for Jeffrey or whoever.

Right, now I’m home and just tried the IOMD 5.25 build in RPCEmu (least trouble reverting) I believe the answer to my question is “probably exactly where IOMD RPCEmu fails – i.e. before any listing of initialised modules and in fact before any screen display”

Broken right at the bottom. Did someone tweak something in the HAL across the board?

Edit:
I supose the good news is that I was moving from a ZeroPain build to ZeroPain build so that isn’t the issue.

Looks like ~270k of files have gone missing from ResourceFS, causing WindowManager to abort on startup.

Should be fixed now – looks like it was just the Wimp that was affected.

https://www.riscosopen.org/viewer/revisions/logs?ident=1523904380-581373.html

That works, OS5.25 is running on the Titanium. Thanks.

The ZeroPain module 0.07 in PreDesk does not load and the OS is in Compatibility mode. It does mean there is no way to log pains.

Nice quick fix.
I’m guessing that the original introduction of the bit you removed didn’t visibly break things on the build because nothing did a clean before the following build, then prep for 5.25 (and ultimately 5.24 stable) involved a clean so the non-build of the Wimp rather tatered things.