Mysterious Files PH

You can get an IDE to USB bridge from all the usual sources, but you may find those fail on the older drives in your collection– apparently they require drives using logical block addressing, which did not become standard until the mid-1990s. Some while some older drives got in on the LBA game early, you were more likely to see Cylinder-Head-Sector (CHS) addressing. That’s why [JJ Dasher], a.k.a [redruM0381] created ATABoy, an open-source IDE bridge that can handle the oldest drives that fit on the bus.

The heart of the build is an RP2350, which serves as both IDE and USB host controller. To computer, after a little bit of setup, the drive attached to ATABoy shows up as a regular USB mass storage device. A little bit of setup is to be expected with drives of this vintage, you may remember. Luckily [JJ] included a handy BIOS-themed configuration utility that can be accessed through any serial console. He says you’ll usually be able to get away with “Auto Detect & Set Geometry,” but if you need to plug in the CHS values yourself, well, it’ll feel just like old times. Seeing is believing, so check it out in the demo video embedded below.

Though the custom PCB has a USB-C connector, and the USB-C standard could provide enough power for ye olde spinning rust drives, [JJ] didn’t include any power delivery with ATABoy. If you’re using it with a desktop, you can use the PSU in the box; MOLEX hasn’t changed. If you’re on a laptop, you’ll need another power supply– perhaps this USB-C powered benchtop unit.

If you’re using a Raspberry Pi or similar SBC, go ahead and skip USB entirely–the GIPO can do PATA IDE.

You wake up in the middle of the night. Is it time to get up? Well, you can look at the nightstand clock. Unless your partner is in the way. Whoops. Even then, without your glasses, the time is just a fuzzball of light. You could ask Alexa, but that’s sure to wake your partner, too. The answer is a projection clock. In its modern form, it shoots a digital time display on a wall or ceiling with digits so large that you don’t need your glasses. If you can see the ceiling, you can tell what time it is.

New Tech

A modern invention, of course. No, not really. According to [Roger Russel], a UK patent in 1909 used an analog clock face and lightbulbs to project the clock face and hands on the ceiling. Unfortunately, [Roger’s] website is no more, but the Wayback Machine is on the job. You can see a device of the same type at the British Museum.

In 1938, [Leendert Prins] filed for a patent on a similar projection clock. Sometimes known as “ceiling clocks” or “night clocks,” these devices often have a regular clock visible as well as a way to project the time. In the old days, this was often an image of a translucent analog clock lit up by light bulbs. In the modern era, it is almost always either LEDs or an LCD with a halogen backlight. Of course, there are many variations. A clock might use numbers on a rotating drum with a lamp behind it, for example.

Development

It isn’t hard to imagine someone putting a pocket watch in a magic lantern as a prototype. In general, some bright light source has to pass through a condenser lens. The light then travels through the LCD or translucent clock face. Finally, a projector lens expands the image.

We couldn’t find much about the actual history of old projection clocks outside of [Roger’s] defunct website. But if you can project an image and build a clock, all you need is the idea to combine them.

Teardowns

Want to get one and tear it open to see how it works? You don’t have to since [Soudnmisen] and [svetnovinek.cz] already did that for you, as you can see in the videos below.

Of course, what you project doesn’t have to be just the time. We’ve seen clocks that can project the weather, for example. But, usually, all you need in the middle of the night is the time.

DIY

Clocks are always a fun project, and a projection clock is certainly in the realm of a homebrew project. You could use a lot of methods to form the clock face, or, like [OSO POLAR MOVIES] did in the video below, just shine a light on your analog clock. Sure, that’s cheating, but it is certainly a hack.

If you prefer, try an LCD. Or a VFD. If you want to go analog and can’t put together a translucent clock face, try making a clock face from a mirror. You can remove the marks and numbers so they don’t reflect, and then use normal clock hands, which will block light just fine. You’ll just have to reverse the clock movement to run backwards, but that’s easy, too.

How about you? What strange method would you use to draw the time on the ceiling? A laser and a galvo come to mind. A tiny CRT? Then again, you could just mount a giant display on your ceiling. That’s how they did it at a Kentucky library. Let us know your plans in the comments, and when you have it done, send us a tip.

One of the issues with nuclear power plants is that they produce long-lived radioactive waste. Storing spent nuclear fuel is a real problem. However, researchers at the Department of Energy’s Thomas Jefferson National Accelerator Facility have made strides not only to produce more electricity from spent fuel but also to break it down into shorter-lived nuclear waste. [Aman Tripathi] shares the details about NEWTON, a program to fire high-energy protons at a target to produce a flood of neutrons that can interact with nuclear waste. You can read the original press release, too.

