In the 1980s there were an incredible number of personal computers of all shapes, sizes, and operating system types, and there was very little interoperability. Unlike today’s Windows-Mac duopoly, this era was much more of a free-for-all but that didn’t mean companies like Microsoft weren’t trying to clean up all of this mess. In 1983 they introduced the MSX standard for computers, hoping to coalesce users around a single design. Eventually it became very successful in Japan and saw some use in a few other places but is now relegated to the dustbin of history, but a new FPGA kit unofficially supports this standard.

The kit is called the OneChip Book and, unlike most FPGA kits, includes essentially everything needed to get it up and running including screen, keyboard, and I/O all in a pre-built laptop case. At its core it’s just that: and FPGA kit. But its original intent was to recreate this old 80s computer standard with modern hardware. The only problem is they never asked for permission, and their plans were quickly quashed. The development kit is still available, though, and [electricadventures] goes through the steps to get this computer set up to emulate this unofficially-supported retro spec. He’s also able to get original MSX cartridges running on it when everything is said and done.

Although MSX is relatively unknown in North America and Western Europe, it remains a fairly popular platform for retro computing enthusiasts in much of the rest of the world. We’ve seen a few similar projects related to this computer standard like this MSX-inspired cyberdeck design, but also others that bring new hardware to this old platform.

youtube.com/embed/Iy7R29bjuJ8?…

hackaday.com/2026/01/03/fpga-d…

[Mike Stewart] powers up a thrust meter from an Apollo lunar module. This bit of kit passed inspection on September 25, 1969. Fortunately [Mike] was able to dig up some old documentation which included the pin numbers. Score! It’s fun to see the various revisions this humble meter went through. Some of the latest revisions are there to address an issue where there was no indication upon failure, so they wired in a relay which could flip a lamp indicator if the device lost power.

This particular examination of this lunar thrust module is a good example of how a system’s complexity can quickly get out of hand. Rather than one pin there are two pins to indicate auto or manual thrust, each working with different voltage levels; the manual thrust is as given but the auto thrust is only the part of the thrust that gets added to a baseline thrust, so they need to be handled differently, requiring extra logic and wiring for biasing the thrust meter when appropriate. The video goes into further detail. Toward the end of the video [Mike] shows us what the meter’s backlights look like when powered.

If you’re interested in Apollo mission technology be sure to check out Don Eyles Walks Us Through The Lunar Module Source Code.

youtube.com/embed/H3bxe7gynQk?…

hackaday.com/2026/01/03/apollo…

While we’re 100 years past Edison’s fear, uncertainty, and doubt campaign, the fact of the matter is that DC is a bit easier to wrap one’s head around. It’s just so honest in its directness. AC, though? It can be a little shifty, and that results in some unexpected behaviors, as seen in this video from [The Action Lab].

He starts off with a very relatable observation: have you ever noticed that when you plug in a pickle, only half of it lights up? What’s up with that? Well, it’s related to the asymmetry he sees on his Jacobs ladder that has one side grow hotter than the other. In fact, it goes back to something welders who use DC know about well: the Debye sheath.

The arc of a welder, or a Jacobs ladder, or a pickle lamp is a plasma: ions and free electrons. Whichever electrode has negative is going to repel the plasma’s electrons, resulting in a sheath of positive charge around it. This positively-charged ions in the Debye sheath are going to accelerate into the anode, and voila! Heating. That’s why it matters which way the current goes when you’re welding.

With DC, that makes sense. In AC, well — one side starts as negatively charged, and that’s all it takes. It heats preferentially by creating a temporary Debye sheath. The hotter electrode is going to preferentially give off electrons compared to its colder twin — which amplifies the effect every time it swings back to negative. It seems like there’s no way to get a pure AC waveform across a plasma; there’s a positive feedback loop at whatever electrode starts negative that wants to introduce a DC bias. That’s most dramatically demonstrated with a pickle: it lights up on the preferentially heated side, showing the DC bias. Technically, that makes the infamous electric pickle a diode. We suspect the same thing would happen in a hot dog, which gives us the idea for the tastiest bridge rectifier. Nobody tell OSHA.

[The Action Lab] explains in more detail in his video, and demonstrates with ring-shaped electrode how geometry can introduce its own bias. For those of us who spend most of our time slinging solder in low-voltage DC applications, this sort of thing is fascinating. It might be old hat to others here; if the science of a plain Jacobs ladder no longer excites you, maybe you’d find it more electrifying built into a blade.

youtube.com/embed/_59b75Vql38?…

hackaday.com/2026/01/03/pickle…

