Iris: There still shared Unix Library clients active

Iris was working on two Raspberry Pi 4 5.28 systems.

But now both systems give the message stated.

I have no idea what I might have changed.

Where do I start?

Reboot, run Iris before anything else.

Iris wants a newer Shared Unix Library, but if anything is using an older version, it can’t run.

Thanks for that suggestion.

Having failed to get it to run, I dosnloaded a new Hardisc4 onto a new SSD. But I now get an error message saying that the Arm CPU strict mode is wrong.

But, the CPU item is missing from the Configuration settings on the new Harddisc4 download.

CPUSetup is Pi-specific and is therefore included with the Pi SD image, not the generic HD4 download.

So the Universal !Boot is not universal after all.

How much time has that wasted!

Where do I download a complete Hardisc4 image for the Raspberry P? I gave up messing about with partitioned SD cards a long time ago.

I’m not sure whether a complete image is readily available, but I’ve put CPUSetup here. Put it in !Boot.RO500Hook.Res.Configure.

Thank You for that – and previous post about the generic HD4 download.

I have now created my own HardDisc4 zip file from the “Complete RISC OS Pi SD card image” and the !Boot directory contains nearly 600 more files than there are in the generic HD4 download! They can’t all be Pi specific.

They can’t all be Pi specific.

There’s a whole pile of extra stuff on the RISC OS Pi SD. Very little of this is Pi-specific, but some of the software does add files to !Boot.

For example, the RISC OS Pi bundle includes PackMan, and PackMan stores a shedload of files in !Boot.Resources.!Packages during normal running (on my Raspberry Pi, !Boot.Resources.!Packages contains 165 files).

I am not talking about the extra stuff. I am not interested in that.

I just wanted a full !Boot which works on a Rasperry Pi.
Or, a note on the downloads section to warn people it is not complete.

So the Universal !Boot is not universal after all.

Ideally it should supply the CPU setup tool, and tailor what parts are active according to the processor in use.

I mean, the rotated loads stuff only applies to the earlier (original?) Pi, whilst whether or not to throw alignment exceptions should apply to most (all?) current devices. So there is a use for it.

Might also be a place to control what exactly happens if &0 is addressed (not strictly CPU, but it doesn’t really fit elsewhere).

One easy solution would be to host the extra components on the Packages server so that the user could download as much (or as little) as they want¹ while keeping HardDisc4 as general-purpose as possible. At first glance, the “must-have” items would be CPUSetup and Fat32FS, but there may be one or two others that I’ve missed.

Another approach would be to augment HardDisc4 with separate downloads for each hardware target (Pi-Resources, Iyonix-Resources etc.) – the user might download HardDisc4 and Pi-Resources, then merge the !Boot directories by means of a SysMerge obey file in Pi-Resources. Sample contents:

• “Pi-Resources” would contain CPUSetup and Fat32FS
• “Iyonix-Resources” would contain Fat32FS
• “IOMD-Resources” would contain… nothing at all.

I’m not sure what needs to be offered for OMAP, iMX6 (etc.) as I have never owned the hardware.

¹ Or obtain the extra items via PackMan, if they prefer.

Bits here and there via PackMan?

What a palaver.

Just make the tool generic and have it respond to the current processor capabilities. OS_ReadSysInfo will tell you that…

What a palaver.

Sure. But I was trying to answer the original question (“how to get a handful of components from RISC OS Pi without loading all 290MB of it”) rather than trying to come up with something that looks like it might morph into a full-blown system installer. I’m not saying that a system installer would be a bad target to aim for, just that it wasn’t what I had in mind.

Thanks for all your comments and suggestions.

I have rebuilt my HardDisc 4 !Boot directory from a fresh download of the 5.28 RISC OS Pi SD Card image.

I now have just 5 files on a new SD card (Cmos, config.txt, Riscos.img, fixup4.dat, start4.elf) and everything else on SCSI Drive 4 mSATA.

!Iris is now working fine once again.