IGEPv5 ROM

I seem to have an inordinate number of difficulties with downloading a good OMAP5 ROM for an IGEPv5. I’ve tried several times now over the past year or so, and each of them fails to work fully, in some way:

Last week, I had an error (can’t remember the number, but a *where said it was in the Kernel). Today’s ROM doesn’t have AUNMsgs included. Softloading the module from another ROM allows the machine to connect to a network as usual, but without it, I can’t even configure the network.

I’m not sure how many IGEPv5 users there are, but am I just unlucky on the days I pick the ROM, or is it not as effective as the other nightly builds? I realise it’s a Nightly Build so isn’t guaranteed to work (so I’m stuck with the CJE 5.23 one from 2018) but it feels like it’s more prone to “not working” than other builds.

Anyone else getting the same?

Today’s ROM doesn’t have AUNMsgs included.

None of the ROMs have AUNMsgs in any more (its slot has been deftly taken by WindowScroll).

What that implies is the disc half of the OS is crusty: !Internet 5.64 (11-Aug-2018) and later will skip the AUNMsgs check, and !InetSetup 0.58 (07-Jan-2017) doesn’t output it in the startup scripts. Update at least those and you’ll be good; the ROM based AUNMsgs has done nothing since 0.28 (09-Oct-2015). You’d need to resave your settings with the newer InetSetup since it lives in !Boot.Choices.Internet.Startup.

On the occasions I’ve used the OMAP5 it’s seemed fine except for being fussy about driving my DVI input monitors.

Today’s ROM doesn’t have AUNMsgs included.

As I recall AUNMsgs was evicted from ROMs when the new WindowScroll module was added. Something to with ROM numbering and unplugs. Obviously I cannot find that now in git. If AUNMsgs is needed it is in pre-RISC OS 5 System resources.

Apart from needing to apply the !Boot updates that Sprow mentions, the current development ROM seems to work fine on my IGEPv5.

Yep, you were (all) right. Thank you.

As it was a new (to me) machine, and several other things were awry, I scrapped the entire disc contents and started with a clean image and everything is now hunky dory.

Thanks again.

I have tried a number of times to use a nightly build rather than an old CJE supplied ROM. I have found that the machine boots up if you use a clean boot (essentially no apps run during boot). This is when the oddity starts. Any app that is ‘self contained’ loads and runs fine. However, load something that also loads a support module, and the load fails. This includes standard things like SparkFS or Zap. The error address is always somewhere high up in the kernel.

All these apps are fine with an old ROM from 2018? (machine isn’t on at the moment to check).

All very strange.

Having now seen the two or three posts that came in while I was composing my post, I guess I ought to update my !Boot again, although the problem I see was present some months ago when I first decided to go with a new ROM on the IGEPv5.