Modern passenger airliners are essentially tubes-with-wings, they just happen to be tubes that are stuffed full with fancy electronics. Some of the most important of these are related to keeping the bits of the tube with humans inside it at temperatures and pressures that keeps them alive and happy. Case in point the Boeing 777, of which [Michel] of Le Labo de Michel on YouTube recently obtained the Cabin Pressure Control System (CPCS) for a teardown.

The crucial parts on the system are the two Nord-Micro C0002 piezo resistive pressure transducers, which measure the pressure inside the aircraft. These sensors, one of which is marked as ‘backup’, are read out by multiple ADCs connected to a couple of FPGAs. The system further has an ARINC 429 transceiver, for communicating with the other avionics components. Naturally the multiple PCBs are conformally coated and with vibration-proof interconnects.

Although it may seem like a lot of hardware just to measure air pressure with, this kind of hardware is meant to work without errors over the span of years, meaning significant amounts of redundancy and error checking has to be built-in. Tragic accidents such as Helios Airways Flight 522 involving a 737-300 highlight the importance of these systems. Although in that case human error had disabled the cabin pressurization, it shows just how hard it can be to detect hypoxia before it is too late.

youtube.com/embed/rsCxEcR-AYE?…

hackaday.com/2026/01/03/teardo…

[Codeolences] tells us about the FORBIDDEN Soviet Computer That Defied Binary Logic. The Setun, the world’s first ternary computer, was developed at Moscow State University in 1958. Its troubled and short-lived history is covered in the video. The machine itself uses “trits” (ternary digits) instead of “bits” (binary digits).

When your digits have three discrete values there are a multiplicity of ways of assigning meaning to each state, and the Setun uses a system known as balanced ternary where each digit can be either -1, 0, or 1 and otherwise uses a place-value system in the normal way.

An interesting factoid that comes up in the video is that base-3 (also known as radix-3) is the maximally efficient way to represent numbers because three is the closest integer to the natural growth constant, the base of the natural logarithm, e, which is approximately 2.718 ≈ 3.

If you’re interested to know more about ternary computing check out There Are 10 Kinds Of Computers In The World and Building The First Ternary Microprocessor.

youtube.com/embed/4vwOJE0Dq38?…

hackaday.com/2026/01/03/the-se…

An accessible 3D printer for metals has been the holy grail of amateur printer builders since at least the beginning of the RepRap project, but as tends to be the case with holy grails, it’s proven stubbornly elusive. If you have the resources to build it, though, it’s possible to replicate the professional approach with a selective laser melting (SLM) printer, such as the one [Travis Mitchell] built (this is a playlist of nine videos, but if you want to see the final results, the last video is embedded below).

Most of the playlist shows the process of physically constructing the machine, with only the last two videos getting into testing. The heart of the printer is a 500 Watt fiber laser and a galvo scan head, which account for most of the cost of the final machine. The print chamber has to be purged of oxygen with shielding gas, so [Travis] minimized the volume to reduce the amount of argon needed. The scan head therefore isn’t located in the chamber, but shines down into it through a window in the chamber’s roof. A set of repurposed industrial servo motors raises and lowers the two pistons which form the build plate and powder dispenser, and another servo drives the recoater blade which smooths on another layer of metal powder after each layer.

As with any 3D printer, getting good first-layer adhesion proved troublesome, since too much power caused the powder to melt and clump together, and too little could result in incomplete fusion. Making sure the laser was in focus improved things significantly, though heat management and consequent warping remained a challenge. The recoater blade was originally made out of printed plastic, with a silicone cord along the edge. Scraping along hot fused metal in the early tests damaged it, so [Travis] replaced it with a stainless steel blade, which gave much more consistent performance. The final results looked extremely promising, though [Travis] notes that there is still room for redesign and improvement.

This printer joins the very few other DIY SLM machines we’ve seen, though there is an amazingly broad range of other creative ideas for homemade metal printers, from electrochemical printers to those that use precise powder placement.

youtube.com/embed/MPXp3hpsdjA?…

hackaday.com/2026/01/03/printi…

Before DOOM would run on any computing system ever produced, and indeed before it even ran on its first computer, the game that would run on any computer of the pre-DOOM era was Zork. This was a text-based adventure game first published in the late 70s that could run on a number of platforms thanks to a virtual machine that interpreted the game code. This let the programmers write a new VM for each platform rather than porting the game every time. [smbakeryt] wanted to see how far he could push this design and got the classic game running on one of the oldest computers ever produced.

