Stuff like Blu-Ray seems to be becoming a Laserdisc like enthusiasts niche system, I don’t think it’s been a big thing for Sony for a while.

(Also doesn’t analogue FM also kinda cut off fairly abruptly?)

The NES expansion port on its own doesn’t seem to have enough lines to support the disk drive, notably it doesn’t have any address lines (CPU or PPU) at all, or the PPU data bus. It seems a bit weird frankly with the choices they made, I’m not sure what it’s actually for, apart from breaking the idea of extra sound chips in cartridges.

A traditional IBM PC has a "dumb" framebuffer, where everything is done by the PC. Simply scrolling the background by 1 pixel basically means redrawing a lot of the screen, and you have to keep track of what graphics behind sprite would need to be redrawn after they move etc. As a bonus, on early consumer level 386 and 486 machines you have a mighty processor, but the graphics card is often still on a 16 bit 8MHz(ish) ISA bus. The PC does have an advantage that it's more flexible, so stuff like 3D was easier to do than on a tile-and-sprite setup (especially once we had stuff like VESA and PCI).

I suspect quite a few as other "modular" systems in the transistor era like the later IBM Standard Modular System and DEC Flip-Chips ended up with plethora of specialised modules, but I'd be interested if that growth had already begun in the tube era.

So it’ll all be very do it yourself. Of course with everything running in ring 0, there’s not much that’s going to get in the way of you.

“The RTX Spark superchip features an NVIDIA Blackwell RTX GPU with 6,144 CUDA cores and fifth-generation Tensor Cores with FP4 precision, connected via the NVIDIA NVLink®-C2C chip-to-chip interconnect to a high-performance, 20-core NVIDIA Grace™ CPU.

MediaTek, a market leader in Arm-based system-on-a-chip designs, collaborated with NVIDIA on the custom CPU design, contributing to its best-in-class power efficiency, performance and connectivity.“

https://nvidianews.nvidia.com/news/nvidia-microsoft-windows-...

Nvidia Grace is an ARM core.

I should also note this error is the return code for MS-DOS’s memory management functions (such as int 21h ax 48h / 49h), vaguely similar to malloc() returning NULL. It’s not a fatal error, so how it’s handled depends on the programme. It could bail out, perhaps with a more general “out of memory” error, or try and carry on, or perhaps just start overwriting parts of the interrupt vector table as that’s where segment 0007h would start at…

(Though in the latter case on DOS just blindly assuming a memory allocation worked would be rather unwise so you’d hope just about everything checks the carry flag first).

[1] I guess in a modern system a process can still trash its own malloc, but not the kernel’s page allocation data.