5.19 running on RPCEmu 0.8.9

Hi there
I’ve decided to have a go at running 5.19 on RPCEmu v0.8.9 but having a bit of difficulty getting it to run correctly.
I got 4.02 running, I updated the boot structure, System files etc..
The most success I have had is when I run the Recompiler version.

I press the Y to softload, it seems to initialise a whole lot of modules but then it returns to the main RISC OS Banner and states:
“Error: Internal error: abort of data transfer at &00012A5C (Error number &80000002) and is at the star prompt.

When I enter the desktop it does appear but applications will not run (‘Application may have gone wrong error’ message) and the boot has obviously not run.

anyone had any success of a way round this? I’ve tried lots of different CPU, DRAM and VRAM combinations to no avail.

any help would be appreciated.

You can use the 5.19 rom immediately, no need to first load 4.02 and than softload 5.19.
The non Recompiler version should work: http://www.marutan.net/rpcemu/manual/romimage.html

If you started off with a RISC OS 4 boot sequence and then added the RISC OS 5 sequence on top of it then there’s a good chance that there’s still some non-32bit RISC OS 4 stuff hanging around and causing problems. I’d suggest ditching the RISC OS 4 boot and starting off with a clean copy of the RISC OS 5 one.

I think there are plans to make the boot sequence more softload-friendly, but I’m not sure if anyone’s currently working on it.

I did make some additions to the ROOL !Boot as it stood a few months back. It basically adds a RO400Hook to !boot that can handle RO4.02 and RO5.19. I currently have it installed on my RiscPC and on RPCemu on my laptop. It also adds an Apps26 directory so you can hide non 32 bit apps away when running 5.19 but use them under 4.02. Another tweak is that it uses HostFS to tell if it is on real hardware and if it is it doesn’t try to init the network.

Shout if you want to give it a try!

Have a RPC running duel-boot – 4.02/5.19/Net100 – works well.

Probably you have a utility prog that is not 32bit (perhaps it would be wise for the OS to use ROL’s 32bit check).

Open ‘Utils’ and make a new DIR ‘26bit’ and shift all the Utility progs into it.
Re-boot and see which programs are called for – and check/replace them as required.

Have a RPC running duel-boot

Is this where two operating systems have a sword fight to decide which one gets to boot?

Is using StubG with the Softload program possible?
ie – so ‘Softload’ could be run from the Run file – without having to load extra modules.

I presume ‘AcornSSL’ 32bit is not available – ‘!Phoenix’ uses it – log on with ROOL.

Sorry Dual not Duel – could always add a RND function to the startup code – see which OS get the go to for launch :-)

Thanks for the helps guys.
Right, I decided to do the clean Boot.
Copied the Boot and Softload over from the Software page, but still having problems.

It complained about not finding CallASWI, so I copied it into 310 folder from RO4 system folder.
It complained about not finding CLIB, so I copied it into 310 folder from RO4 system folder.

Now the error message on the RISC OS Banner screen is Message token * not found (Error number &AC2)

Does not even get to the ‘Do you wish to Softload?’ something is amiss!

EDIT:
I forgot to mention that the !Boot file for !Internet needs fixing; it read X IconSprites. The X needs removing as it brings up an error.

You can use the 5.19 rom immediately, no need to first load 4.02 and than softload 5.19.
On your host (Linux/windows e.d) find deep in the !!Softload directory the file “riscos”, copy that to rpcemu/roms/ROM.

Thanks, I think I needed my hand holding. I never quite grasped the fact that you could Boot straight to RO5 from cold. duuuh!

Anyway, After doing this and changing the CPU from 610 to StrongARM (I was getting the ofla error message) it now works.

Thanks ever so much. Look forward to seeing all the improvements over RO4.02.

@Colin Ferris: “Have a RPC running duel-boot – 4.02/5.19/Net100 – works well.” What happens to your 4.02 HardDisc4 under 5.19?

I’ve got ROS 4 working fine using the RPCEmu and had a fiddle with it.
However when I try ROS 5, I down load the “Softimage”..

cp soft/\\!SoftLoad/riscos ~/rpcemu/roms/rom

I then get a window that flashes continually saying:
“Internal error: abort on instruction fetch at &EC112C70”

I’ve copied the HardDisc4 stuff but I can’t access it as it seems it can’t use hostfs

Any help appreciated

HI there
I think you are running in to the same problem I was.
It turns out that you do not need to softload RO5 over RO4 for it to work once you have the Boot downloaded.

Assuming you only want to run RO5 going forward these would be the rough steps I would follow:
1) Get RO4 working on RPCEmu
2) Download the RO5 HardDisc zip file
3) Download the IOMD Softload tool zip file
4) Load RPCEmu and boot into RO4 as per usual
5) Move your current Boot folder to another folder (for safe keeping)
6) Unzip the harddisc zip file to the root folder of your hostfs folder (using RPCEmu)
7) Unzip the Softload zip file and find the rom file from within it. I think it is called ‘RISCOS’ (Using RPCEmu)
8) Exit RPCEmu
9) In host platform go to the Rom folder and move the current RO4 RISC OS rom file to another folder
10) Copy the RO5 RISCOS rom file you unzipped in step 7 to the Rom folder
11) Restart RPCEmu and it should boot into RO5 without problems