The computer in question is the ubiquitous Intel 4004 processor, the first commercially available general-purpose microprocessor produced. This was a four-bit machine and predates the release of Zork by about eight years. As discussed earlier, though, the only thing needed to get Zork to run on any machine is the Z-machine for that platform, so [smbakeryt] got to work. He’s working on a Heathkit H9 terminal, and the main limitation here is the amount of RAM needed to run the game. He was able to extended the address bus to increase the available memory in hardware, but getting the Z-machine running in software took some effort as well. There’s a number of layers of software abstraction here that’s a bit surprising for 70s-era computing but which make it an extremely interesting challenge and project.

As far as [smbakeryt]’s goal of finding the “least amount of computer” that would play Zork, we’d have a hard time thinking of anything predating the 4004 that would have any reasonable user experience, but we’d always encourage others to challenge this thought and [smbakeryt]’s milestone. Similarly, DOOM has a history of running on machines far below the original recommended minimum system requirements, and one of our favorites was getting it to run on the NES.

youtube.com/embed/VcTQyA80Apg?…

hackaday.com/2026/01/03/zork-r…

Despite faster CPUs, RAM and storage, today’s Windows experience doesn’t feel noticeably different from back in the 2000s when XP and later Windows 7 ruled the roost. To quantify this feeling, [TrigrZolt] decided to run a series of benchmarks on a range of Windows versions.

Covering Windows XP, Vista, 7, 8.1, 10 and 11, the Pro version of each with the latest service packs and updates was installed on the same laptop: a Lenovo ThinkPad X220. It features an Intel i5 2520M CPU, 8 GB of RAM, built-in Intel HD Graphics 3000 and a 256 GB HDD.

For start-up, Windows 8.1 won the race, probably due to having the Fast Boot feature, while Windows 11 came in dead last as it showed the desktop, but struggled to show the task bar. Windows XP’s install size was the smallest and also had the lowest RAM usage with nothing loaded at 800 MB versus 3.3 GB for Windows 11 in last place.

Using the Chrome-based Supermium browser, memory management was tested, with XP performing as poorly as Windows 11, while Windows 7 and 8.1 took home the gold at over two-hundred tabs open before hitting the total RAM usage limit of 5 GB. That XP performed so poorly was however due to an issue with virtual memory and not hitting the RAM limit, which means that Windows 11 is the real dunce here.

This is a pattern that keeps repeating: Windows 11 was last in the battery test, took longer to render a video project in OpenShot, took its sweet time opening the File Explorer window, and opening built-in applications like MS Paint left enough time to fetch a fresh cup of coffee. Not to mention Windows 11 taking the longest to open websites and scoring worst of all in single-threaded CPU-Z.

Much seems to be due to the new code in Windows 11, as Microsoft has opted to start doing major rewrites since Windows 7, hitting a crescendo with Windows 11. Although there’s the unhelpful fact that Windows 11 by default encrypts the storage with the very slow software-based BitLocker, its massive RAM usage and general sluggishness are such a big deal that even Microsoft has acknowledged this and added workarounds for the slow File Explorer in Windows 11 by preloading components into RAM.

All of this appears to be part of the same trend in software development, where more resources are pointlessly used due to developing for the hardware, and performance increasingly takes a backseat to abstractions and indirections that effectively add bloat and latency.

youtube.com/embed/7VZJO-hOT4c?…

hackaday.com/2026/01/02/benchm…

For various reasons, crypto mining has fallen to the wayside in recent years. Partially because it was never useful other than as a speculative investment and partially because other speculative investments have been more popular lately, there are all kinds of old mining hardware available at bargain prices. One of those is the Asrock AMD BC250, which is essentially a cut down Playstation 5 but which has almost everything built into it that a gaming PC would need to run Steam, and [ETA PRIME] shows us how to get this system set up.

The first steps are to provide the computer with power, an SSD, and a fan for cooling. It’s meant to be in a server rack so this part at least is pretty straightforward. After getting it powered up there are a few changes to make in the BIOS, mostly related to memory management. [ETA PRIME] is uzing Bazzite as an operating system which helps to get games up and running easily. It plays modern games and even AAA titles at respectable resolutions and framerates almost out-of-the-box, which perhaps shouldn’t be surprising since this APU has a six-core Zen 2 processor with a fairly powerful RDNA2 graphics card, all on one board.

It’s worth noting that this build is a few weeks old now, and the video has gotten popular enough that the BC250 cards that [ETA PRIME] was able to find for $100 are reported to be much more expensive now. Still, though, even at double or triple the price this might still be an attractive price point for a self-contained, fun, small computer that lets you game relatively easily and resembles the Steam Machine in concept. There are plenty of other builds based on old mining hardware as well, so don’t limit yourself to this one popular piece of hardware. This old mining rig, for example, made an excellent media server.

youtube.com/embed/q_CxcbS5HI8?…

