A couple of issues I noticed using RO 5 at IRUG meeting.

Using an A7000 with RO5 on an old Acorn monitor, the display wouldn’t lock. (The same install was fine on my LCD at home.)
The display was fine before softload.

After changing networking from DHCP to static on a Pi, doing reset now caused a freeze at the setup net part of boot. Power cycling it resolved it.

If you leave a gateway entry when setting DHCP, it gives an error on boot.

RISC OS 5 has always errored if “you leave a gateway entry when setting DHCP”

Using an A7000 with RO5 on an old Acorn monitor, the display wouldn’t lock. (The same install was fine on my LCD at home.) The display was fine before softload.

Are you able to try this on a Risc PC? The monitor id line is done slightly differently on the two and it’s possible on the A7000 it thinks it’s a composite sync TV. All my testing with A7000/A7000+/Risc PC use various shape LCD monitors – I don’t have any CRT’s any more.

If you explicitly configure a monitor type (other than auto) is the behaviour different?

You did remember to load the MDF for the old monitor, right? Which model?

Are you able to try this on a Risc PC? The monitor id line is done slightly differently on the two and it’s possible on the A7000 it thinks it’s a composite sync TV.

I probably can, but it won’t be for a while. It was the monitor at the local club. But I should be able to take an RPC next time.

All my testing with A7000/A7000+/Risc PC use various shape LCD monitors – I don’t have any CRT’s any more.

I suspected that was the case, I have no (compatible) CRTs at home either and it was fine here.

If you explicitly configure a monitor type (other than auto) is the behaviour different?

Yes, tried various numbers (typing blind) and it changed the pattern on screen.

You did remember to load the MDF for the old monitor,

It didn’t get that far, it was rolling as soon as the text screen came up.

right? Which model?

It was an Acorn monitor, the standard one for early RPCs I think. The sort that do 800×600 well and can be used at 1024×768 max.

We can do any tests you want next meedting. (The machine is there, still)

Rather than change the monitor type have you tried changing the Sync?
F12
*CON. Sync 0
RETURN
RETURN
It has immediate effect on RISC PCs can’t remember on Iyonix but worth a try on the Pi.
If 0 doesn’t work try 1 (Most LCDs need 1 on a RiscPC, CRTs tended not to matter)

Yesterday I tried RISC OS 5 on a Risc PC with a crt. I found the same problems that the display did not want to sync. The monitor showed that the frequency was out of range. As this was done at our club meeting can not provide any more info (I do not recall the horizontal and vertical frequencies that the crt detected). I do wonder however if there has been any progress with this.

Progress with what? The hardware capability of the Risc PC is defined by design. You need to choose a mode under RISC OS that is within the spec of the monitor you connect. Power on delete or waiting a long time after boot, typing f12 and then wimpmode 20 (or whatever)to try to find such a setting that a new monitor will like has always been difficult and is equally dificult under Windows. New flat screen monitors can tell the computer what screen modes they support and so an HDMI connected monitor on the Raspberry Pi should always show a picture…

It appears to be an error in driving the screen that old monitors (such as those donated to clubs) take exception to, but new monitors (such as most developers would have) don’t.

Perhaps a sync pulse issue?

I found the same problems that the display did not want to sync. The monitor showed that the frequency was out of range.

Just had a look at this on the scope, and yes, the syncs are correct but the sync type has got reversed – so when you want composite sync you get separate, and when you want separate (the default for “Auto” when a computer monitor is plugged in) you get composite!

Softloaded fix seems to solve it, but will do some physical ROMs tomorrow to double check.