Cold War–era computing has a poor reputation. The picture is one of a landscape littered with uninspired attempts to copy American IBM PCs, British ZX Spectrums, and other Western computers. But then there was Yugoslavia’s Galaksija, a very inspired bid to put a computer into the hands of regular comrades. The Galaksija is a Z80-based, 8-bit DIY machine, cleverly designed so that its bill of materials meshed exactly with what a Yugoslavian was able to import from Western Europe. During its brief heyday, thousands were built, leading to commercially assembled Galaksijas finding their way into homes and schools across the country. And now you can try this scrappy machine for yourself. There’s a huge world of computing to discover in former USSR countries, former USSR satellite states, and other countries that delicately straddled the west and east such as former Yugoslavia, many of which most people in the west have never heard of. While many of them may not have been competitive with what the Americans and Europeans were building, that doesn’t mean they’re not interesting or that there’s nothing to learn from the approaches the engineers took.

‘Dread’ has been featured many times on Indie Retro News, as with every new update the Amiga 500 version looked better than ever with fabulous new textures and new zones to visit. Well if you’re looking for more gaming news on this upcoming first person shooter, we have not only been informed that a new demo has been made available, but the latest footage and detailed press release shows that John is true to his word in bringing a Doom-like experience to the Amiga as the holy-grail of Amiga gaming! So without further-ado, here’s the latest blurb about this incredible looking game. I can’t believe they manage to squeeze this out of an A1200, let alone an A500. This is some serious wizardry.

Microsoft has announced it’s removing VBScript from future Windows releases. VBScript is being deprecated. In future releases of Windows, VBScript will be available as a feature on demand before its removal from the operating system. VBScript has been part of Windows for almost 30 years, first shipping in 1996. VBScript has a long history of serving as a vector for malware, which probably explains its removal from Windows.

Debian Bookworm itself is mostly made up of incremental updates of the software that was in the previous Debian Bullseye release. There are a few small changes — have a look here for the list — but they mostly won’t affect Raspberry Pi users. So Bookworm itself really hasn’t resulted in many changes. However, for the last year or so we have been working on some major architectural changes to the Raspberry Pi Desktop, and these are launched for the first time in the Bookworm release. And this is where you might notice some differences. With this new release, Raspberry Pi OS moves to Wayland and a Wayfire desktop, but it looks and feels exactly the same as what came before with X.Org. It now also comes with Pipewire, as well as an up-to-date version of Firefox that has been modified in cooperation with Mozilla to make better use of the hardware features found in the Pi.

This means the next time you sign in to your account, you’ll start seeing prompts to create and use passkeys, simplifying your future sign-ins. It also means you’ll see the “Skip password when possible” option toggled on in your Google Account settings. To use passkeys, you just use a fingerprint, face scan or pin to unlock your device, and they are 40% faster than passwords — and rely on a type of cryptography that makes them more secure. But while they’re a big step forward, we know that new technologies take time to catch on — so passwords may be around for a little while. That’s why people will still be given the option to use a password to sign in and may opt-out of passkeys by turning off “Skip password when possible.” I just don’t know how to feel about this universal, cross-corporate push from tech companies towards passkeys. I feel like when making the switch to passkeys, you’re giving something up. Something about it just doesn’t sit well with me, and for now, I’m going to be sticking to my trust password manager.

That second agent proved quite capable, not only agreeing that the situation was strange, but also looking into issues on Apple’s side. Which led to the somewhat bizarre conclusion of this story: after perhaps 20 minutes on the phone, he seemed to hit on something. I heard him laugh and say something along the lines of “that explains it” and then, with my consent, put me on hold. When he came back, he said—and I’m not exactly quoting, but close enough: “I’m sorry, I can’t tell you any more than this, but all your services should be back up pretty much exactly 12 hours after they went down.” Cloud computing is bizarre. Cloud computing at Apple – doubly so.

Nightcap lets you run old Windows screensavers under XScreenSaver, using wine. That’s it. That’s the Github description.

Today marks the 6th time we are releasing new functionality in the Qt 6 series, with small and large additions that make both UI and backend development more productive and fun. Several of the new features come as technology previews, and we are looking forward to your feedback so that we can get everything in tip-top shape for the next LTS release! Lots of new goodies for Qt developers.

To the surprise of absolutely nobody, Apple’s macOS gaming policy of only offering a proprietary, Apple-only API isn’t exactly paying off. One of the most popular online games in history, CS:GO, is removing support for macOS, and it won’t be coming back. From here on out, the game will only be available on 64-bit Windows and Linux. That cycle played out again in Valve’s recent Counter-Strike 2 update, which removed the Mac support already present in the outgoing Counter-Strike: Global Offensive. Today, a Valve support document for CS2 confirmed that Mac support had been removed and wasn’t likely to be re-added, along with support for ancient DirectX 9-class GPU hardware and legacy 32-bit operating systems. Fret not, though, Mac gamers – there’s always Super Tux Kart.