hackaday.com/2026/01/02/a-stea…

Over the decades we have seen many DIY clocks and wrist watches presented, but few are as likely to get you either drawing in the crowds, or quietly snickered at behind your back, as a binary watch of some description does. A wrist watch like [qewer]’s qron0b project which also uses BCD encoding to display the current time is among our more rare project types here, with us having to go all the way back to 2018 for a similar project as well as a BCD desk clock.

As is typical, a single CR2032 coin cell powers the entire PCB, with an ATtiny24A or compatible as the MCU, a DS1302 RTC and the requisite 4×4 LED matrix to display the hours and minutes. Technically three LEDs are unneeded here, but it looks nicely symmetrical this way, and the extra LEDs can be used for other tasks as the firmware is expanded from the current setting and reading of the time.

The AVR C firmware can be found in the above linked GitHub repository, along with the KiCad PCB project and FreeCAD design files for the watch body. The body accepts a 22 mm GT2/GT3-style watch strap to complete the assembly. With a single CR2032 you’re assured of at least a few months of runtime.

hackaday.com/2026/01/02/qron0b…

In my country, we have a saying: the sun is a deadly lazer. Well, it’s not so much a folk saying as a meme, and not so much in one country as “the internet”. In any case, [LiamTronix] was feeling those cancer rays this harvest season when running his electric tractor, and realized that– since he’s already charging it with ground-mounted solar panels anyway–if he’s going to build a roof for his ride, he might as well make charge the batteries.

Another bonus is safety: the old Massey-Ferguson at the heart of the electric tractor build didn’t come with any rollover protection from the factory back in the 1960s. Since having however many tons of tractor roll onto you was bad enough before it got a big hefty battery pack, we heartily approve of including a roll cage in this build. Speaking of battery packs, he’s taking this chance to upgrade to a larger LiFePo pack from the LiIon pack he installed when we first featured this conversion in 2024.

Atop the new roll cage, and above the new battery, [Liam] installed four second-hand 225 W solar panels. Since that’s under 1kW even if the panels have not degraded, the tractor isn’t going to be getting much charge as it runs. In the northern winter, [Liam] is only able to pull 80 W from the set. That’s not getting much work done, but who wants a tractor without a cab or heater when it’s below freezing? In the summer it’s a much better story, and [Liam] estimates that the roof-mounted panels should provide all of the energy needed to run the tractor for the couple hours a day he expects to use it.

If you’re wondering how practical all this is, yes, it can farm — we covered [Liam] putting the project through its paces in early 2025.

hackaday.com/2026/01/02/adding…

As locked-down as the Amazon Echo Show line of devices are, they’re still just ARM-based Android devices, which makes repurposing it somewhat straightforward as long as what you want is another Android device.
Running Home Assistant on an Echo Show 8 with LineageOS.
In this case, we’re talking about the first-generation Amazon Echo Show 8, which is a 2019-era device that got jailbroken back in November by [Rortiz2]. The process was then demonstrated in a video by [Dammit Jeff].

Currently only two devices are supported by this jailbreak, with the Echo Show 5 being the other one. If there’s enough interest, there doesn’t appear to be any technical reason at least for why this support couldn’t be extended to other devices. One major reason for jailbreaking is to put LineageOS on your Echo device courtesy of these Echo Show devices recently beginning to show advertisements, with no way to disable this.

The process of jailbreaking and installing the LineageOS ROM is somewhat long as usual, with plenty of points where you can make a tragic mistake. Fortunately it’s pretty simple as long as you follow the steps and afterwards you can even install the Google apps package if that’s your thing. Just mind the 1 GB RAM and 8 GB of storage on the Echo Show 8. In the case of [Jeff] he mostly replicated the home automation and entertainment features of Amazon’s FireOS with far less locked-down alternatives like Home Assistant.

youtube.com/embed/h0-MlJ38BXw?…

hackaday.com/2026/01/02/jailbr…

Elliot was of at Europe’s largest hacker convention: Chaos Communication Congress. He had an awesome time, saw more projects than you might think humanely possible, and got the flu. But he pulled through and put this audio tourbook for you.

So if you’ve never been to CCC, give it a listen!

html5-player.libsyn.com/embed/…

In the far future, all the cool kids will be downloading MP3s of their favorite podcasts.

Where to Follow Hackaday Podcast

Places to follow Hackaday podcasts:

• iTunes
• Spotify
• Stitcher
• RSS
• YouTube
• Check out our Libsyn landing page

What’s That Sound

• If you think you know what the mystery sound was this week, give us your best guess for a chance at a Hackaday Podcast t-shirt.

hackaday.com/2026/01/02/hackad…