Short-lived, of course, is a relative term. Unprocessed spent fuel may be dangerous for about 100,000 years. After the proposed processing, the danger period is down to “only” 300 years. On the plus side, the process generates a lot of heat, which you can convert to electricity in the usual way.

While 300 years is a long time, it isn’t difficult to imagine storing waste for that period of time. So why isn’t this a no-brainer? The process is not efficient. You need cryogenic cooling for superconducting, although there is work to make higher-temperature alternatives.

The other hurdle is power usage. You probably have a microwave oven with a magnetron. The magnetron in this project needs 10 megawatts of power. Researchers hope to process all of the US nuclear waste within the next 30 years.

If you haven’t heard of Jefferson Labs, don’t feel bad. But their YouTube channel is full of fun physics demos that would work well in a science class or with any group of kids. For example, check out “Can it Roll” below.

If you think locking up waste for 100,000 years is easy, keep in mind the oldest Egyptian pyramid is about 5,000 years old. Another alternative is to find a way to use the waste, but that can be challenging as well.

Many people who use water cooling in their computer systems like to go full-bore with ‘aquarium’ aesthetic, which includes adding a window to their cooling blocks so that they see the water flowing through the window from behind the case’s window. Traditionally PMMA acrylic is used for these windows, as it’s quite durable and easy to handle.

Using glass offers some advantages over acrylic, but has its own disadvantages, most of all that it’s hard to process, but also that it’s known for shattering quite easily if pushed beyond its limits.

This is why [der8auer] as a manufacturer of such water blocks has now spent a few years investigating the viability of using glass for this purpose. First and foremost is safety, with an early prototype glass water block suddenly shattering without clear cause.

Although normally the water cooling loop is only expected to experience pressures of about 600 mbar, the new glass windows that are now entering mass-production had to be tested to their breaking point. This involves pumping water into a few test blocks until they fail, using the test rig that you can see above.

First the big GPU water block was tested, with the acrylic version breaking at around 8-9 bar, while the glass plate shattered at around 5 bar. The failure mode was also interesting, with the glass plate shattering into fragments, while the two acrylic plates tested failed in a completely different location and manner.

A smaller water block with glass window failed at about 10 bar, demonstrating mostly that smaller glass windows are a lot sturdier. Effectively glass windows in water cooling loops are viable, and they also do not suffer from e.g. discoloration, but you do give up a big chunk of your safety margin if your water cooling loop suffers a major pressurization event. Which of course should never happen, but we’re definitely looking forward to the upcoming field trials of these new water blocks.

We’ll start things off this week with some breaking news from NASA: just days after the space agency announced the Artemis II crew was preparing to blast off towards the Moon as soon as March 6th, a new problem with the Space Launch System rocket has pushed the launch back indefinitely. According to NASA Administrator Jared Isaacman, problems encountered while loading helium into the Interim Cryogenic Propulsion Stage (ICPS) necessitate rolling the massive rocket back to the Vehicle Assembly Building (VAB) for diagnosis and repair.

The logistics of shuffling the vehicle 6.8 kilometers (4.2 miles) from the pad to the VAB is going to eat up at least a week, and sending it back the other way is naturally just as much of a production. Add in the time they’ll need to actually figure out what’s wrong with the ICPS and make the necessary repairs, and it’s easy to see why a March launch is almost certainly off the table. It’s frustrating to see the Artemis II mission get delayed this close to launch, but sending humans into space isn’t the sort of thing you can cut corners on.

Well, you’d think so at least. This week NASA also released a scathing report detailing the multitude of technical issues that came up during the 2024 test flight of Boeing’s CST-100 Starliner spacecraft. While astronauts Butch Wilmore and Suni Williams eventually made it back home safely aboard a SpaceX Dragon, the space agency has still categorized it as a Type A mishap — their highest incident classification and the same rating given to the losses of Apollo 1, Challenger, and Columbia.

On the subject of companies we love to hate, a recent post by Brian Merchant on his blog Blood in the Machine (awesome band name, called it) points out the precipitous rise in Flock attacks. That is, folks are taking matters into their own hands and destroying the surveillance devices all over the US. Now Hackaday certainly isn’t condoning the destruction of anyone’s property, but we definitely appreciate the rebellious cyberpunk vibe.

Before you go out hunting for Flocks, keep in mind that at least one person has caught a charge already. In fact Jefferey Sovern picked up thirteen charges, as that’s how many Flock cameras he managed to bag before the law caught up to him. According to reports, he also admitted to “keeping some of the wiring, batteries and solar panels taken from the cameras.” Sounds like Jeff would fit in just fine around these parts.

