Looking at pictures, it appears cameraless iPhones tend to have backs without camera holes / lumps, so some custom work is involved beyond just removing the module. Though there’s going to be a degree of “the government can afford it” in the pricing.
Drilling has some obvious issues, most notable if you go too deep you’re going to hit the screen.
I’m not sure if Sony has been pushing their video disc formats with PlayStations for a while. PS4 Pro was the “4K” upgrade over PS4, but didn’t support UHD Blu-Ray. And there’s been a disc drive-less PS5 since launch.
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.
Closing the online store for older systems simultaneously with announcing the dropping of physical media leaves an interesting question for the future. Even if you’ve never bought an online PS3 or Vita game, you’ll still be able to use the systems for physical games. Presumably once the PS6 store is gone, any console is just an ornament if you don’t have access to an account with games already purchased (and how long will the download servers stay up anyway? What is the foreseeable future?).
Bit of hindsight bias there, DAB was first developed in the mid 1990s, ubiquitous fast wireless IP in everyone’s pockets is at least a decade, perhaps nearer to 20 years in the future. There are quite a few transitionary technologies that we needn’t have developed had we just waited for something better to come along (but without the R&D into some of them…).
(Also doesn’t analogue FM also kinda cut off fairly abruptly?)
As far as I know the medium wave services aren’t transmitted from the same antenna as Radio 4 LW, they have separate antenna, albeit with one of them (5 Live) doubling up as one of the support towers for the large long wave T antenna slung between the two large towers on site. Although I suspect the plan would be to move 5 Live to the currently unused Absolute / Virgin antenna eventually so they can demolish the long wave setup.
It’s interesting that the gate arrays are supplied by Seiko, and the only known MCGA systems apart from IBM are from Epson. The bit of Seiko that made the gate arrays appears to be… Seiko Epson. So is it a coincidence? Sub-licensing? Skullduggery?
The Disk System RAM Adapter plugged into the cartridge port on a Famicom. The Famicom 15 pin expansion port is just a fancy joystick port (the console is otherwise limited to a pair of hardwired joypads).
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.
It's basically a case of hardware acceleration. Most games consoles and fancier micros have some of dedicated graphics chip that handles the heavy lifting of generating graphics. So for basic game graphics the CPU largely acts as a manager adjusting things like tilemaps and their viewport offsets, and sprite locations (possibly updating things several times mid frame, for fancier effects). The exact setup differs between systems, tilemaps and spites like the SNES is common, though you also have setups with some sort of framebuffer and a Blitter to speed up drawing to it instead.
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).
Roughly how many varieties of module were used for a full 604 system?
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.
From somewhere in the middle of Nvidia’s endless press waffle:
“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.“
I suspect Windows 2000 (and NT based stuff in general) is too near to modern Windows to be (officially) released. DOS is long dead, but modern Windows still uses the NT kernel and Win32 and so on, and they probably don't want to give an official peek behind the curtain, even if it's an over a quarter century old version.
Yes, Microsoft had established themselves as supplier of BASIC interpreters to most of the US microcomputer manufacturers. There initial contact with IBM was to provide a version of Microsoft BASIC for the new computer.
You wouldn’t be getting a protection fault when protection isn’t enabled.
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).
MS-DOS doesn’t have memory protection, so another option is that the running program[1] or something like a TSR or driver could have corrupted the headers.
[1] I guess in a modern system a process can still trash its own malloc, but not the kernel’s page allocation data.
Drilling has some obvious issues, most notable if you go too deep you’re going to hit the screen.