2025-08-23 13:00:48
As the march of time continues on, it becomes harder and harder to play older video games on hardware. Part of this is because the original hardware itself wears out, but another major factor is that modern operating systems, software, and even modern hardware don’t maintain support for older technology indefinitely. This is why emulation is so popular, but purists that need original hardware often have to go to extremes to scratch their retro gaming itch. This project from [Eivind], for example, is a completely new x86 PC designed for the DOS and early Windows 98 era.
The main problem with running older games on modern hardware is the lack of an ISA bus, which is where the sound cards on PCs from this era were placed. This build uses a Vortex86EX system-on-module, which has a processor running a 32-bit x86 instruction set. Not only does this mean that software built for DOS can run natively on this chip, but it also has this elusive ISA capability. The motherboard uses a Crystal CS4237B chip connected to this bus which perfectly replicates a SoundBlaster card from this era. There are also expansion ports to add other sound cards, including ones with Yamaha OPL chips.
Not only does this build provide a native hardware environment for DOS-era gaming, but it also adds a lot of ports missing from modern machines as well including a serial port. Not everything needs to be original hardware, though; a virtual floppy drive and microSD card reader make it easy to interface minimally with modern computers and transfer files easily. This isn’t the only way to game on new, native hardware, though. Others have done similar things with new computers built for legacy industrial applications as well.
Thanks to [Stephen] for the tip!
2025-08-23 10:00:08
Sometimes it seems like there’s nothing Emacs can’t do. Which, of course, is why some people love it, and some people hate it. Apparently, [mbork] loves it and devised a scheme to show a video (with a little help), accept cut-in and out marks, and then use ffmpeg to output the video clip, ready for posting, emailing, or whatever.
This was made easier by work already done to allow Emacs to create subtitles (subed). Of course, Emacs by itself can’t play videos, but it can take control of mpv, which can. Interestingly, subed doesn’t insist on mpv since it won’t work on Windows, but without it, your editing experience won’t be as pleasant.
Back to creating a clip, once you have control of mpv, it is almost too simple. A keybinding remembers where mpv is when you mark the beginning, and another one grabs the end mark, works out the arguments, and calls ffmpeg to do the actual work.
This is one of those cases where Emacs really isn’t doing much of the work; it is more of a sophisticated scripting, orchestration, and user-interface system. But it reminds us of the old Russian proverb: The marvel is not that the bear dances well, but that the bear dances at all.
Emacs is a hot topic of debate in the Hackaday bunker. Some of us have our browsers emacs-ified. We hear a rumor that one among us may even boot directly into the editor. But not all of us, of course.
2025-08-23 07:00:33
When [Tom Nardi] reported on NOAA’s statement that many of its polar birds were no longer recommended for use, he mentioned that when the satellites do give up, there are other options if you want to pull up your own satellite weather imagery. [Jacopo] explains those other options in great detail.
For example, the Russian Meteor-M satellites are available with almost the same hardware and software stack, although [Jacopo] mentions you might need an extra filter since it is a little less tolerant of interference than the NOAA bird. On the plus side, Meteor-M is stronger than the NOAA satellite on 1.7 GHz, and you can even use a handheld antenna to pick it up. There are new, improved satellites of this series on their way, too.
Another possibility is Metop-B and -C. These do require a wide bandwidth but that’s not hard to do with a modern SDR. Apparently, these satellites will operate until 2027 and beyond.
Even the US GOES satellites are still operational and should continue working for the foreseeable future. There are plenty more choices. Weather not your thing? Jason-3 sends data on radiation and humidity. There are even solar images you can pluck out of the airwaves.
If you’re interested, read on to the bottom, where you’ll find coverage of what you need and how to get started. Of course, you can still get the last gasp of some of the classic satellites, at least for now. You can even print your own antennas.
2025-08-23 04:00:33
If you’ve ever lost gear to lightning or power spikes, you know what a pain they are. Out in rural Arkansas, where [vinthewrench] lives, the grid is more chaos than comfort – especially when storms hit. So, he dug into the problem after watching a cheap AC-DC module quite literally melt down. The full story, as always, begins with the power company’s helpful reclosers: lightning-induced surges, and grid switching transients. The result though: toasted boards, shorted transformers, and one very dead Raspberry Pi. [vinthewrench] wrote it all up – with decent warnings ahead. Take heed and don’t venture into things that could put your life in danger.
Back to the story. Standard surge suppressors? Forget it. Metal-oxide varistor (MOV)-based strips are fine for office laptops, but rural storms laugh at their 600 J limits. While effective and commonly used, MOVs are “self-sacrificing” and degrade over time with each surge event.
[vinthewrench] wanted something sturdier. Enter ZeusFilter 1.0 – a line-voltage filter stitched together from real parts: a slow-blow fuse, inrush-limiting thermistor, three-electrode gas discharge tube for lightning-class hits, beefy MOVs for mid-sized spikes, common-mode choke to kill EMI chatter, and safety caps to bleed off what’s left. Grounding done right, of course. The whole thing lives on a single-layer PCB, destined to sit upstream of a hardened PSU.
As one of his readers pointed out, though, spikes don’t always stop at the input. Sudden cut-offs on the primary can still throw nasty pulses into the secondary, especially with bargain-bin transformers and ‘mystery’ regulators. The reader reminded that counterfeit 7805s are infamous for failing short, dumping raw input into a supposedly safe 5 V rail. [vinthewrench] acknowledged this too, recalling how collapsing fields don’t just vanish politely – Lenz makes sure they kick back hard. And yes, when cheap silicon fails, it fails ugly: straight smoke-release mode.
In conclusion, we’re not particularly asking you to try this at home if you lack the proper knowledge. But if you have a high-voltage addiction, this home research is a good start to expand your knowledge of what is, in theory, possible.
2025-08-23 02:30:28
Over time, web browsers have accumulated a ton of features beyond what anyone from the 90s might have imagined, from an application platform to file management and even to hardware access. While this could be concerning from a certain point of view, it makes it much easier to develop a wide range of tools. All a device really needs to use a browser as a platform is an IP address, and this project brings a web UI dashboard to Zephyr to simplify application development.
Zephyr is a real-time operating system (RTOS) meant for embedded microcontrollers, so having an easy way to access these systems through a web browser can be extremely useful. At its core, this project provides a web server that can run on this operating system as well as a REST API that can be used by clients to communicate with it. For things like blinking lights this is sufficient, but for other things like sensors that update continuously the dashboard can also use WebSocket to update the web page in real time.
The web dashboards that can be built with this tool greatly reduce the effort and complexity needed to interact with Zephyr and the microcontrollers it typically runs on, especially when compared to a serial console or a custom application that might otherwise be built for these systems. If this is your first time hearing about this RTOS we recently featured a microcontroller-based e-reader which uses this OS as a platform.
2025-08-23 01:00:15
A couple of decades ago now, several things happened which gave life to our world and made it what it has become. Hackerspaces proliferated, giving what was previously dispersed a physical focus. Alongside that a range of hardware gave new expression to our projects; among them the Arduino, affordable 3D printing, and mail-order printed circuit boards.
The result was a flowering of creativity and of a community we’d never had before.Visiting another city could come with a while spent in their hackerspace, and from that new-found community blossomed a fresh wave of events. The older hacker camps expanded and morphed in character to become more exciting showcases for our expression, and new events sprang up alongside them. The 2010s provided me and my friends with some of the most formative experiences of our lives, and we’re guessing that among those of you reading this piece will be plenty who also found their people.
And then came COVID. Something that sticks in my mind when thinking about the COVID pandemic is a British news pundit from March 2020 saying that nothing would be quite the same as before once the pandemic was over. In our community this came home to me after 2022, when the first large European hacker camps made a return. They were awesome in their own way, but somehow sterile, it was as though something was missing. Since then we’ve had a few more summers spent trailing across the continent to hang out and drink Club-Mate in the sun, and while we commend the respective orgas for creating some great experiences, finding that spark can still be elusive. Hanging out with some of my friends round a European hackerspace barbecue before we headed home recently, we tried to put our finger on exactly where the problem lay.
Perhaps the most stinging criticism we arrived at was that our larger events seem inexorably to be morphing into festivals. It’s partly found on the field itself and we find events hosting music stages, but also in the attendees. Where a decade or more ago people were coming with their cool hacks to be the event, now an increasing number of people are coming as spectators just to see the event. This no doubt reflects changing fashions in a world where festival attendance is no longer solely for a hard core of music fans, but its effect has been to slowly turn fields of vibrant villages where the real fun happened, into fields of tents with a few bright spots among them, and the attendees gravitating toward a central core where increasingly, the spectacle is put on for them.
The other chief gripe was around the eternal tussle in our community between technology and activism. Hackers have always been activists, if you doubt that take a read of Hackaday’s coverage of privacy issues, but the fact remains that we are accidental activists; activism is not the reason we do what we do. The feeling was that some events in our community have become far more about performative imposition of a particular interpretation of our culture or conforming to political expectations than they have about the hacks, and that the fun has been sucked out of them as a result.
People who know me outside my work for Hackaday will tell you that I have a significant career as an activist in a particular field, but when I’m at a hacker camp I am not there to be lectured at length about her ideology by an earnest young activist with blue hair and a lot of body piercings. I am especially not there to be policed as some kind of enemy simply because I indicate that I’m bored with what she has to say; I know from my own activism that going on about it too much is not going to make you any friends.
It’s evident that one of the problems with the larger hacker camps is not only that they have simply become too big, but that there are also some cultural traps which events can too readily fall into. Our conversation turned to those events we think get it right, and how we would approach an event of our own. One of my favourite events is a smaller one with under 500 attendees, whose organisers have a good handle on what makes a good event because they’re in large part making the event they want to be at. Thus it has a strong village culture, a lack of any of the trappings of a festival, and significant discouragement when it comes to people attending simply to be political activists.
That’s what I want to see more of, but even there is danger. I want it to remain awesome but not become a victim of its own success as so many events do. If it grows too much it will become a sterile clique of the same people grabbing all the tickets every time it’s held, and everyone else missing out. Thus there’s one final piece of the puzzle in ensuring that any hacker event doesn’t become a closed shop, that our camps should split and replicate rather than simply becoming ever larger.
Condensing the above, my friends and I came up with a four-rule model for the hacker camps we want.
Limited numbers, self replicating, village led, bring a hack.
Let’s look at those in more detail.
There’s something special about a camp where you can get to know everyone on the field at some level, and it’s visibly lost as an event gets larger. We had differing views about the ideal size of a small camp with some people suggesting up to 500 people, but I have good reasons for putting forward a hundred people as an ideal, with a hard limit at 150. The smaller a camp is the less work there is for its orga, and by my observation, putting on a camp for 500 people is still quite a lot of effort. 150 people may sound small, but small camps work. There’s also the advantage that staying small ducks under some red tape requirements.
As an event becomes more popular and fills up, that clique effect becomes a problem. So these events should be self replicating. When that attendee limit is reached, it’s time to repeat the formula and set up another event somewhere else. Far enough away to not be in direct competition, but near enough to be accessible. The figure we picked out of the air for Europe was 200 km, or around 120 miles, because a couple of hours drive is not insurmountable but hardly on your doorstep. This would eventually create a diverse archipelago of small related events, with some attendees going to more than one. Success should be measured in how many child events are spawned, not in how many people attend.
The strength of a hacker camp lies in its villages, yet larger camps increasingly provide all the fun centrally and starve the villages. The formula for a small camp should have the orga providing the field, hygiene facilities, power, internet, and nothing else, with the villages making the camp. Need a talk track? Organise one in your village. Want a bar to hang out and drink Club-Mate at? Be the bar village. It’s your camp, make it.
An event I wish I was in a position to attend is the Wasteland weekend, a post-apocalyptic festival in the Californian desert. Famously you will be denied entry to Wasteland if you aren’t post-apocalyptic enough, or if you deem post-apocalyptic to be merely cosplaying a character from a film franchise. The organisers restrict entry to the people who match their vision of the event, so of course all would-be attendees make an effort to follow their rules.
It’s an idea that works here: if you want to be part of a hacker camp, bring a hack. A project, something you make or do; anything (and I mean anything) that will enhance the event and make it awesome. What that is is up to you, but bringing it ensures you are not merely a spectator.
With those four ingredients, my friends and I think being part of the hacker and maker community can become fun again. Get all your friends and their friends, hire a complete camping site for a weekend outside school holidays, turn up, and enjoy yourselves. A bunch of Europeans are going to make good on this and give it a try, before releasing a detailed version of the formula for others to try too.
Maybe we’ll see you next summer.
