Category Archives: Tech

Technology in general

DTK 286/12 board repair and restoration

Posted on by

I’ve been on a bit of a retro restoration kick lately and decided to take a look at a couple of motherboards I’d saved from my childhood. The boards were from my first 2 PCs, an XT clone and an AT clone. At some point towards the end of college, I was running out of space to keep the older computers I had collected to that point. Rather than give up my first machines entirely, I decided to strip them down and save the core parts and interesting bits that still worked and trash the rest. (something I now regret as these parts have become quite rare and expensive)

Fast forward a few decades… these parts have been sitting, stored in the attic and the room over my garage. Interested to see if they still worked, I pulled the motherboards out of their anti-static bags only to discover a horror common to many retro computer enthusiasts. A CMOS battery had leaked and corroded a small, but important section of the board. Back in the old days of IBM-compatible PCs, manufacturers used to include a rechargeable 3.6v battery, (typically Ni-Cd) soldered to the board. These were great and often lasted well beyond the design life of the system, however they became a liability later in storage.

Sadly, I didn’t think to take pictures of the damage when I discovered it, but moved to quickly get rid of the old leaky battery and proceeded to clean up the board with isopropyl alcohol. The acid crystals and much of the corrosion came off of the board, but what became obvious was that a lot of damage had been done. During the time that acid was sitting on these components, it was eating through the metal contacts and traces of the board and its components. This included several sets of jumper pins, a large 40-pin socketed DIP chip, a 1″ PLCC socketed chip and other associated logic chips.

The 40-pin DIP socket was closest to the battery and took the most damage with several of it’s pins and sockets completely disintegrating when I tried to clean them up. Most of the jumper pins cleaned up with a fiberglass brush and I was able to leave them in the board. (though I did have to replace all of the jumpers as they were too far gone) The next big worry was the PLCC chip and its socket as well as a few of the logic chips under it. One of the logic chips was pretty badly corroded, but stayed intact when I cleaned it. I cleaned up the contacts as much as possible with the fiberglass pen and attempted to flow some new leaded solder into the vias in the hopes it would help. Thankfully continuity tests revealed it was making contact, but I really didn’t know how much material was left inside or if it would be enough for the chip to function. This is a common source of problems for systems based on TTL logic where corroded traces can cause too much resistance and won’t allow a line to be driven high. Adrian Black recently detailed a similar issue while working on a much older TRS-80 Model III. (see his reaction at 40:15 when he realizes it was just a corroded ribbon cable)

The PLCC socket turned out to be less of an issue that I’d thought. While it did have some corrosion, it seemed to be mostly be on the surface. A good wash down with IPA, scrubbing and some contact cleaner got the socket looking much better. The fiberglass pen cleaned up the contacts on the chip and it slotted back into the socket perfectly. After replacing the bad DIP socket and a few more clean-ups and re-soldering of components and I was ready to try powering it up. Unsurprisingly it didn’t work the first time. I cleaned out some additional surface corrosion I found in some of the ISA slots, reseated a few chips and tried again. At first, it didn’t seem like anything was happening. I tried reseating the VGA card and tried again and amazingly the 286 POSTed!

Testing the mainboard
First POST

I ended up evicting my old 486SLC-33 from the case seen above and installed the DTK motherboard into it. I also initially borrowed a more modern multi-io controller from the same system, but quickly realized this wasn’t ideal. The BIOS for this machine, while quite advanced for the time, had a hard-coded list of supported hard disk types with specific sector/track layouts. (this was actually common on motherboards up through the 386 era and even early 486 systems.) While I could pick a similar track/sector layout and read from an IDE hard drive, I wouldn’t be able to boot from one. (and it would be risky to attempt to write to it) Sadly the original 20MiB MFM hard disk and controller that was originally attached to the 286 had long been discarded. The smallest functioning hard disk I had was a 500MiB Connor drive from the 486 era. (also donated from the 486SLC) I would continue to solve these problems and others, but that’s a story for another time. The board worked and was able to boot from a floppy disk and read a DOS-formatted hard disk. The resurrection of the 286 was a success!

Remembering Challenger

Posted on by

35 years ago, I was sitting in my 5th grade classroom watching along with my teachers and fellow students as Christa McAuliffe and the other six members of STS-51-L roared into the air on a cold morning in January, 1986. I was excited to be able to see a launch on TV with my classmates. Little did I know that I was a little over a minute away from witnessing the first of 2 tragic moments in the history of the Space Shuttle program.

STS-51-L Mission Logo
Flight crew of the Space Shuttle Challenger, STS-51-L

