DDE27 on RISC OS 4

I installed DDE27 on RISC OS 4 and found the following problem: AcornC/C++.Developer.!SysMerge, which should be executed after extracting the package, shows an error because it tries to RMEnsure BootCommands 1.25, which is not available in RISC OS 4.02 (1.19 is the version in ROM). It then tries to RMLoad BootCmds from its own !System.310.Modules, but again fails because it is just not there.

The obey seems to run fine with BootCommands 1.19, so I just commented out the line.

BootCommands 1.25 (from 2002) corresponds to when the ‘X’ command was added (the CVS commit message suggests that it was previously available as a transient utility located in !Internet). So chances are it’s just trying to make sure you’ve got ‘X’ available.

So then, the later BootCommands module should be included in the Developer !System.

So then, the later BootCommands module should be included in the Developer !System.

Perhaps ROOL were expecting people to install a copy from somewhere else – like maybe !PlingSystem ?

So then, update the docs! But the workflow would be strange: extract the module from the !System you downloaded and put it into the Developer !System at the right location so that the obey script finds it…

Really, it is just a damn bug. Easily work-aroundable, but still a bug.