If you’ve ever bought a modchip that adds features to your game console, you might have noticed sanded-off IC markings, epoxy blobs, or just obscure chips with unknown source code. It’s ironic – these modchips are a shining example of hacking, and yet they don’t represent hacking culture one bit. Usually, they are more of a black box than the console they’re tapping into. This problem has plagued the original XBOX hacking community, having them rely on inconsistent suppliers of obscure boards that would regularly fall off the radar as each crucial part went to end of life. Now, a group of hackers have come up with a solution, and [Macho Nacho Productions] on YouTube tells us its story – it’s an open-source modchip with an open firmware, ModXO.

Like many modern modchips and adapters, ModXO is based on an RP2040, and it’s got a lot of potential – it already works for feeding a BIOS to your console, it’s quite easy to install, and it’s only going to get better. [Macho Nacho Productions] shows us the modchip install process in the video, tells us about the hackers involved, and gives us a sneak peek at the upcoming features, including, possibly, support for the Prometheos project that equips your Xbox with an entire service menu. Plus, with open-source firmware and hardware, you can add tons more flashy and useful stuff, like small LCD/OLED screens for status display and LED strips of all sorts!

If you’re looking to add a modchip to your OG XBOX, it looks like the proprietary options aren’t much worth considering anymore. XBOX hacking has a strong community behind it for historical reasons and has spawned entire projects like XBMC that outgrew the community. There’s even an amazing book about how its security got hacked. If you would like to read it, it’s free and worth your time. As for open-source modchips, they rule, and it’s not the first one we see [Macho Nacho Productions] tell us about – here’s an open GameCube modchip that shook the scene, also with a RP2040!

If you want to read something from magnetic tape, you need a tape head, right? Or you could do like [Igor Brichkov] and make your own. It looks surprisingly simple. He used a washer with a small slot cut in it and a coil of wire.

The first experiment, in the first video below, is using a commercial tape head connected to a preamp. Music playing “through” the homemade head is readable by the commercial tape reader. This is a prelude to creating an entire tape deck using the head, which you can see in the second video below.

The homemade deck is a collection of small protoboards along with some hodgepodge components, a Bluetooth board, and aluminum foil shielding. One of the protoboards has a simple VU meter using eight LEDs.

We aren’t sure what possessed [Igor] to want to make a tape deck, and — to be fair — it looks like he borrowed the transport mechanism from a commercial player. But we never really need an excuse to build something cool, so we appreciate him sharing his DIY tape deck with us and the world.

If you want to know just about anything related to tape decks, we have some suggested reading for you. If you have trouble finding parts for your cassette collection, maybe fire up your 3D printer.

You know the feeling of having just created a perfect setup for your hacker lab? Sometimes, there’s just this missing piece in the puzzle that requires you to do a small hack, and those are the most tempting. [maxime borges] has such a perfect setup that involves a HDMI 4:2 switch, and he brings us a write-up on integrating that HDMI switch into Home Assistant through emulating an infrared receiver’s signals.

The HDMI switch is equipped with an infrared sensor as the only means of controlling it, so naturally, that was the path chosen for interfacing the ESP32 put inside the switch. Fortunately, Home Assistant provides the means to both receive and output IR signals, so after capturing all the codes produced by the IR remote, parsing their meaning, then turning them into a Home Assistant configuration, [maxime] got HDMI input switching to happen from the comfort of his phone.

We get the Home Assistant config snippets right there in the blog post — if you’ve been looking for a HDMI switch for your hacker lair, now you have one model to look out for in particular. Of course, you could roll your own HDMI switch, and if you’re looking for references, we’ve covered a good few hacks doing that as part of building a KVM.

Some people trick out their cars. Some, their computers. There are even people who max out their audio systems, although back in 1979, there was more of that going on, probably, than today where you discresionary income is split so many ways. Case in point: [Alan Cross] remembers how excited he was to get the Radio Shack catalog that year. He was working at a grocery store, saved his money, and — over time — picked up a haul ranging from an equalizer to a strobe light.

Who didn’t need a power meter or a “light organ?” These gadgets seem cheap until you realize it was 1979 and [Alan] was a student working at a grocery store. He points out that the $20 power meter is about the same as $80 today.

Not that he got everything he wanted back then, either. He also wanted an Atari light synthesizer known as the C240. This oddball device converted sound from your stereo into video patterns on your TV. What did that look like? An old video from [World One Video] shows it off:

If you could find one in 1977, the $170 price tag might have put you off.