If you run into problems you may want to check the following:
a) RPCEmu Settings are StrongARM, 128MB DRAM, 0MB VRAM

Hopefully that should get you going. Let us know how you get on. It’s a lovely little OS.

Still Exactly the same problem, I can’t be bothered at this time to get it to work (I’m fasting at the moment so patience and thinking is difficult) – it really isn’t worth the effort.
The reason being I have a Pi with RISC OS on it :-D, I’m just waiting for my HDMI-DVI connector to come then I can plug it into my monitor rather than my TV.
It is a great OS, I started using Arthur on an a310 many years ago, then got an a3000 and remember upgrading to 4MB of ram and an arm3.
Those were the days :-D

Once I have a little more patience I’ll get it working! Thanks for the walkthrough, I probably did something silly.

Unziping in linux probably wasn’t a good idea….

I’ve got a little further, I got it to boot into the desktop by booting of the hostfs filesystem.

I extracted the harddisc image (using the self extracting image) onto the hostfs disc, then copied the contents to the root inside RPCEMU.
Then I rebooted and reset the cmos, and did:
*configure filesystem emufs
*configure boot

Now it boots into the desktop fine, and I see RISC OS 5 – but I still have that error window going mental “Internal error: abort on instruction fetch at &EC112C70”

I set the settings to:

mouse_following = 1
cdrom_type = 0
cdrom_enabled = 0
blit_optimisation = 0
refresh_rate = 60
stretch_mode = 0
sound_enabled = 0
vram_size = 0
cpu_type = SA110
mem_size = 128
ipaddress = 172.31.0.1
[hostfs]
; = When you want to use EmuFS under RISC OS:
; = 1. Create a directory hostfs in emulator dir
; = 2. Remove the underscore in above section identifier
hostfs.drive0.name = Boot
hostfs.drive0.path = ./hostfs
hostfs.drive0.permissions = read,write
hostfs.drive1.name = Home
hostfs.drive1.path = ~
hostfs.drive1.permissions = read
hostfs.boot.drive = 0

All sounds very much like the problem I was having. If I recall correctly, I believe it was a setting issue with RPCEmu.

I use Windows, and have just downloaded the harddisc4 self extracting file and the current IOMD zip file, and got RPCEmu to work first time with it, so I am happy that nothing has broken with the overnight ROMs on the website.

I am 99% certain it is a RPCEmu setting problem.

My rpc.cfg file settings (due to be on windows) may be different, but here they are:
mouse_twobutton = 1
network_type = off
mouse_following = 0
cdrom_type = 0
cdrom_enabled = 1
refresh_rate = 60
stretch_mode = 1
sound_enabled = 0
vram_size = 0
cpu_type = SA110
mem_size = 128
ipaddress = 172.31.0.1
cpu_idle = 0

On Windows we have two exe files; Interpreter and Recompiler. Try both;

Also worth changing the cpu type, mem-size and vram_size values until one works.

You are 99% there. Don’t give up.

forgot to say, when in RISCOS 4 at the beginning, isn’t the command *configure filesystem hostfs instead of emufs?

That configure command is at my first attempt to boot RISC OS 5.
I boot it and then have to drop to a supervisor prompt enter the two commands to make it boot off emufs
using hostfs makes it say something like hostfs doesn’t exist

If I try copying the files to the adfs internal disc it still gives the same error, but doesn’t boot to the desktop.

Setting the boot method using hostfs in riscos 4 or using emufs in ro5 doesn’t make a difference, it has the same outcome :-(

What is in rpcemu\poduleroms ?
There should be: hostfs,ffa SyncClock,ffa and hostfsfiler,ffa

And what does, in RISC OS, give *rommodules?
The last lines should give:
1 Podule 0 RPCEmuHostFSFiler 0.03 Active
2 Podule 0 SyncClock 0.11 Active
3 Podule 0 RPCEmuHostFS 0.07 Active

And the harddisc4 file was settyped to ‘Utility’ and then doubleclicked?
This should has extracted all the files to a new folder. You then move all the files within to any empty root hostfs folder.

Just want to make sure the files extracted okay with all their fileypes in tact.

Wouter:

In poduleroms I have:

malcolm@desktop ~/rpcemu/poduleroms $ ls
emufs.1 emufs.2 emufs.3

And *rommodules gives

1 Podule 0 EmuFSFiler 0.04 Active
2 Podule 0 EmuFSRes 0.08 Active
3 Podule 0 EmuFS 0.15 Active

Alan:

Yes i settyped to utility and double-clicked, then moved files up a directory (to the root of hostfs)

sorry to hear that you’re still having problems mate.

It might be worth renaming the !Boot folder to a something like !temp' so it does not run on Boot up

If the error message does not appear, then the issue is with something it is trying to load during Boot process once it reaches the desktop.

If the error message does appear then at least we know it’s something to do with the RPCEmu set up.

Sorry, no definite solutions for you here. Hopefully we will get there soon.