Should you travel around Europe, you may notice that things in France are ever so slightly different. Not necessarily better or worse, simply that the French prefer to plough their own furrow rather than importing cultural tends from their neighbors.

In the 1980s this was evident in their home computers, because as well as a Minitel terminal in your house, you could have an all-French machine plugged into your TV. [Retro Krazy] has just such a machine — it’s a Matra Hachette Alice 32, and its red plastic case hides hardware any of us would have been proud to own back in the day.

At first sight it appears superficially similar to a Sinclair Spectrum, with its BASIC keywords next to the keys. But under that slightly calculator style AZERTY keyboard is an entirely different architecture, a Motorola 6803. The first Alice computer was a clone of a Radio Shack model, and while this one has no compatibility with its predecessor it retains some silicon choices. On the back are a series of DIN sockets, one for a SCART adapter, and more for serial connectivity and a cassette deck. The overall impression is of a well-engineered machine, even if that red color is a little garish.

The Alice hasn’t appeared here on its own before, but we have taken a look at French retrocomputers here in the past.

From Blog – Hackaday via this RSS feed

From Al Jazeera – Breaking News, World News and Video from Al Jazeera via this RSS feed

The advantage of a radio-controlled clock that receives the time signal from WWVB is that you never have to set it again. Whether it's a little digital job on your desk, or some big analog wall clock that's hard to access, they'll all adjust themselves as necessary to keep perfect time. But what if the receiver conks out on you?

Well, you'd still have a clock. But you'd have to set it manually like some kind of Neanderthal. That wasn't acceptable to [jim11662418], so after he yanked the misbehaving WWVB receiver from his clock, he decided to replace it with an ESP8266 that could connect to the Internet and get the current time via Network Time Protocol (NTP).

This modification was made all the easier by the fact that the WWVB receiver was its own PCB, connected to the clock's main board by three wires: one for the clock signal, another that gets pulled low when the clock wants to turn on the receiver (usually these clocks only update themselves once a day), and of course, ground. It was simply a matter of connecting the ESP8266 dev board up to the two digital lines and writing some code that would mimic the responses from the original receiver.

If you take a look through the provided source code, a comment explains that the WWVB signal is recreated based on the official documentation from the National Institute of Standards and Technology (NIST) website. There are functions in the code to bang out the 500 ms "one" and 200 ms "zero" bits, and once the microcontroller has picked up the correct time from the Internet, they're called in quick succession to build the appropriate time signal. As such, this code should work on any clock that has an external WWVB receiver like this, but as always, your mileage may vary.

This is a very clean hack, but if you wanted to pull off something similar without having to gut all the clocks in your house, we've seen a WWVB simulator that can broadcast an NTP-backed time signal to anything listening nearby.

From Blog – Hackaday via this RSS feed

We've got a love-hate relationship with discount tool outlet Harbor Freight: we hate that we love it so much. Apparently, [James Clough] is of much the same opinion, at least now that he's looked into the quality of their outlet strips and found it somewhat wanting.

The outlet strips in question are Harbor Freight's four-foot-long, twelve-outlet strips, three of which are visible from where this is being written. [James] has a bunch of them too, but when he noticed an intermittent ground connection while using an outlet tester, he channeled his inner [Big Clive] and tore one of the $20 strips to bits. The problem appears to be poor quality of the contacts within each outlet, which don't have enough spring pre-load to maintain connection with the ground pin on the plug when it's wiggled around. Actually, the contacts for the hot and neutral don't look all that trustworthy either, and the wiring between the outlets is pretty sketchy too. The video below shows the horrors within.

What's to be done about this state of affairs? That's up to you, of course. We performed the same test on all our outlets and the ground connections all seemed solid. So maybe [James] just got a bad batch, but he's still in the market for better-quality strips. That's going to cost him, though, since similar strips with better outlets are about four times the price of the Harbor Freight units. We did find a similar strip at Home Depot for about twice the price of the HF units, but we can't vouch for the quality. As always, caveat emptor.

Thanks to [cliff claven] for the tip.

From Blog – Hackaday via this RSS feed

Afficionados of vintage electric organs will know about the Melotron, an instrument from the 1960s that had pre-recorded sounds on a bank of tape loops. A real Melotron in working order will set you back a bit, but it's possible to play with the idea using much more attainable hardware. [Decurus] has made a simple tape based synth using a cassette deck.

It uses a loop of cassette tape, and varies the pitch by changing the speed of the cassette motor. There's an RP2040 and a motor controller, which can take a MIDI signal and use it to drive the motor. We're sorry to see that there's no recording of the result, but it's described as a drone.