Looking for some new wheels? Got a handy source of hydrogen? If so, you might be in luck. According to CarBuzz, the resale value of Toyota’s Mirai has absolutely cratered. When they were sitting on the lot a new Mirai would have cost you a bit more than $50,000, but on the second-hand market you can get last year’s model for as little as $15,000. If you’re not too picky, you can get one even cheaper. We did a little searching of our own, and found a 2021 Mirai with less than 40K miles for just $9,000. That’s an insane price for a mid-size luxury car, but of course it doesn’t really matter how cheap the car is if you can’t find anywhere to fill the thing up.

Finally, the folks at F-Droid have sounded the alarm about some concerning changes Google has planned for Android. As we first covered back in October, anyone looking to develop applications for the world’s most popular mobile operating system will soon have to register with Google through a process which is still not entirely clear. Although the search giant has hinted that the system will feature some special consideration for students and hobbyists, F-Droid isn’t convinced. Until there is more transparency, they are urging developers and Android users to push back via keepandroidopen.org.

See something interesting that you think would be a good fit for our weekly Links column? Drop us a line, we’d love to hear about it.

Meshtastic has been experiencing a bit of a renaissance lately, as the off-grid, long-range radio text messaging protocol gains a ton of new users. It’s been used to create mesh networks in cities, during disasters and protests, in small groups while hiking or camping, and for search and rescue operations. Although it’s connected plenty of people together in all of these ways, [GreatScott!] wanted to put it to work connecting some computing resources instead. He has a garden shed that’s too far for WiFi, so Meshtastic was used to connect it instead.

This isn’t a project to bring broadband Internet out to the shed, though; Meshtastic is much too slow for that. All he really wanted to do here was to implement a basic alarm system that would let him know if someone had broken in. The actual alarm triggering mechanism is an LED emitter-detector pair installed in two bars, one of which sends a 12V signal out if the infrared beam from the other is broken. They’re connected to a Heltec ESP32 LoRa module which is set up to publish messages out on the Meshtastic communications channel. A second module is connected to the WiFi at the house which is communicates with his Home Assistant server.

Integrating Meshtastic devices into Home Assistant can be pretty straightforward thanks to the various integrations already available, but there is some configuration to get these specific modules working as an alarm. One of the pins on the remote module had to be set up to watch the light bar, and although sending the alarm message out when this triggered worked well, the received signal never passed through to Home Assistant until [GreatScott!] switched to using the RadioLib library an an MQTT integration instead. But with perhaps more configuration than he planned for out of the way, [GreatScott!]’s alarm is up and running. Meshtastic projects often balloon into more than we had originally planned though, in more ways than one. You can follow along as our own [Tom Nardi] attempts to connect all of New Jersey with this new protocol.

You might not have noticed, but we here at Hackaday are pretty big fans of Open Source — software, hardware, you name it. We’ve also spilled our fair share of electronic ink on things people are doing with AI. So naturally when [Jeff Greerling] declares on his blog (and in a video embedded below) that AI is destroying open source, well, we had to take a look.

[Jeff]’s article highlights a problem he and many others who manage open source projects have noticed: they’re getting flooded with agenetic slop pull requests (PRs). It’s now to the point that GitHub will let you turn off PRs completely, at which point you’ve given up a key piece of the ‘hub’s functionality. That ability to share openly with everyone seemed like a big source of strength for open source projects, but [Jeff] here is joining his voice with others like [Daniel Stenberg] of curl fame, who has dropped bug bounties over a flood of spurious AI-generated PRs.

It’s a problem for maintainers, to be sure, but it’s as much a human problem as an AI one. After all, someone set up that AI agent and pointed at your PRs. While changing the incentive structure– like removing bug bounties– might discourage such actions, [Jeff] has no bounties and the same problem. Ultimately it may be necessary for open source projects to become a little less open, only allowing invited collaborators to submit PRs, which is also now an option on GitHub.

Combine invitation-only access with a strong policy against agenetic AI and LLM code, and you can still run a quality project. The cost of such actions is that the random user with no connection to the project can no longer find and squash bugs. As unlikely as that sounds, it happens! Rather, it did. If the random user is just going to throw their AI agent at the problem, it’s not doing anybody any good.

First they came for our RAM, now they’re here for our repos. If it wasn’t for getting distracted by the cute cat pictures we might just start to think vibe coding could kill open source. Extra bugs was bad enough, but now we can’t even trust the PRs to help us squash them!