RISC OS 5.30 Issue

I just updated to 5.30 and I get a Internal error: abort on data transter at &20244620 (Error number &80000002). Removing Geminus module clears that error but then I get another error: SWI name not known 187.

I tried *unplug bootfx and that did nothing, I still get the splash screen. Saved the CMOS as well.

One other thing I am seeing is that the Boot Loader folder is showing some other folder and not my PiBoot partition. My config.txt in the Boot Loader folder was different than the PiBoot partition’s config.txt, is there a way to fix this? This might be why when I save the CMOS the changes aren’t saved where they should be?

One other thing I am seeing is that the Boot Loader folder is showing some other folder and not my PiBoot partition.

I sounds like you’ve broken the link between !Boot.Loader and the PiBoot partition: applications such as SystemDisc or Partition Manager set these up so that they point to the same place on the SD card, but it’s all to easy to mess this up by accident.

If you’ve got SystemDisc, use that to create a new boot SD. It will prompt you to populate the PiBoot partition and the FileCore drive: you can use the contents of your existing drive.

Be very careful when populating the FileCore partition on the new SD card: you must not copy !Boot.Loader, as that would break the link between !Boot.Loader and the PiBoot partition. Copy the other files and directories inside !Boot (!Boot, !Help, !Run, Choices, Library etc.) to the new !Boot, instead of just dragging the !Boot directory itself. Tip: After you’ve finished copying everything to the SD card, click on the “Refresh” button in the SystemDisc window. That will tell you if the SD card format is still good.

Partition Manager can also be used to create a new boot SD, but it will populate it with a “default” RISC OS build. However the partition layout will be correct, so – provided that you don’t try to overwrite !Boot.Loader – getting all your stuff onto the new SD should be straightforward.

Thanks.. it looks like I used PiTools at some point. It looks like the Boot Loader directory has the firmware contents from that program. I will try. I had to wipe my PiBoot partition as my machine locked up and when I restarted, it wouldnt boot.

I think it might help us if you could describe your setup (ie. Pi board, and what discs you have attached). PiTools can’t/doesn’t create or mess with the !Boot.Loader directly (although it will modify config.txt file in an existing !Boot.Loader to enable/disable features). It will try and detect the best !Boot.Loader partition for the system (if more than one is found), but in that scenario (ie. you have two !Boot.Loader) you’re probably not in the clearest/most well-defined place initially.

This is why I ask about the disk setup – which device does the Pi boot itself from (SD?) and where does your !Boot lie? It may be the same (one SD card for both) – that’s the “normal” Pi setup. However, you may be using an SSD via USB or something, which makes things a touch more complex, esp when it comes to CMOS and date/time.

Feel free to drop me a support email, though – as a PiTools owner, you’re welcome to tech support from me via email etc.

Good luck :)

PS, the firmware supplied with 5.30 is newer than that supplied with PiTools. Use those Start4 (etc) files instead of the ones in the PiTools zip.

Hi Andrew,

It’s a Pi3b that I used PartMgr to partition the SD card to use the entire card. I think I will use System Disc to fix the issue, thanks for checking in. PiTools is great, I just happened to notice that the files in Boot Loader were the ones from Pi Tools.

Anybody long back to Acorn’s days, where they delivered flawless ROMs?

PS: Plurality isn’t always a plus.

I refer the above poster to RISC OS 3.0.

I’d say 3.7. Could sqibble about it over at Egham Hills, if you’re there.

where they delivered flawless ROMs?

Ha ha.

Hahaha.

Nyaaaahahahahahaha.

Okay, things were a lot better back then then some of the crap being shovelled out these days, but that isn’t because Acorn were awesome but rather nowadays we’ve been conditioned to accept abject mediocrity.

As for flawless ROMs, let me know when you find one because they all had bugs. Just, thankfully, not much in the way of show stoppers.

But, then, FileCore in use or Broken directory or TaskWindow suffering a bout of projectile diarrhoea if you try to stop the compiler mid-build, or MessageTrans losing its marbles “because something”, or that one weird quirk that causes every application to die fatally one after the other until you’re looking at a blank grey screen (that oddity is still around these days).

I must have just been dreaming ROMPatch

I must have just been dreaming ROMPatch

The wrong cheese after midnight will get you like that every time. Always gremlins

And ROMpatch exists because there were…

<drum roll>

Bugs!
In the ROM!

Loops and vectors and bugs, oh my!

I finally got a new version of SystemDisc installed on my Pi. I was able to delete the old PCLoader directory and create a new partition and copy my files over. I’m seeing now an issue where I unplug a module (BootFX) and then save CMOS. It’s saving in the PCLoader directory but when I reboot, BootFX is active. Am I doing something wrong? I’m having the issue with Geminus and BootFX..

Post the contents of your CONFIG/TXT file. It sounds like it might not have the right path to the CMOS file.

disable_overscan=1
fake_vsync_isr=1
gpu_mem=64
init_emmc_clock=100000000
ramfsfile=CMOS
ramfsaddr=0x50800
kernel=RISCOS.IMG
[pi4]
enable_gic=1

Are your CMOS and RISCOS/IMG files in the same directory as CONFIG/TXT? If so, then I can’t see anything wrong :(

OK, figured it out. When I saved the CMOS to file, it was saving it to the !boot.Choices directory. I deleted the CMOS file on the boot partition and copied over the newly created one, and all is good. Still getting an “SWI name not known 187” error on startup. Not sure what its complaining about.

Figured it out. It was ReDHCP.