!SysMerge / WindowManager

I’ve noticed HELP for WimpVisualFlags reports several message tokens (HWNMVF and SWNMVF) are missing on RO 3.71 after a !SysMerge, should !SysMerge include an updated Messages file for WindowManager?

I’ve noticed HELP for WimpVisualFlags reports several message tokens (HWNMVF and SWNMVF)

The WimpVisualFlags give help here.

Threading another bead on my neckless where you’d previously tripped up with a mismatched PreDesktop not killing BorderUtils, wondering where AcornSSL was, and unset path variables tripping up PinSetup I’m going to stick my neck out and guess you’re trying to manually load the Wimp with a plain RMLoad somehow.

That’s a sure path to failure. You must use the LoadWimp tool provided in the boot sequence (and, indeed, that’s exactly what the ROOL supplied PreDesktop does) as various extra tricks are needed to workaround bugs/differences between the ROM Wimps when killed.

I did spot the clipboard tokens never got updated so submitted a fix for that, which should be in today’s HardDisc4 download.

guess you’re trying to manually load the Wimp with a plain RMLoad somehow.

Thanks.

Not loading manually, as mentioned in the OP, I noticed it following a !SysMerge. I had to rollback Wimp soon after because of this issue, but I’ll grab the latest HardDisc4 and compare it against my post-!SysMerged !Boot to confirm how it’s loading Wimp.

EDIT: Having checked, PreDesktop I can confirm its loading Wimp via LoadWimp. I have however spotted there’s a Messages file in !Boot.Resources.Wimp which is probably the Messages file in question. I suspect it didn’t get updated when I copied HardDisc4 over as its marked as Protected – I’ll recopy it later and confirm that was the issue.

Comparing my PreDesktop however against HardDisc4, I can see it’s not been updated as HardDisc4 is reliant on Choices.Boot being blank on first boot, following an update. Essentially updating from HardDisc4 requires the contents of Choices.Boot to be manually deleted before rebooting.

I’m sure there’s probably an HardDisc4 update document that covers this which I’ve missed.

EDIT2: Replacing !Boot.Resources.Wimp resolved the issue.