ECC support has been standard on Ryzen processors, but with the recent introduction of the Ryzen 7000 series and the new AM5 socket, any mention of ECC was dropped from specification pages and similar documentation. It turns out, though, that there’s more to this story. A couple months ago I came across a topic on the ASRock forums talking about ECC support on AM5 motherboards, in which a user called ApplesOfEpicness said that they’d worked with an AMD engineer to get ECC RAM going within AMD’s AGESA firmware. They’d claimed to have tested it on an ASRock motherboard with an updated UEFI, by shorting ground and data pins, and seeing errors be reported up to the OS. I was intrigued by this! Even though I didn’t have the same motherboard that ApplesOfEpicness did, I had chosen an ASRock board (the B650E PG Riptide)—I had figured that if ECC was possible on any AM5 board at all, it would be supported on ASRock. So based on the forum post, last week I ordered a pair of 32 GB server-grade ECC sticks from v-color. I updated my motherboard’s UEFI to the latest version (version 1.28 with AGESA 1.0.0.7b), and then replaced my existing RAM with the new sticks. I started up the system, and after a very long link training process… it booted up! It boots, but does it actually work? This may seem like a simple question to answer, but it turns out it’s a lot harder to verify working ECC than you might think. Excellent investigative work by the author, Rain.

As many of you will know from personal experience, there is a longstanding issue with VoiceOver on Mac where Safari will frequently become unresponsive with VoiceOver repeatedly announcing the message “Safari not responding.” When this issue occurs, the user’s Mac may become unusable for up to several minutes at a time. Sometimes it can be resolved by switching away from Safari. Sometimes restarting VoiceOver can resolve the issue. However, far too often, the user is unable to switch away from Safari or turn VoiceOver off, instead having to simply wait for their Mac to become responsive again. This “Safari not responding” behaviour when using VoiceOver dramatically impacts productivity and overall usability of Macs for blind and low vision users. Furthermore, it appears that the issue extends beyond just Safari – many other common applications that utilise Apple’s WebKit browser engine can also be affected by the “not responding” problem. I’m not highlighting this to make Apple look bad – for once – or to fill some quota. The fact of the matter is that in the blind and vision-impaired community, the Mac and iPhone are immensely popular for their accessibility features other platforms just cannot match. If you’ve ever seen a blind person use an iPhone, you know just how different their way of using it is from sighted people. As such, having a major bug like this is a huge deal. It impacts people who really have nowhere else to go, technology-wise, since switching to other platforms really isn’t a viable option in most cases. This issue must be fixed, and can’t be left by the wayside because it only impacts a relatively small number of people. Blind and vision-impaired folks have placed their trust in Apple because they’ve got nowhere else to go, and Apple needs to step up and take this seriously. Now.

ZFS was promised, and didn’t arrive. In fact, there were about 4 of us on the beta program who saw the original zfs implementation, and it was quite different from what we have now. What eventually landed as zfs in Solaris was a complete rewrite. The beta itself was interesting – we were sent the driver, 3 binaries, and a 3-line cheatsheet, and that was it. There was a fundamental philosophy here that the whole thing was supposed to be so easy to use and sufficiently obvious that it didn’t need a manual, and that was actually true. (It’s gotten rather more complex since, to be fair.) Peter Tribble – long-time Solaris expert and creator of Tribblix – gives a gimpse into the earliest versions of ZFS, and just how different it was from the shipped release.

In this guide, we’ll build a very tiny Linux kernel, weighing in at 789 K, and requiring no MMU support. We’ll write some userspace code and this will be deployed on a virtual RISC-V 64-bit machine, without MMU, and we’ll run some tiny programs of our own. As a reminder, please go through the guide for a micro Linux distro to understand the concepts behind what we’re doing today: building the kernel, initramfs, etc. This guide is basically a continuation of that one and an exercise in making an absolutely minimal Linux deployment for (in theory) extremely cheap hardware. This follows up on the mentioned earlier article.

Debian is a large, complex operating system, and a huge open source project. It’s thirty years old now. To many people, some of its aspects are weird. Most such things have a good reason, but it can be hard to find out what it is. This is an attempt to answer some such questions, without being a detailed history of the project. The fact that Debian is a relatively slow-acting, complex democracy is probably why it has survived for so long, and why it’s become the bedrock for so many derivative distributions.