Inside Raiders Of The Lost Ark (Atari Style)

It’s a bit ironic that an Atari 2600 game based on Raiders of the Lost Ark — a movie about archaeology — is now the subject of its own archaeological expedition as [Dennis Debro] and [Halkun] spent time reverse-engineering the game. Luckily, they shared their findings, so you can enjoy it the same way you can visit a king’s tomb without having to discover it and dig for it. If you don’t remember the game, you might enjoy the demo from [Speedy Walkthroughs] in the video below.

If you are only used to modern software, you might think this is little more than someone dumping the program code and commenting it. However, on these old, limited systems, you have to really understand the actual architecture because there are so many things you have to manage that are specific to the hardware.

For example, the game has two 4K ROM banks that use a strange switching mechanism. The entire game is built around the NTSC television signal. Everything is oriented toward generating the 60 Hz frame rate. Game logic runs during the vertical blanking and over-scan sections to prevent strange visible artifacts due to software running.

This is a fascinating look inside game coding as it existed around 1982. Of course, you can also run everything using emulation. Usually, our reverse engineering is more hardware-related. But we do love these old games, too.

Continue reading “Inside Raiders Of The Lost Ark (Atari Style)”

The Engineering Of The Falkirk Wheel

We live in an age where engineering marvels are commonplace: airplanes crisscross the sky, skyscrapers grow like weeds, and spacecraft reach for the stars. But every so often, we see something unusual that makes us take a second look. The Falkirk Wheel is a great example, and, even better, it is functional art, as well.

The Wheel links two canals in Scotland. Before you click away, here’s the kicker: One canal is 35 meters higher than the other. Before 1933, the canals were connected with 11 locks. It took nearly a day to operate the locks to get a boat from one canal to the other. In the 1930s, there wasn’t enough traffic to maintain the locks, and they tore them out.

Fast Forward

In the 1990s, a team of architects led by [Tony Kettle] proposed building a wheel to transfer boats between the two canals. The original model was made from [Tony’s] daughter’s Lego bricks.

The idea is simple. Build a 35-meter wheel with two caissons, 180 degrees apart. Each caisson can hold 250,000 liters of water. To move a boat, you fill the caissons with 500 tonnes of water. Then you let a boat into one of them with its weight displacing an equal amount of water, so the caissons stay at the same weight.

Once you have a balanced system, you just spin the wheel to make a half turn. There are 10 motors that require 22.5 kilowatts, and each half-turn consumes about 1.5 kilowatt-hours.

Continue reading “The Engineering Of The Falkirk Wheel”

Does This Electron Make Me Look Fat? Weighing An Electron

[The Signal Path] shows us how to recreate a classic science experiment to measure the weight of an electron. Things are easier for us, because unlike [J. J. Thomson] in 1897, we have ready sources of electrons and measuring equipment. Check it out in the video below.

The main idea is to trap an electron using a magnetic field into a circular path. You can then compute the forces required to keep it in that circle, along with some other equations, and combine them. The result lets you compute the charge to mass ratio using parameters you can either control or measure, like the radius of the circular path and the electric field.

Helmholtz coils create the magnetic field, and a cold cathode tube provides the electrons. Honestly, the equipment looks a bit like something out of an old monster movie.

Continue reading “Does This Electron Make Me Look Fat? Weighing An Electron”

Bash Via Transpiler

It is no secret that we often use and abuse bash to write things that ought to be in a different language. But bash does have its attractions. In the modern world, it is practically everywhere. It can also be very expressive, but perhaps hard to read.

We’ve talked about Amber before, a language that is made to be easier to read and write, but transpiles to bash so it can run anywhere. The FOSDEM 2026 conference featured a paper by [Daniele Scasciafratte] that shows how to best use Amber. If you prefer slides to a video, you can read a copy of the presentation.

Continue reading “Bash Via Transpiler”

PROFS: The Office Suite Of The 1980s

Today, we take office software suites for granted. But in the 1970s, you were lucky to have a typewriter and access to a photocopier. But in the early 1980s, IBM rolled out PROFS — the Professional Office System — to try to revolutionize the office. It was an offshoot of an earlier internal system. The system would hardly qualify as an office suite today, but for the time it was very advanced.