Part of this project is a 3D printed tape loop holder to fit a cassette mechanism. We won't go as far as to call it a cassette in itself, instead it's a sort of tape loop frame. We can see that it might be an interesting component for other tape loop experimenters, now that cassettes themselves are no longer ubiquitous. This certainly isn't the first tape pitch synth we've seen.

From Blog – Hackaday via this RSS feed

Yeah, yeah -- not a keyboard. But one keyboard-adjacent topic I'm certainly interested in is that of finding a satisfying mouse. Why settle for ticky micro-switches when you could have full-on thock in both peripherals?

My own personal peripherals. Banana mat for scale.

I've been using a Logitech Ergo M575 for a couple of years now. As you can see, it's a trackball with two extra buttons, which come programmed for forward and back. I find this next to useless, so I employed AutoHotKey and changed them to Ctrl+C on the up switch, and Ctrl+V on the down switch.

[Aknup] commented on the previous Keebin' and brought up MMO mice, which, I didn't know those things had a name other than maybe 'multi-button mice'. And yes, there are a few trackball MMOs out there. I've got my eye on a couple already.

Does anyone have a trackball MMO? I hate to spend $100+ on something I won't like. I'm intrigued that the one I found that's the most attractive is less a thumb trackball and more a two-fingers-at-once kind of situation. That will take some getting used to, but the way my trackball moves sometimes, it could be a really positive change.

Embrace the Jank, Why Don't You?

[VideoPuzzleheaded884] built this keyboard over a the course of a few evenings for a total cost of around $30 AUD ($18.33 USD as of this writing), as a way to motivate themselves to finally start soldering.

Image by [VideoPuzzleheaded884] via redditI for one like the look of the acrylic plate, which was worked with a Dremel and hand tools. And the wiring looks fine to me, so I hesitate to actually call this janky myself. But [VideoPuzzleheaded884] did it for me.

You can tell [VideoPuzzleheaded884] is one of us -- they cobbled this Corne mini layout-having keyboard together with stuff on hand, and did a fine job of soldering one of their first projects. Hey, if it works, it works. And the use of all-black wires should be commended.

The microcontroller is an ESP32-C3 [VideoPuzzleheaded884] found in box somewhere, and the switches are Gateron Silvers from an unknown time. All in all, this project was a fun diversion from programming, and this probably won't be the last keyboard they solder.

The Centerfold: Alas, Poor Yorick; I Knew Thee Cozy Vibes Well

Image by [Ryuk_void666] via redditThis one's all about the vibes, and not necessarily the peripherals. The keyboard is an Amazon UK number and the mouse is whatever, but the wrist rests sure look comfy, and the padding around the edge of the desk is divine.

The moon lamp looks great along with the fill light coming in from the right, and I could totally get down with some death metal and WFH with this setup.

Do you rock a sweet set of peripherals on a screamin' desk pad? Send me a picture along with your handle and all the gory details, and you could be featured here!

Historical Clackers: Oh Maskelyne, Why Can't You Be True?

What's a magician to do if they need something to fall back on? Sell typewriters, I suppose. Why else would a father-and-son team of illusionists named John Nevil Maskelyne (Jr. and Sr.) do such a thing?

Image via ozTypewriter

The Maskelynes' machine was initially seen at the Paris World's Fair, which lasted from May to October 1889. Four years later, it finally hit the market.

The main selling point of the Maskelyne was that it offered differential spacing. Most typewriters output monospaced text -- the skinny 'i' takes up the same width on the page as the 'w' does. On the Maskelyne, each character takes up a different amount of horizontal space. This makes for a nicer-looking document overall.

By 1897, the writing was on the wall. Maskelynes under heavy usage were falling apart. They were not built to withstand the vibration that typewriters must endure. As a result, things would go awry -- maybe the escapement clutch no longer moved far enough, or went too far, or the bars needed to make differential spacing possible clashed together.

By the third model of Maskelyne, they did away with differential spacing. But the investors were unhappy, and by 1899, the Maskelyne Typewriter concern did a disappearing act.

ICYMI: Stop Me If You Saw This Keyboard

We're embracing the jank this week, remember? And the end result of [nomolk]'s labor? Not janky at all.

Image by [nomolk] via YouTubeAfter sawing apart a perfectly good mechanical keyboard and re-connecting about 50 wires, [nomolk] managed to get it working again, and now has a true split keyboard. Be sure to watch the video!

This labor of love took almost three weeks, between rewiring all the broken connections and testing the wiring. [nomolk] tried it out and found it wasn't working as expected, with some keys not registering, and other keys registering two characters.

Once it was working, [nomolk] had a fine mess of all-black wires (!) to deal with. Between the zip ties and the plastic spiral wire wrap thingy, the beast was eventually tamed. That Spacebar would drive me crazy, though.

