Hackaday readers fit into two broad categories: those who experienced the wild and woolly early days of the Internet, and those who are jealous that they missed it. And it’s safe to say that both groups will get something out of this aggressively Web 1.0 retro experience, courtesy of a server that was actually part of it.

This comes to us via The Serial Port, a virtual museum dedicated to 90s technology, where curators [Mark] and [Ben] managed to find a pair of Cobalt RaQ 3 servers from the late 1990s. The RaQ was the first true “Internet appliance,” designed to be as simple as possible to set up and operate. If you wanted to get your small business online, machines like these were just the ticket. They were designed to be as plug-and-play as possible, and they did a pretty good job of it, at least for the time.

The machines that showed up were quite the worse for the wear, which is understandable given the decades since they were last relevant, but that just makes it all the more fun to get them going again. One didn’t even come close to booting, but the other showed more promise.

The video below is the first of a three-part series, and has a nice introduction to the RaQ and its important place in the early Internet, as well as a peek inside the two machines. That revealed some leaky caps that needed replacement in Part 2; after that minor surgery and a little persuasion, the 300-MHz screamer was ready for a test run. It worked, and The Serial Port put it right to work in Part 3 hosting a gloriously retro home page. Hit the link at the top of the article and enjoy the 90s all over again — the visitor counter, the mixed fonts, the “Under Construction” animated GIF, and the reminder to bookmark this page in your browser, which was probably Netscape Navigator. We love the guestbook, too. But — no marquee?

Nice job, [Mark] and [Ben], and kudos for keeping this little slice of computing history alive.

Looking back on what programming used to be like can be a fascinatingly entertaining thing, which is why [Tough Developer] decided to download and try using Turbo C and C++, from version 1.0 to the more recent releases. Borland Turbo C 1.0 is a doozy as it was released in 1987 — two years before the C89 standardization that brought us the much beloved ANSI C that so many of us spent the 90s with. Turbo C++ 1.0 is from 1991, which precedes the standardization of C++ in 1998. This means that both integrated development environments (IDEs) provide a fascinating look at what was on the cutting edge in the late 80s and early 90s.

It wasn’t until version 3.0 that syntax highlighting was added, with the IDE’s focus being mostly on features such as auto-indentation and tool integration. Version 2.0 added breakpoints and further integration with the debugger and other tools, as well as libraries such as the Borland Graphics Interface (BGI). Although even editors like Notepad++ and Vim probably give these old IDEs a run for their money nowadays, they were totally worth the money asked.

Those of us that have been around long enough to have gotten their start in C++ by using the free Turbo command line tools in the 1990s, or lived through the rough, early days of GCC 2.x+ on Linux, will remember that a development environment that Just Worked^© was hard to obtain without shelling out some cash. Within that environment Turbo C and C++ and later Visual Studio and others served a very grateful market indeed.

Beyond the IDE itself, these also came with language documentation, as in the absence of constant internet access, referencing APIs and syntax was done using dead-tree reference books or online documentation. Here “online” meaning digital documentation that came provided on a CD and which could be referenced from within the IDE.

[Tough Developer] walks the reader through many features of the IDE, which includes running various demos to show off what the environment was capable of and how that in turn influenced contemporary software and games such as Commander Keen in Keen Dreams. While we can’t say that a return to Turbo C is terribly likely for the average Hackaday reader, we do appreciate taking a look back at older languages and development environments — if for no other reason than to appreciate how far things have come since then.

Despite having been technologically obsolete for a decade or two, analog photography is still practiced by hobbyists and artists to achieve a particular aesthetic. One might imagine a similar thing happening with early digital cameras, and indeed it has: the Game Boy Camera has seen use in dozens of projects. [Michael Fitzmayer] however decided to combine the worlds of analog and early digital photography by equipping a Holga with the image sensor from a Game Boy Camera.

