Remembering The Tech We Lost With A Virtual Graveyard

Although 1999 might still feel like yesterday for some of us, in the world of technology the intervening years are practically an eternity. New websites, applications and devices pop up all the time, only to die off just as fast again for a variety of reasons. Amidst such chaos it’s always good to take a breather and reflect on all that we have lost, such as on the virtual graveyard that [Burak Ozdemir] created with hand-written obituaries and only the classiest of 90s-era web design.

Remembered are everything from instant messengers and social networks to web hosts and devices. Who still remembers their ICQ number? There was a good chance that you were also on GeoCities or similar web host back then too. Maybe you weren’t really into Google+, but some of us still have fond memories of its virtual hangouts that provided a connection to people around the world in a way not since replicated.

Not all of the entries are as well-known, of course, with not everyone remembering or ever having heard about services like Songza. A few rare entries on the list have punched a zombified hand through six feet of soil and shambled back into the daylight, such as the Pebble devices. Some entries are quite more recent, with many probably remembering Microsoft’s short-lived Tay that made clear that public chatbots need a lot of safety rigging, a lesson that was mostly remember by subsequent chatbots.

Although some things like forum signatures and personal homepages arguably still live on, the death of Clippy will definitely be mourned by many.

Electroplating 3D Prints Without Requiring A Big Vat

Electroplating 3D prints is a good way to get a pretty nice coating on even a basic PLA part, but generally you’re expected to dunk the entire part into a big vat with electrolyte after coating it with the requisite conductive paint layer. This is great for small parts, like a ring you’d put on a finger, but gets rather silly when it’s a much larger part, such as the one in [Hendrik]’s recent video. Out of curiosity he tried to see whether rotating the part through a much smaller vat would still get you an even coating, or not.

Perhaps ironically this process required building a custom vat out of acrylic, as well as an entire rig to hold up the part and gently rotate it. This highlights the main disadvantage of this approach, in that unless you’re doing a small production run or otherwise get to re-use the rig a lot it’s a lot of extra effort.

That said, the rotation is controlled by an ESP32 and a stepper motor along with a requisite stepper driver, with the most exotic part being the whole custom PCB and enclosure, all of which can be used repeatedly. With all of that tested and confirmed working, the part to be plated was sanded, sprayed with conductive paint and hooked up to the rotating rig for an overnight run.

Following that the part’s new copper coating was polished before more layers of electroplating were applied to get the desired two different colors from different metals. Along the way no issues were found with this method of rotating electroplating, so if you regularly struggle with oversized parts to electroplate, this would seem to be a viable method.

Continue reading “Electroplating 3D Prints Without Requiring A Big Vat”

Building A Working Replica Of The Chernobyl Power Plant’s SKALA Display

In a recent video by the [Chornobyl Family] it’s shown how they made the SKALA status display which was featured at the recent 40-year memorial exhibition of the Chornobyl Nuclear Power Plant (ChNPP) #4 reactor accident, along with the RBMK reactor control panel replica and SKALA console which they had made previously.

Detail of the SKALA display. (Credit: Chornobyl Family, YouTube)

We previously covered this SKALA control system of the ChNPP’s RBMK reactors, as well as its 1990s modernization. This SKALA status display is one of the original elements of the control room, providing a status overview of the entire control system at a glance, including its processors and peripheral devices.

The replica uses similar looking components, with a metal casing and LED lighting that invokes the aesthetics of the original electroluminescent mnemonic panels. Overall the goal was to keep the appearance as close to the original as possible — they even had operators of the ChNPP reactors look over the panel and give it their stamp of approval.

Some of the components like the error indicators had to be 3D printed, while the metal case was cut out of sheet metal. There’s also a very big speaker for the alarm, at the top right of the panel. Along with the LEDs for the electroluminescent-style indicators this meant a lot of addressable LEDs and a lot of wiring.

The full build plans are available via the [Chornobyl Family] Patreon, if you feel like building up your own RBMK-style reactor control room.

Continue reading “Building A Working Replica Of The Chernobyl Power Plant’s SKALA Display”

Turning A Junk Laptop Screen Into A Portable Monitor

Sure, you can buy a portable monitor off your favorite e-tailer, but with perfectly fine displays in devices like laptops being tossed out every single day, why not repurpose those instead? That’s what [ScuffedBits] recently did with the panels  pulled from some old laptops.

A good question with any such salvaged panel is just how practical it is to still use them, with disqualifying features being things like passive-matrix TFTs as well as the use of CCFL backlighting as with one of the three panels demonstrated in the video.

Looking up the model number of a panel on a site like panelook.com will tell you the display technology, resolution and other important details before you decide to commit to using it. If it’s using a LED backlight and at least Low-Voltage Differential Signaling (LVDS) but ideally eDP you can likely find a cheap driver board for it that has all the requisite inputs like HDMI and power.