Got a hot tip that has like, anything to do with keyboards? [Help me out by sending in a link or two](mailto:tips@hackaday.com?Subject=[Keebin' with Kristina]). Don't want all the Hackaday scribes to see it? Feel free to [email me directly](mailto:kristinapanos@hackaday.com?Subject=[Keebin' Fodder]).

From Blog – Hackaday via this RSS feed

While low-cost professional PCB fabrication has largely supplanted making circuit boards at home, there's still something to be said for being able to go from design to prototype in an afternoon. Luckily we aren't limited to the old toner transfer trick for DIY boards these days, as CNC routers and powerful lasers can be used to etch boards quickly and accurately.

But there's still a problem -- those methods leave you with a board that has exposed traces. That might work in a pinch for a one-off, but such boards are prone to shorts, and frankly just don't look very good. Which is why [Mikey Sklar] has been experimenting with applying both a soldermask and silkscreen to his homemade boards.

The process he describes starts after the board has already been etched. First he rolls on the soldermask, and then sandwiches the board between layers of transparency film and clear acrylic before curing it under a UV light. After two coats of the soldermask, the board goes into a fiber laser and the silkscreen and mask layers are loaded into the software and the machine is set to a relatively low power (here, 40%). The trick is that the mask layer is set to run four times versus the single run of the silkscreen, which ensures that the copper is fully exposed.

Since the board doesn't need to be moved between operations, you don't have to worry about the registration being off. The end result really does look quite nice, with the silkscreen especially popping visually a lot more than we would have assumed.

We've previously covered how [Mikey] uses his CNC router and fiber laser to cut out and etch the boards, so this latest installment brings the whole thing full circle. The equipment you'll need to follow along at home isn't cheap, but we can't argue with the final results.

From Blog – Hackaday via this RSS feed

Over the history of the Web, we have seen several major shifts in browsing software. If you're old enough to have used NCSA Mosaic or any of the other early browsers, you probably welcomed the arrival of Netscape Navigator, and rued its decline in the face of Internet Explorer. As Mozilla and then Firefox rose from Netscape's corpse the domination by Microsoft seemed inevitable, but then along came Safari and then Chrome. For a glorious while there was genuine competition between browser heavyweights, but over the last decade we've arrived at a point where Chrome and its associated Google domination is the only game in town. Other players are small, and the people behind Firefox seem hell-bent on fleeing to the Dark Side, so where should we turn? Is there a privacy-centric open source browser that follows web standards and doesn't come with any unfortunate baggage in the room? It's time to find out.

It's All In The Engine

It's Hackaday, in NetSurf!

If you look at the breadth of standards which a modern web browser has to support, it's clear that writing a web browser is a Herculean task. Many browsers take the route of not trying to implement everything, for example minimalist browsers such as Dillo or NetSurf concentrate only on rendering web pages. For the purposes of this piece we're looking at full-fat browsers capable of being a daily driver though, and for that a browser needs some very capable software. Many development teams are not capable of writing such a browser engine, and thus use one developed for another browser. Despite there being many names on the table then, peering under the hood there are surprisingly few options. The Apple Webkit and Google Blink family of browsers dominate, followed by Mozilla Gecko and its Goanna fork, and then by promising bit-part players such as Servo, or the Ladybird browser's LibWeb. Having so much of the web's browser software dominated by Apple and Google is not an ideal situation, but it's where we find ourselves.

It's Hackaday, in Ladybird!

So when choosing a browser, the first thing we look at is its engine. Whose ecosystem are we becoming part of, and does that have any effect on us? Within reason all modern full-featured browser engines render websites the same, so there should be little to choose from in terms of the websites themselves.

Having considered the browser engine, next up are whatever the developer uses to differentiate themselves. It's suprisingly straightforward to construct a bare-bones web browser on top of WebKit, so to stand out each browser has a unique selling point. Is it privacy you're after, ad blocking, or just following a UI path abandoned by a previous browser? And perhaps most importantly, are you simply departing a problematic developer for one even shadier? It's worth doing your homework, and not being afraid to try multiple browsers before you find your home.

So Where Did Hackaday Land?

It's Hackaday, in Vivaldi! (We are sure you are getting the idea by now)

Over the course of writing for Hackaday it's inevitable that a bunch of different browsers will find their way on to my bench. Some of them like Ladybird or Servo I would love the chance to use as my daily driver, but they simply aren't mature enough for my needs. Others such as Brave have too much of a whiff of controversy around them for someone seeking a quiet life of open-source obscurity. As I write this I have a preposterous number of browsers installed on my machine, and if there's one thing which the experience has taught me it's that they are much more the same than I expected. In three decades our expectation of a browser has homogenised to the extent that I'm hard pressed to tell between them. How do I pick one, without blindly throwing a dart at a corkboard covered in browser logos?

In the end, I looked for two candidates, one each from the Firefox and Apple/Google orbits. I tried them all, and settled on LibreWolf from the former, and Vivaldi from the latter. LibreWolf because it's done a fine job of making Firefox without it being Firefox, and Vivaldi because its influence from the early Opera versions gave it a tiny bit of individuality missing in the others. I set up both with my usual Hackaday bookmarks, tabs, and shortcuts, changed the search engine to the EU-based Qwant. I'm ready to go, with a bit more control over how my data is shared with the world once more.

A refugee from the early Web writes…

It's a fairly regular occurrence, that I will Do a Linux Thing in my hackerspace, only to have one of my younger friends point out a much newer and better tool than the one I know, which I probably learned to use some time in the mid-1990s. I've fond looking at web browsers to be in some respects a similar experience even if the browsers are much closer to each other than I expected, because for a couple of decades now I've been a Firefox user simply because Firefox was the plucky upstart open-source browser. Mozilla's previous attempts to take Netscape 6 and make it the only piece of Internet software you needed were horribly bloated, and Firefox, or "Phoenix" as it launched, was an easy choice. Just as my operating system journey taught me about software complacency a couple of years ago, so I've now had the same awakening in the browser. The Web will never look the same again.

From Blog – Hackaday via this RSS feed

Using USB for powering devices is wonderful, as it frees us from a tangle of incompatible barrel & TRS connectors, not to mention a veritable gaggle of proprietary power connectors. The unfortunate side-effect of this is that the obvious thing to do with power connectors is to introduce splitters, which can backfire horribly, especially since USB-C and USB Power Delivery (USB-PD) were introduced. The [Quiescent Current] channel on YouTube recently went over the ways in which these handy gadgets can literally turn your USB-powered devices into a smoldering pile of ashes.

Much like Qualcomm's Quick Charge protocols, USB-PD negotiates higher voltages with the power supply, after which this same voltage will be provided to any device that's tapped into the power supply lines of the USB connector. Since USB-C has now also taken over duties like analog audio jacks, this has increased the demand for splitters, but these introduce many risks. Unless you know how these splitters are wired inside, your spiffy smartphone may happily negotiate 20V that will subsequently fry a USB-powered speaker that was charging off the same splitter.

In the video only a resistor and LED were sacrificed to make the point, but in a real life scenario the damage probably would be significantly more expensive.

From Blog – Hackaday via this RSS feed

If you made something blink, and now it’s time for you to make something move , something like a point-to-a-satellite tracker is a great idea. [Farid] made this moving arrow that always points at the ISS, and documented it nicely to boot.

And there’s a little bit of everything here, from orbital mechanics and fetching the two-line elements (TLE) from the web, to writing the code to translate that into the tabletop machine’s coordinate system. It looks like [Farid] hadn’t done much 3D CAD before, so he got a chance to stretch those muscles too. Finally, it served as an introduction to resource-constrained programming: “This was the first time I’ve had to think about the size of a compiled binary - the most frustrating part was figuring out that using a C++ stringstream was adding too much code to my binary.”

[Farid] is learning a lot here, and you might too. For instance, using pencil lead (graphite) as a lubricant on sliding 3D-printed parts is new to us, but makes sense. We’ll have to try that out.

And while this is a simple desktop tracker, with a lot more mechanical design, the same basics could be put to real use for pointing a receiver dish. Of course, who says you need fancy motors and computers to point a satellite dish anyway? If you work on your arm muscles a bit, you could become the satellite pointer.

From Blog – Hackaday via this RSS feed

It's likely that among the readers of this article there will be many who collect something. Whether it's rare early LEDs or first-year-of-manufacture microprocessors, you'll scour the internet to find them, and eagerly await mystery packages from the other side of the world.

There's a tale emerging from Australia featuring just such a collector, whose collection now has him facing a jail sentence for importing plutonium. The story however is not so clear-cut, featuring a media frenzy and over-reaction from the authorities worthy of Gatwick Airport. [Explosions&Fire] has a rather long video unpacking the events, which we've placed below the break.

Emmanuel Lidden is an element collector, someone who tries to assemble an entire Periodic Table in their collection. He ordered a range of elements from an American element collectors' supply website, including samples of plutonium and thorium. He seems to have been unaware he was committing any crime, with the microscopic samples available from legitimate websites with no warnings attached. The case becomes murkier as the Australian authorities flagged the thorium sample and instructed the courier not to deliver it, which they did anyway. Then a raid of the type you'd expect for the terrorists who stole the plutonium in Back To The Future was launched, along with that Gatwick-esque media frenzy.

We're inclined to agree that the penalty likely to be meted out to him for buying a sliver of a Soviet smoke detector embedded in a Lucite cube seems overly steep, but at the same time his obvious naivety over dealing in radioactive materials marks him as perhaps more than a little foolhardy. It's something over which to ponder though, have we managed to amass anything illegal disguised as outdated devices? Have you? Perhaps it's something to discuss in the comments.

From Blog – Hackaday via this RSS feed

The RTL-SDR dongles get most of the love from people interested in software-defined radio, but the Pluto is also a great option, too. [FromConceptToCircuit] shares code to turn one of these radios into a spectrum analyzer that sweeps up to 6 GHz and down to 100 MHz. You can see a video of how it works below.

While it may seem that 100 MHz is a bit limiting, there's plenty of activity in that range, including WiFi, Bluetooth, radio systems, both commercial and amateur, and even cell phones.

The system uses a lock-in amplifier technique for best performance. The Python code is straightforward. You simply scan all frequencies and determine the signal strength at each point. Of course, the devil is in the details.

We covered using Pluto with GNU Radio a while back. We like how it connects like a network adapter, among other things. Spectrum analysis is a common project for one of these SDRs.

From Blog – Hackaday via this RSS feed

A couple of months back, Electronic Arts did something uncharacteristically benevolent and released several of the old Command and Conquer games under the GPLv3. Logically, we knew that opened the doors up to the games being ported to new operating systems and architectures, but we admit that it was still a little surprising to see Command and Conquer: Red Alert running on the Raspberry Pi Pico 2.

[Charlie Birks] documented the process of getting the 1996 game up and running on the microcontroller in a series of Mastodon posts spanning a few days in March. Seeing the incremental progress made each day makes for interesting reading, as he moves from the game just barely starting up to being able to complete missions and eventually even get multiplayer going between two Picos.

As [Charlie] clarifies, he's technically using the Pimoroni Pico Plus 2 W, which takes the RP2350B from the official Pico 2, adds 8 MB of PSRAM, and bumps the onboard flash to 16 MB. The upgraded specs and an SD card are required to get the game running, as content that would have originally been held in RAM on the computer must instead be pulled from flash.

For an even more streamlined experience, he eventually slaps the Pico Plus 2 W into the Pimoroni Pico VGA Demo Base -- which provided not only an integrated SD card slot, but (as the name implies) VGA output.

It's still early days, but [Charlie] has been pushing all of his code changes into his fork of Red Alert on GitHub for anyone who wants to play along at home. If you get his fork compiled and running on your own Pico, we'd love to hear about it in the comments.

From Blog – Hackaday via this RSS feed

There's a dedicated group of users out there that aren't ready to let their beloved IBM PC110 go to that Great Big Data Center in the Sky. Unfortunately, between the limited available technical information and rarity of replacement parts, repairing the diminutive palmtops can be tricky.

Which is why [Ahmad Byagowi] has started a project that aims to not only collect all the available schematics and datasheets that pertain to the machine, but to reverse engineer all of the computer's original circuit boards. Working from optical and x-ray scans, the project has already recreated the motherboard, power supply, modem, keyboard, and RAM module PCBs in KiCad.

Just last week the project released production-ready Gerbers for all the boards, but considering there have been 45+ commits to the repository since then, we're going to assume they weren't quite finalized. Of course, with a project of this magnitude, you'd expect it to take a few revisions to get everything right. (Hell, we've managed to screw up board layouts that had fewer than a dozen components on them.)

If you'd like to lend a hand, [Ahmad] says he could use the help. Beyond checking the boards for problems and reporting issues, he's also on the hunt for any datasheets or other documentation that can be found for the PC110 or its components. It looks like there's still schematic work that needs to be done as well, so if your idea of zen is figuring out how ~30 year old computers were wired up internally, this might be the perfect summer project for you.

Interestingly, our very own [Arya Voronova] has been working on creating a drop-in replacement motherboard for the Sony Vaio P using KiCad and imported board images. That hobbyists are now able to do this kind of work using free and open source tools is a reminder of just how far things have come in the last few years.

Thanks to [adistuder] for the tip.

From Blog – Hackaday via this RSS feed

If Clive Sinclair's genius in consumer electronics was in using ingenious hacks to make cheaper parts do greater things, then his Amstrad competitor Alan Sugar's was in selling decade-old technology to consumers as new and exciting. His PCW series of computers are a great example, 1970s CP/M machines smartly marketed for late 1980s home offices. They were a popular choice at the time, and [Retro Recipes] has one. In a video filmed in period standard definition he's taking us through a repair to its Gotek drive, and then a RAM upgrade.

The repair and upgrade are fairly straightforward, the former being a failed OLED screen on the drive and the latter being the installation of a bank of DIP memory chips. The interest lies in how they cost-minimised a CP/M machine as a consumer product. The board relies heavily on custom chips as you might expect, and there's a brief glimpse of one of those unusual 3″ floppy drives. The power supply is part of the monitor board as was often the case with Amstrad machines, and the whole thing is about as simple as it can be. The full video can be found below the break.

We're guessing that particularly in the UK there will be plenty of PCWs still languishing in dusty attics, but surprisingly given their popularity at the time we see less of them that might be expected. There has been a significantly upgraded model on these pages though.

From Blog – Hackaday via this RSS feed

[Georges Gagnerot] has been trying to emulate iOS and run iPhone software in a virtual environment. There were a few choices, and qemu-t8030 had a number of interesting features that you can check out in his post.

The project requires a patched QEMU, and [Georges] did some basic jailbreaking techniques. The real problem, of course, was not having the Apple Silicon GPU. Older versions of iOS let you select software rendering, but that option is gone on newer versions. However, it was possible to patch the phone to still use software rendering. There are still apps that directly use Metal or OpenGL that won't run, but that's another problem.

There is a plan to explore forwarding GPU calls to a real device. However, that seems difficult so it will have to wait for now.

That wasn't the last problem, of course. But the post gives you a great view into the detective work. There is still work to go, but it looks like a lot of progress.

You can find the t8030 code on GitHub. Most of the iPhone hacking we see is hardware even if it means cutting the screen.

From Blog – Hackaday via this RSS feed

It's been 30 years since Windows 95 launched. [Ms-Dos5] and [Commodore Z] are celebrating with an epic exhibit at VCF East 2025. They had no fewer than nine computers -- all period-correct machines running versions of Windows 95. The pictures don't do it justice, so if you are near Wall, NJ, on Sunday, April 5, 2025, definitely go check out this and the rest of the exhibits at VCF.

An exhibit like this isn't thrown together overnight. [Commodore Z] and [Ms-Dos5] worked for months to assemble the right mix of desktops, laptops, and prehiperals to showcase Windows 95. Many of the computers are networked as well - which was no easy task. One particular Thinkpad 760e required pliers and force to remove a stuck PCMCIA modem card. After a struggle that was ultimately destructive to the card, the pair determined it was stuck due to a sticker that had effectively glued the card into the laptop. As the sticker finally gave up, the card popped itself out of the laptop.

Hardware isn't the only story of this Windows 95 exhibit. An operating system is software, after all. The team has plenty of software running. Some highlights are Kidpix, MS-paint, Lego Island, LucasArts Full Throttle, Duke Nukem 3D, Word 97, and Space Cadet Pinball, which came with the Plus! expansion pack. There is a huge array of original boxes for Windows 95 software. It's a nostalgia trip to see software in boxes, especially in all those bright 90's colors.

The various versions of Windows 95 are also represented. [Ms-Dos5] and [Commodore Z] are running all major versions from Chicago beta 73g to Windows 95 C / OSR2.5.

If you're old enough to remember 1995, the Windows 95 launch event was a big deal. Windows 3.0 series was five years old at that point. Millions of people owned PC compatible computers and were ready for something new and flashy, and Windows 95 delivered. Thanks to [Commodore Z] and [Ms-Dos5] keeping this bit of internet history alive.

From Blog – Hackaday via this RSS feed

The F-number of a photographic lens is a measure of its light-gathering ability, and is expressed as its aperture diameter divided by its focal length. Lenses with low F-numbers are prized by photographers for their properties, but are usually expensive because making a good one can be something of a challenge. Nevertheless [Rulof] is giving it a go, making an 80mm F0.5 lens with a Sony E-mount. The video below the break has all the details, and also serves as a fascinating primer on lens design if you are interested.

Rather than taking individual lenses, he's starting with the second-hand lens from an old projector. It's got the required huge aperture, but it's by no means a photographic lens. An interesting component is his choice of diaphragm for the variable aperture, it's a drafting aid for drawing circles which closely resembles a photographic part. This is coupled with the triplet from an old SLR lens in a 3D-printed enclosure, and the result is a lens that works even if it may not be the best. We know from experiences playing with lens systems that adjusting the various components of a compound lens like this one can be very difficult; we can see it has the much sought-after bokeh or blurred background, but it lacks sharpness.

Perhaps because a camera is an expensive purchase, we don't see as much of this kind of hacking as we'd like. That's not to say that lenses don't sometimes make their way here.

From Blog – Hackaday via this RSS feed

[Ben Eater]’s breadboard 6502 computer is no stranger to these parts, so it was a bit of a surprise that when [Mark] wrote in asking us if we’d covered [Ben]’s getting MS BASIC running on the breadboard, that our answer was “no”. Well, that changes today!

This is a three-part video series, documenting how [Ben Eater] ports a 1977 version of MS BASIC to his 6502-based computer. The first video is all about just getting the BASIC up and working. It’s full of detail about how MS BASIC adapts to different architectures on the inside, and [Ben] essentially defines his own along the way.

Once he has BASIC working, the next two videos are about making it work not just with the serial terminal that he has attached, but also with the LCD display peripheral he has plugged into the breadboard. BASIC fans will not be surprised to see that it’s all about using POKE. But that ends up being to slow, so he extends it out with his own LCDPRINT command written in assembly.

Now that he can write a character to the LCD, he wants to be able to pass it a string: LCDPRINT “Hello world”. But that requires his command to be able to parse a string, and this has him diving down the rabbit hole into how MS BASIC parses strings, handles evals, and so on. If you want to know how MS BASIC works on the inside, this is the video for you. This video makes a lot of use of wozmon, which seems an almost ideal tool for this kind of low-level poking around.

All of this is done in [Ben]’s very well rehearsed, accessible, but pulling-no-punches style. Get ready to nerd out. All three of the videos are embedded just below the break.

While it’s not the Altair BASIC that Bill himself was writing about last week, it’s probably a direct descendent, and reading about the Altair version was what spurred [Mark Stevens] to send us the tip. Thanks!

From Blog – Hackaday via this RSS feed

If you think of records as platters, you are of a certain age. If you don't remember records at all, you are even younger. But there was a time when audio records were not flat -- they were drums, which was how the original Edison phonograph worked. [Our Own Devices] did a video earlier showing one of these devices, but since it was in a museum, he didn't get to open it up. Lucky for us, he now has one of his own, and we get to see inside in the video below.

Ironically, Edison was deaf yet still invented the phonograph. While he did create the working phonograph -- his self-identified most important invention -- the original invention wasn't commercially viable. You could record and playback audio on tin foil wrapped around a drum. But you couldn't remove the foil without destroying it.

Edison was busy, but another inventor related to Bell created a similar system that used wax cylinders instead of foil. Edison's vision for his invention didn't include popular music, which hurt sales.

If you want to skip the history lesson -- although it is well worth watching -- you can skip to the 9-minute mark. You can hear the machine play and then see the box come off.

Oddly, people were recording things before they were able to play them back. Keeping a machine like this running can be quite a challenge.

From Blog – Hackaday via this RSS feed

If you're living your life right, you probably know what as MOSFET is. But do you know the MESFET? They are like the faster, uninsulated, Schottky version of a MOSFET, and they used to rule the roost in radio-frequency (RF) silicon. But if you're like us, and you have never heard of a MESFET, then give this phenomenal video by [Asianometry] a watch. In it, among other things, he explains how the shrinking feature size in CMOS made RF chips cheap, which brought you the modern cellphone as we know it.

The basic overview is that in the 1960s, most high-frequency stuff had to be done with discrete parts because the bipolar-junction semiconductors of the time were just too slow. At this time, MOSFETs were just becoming manufacturable, but were even slower still. The MESFET, without its insulating oxide layer between the metal and the silicon, had less capacitance, and switched faster. When silicon feature sizes got small enough that you could do gigahertz work with them, the MESFET was the tech of choice.

As late as the 1980s, you'd find MESFETs in radio devices. At this time, the feature size of the gates and the thickness of the oxide layer in MOSFETs kept them out of the game. But as CPU manufacturers pushed CMOS theses features smaller, not only did we get chips like the 8086 and 80386, two of Intel's earliest CMOS designs, but the tech started getting fast enough for RF. And the world never looked back.

If you're interested in the history of the modern monolithic RF ICs, definitely give the 18-minute video a watch. (You can skip the first three or so if you're already a radio head.) If you just want to build some radio circuits, this fantastic talk from [Michael Ossmann] at the first-ever Supercon will make you an RF design hero. His secrets? Among them, making the most of exactly these modern everything-in-one-chip RF ICs so that you don't have to think about that side of things too hard.

Thanks [Stephen] for the tip!

From Blog – Hackaday via this RSS feed

Meet the little board that could: [alcor6502]'s tiny USB relay controller, now evolved into a multifunction marvel. Originally built as a simple USB relay to probe the boundaries of JLCPCB's production chops, it has become a compact utility belt for any hacker's desk drawer. Not only has [alcor6502] actually built the thing, he even provided intstructions. If you happened to be at Hackaday in Berlin, you now might even own one, as he handed out twenty of them during his visit. If not, read on and build it yourself.

This thing is not just a relay, and that is what makes it special. Depending on a few solder bridges and minimal components, it shape-shifts into six different tools: a fan controller (both 3- and 4-pin!), servo driver, UART interface, and of course, the classic relay. It even swaps out a crystal oscillator for USB self-sync using STM32F042's internal RC - no quartz, less cost, same precision. A dual-purpose BOOT0 button lets you flash firmware and toggle outputs, depending on timing. Clever reuse, just like our mothers taught us.

It's the kind of design that makes you want to tinker again. Fewer parts. More function. And that little smile when it just works. If this kind of clever compactness excites you too, read [alcor6502]'s build log and instructions here.

From Blog – Hackaday via this RSS feed

3D scanning is becoming much more accessible, which means it's more likely that the average hacker will use it to solve problems -- possibly odd ones. That being the case, a handy tool to have in one's repertoire is a way to work with point clouds. We'll explain why in a moment, but that's where CloudCompare comes in (GitHub).

Not all point clouds are destined to be 3D models. A project may call for watching for changes in a surface, for example.

CloudCompare is an open source tool with which one can load up and do various operations on point clouds, including generating mesh models from them. Point clouds are what 3D scanners create when an object is scanned, and to become useful, those point clouds are usually post-processed into 3D models (specifically, meshes) like an .obj or .stl file.

We've gone into detail in the past about how 3D scanning works, what to expect from it, and taken a hands-on tour of what an all-in-one wireless scanner can do. But what do point clouds have to do with getting the most out of 3D scanning? Well, if one starts to push the boundaries of how and to what purposes 3D scanning can be applied, it sometimes makes more sense to work with point clouds directly instead of the generated meshes, and CloudCompare is an open-source tool for doing exactly that.

For example, one may wish to align and merge two or more different clouds, such as from two different (possibly incomplete) scans. Or, you might want to conduct a deviation analysis of how those different scans have changed. Alternately, if one is into designing wearable items, it can be invaluable to be able to align something to a 3D scan of a body part.

It's a versatile tool with numerous tutorials, so if you find yourself into 3D scanning but yearning for more flexibility than you can get by working with the mesh models -- or want an alternative to modeling-focused software like Blender -- maybe it's time to work with the point clouds directly.

From Blog – Hackaday via this RSS feed

Usually when we talk about retrocomputing, we want to look at -- and in -- some old hardware. But [Z→Z] has a different approach: dissecting MacPaint, the Apple drawing program from the 1980s.

While the program looks antiquated by today's standards, it was pretty hot stuff back in the day. Things we take for granted today were big deals at the time. For example, being able to erase a part of something you drew prompted applause at an early public demo.

We enjoyed the way the program was tested, too. A software "monkey" was made to type keys, move things, and click menus randomly. The teardown continues with a look inside the Pascal and assembly code with interesting algorithms like how the code would fill an area with color.

The program has been called "beautifully organized," and [Z→Z] examines that assertion. Maybe the brilliance of it has been overstated, but it did work and it did influence many computer graphics programs over the years.

We love digging through old source code. Even old games. If you do your own teardowns, be sure to send us a tip.

From Blog – Hackaday via this RSS feed

[Antoine Pirrone] and [Grégoire Passault] are making a DIY miniature re-imagining of Disney's BDX droid design, and while it's still early, there is definitely a lot of progress to see. Known as the Open Duck Mini v2 and coming in at a little over 40 cm tall, the project is expected to have a total cost of around 400 USD.

The inner workings of Open Duck Mini use a Raspberry Pi Zero 2W, hobby servos, and an absolute-orientation IMU.

Bipedal robots are uncommon, and back in the day they were downright rare. One reason is that the state of controlled falling that makes up a walking gait isn't exactly a plug-and-play feature.

Walking robots are much more common now, but gait control for legged robots is still a big design hurdle. This goes double for bipeds. That brings us to one of the interesting things about the Open Duck Mini v2 : computer simulation of the design is playing a big role in bringing the project into reality.

It's a work in progress but the repository collects all the design details and resources you could want, including CAD files, code, current bill of materials, and links to a Discord community. Hardware-wise, the main work is being done with very accessible parts: Raspberry Pi Zero 2W, fairly ordinary hobby servos, and an BNO055-based absolute orientation IMU.

So, how far along is the project? Open Duck Mini v2 is already waddling nicely and can remain impressively stable when shoved! (A "testing purposes" shove, anyway. Not a "kid being kinda mean to your robot" shove.)

Check out the videos to see it in action, and if you end up making your own, we want to hear about it, so remember to send us a tip!

From Blog – Hackaday via this RSS feed