The Holga, if you’re not familiar, is a cheap film camera from the 1980s that has achieved something of a cult following among retro-photography enthusiasts. By equipping it with the sensor from what was one of the first mass-market digital cameras, [Michael] has created a rather unusual digital point-and-shoot. The user interface is as simple as can be: a single button to take a photo, and nothing else. There’s no screen to check your work — just as with film, you’ll have to wait for the pictures to come back from the lab.

The sensor used in the Game Boy Camera is a Mitsubishi M64282FP, which is a 128 x 128 pixel monochrome CMOS unit. [Michael] hooked it up to an STM32F401 microcontroller, which reads out the sensor data and stores it on an SD card in the form of a bitmap image.

With no film roll present, the Holga has plenty of space for all the electronics and a battery. The original lens turned out to be a poor fit for the image sensor, but with a bit of tweaking the Game Boy optics fit in its place without significantly altering the camera’s appearance.

[Michael] helpfully documented the design process and shared all source code on his GitHub page. Holgas shouldn’t be hard to find to find, but if none are available in your area you can just roll your own. The Game Boy Camera is actually one of the most versatile cameras out there, having been used for everything from video conferencing to astrophotography.

• View this command to comment, vote or add to favourites
• View all commands by emphazer

Diff your entire server config at ScriptRock.com

We’re not sure, but the number of recognizable alphanumeric characters that a seven-segment display can manage seems to have more to do with human pattern recognition than engineering. It takes some imagination, and perhaps a little squinting, to discern some characters, though. Arguably better is the fourteen-segment display, which has been pressed into service in this just-for-funsies IOT message board.

As [Steve] tells the story, this is one of those “boredom-buster” projects that start with a look through the junk bin to see what presents itself. In his case, some fourteen-segment common-cathode LEDs presented themselves, and the result was a simple but fun build. [Steve] used some clever methods to get the display stuffed onto two protoboards, including mounting the current-limiting resistors cordwood-style between the boards. A Raspberry Pi drives the display through a very neatly routed ribbon cable, and the whole thing lives in a tidy wooden box.

The IOT part of the build allows the display to show messages entered on [Steve]’s web page, with a webcam live stream to close the loop. Strangely, the display seems stuck on the “HI HACKADAY!” we entered as a test after [Steve] tipped us off, so we’re not sure if we busted it or what. Apologies if we did, [Steve]. And by the way, if your cats are named [Nibble] and [Pixel], well done!

No matter what you do with them, multi-segment displays are pretty cool. But if you think they’re something new, you’ve got another think coming.

[IMSAI Guy] has an old HP 3488A Switch Control Unit that he wants to dismantle for parts ( see video below the break ). The 3488A is pretty simple as far as HP test equipment goes — a chassis that can hold various types of relay cards and is programmable over GPIB. He notes up front that these are plentiful and inexpensive in the used test equipment market.

Around the back of the unit is a card cage that accepts up to five option cards providing

• 4×4 matrix switching
• on/off SPST switching
• switching signals to a common bus
• VHF switching
• Digital I/O signalling

The teardown is an interesting glimpse into the solid engineering design of 1980s HP test equipment. The option cards are well shielded, and have an interesting back panel connector that breaks out the signals to screw terminals and provides strain relief. The brains of switcher was a Motorola 6809 and connectivity was provided by an Intel 8291A GPIB interface chip. The power supply is solid, and many of its parts can be reused on other projects, such as the transformer and a beefy 20W DC-DC converter by ST. [IMSAI Guy] also scores a bunch of latching relays from the option cards which will no doubt come in handy on future projects.

These kinds of programmable relays can be very useful when building automated test fixtures. There were other solutions for this as well, back in the day. Metrabyte ( bought by Keithley, bought by Tektronix ) was one company that made a whole line of switching interface modules that hooked up to your PC’s ISA bus. Omron also offered similar products. Have you ever needed banks of programmable relays for your projects? If so, let us know your solution in the comments below.