The hardest part is probably the case for the panel, as they’re rather thin and fragile. Here [ScuffedBits] opted to 3D print two different types of cases, with the second variant probably being the best version as it protects most of the panel. Installing these is quite easy: slide the panel into the first half, then add the second half of the case to close it up. Permanently keeping the case in place was left as an exercise to a future [ScuffedBits], while demonstrating why it’s definitely the hardest part of repurposing an old laptop display.

Continue reading “Turning A Junk Laptop Screen Into A Portable Monitor”

Qualcomm’s New QCC74x Appears To Target The ESP32 MCUs

These days wireless microcontrollers featuring built-in WiFi and Bluetooth are all the rage, with Espressif’s range of ESP32 MCUs being the default option for commercial and hobbyist projects alike. This makes Qualcomm’s recently released QCC74x MCU rather interesting, as specification-wise it would seem to be placed firmly in ESP32 territory.

On the radio side you get 1×1 WiFi 6, Bluetooth 5.4, and IEEE 802.15.4 (e.g. Thread and Zigbee), coupled with a single-core 352 MHz RISC-V CPU with FPU and DSP features and 484 kB of SRAM. The SDK for this MCU is hosted on Codelinaro, featuring the typical FreeRTOS-based stack, though confusingly Bluetooth and Zigbee support are currently marked as ‘not supported’. This might still be in progress.

Where the competition with Espressif feels clear is in the pricing, with the highest-performance evaluation board (QCC748M EVK, pictured above) listed for $13 (before taxes/tariffs). This gets you 8 MB of PSRAM built-in with unspecified link speed, but likely the same QSPI as used for the NOR Flash. USB support is available on this higher-end tier, while absent on the QCC743. Development documentation is also available, and looks fairly complete based on first glance.

Overall the QCC74x looks to be an upgrade to the older and significantly less powerful QCC730 MCU. Depending on software support and final pricing it could make for an interesting competitor to some of Espressif’s modules like its ESP32-C series or ESP32-S2, though the upcoming ESP32-S31 would seem to have it matched or beat on all metrics.

Running Windows CE On The Nintendo 64

Although Windows CE doesn’t use the NT kernel, it’s similarly designed to run on a wide variety of system architectures. Since the Nintendo 64 uses a MIPS CPU it should basically just run either kernel. You might assume that the N64’s rather limited specs are a bit of a problem, but fortunately Windows CE is designed to run on a digital potato, and requires only a MB of RAM. Since that just so happens to be what the N64 has under the hood, [Throaty Mumbo] was optimistic about getting Windows CE running on the 1990s game console.

The idea for this project came when [Throaty] was tinkering with an IBM Workpad Z50 laptop that uses almost the same CPU as the N64 and also runs Windows CE. Although said laptop is probably a lot more practical of a platform to run Windows on, this didn’t mean that it wouldn’t be a fun challenge.

Since CE was intended to be customized by companies for their own embedded hardware this means that you can use an official SDK, such as Microsoft Windows CE 2.11 Platform Builder. Making Windows CE 2.11 run on an N64 thus involves creating a board-specific configuration and compile that against said SDK.

If you want to give it a shot yourself, the entire project is available on GitHub which is where you find most of the technical details as well. When using a flash cart such as the EverDrive, you can also put applications on the SD card and run them from within the Windows GUI. You’ll still be limited by the N64 hardware, but otherwise the experience is very smooth as the video below demonstrates.

Continue reading “Running Windows CE On The Nintendo 64”

After Stumbling From CVE To CVE Will Linux Get A Kill Switch?

For the few people who have spent the past weeks living under a security rock, the Linux kernel has found itself the subject of multiple severe bugs in the form of Copy Fail and Dirty Frag, both of which allow for privilege escalation. They’ve made many people very upset, and also potentially put many thousands of systems at risk of exploitation. Worse is that system managers are generally left to twiddle their thumbs while waiting for patches to be rolled out. This is where NVIDIA engineer [Sasha Levin] has proposed a ‘kill switch’ for affected kernel functions.

The basic concept seems rather simple, with this feature merely intercepting a call to the affected function and instead returning a predefined return value. This makes it less extreme than hitting a general SCRAM button on the entire kernel, and could theoretically allow the affected systems to keep running until the patched kernel becomes available.

A disadvantage of this is that it obviously modifies the kernel, patching it in-memory so that you need to reboot the system to clear it. Another potential disadvantage is that it opens a potentially massive attack vector, with people in the Cybersecurity sub-Reddit roundly rejecting the idea. Amidst all the other anxious conversions there is also the concern that this particular patch was at least partially generated by an LLM (Claude Opus 4.7) , so one may hope that if it does gets merged into mainline it’ll at least be properly vetted by multiple pairs of well-caffeinated human eyes.