#Update

Join & Support This Channel To Get Access To Additional Perks & Exclusive Videos:
/ @wifisheep
(TinyBASIC Tool Kit is ONLY available via Patreon and NOT KZbin Memberships at this time)
Wi-Fi Sheep Patreon join from $1 USD: / wifisheep
Amazon Affiliates: Buy on Amazon via this link and help support the channel!
amzn.to/3KtFSUZ
Wi-Fi Sheep Channel Two is Now Live!
two.wifisheep.co.uk @wifisheeptwo
For up & coming exhibition and show details see:
events.wifisheep.co.uk
=======================================================
Twitter: / wifisheep | @WiFiSheep
Mastodon: qoto.org/@UCyoGtuvngylmF2a20s...
Facebook: / wifisheep
Instagram: / wifisheep
=======================================================
Don't forget to like and subscribe!!!
Music Credits - Tracks Used
Kevin MacLeod - Incompetech.com
incompetech.com/
Gocart

[@jamesdecross1035]

Q: what is the difference between an early and a late Pi400? Thanks.

[@WiFiSheep]

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

[@johnnelms5117]

I am using rpi zero w itworks beyond wonderfull. everything works.

[@stephenfletcher2439]

You were probably trying to connect to the 5g network rather than 2.4 network (the slow connection) which you did on the pi 4, try connecting again on the pi400 using the slow connection.

[@LucyLlewyTechGirl]

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)

[@detaart]

I wish riscos had SMP support ...

[@WiFiSheep]

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.

[@detaart]

@@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.

[@nytrex2001]

@@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.

[@petergathercole4565]

@@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.

[@richardwalker5492]

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

[@coldsalt6678]

Risc os direct 5.30 when?

[@WiFiSheep]

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

[@martinparker9044]

Can you get rid of the black border around screen?

[@WiFiSheep]

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