There are other gadgets to explore. A tiny TV/oscilloscope, an audio expander, and quite a few other period gizmos.

We are suckers for old tech around here, although usually towards electronic hobby gadgets. Not that we didn’t take an interest in mobile record players or 8-track scanners.

Usually when we see arcade cabinet builds, they’re your standard single-player stand up variety. Even one of them takes up quite a bit of room, so as appealing as it might be to link up two or more cabinets together for the occasional multiplayer session, the space required makes it a non-starter for most of us.

But this cleverly designed 4-player cocktail cabinet from [OgrishGadgeteer] goes a long way towards solving that problem. The circular design of the cabinet gives each player a clear view of their respective display in a much smaller footprint than would otherwise be possible, and the glass top allows the whole thing to double as an actual cocktail table when it’s not game time.

According to a post on r/cade, it took [OgrishGadgeteer] three months to go from paper sketches of the cabinet’s basic shape to the final product. Most of the components were picked up on the second hand market, which brought the total cost of the build to around $350. That wouldn’t have been a surprising price for a traditional full-size cabinet build, so for this, it seems like an absolute steal.

A Dell OptiPlex 7060 small form factor PC provides the power for this build, with the video output passing through a 4-way VGA distribution amplifier into 20 inch monitors. At $75, the four player control kit ended up being the single most expensive component of the build, though you could make do with some parts bin buttons and a Pi Pico if you wanted to really bring this one in on a budget.

Perhaps the most surprising element of the whole build is that, despite the cabinet’s complex design, [OgrishGadgeteer] pulled it off without a CNC to cut the plywood panels. Instead, a vinyl cutter was used to make full-size templates of the cuts and holes that needed to be made, which were attached directly to the wood. After that, it was just a matter of following the lines with a jigsaw. Not the fastest or most convenient solution, but it’s hard to argue with the final results.

We’ve seen other cocktail cabinet builds in the past, but this is the first that managed to cram four players in. Well, unless you count Dungeons & Dragons, anyway.

A good amount of hacks can be done with off-the-shelf hardware – what’s more, it’s usually available all over the world, which means your hacks are easier to build for others, too. Say, you’ve built something around a commonly available portable router, through the magic of open-source software. How do you make the fruits of your labour easy to install for your friends and blog readers? Well, you might want to learn a thing or two from [Albert], who shows us a portable DLNA server built around a GL-MT300N-V2 pocket router.

[Albert]’s blog post is a tutorial on setting it up, with a pre-compiled binary image you can flash onto your router. Flash it, prepare a flash drive with your media files, connect to the WiFi network created by the router, run the VLC player app, and your media library is with you wherever you go.

Now, a binary image is good, but are you wondering how it was made, and how you could achieve similar levels of user-friendliness in your project? Of course, here’s the GitHub repository with OpenWRT configuration files used to build this image, and build instructions are right there in the README. If you ever needed a reference on how to make commonly available OpenWRT devices do your bidding automagically, this is it.

This is an elegant solution to build an portable DLNA server that’s always with you on long rides, and, think of it, it handily beats a typical commercialized alternative, at a lower cost. Want software upgrades? Minor improvements and fixes? Security patches? Everything is under your control, and thanks to the open-source nature of this project, you have a template to follow. There won’t always be a perfectly suited piece of hardware on the market, of course, as this elegant dual-drive Pi-based NAS build will attest.

Any reader who has bought a TV in recent years will know that it’s now almost impossible to buy one that’s just a TV. Instead they are all “smart” TVs, with an on-board computer running a custom OS with a pile of streaming apps installed. It fits an age in which linear broadcast TV is looking increasingly archaic, but it brings with it a host of new challenges.

Normally you’d expect us to launch into a story of privacy invasion from a TV manufacturer at this point, but instead we’ve got [Priscilla]’s experience, in which her HiSense Android TV executed a denial of service on the computers on her network.

The root of the problem appears to be the TV running continuous network discovery attempts using random UUIDs, which when happening every few minutes for a year or more, overloads the key caches on other networked machines. The PC which brought the problem to light was a Windows machine, which leaves us sincerely hoping that our Linux boxen might be immune.

It’s fair to place this story more under the heading of bugs than of malicious intent, but even so it’s something that should never have made it to production. The linked story advises nobody to buy a HiSense TV, but to that we’d have to doubt that other manufactures wouldn’t be similarly affected.

Header: William Hook, CC-BY-SA 2.0.

Thanks [Concretedog] for the tip.