In light of this, I'm recalling that #beos has a more message passing mechanism and I'm wondering if that avoided this problem considerably...
I stumbled upon an interesting blog today while searching for an image of the Silicon Graphics 3D cube logo. Named "Abort Retry Fail" by Bradford Morgan White, the blog's articles document computer history. I eventually wound up reading three of them.
#3 "'Be' is nice. End of story."
@linuxmagazine as someone who was there for #BeOS, this feels a lot like the BeOS situation, which does not bode well
So, I decided to max the RAM out on my #Lenovo #Thinkstation #P340. It takes 128GB of RAM. It gets here, I install it, machine just turns off and on. I troubleshoot, and if I pull the ram from DIMM slot 4, it boots fine. Not a bad stick as I rotate through them and they all test fine. I reinstall the original ram (2x 16GB sticks) and I notice the same slot is bad.
Call in to get warranty work, get the mobo swapped, same issue. 
While the tech is on the phone to get another mobo on the way, I get some idea that maybe it's an allocation issue since it's happening during POST- you know- like the old #BeOS >1GB RAM issue. I pull my 3.2TB Samsung PCIe AIC NVME and 
, machine boots and posts all ram- including DIMM slot 4. I try my NVME in another slot and same issue. 
So, weird issue- I can't have a PCIe AIC NVME (or at least this one anyway) and have all 4 ram slots work in a Lenovo ThinkStation P340 tower system. You'd think for a workstation-class machine, this wouldn't be an issue. But here we are. 128GB of RAM or an additional 3.2TB of screamin fast PCIe NVME server-class storage. 
/* Err. Should that be 4 fs blocks or 4k??? It matters on large blocksize volumes */
https://elixir.bootlin.com/linux/v6.13.7/source/fs/befs/befs_fs_types.h#L39-L40
Colleague of mine was sorting through some old stuff of his and found this.
Ah, memories! 
#NVIDIA's #OpenSource Kernel Driver Ported To #HaikuOS. #Haiku also ported the #MesaNVK Vulkan driver to be able to run atop the NVIDIA kernel driver interface. https://www.phoronix.com/news/NVIDIA-Haiku-OS-NVRM #BeOS
On March 22, 2008, the Haiku team announced, that ACCESS Co Ltd. agreed to publish the BeBook and the Be Newsletters. These ressources provided valuable reference material for developers. #BeOS #ACCESS #HaikuOS https://www.haiku-os.org/news/2008-03-21_bebook_and_be_newsletters_available_online/
Best alternative operating systems of 2025
ArcaOS (based on OS/2).
HaikuOS of course (based on BeOS).
ReactOS (still trying to reimplement Windows NT, currently about 20 years behind as it catches up to Windows Server 2003).
FreeDOS (ok, makes sense)
Wayne OS (Chromium OS fork intended to run from a USB thumb drive).
OpenIndiana (continuing from the last open release of OpenSolaris)
KolibriOS (based on MenuetOS, written in assembler, focus on retrogaming)
Visopsys (a CS student project)
Icaros (not exactly an Amiga clone, but reimplementing its API)
If you want to run BeOS on the 86Box, create a machine using the specifications on the website. I will soon create a VM for BeOS using the 86Box.
https://asleson.org/public/mirrors/www.be.com/support/guides/beosreadylist_intel.html
Most of you already know ScummVM, the retro gaming engine, this has been available in Haiku since the BeOS days and being kept on par with upstream releases.
Haiku Insider created a nice blog about how to setup/add games and play them at: https://www.haikuinsider.org/scummvm-emulation
Gives a nice reading tutorial! Happy gaming!
@marquisdegeek but said teapot is not red, nor multhreaded nor turning
#beos
Nouvelles de Haiku - Hiver 2024-25 https://linuxfr.org/news/nouvelles-de-haiku-hiver-2024-25 #iceweasel #Haiku #haiku #beos
Nvidia (porting Nvidia GPU driver) 
