Indeed.... I've been saying this regarding new users for years... And as i quoted in the last video far too little for too late ... 2012 - 2014 there as a real opportunity under the Pi1 for RISC OS as at that time it ran rings around the much slower Raspbian Debian Linux .... however as we all know the PI hardware and Linux builds get faster and better (With a few exceptions) whist RISC OS stood almost totally still. Leaving aside the fact you cant actually compile this supposed 'open source' OS without an outdated paywalled complier ... and it leaves any new entrant less then underwhelmed.....

I think RISC OS has always had a reputation for being paywalled, even back in the day. Last year I dropped a bucket of cash upgrading software I already had on my original RiscStation 7500+ clone for the RPi. To my surprise one package requires online authentication, which means it will eventually undergo digital rot and will stop installing when the servers go offline. In a world of FOSS I didn't have to buy these things, I wanted to give back to the community, but I think that the time has come to accept that it is what it is and, sadly, move on.

The problem with the 'giving back to the community' thing - which i get you did with good intentions is it give a false economy and just drives others to attempt to extort more money.. there have been a few examples of this in recent times. I guess you are probably aware of my work in the scene in recent years, which sadly has come to nothing, more as I was promised things that never happened or got withdrawn, and have seen my own free work 'paywalled' by others, so it just got to the point that I couldn't in all good faith support it anymore.... As a retro historic, plaything...... its great ... it works well on the early Pis, the back catalog of software mainly games is interesting, and the native 32-bit BBC BASIC V is the real highlight for me.... but daily driver..... no ..... But it could have been a strong hobby board / micro controller OS and it had a chance, like I said back in 2012 - And the owners / community blow it big time! We'll revisit occasionally, but i'm not pushing it the way I was a few years back!

My friend, your work and your excellent videos are the reason I got back into RISCOS as much as I did. So, you have a very big thank you from me.

That's exactly what happened - unclear if that is the reason it worked, but they were connecting the pi400 to channel 36 (5GHz) while they connected the pi4 to channel 11 (2.4GHz)

A number of hardware revisions, the main one being the Network Chip for Ethernet and Wireless changed - hence the issue your seeing in my videos. Off the top of my head cant think what the others are, but my 400 has been known to run code slower then other 2nd gen 400s

The problem you've got is even if the OS did this and lets say also supported 64bit running. You've got no software, no one wants to develop without charging £££s for there creations and the top of the 'community' is actively hostile to seeing ports of useful software such as Libra Office, VCL or Arduino IDE, hence its stuck in this vacuum.... fine if you view it as a'retro play thing' of the past, but really useless as a daily driver even on a hobby system like the Raspberry Pi.

@@WiFiSheep Even if the applications aren't multi threaded, if they have an smp enabled kernel and scheduler, it will still massively benefit the OS, as different applications could run on different cores. As to the community being against porting, well, that's just sad. It would be a massive boon to the project if it had some form of posix compliance where things could get ported.

@@detaart There is an SMP module being developed that provides scheduling across all available cores. Tasks must register with the SMP module to declare that it is multi-core aware and is written with threads and atomic variables where necessary as you would expect. The early version is already in the RISC OS Open Git repo, but I believe the developer was waiting for 5.30 to be launched before uploading his newer code from his own local branch (I think). Regardless, I think it will allow newer applications to be written and for existing apps to be modified to make use of the extra cores. Recently, it was mentioned that the zip compressor/decompressor app 'SparkFS' could be enhanced to speed it up significantly using the extra cores. RISC OS does have plenty of problems, but progress is made from time-to-time. I still enjoy using it, and in the end, I think that's all that really matters. I don't care that it won't ever replace Linux or Windows. It's fun to use.

@@WiFiSheep The operating concepts of RiscOS are completely different from pretty much any current OS. The fact that it does not provide memory protection from the different processes plus the lack of Unix-like API and libraries mean that porting anything but the most simple modern software to RiscOS is a non-trivial task (even early versions of the Windows network API provided a very Unix-like environment to developers). The memory protection in particular makes it very difficult to write thread-safe multiprocessor software. You are more likely to see a RiscOS compatibility layer on another OS like Haiku or even Linux before you're likely to see an SMP friendly version of RiscOS. RiscOS is a throw-back to a more simple time. It was very impressive when it was current, but it was very much in the era of Windows 3.1 and other 8/16 bit OS's. The fact that it runs at all on true 32 bit ARM systems (the original ARM was a 24 bit address space, with the other 8 bits of the Program Counter effectively providing the PSW) was a major hurdle, and we can be grateful that the work was done so that we can keep RiscOS alive.

@@detaart it does have some level of posix compliance. Many Unix tools have been ported. Someone is even porting WebKit!!!

No idea, im not involved in the project anymore, so best contact them directly

Yeah it’s just the pis overscan video setting which can be disabled in the config.txt file on the SD card the same way you can on Debian Linux builds