I grew up in northern Florida and was always interested in the space program, even at a very early age. My parents would often take me to the library where I would invariably pick out books on rockets and airplanes. I remember reading about the Apollo Program and the early history of NASA and how it captured my imagination. However, as a child of the mid 70’s, the new Space Shuttle program was what I remember getting to see. Even in north Florida, on a clear day I could see the Space Shuttle rising into the sky from my back yard. (though I only remember seeing this once) Shuttle launches had been a regular part of my childhood growing up and they were one of my favorite things to see.

A while back, I noticed a documentary appeared on Netflix titled “Challenger: The Final Flight.” I was interested, but initially resisted the urge to watch it with mixed feelings. After all, I had been there. The images had been seared into my 11 year old brain along with the knowledge of the investigations that came after. I knew what happened and why, and I wasn’t sure I wanted to re-live it. I finally ended up watching it and while the experience was fairly emotional, (particularly the last 2 parts) it was worth it.

The morning of January, 28th 1986, in the last class before lunch, my teacher wheeled out a media cart with a TV for us to watch the launch. We all got quiet as the countdown proceeded. “T-minus 9, 8, 7, 6… we have main engine start… 4, 3, 2, 1 and lift off! Lift off of the 25th Space Shuttle mission and it has cleared the tower.” Challenger rose above the tower as it had before, rolled and pitched over into it’s launch trajectory. Everything looked fine until those final words just a little over a minute into the flight, “Challenger, go with throttle up.”… “Rodger, go throttle up.”

I remember people being confused, perhaps thinking that this was the solid boosters staging, but I knew better. The moment I heard the crackle over the radio and saw the fireball and expansion of the contrail, I knew exactly what had happened. Challenger was gone. Even now as I write this over 35 years later, it’s difficult to hold back my emotions. We were all expecting to see this beautiful young teacher rocket into space, but in an instant my astronaut heroes and their spacecraft disintegrated in front of my eyes.

challenger explosion
Moments after throttle-up, Challenger’s main fuel tank explodes

The documentary tries to tell the whole story, giving background on the engineers at Morton Thiokol, the diversification of the astronaut corps, and the selection of the candidates for the teacher in space mission. It’s a powerful and moving story including interviews with most of the major players and family members of the 7 astronauts who died. Overall, I’m glad I watched this as it’s a reminder that overconfidence and pressure to meet deadlines can be a dangerous combination. If you haven’t seen it, I’d highly recommend it, but bring a box of tissues.

Why I won’t buy a Tesla

Posted on by

Elon Musk is a brilliant entrepreneur and futurist. He has singlehandedly revived the EV market and pushed the technology farther than anyone thought possible. Tesla’s cars are arguably the best EVs on the market. So why wouldn’t I want to buy one? It has to do with the right to repair and also who really owns the car.

When you buy a car from any of the usual manufacturers, you own that product. If I purchase a BMW and decide I want to change my own brakes or install a new battery, I can do that. The manufacturer can’t even refuse to warranty other parts of the car due to these changes. The Magnuson-Moss Warranty Act states that a dealer must prove that equipment caused the need for repairs before it can deny warranty coverage.

Right to repair got a boost from Massachusetts in 2012 with a new law that required auto manufacturers to share their diagnostic codes and information. This led to an agreement between the automakers in 2014 that is now effective across all 50 states and is in part responsible for the range of aftermarket diagnostic equipment that is now readily available to consumers.

Sure, you say… so what does this have to do with Tesla? One of the main differences in a Tesla EV and other cars on the market is the tight integration Tesla has between their hardware and the software that drives it. Like Apple and the iPhone, Tesla controls every part of their product. Each Tesla is in constant contact with the company via wireless communication. Tesla vehicles send diagnostic data back to Tesla that they can then use to make improvements. This enables some amazing benefits such as over-the-air updates that add features or improve performance. However, this level of control also has a downside. What Tesla gives it can also take away, and there’s absolutely nothing you can do about it. (If you want a good example, check out the Rich Rebuilds channel on YouTube)

Recently Tesla reversed an earlier policy where they would allow recertified Tesla’s that had been damaged, but later repaired to either retain or get back their ability to supercharge. (Tesla’s high current fast DC charging ability that is one of it’s main selling points) Now even cars that owners paid thousands of dollars to certify are unable to be used effectively on anything other than short commutes.

It’s not just salvaged Teslas that are affected though. Because many of the features of a Tesla vehicle are little more than software, Tesla licenses them to specific owners and can take them away when the vehicle is sold and then charge license fees to the new owner to enable these features again. This begs the question, who really owns a Tesla? Most owners would say that they do, but with this sort of complete control over the vehicle, is that really true? Is it ok for Tesla to remove essential features like fast charging capabilities over the air without warning or recourse? I don’t think so. As long as this is their policy I won’t be purchasing any of their products, and I don’t think you should either.