The key component was an editor you could use to input notes and e-mail messages. PROFS also kept your calendar and could provide databases like phonebooks. There were several key features of PROFS that would make it hard to recognize as productivity software today. For one thing, IBM terminals were screen-oriented. The central computer would load a form into your terminal, which you could fill out. Then you’d press send to transmit it back to the mainframe. That makes text editing, for example, a very different proposition since you work on a screen of data at any one time. In addition, while you could coordinate calendars and send e-mail, you could only do that with certain people.

A PROFS message from your inbox

In general,  PROFS connected everyone using your mainframe or, perhaps, a group of mainframes. In some cases, there might be gateways to other systems, but it wasn’t universal. However, it did have most of the major functions you’d expect from an e-mail system that was text-only, as you can see in the screenshot from a 1986 manual. PF keys, by the way, are what we would now call function keys.

The calendar was good, too. You could grant different users different access to your calendar. It was possible to just let people see when you were busy or mark events as confidential or personal.

You could actually operate PROFS using a command-line interface, and the PF keys were simply shorthand. That was a good thing, too. If you wanted to erase a file named Hackaday, for example, you had to type: ERASE Hackaday AUT$PROF.

Styles

PROFS messages were short and were essentially ephemeral chat messages. Of course, because of the block-mode terminals, you could only get messages after you sent something to the mainframe, or you were idle in a menu. A note was different. Notes were what we could call e-mail. They went into your inbox, and you could file them in “logs”, which were similar to folders.

Continue reading “PROFS: The Office Suite Of The 1980s”

Forget Waldo. Where’s Luna 9?

Luna 9 was the first spacecraft to soft-land on the moon. In 1966, the main spacecraft ejected a 99-kg lander module that used a landing bag to survive impact. The problem is, given the technology limitations of 1966, no one is exactly sure where it is now. But it looks like that’s about to change.

A model of the Luna 9 lander with petals deployed.

We know that the lander bounced a few times and came to rest somewhere in Oceanus Procellarum, in the area of the Reiner and Marius craters. The craft deployed four stabilizing petals and sent back dramatic panoramas of the lunar surface. The Soviets were not keen to share, but Western radio astronomers noticed the pictures were in the standard Radiofax format, so the world got a glimpse of the moon, and journalists speculated that the use of a standard might have been a deliberate choice of the designers to end run against the government’s unwillingness to share data.

Several scientists have been looking for the remains of the historic mission, but with limited success. But there are a few promising theories, and the Indian Chandrayaan-2 orbiter may soon confirm which theory is correct. Interestingly, Pravda published exact landing coordinates, but given the state of the art in 1966, those coordinates are unlikely to be completely correct. The Lunar Reconnaissance Orbiter couldn’t find it at that location. The leading candidates are within 5 to 25 km of the presumed site.

The Luna series had a number of firsts, including — probably — the distinction of being the first spacecraft stolen by a foreign government. Don’t worry, though. They returned it. Since the Russians didn’t talk much about plans or failures, you can wonder what they wanted to build but didn’t. There were plenty of unbuilt dreams on the American side.


Featured Art – 1:1 model of the Luna 9, Public Domain.

Pi Pico Learns Morse Code

When [101 Things] didn’t want to copy Morse code, he decided to build a Pi Pico system to read it for him. On the face of it, this doesn’t seem particularly hard, until you look at the practical considerations. With perfectly timed dots and dashes, it would be trivial. But in real life, you get an audio signal. It has been mangled and mixed with noise and interference as it travels through the air. Then there’s the human on the other end who will rarely send at a constant speed with no errors.

Once you consider that, this becomes quite the project, indeed. The decoder captures audio via the Pi’s analog-to-digital converter. Then it resamples the input, applies an FFT, and converts the output via a complex classification pipeline that includes, among other things, Bayesian decoding. Part of the pipeline makes simple typo corrections. You can see the device do its thing in the video below.

Continue reading “Pi Pico Learns Morse Code”