Can't boot ROOL in RPCEmu

Hi!

I just added rpcemu to pkgsrc and wanted to test it with ROOL. I’m doing so on macOS, so I quickly realized that I need the following patchset: http://www.riscos.info/pipermail/rpcemu/2018-November/002703.html

I followed https://www.riscosopen.org/wiki/documentation/show/RPCEmu%20and%20RISC%20OS%205%20on%20Windows and also copied over the poduleroms for HostFS. I executed the self-extracting file as mentioned in the howto before and copied it over to HostFS, but when I then try to reboot, I get the following: https://matrix.nil.im:8448/_matrix/media/r0/download/nil.im/KGLrNAsKyBEtERuZMrjUegCZ

Any ideas?

I followed https://www.riscosopen.org/wiki/documentation/show/RPCEmu%20and%20RISC%20OS%205%20on%20Windows

Surely you mean you followed the instructions in RPCEmu and RISC OS 5 on Mac OS X

BTW. When including a link if you precede the link with "RPCEmu and RISC OS 5 on Mac OS X": it presents something more readable like the Mac OS X text in the link I’ve just done.

No, I followed the one for Windows as that’s what I found using Google, and since I was compiling RPCEmy myself :). I mean, they are pretty much equal anyway, minus locations of where to store things, and which binary to download (which I did not do anyway).

There is a later patch for RPCEmu 0.9.3. A mac binary build of 0.9.3 with source here. and the patch.

A command line build here worked, RISC OS starts up as expected. I don’t know what is going wrong in the above example.

I can’t help with pkgscr.

I mean, they are pretty much equal anyway, minus locations of where to store things, and which binary to download (which I did not do anyway).

You mean apart from the Mac page referencing v0.8.14 and the Windows page referencing the current v0.9.3. as in the links supplied by David.(base build and patch)

David, might be worth editing the Mac page to point to the 0.9.3 build and patch to assist other Mac users.

I think this is a good example of why this site shouldn’t try to be the one-stop-shop for all things RISC OS that some people were suggesting yesterday.

Pointers to external sites, yes, they are very useful, but we ought to leave the detail over there, not try to helpfully reproduce it here.

I think this is a good example of why this site shouldn’t try to be the one-stop-shop for all things RISC OS that some people were suggesting yesterday.

I think it’s an example of evolution. When I created the Windows install page, back in 2013, step-by-step install information for RO5 on RPCEmu was pretty much non-existent¹.
The same held true for Linux and Mac.

I recently contemplated the option of modifying the page to simply link to the RPCEmu site with specific link to the bundles page. That’s when I realised that the assisted install instructions are still limited to RO 3.71² so the only easy install for RO5 is a bundle over 1Gb. So, debatable whether the RPCEmu site offers all that is required.

Now we look at the Mac install covered by this thread – the only working install is on another site, linked out from the RPCEmu site. I have no idea whether that link is for a patched version or whether further patching is required.

Linux – I don’t think anyone ever felt what they had in the way of information was any better than the compiling instructions on the RPCEmu site.

I am not one for re-inventing the wheel nor change for changes sake, but if the wheel doesn’t exist (and it didn’t) then I will look for something that works.
The wheel exists now, but I’m not sure it’s the right size.

In summary, I disagree that the situation currently merits any change in the ROOL wiki pages beyond some small editing.

¹ Unless you want to use a Risc OS Direct image bundle you’re still out of luck for an assisted RO5 install. The bundle uses RO5.27 (unstable) my document (with modifications from Sprow) has consistently recommended the stable revision.

Thanks for the newer rpcemu patch – I updated the package in pkgsrc to use it. However, unfortuntately, I am still faced with the same error, despite following the instructions again from start.

Is there any way I could debug this? “Error: Internal error” really doesn’t say much.