Setting the Stage: Starting the RACSIII.NET Restoration Journey

In the beginning there was…..

(table, and it was good)

Where to start

So the natural place to start is at the beginning. Well, I don’t have to do that if you read “The WHO of RACSIII .NET”. But you need to start at the bottom and work your way up, so that’s what I’ll do.

The Origin of RACS III Tables

The original RACS III setup comprised two wooden tables, each with a distinctive “hump” design. These tables served a crucial purpose, providing the necessary space to accommodate the Expansion Interface underneath while supporting the TV on top. However, in the picture presented, these tables are notably absent, replaced instead by an extension table. This decision was driven by practical considerations, primarily the limited space available in the office. By opting for the extension table, I aimed to maximize space efficiency without sacrificing functionality.

We can’t TABLE that question – RACSIII

So, truthfully, the original RACS III consisted of 2 tables. They were the wood ones with a “hump”. Its where you could fit the Expansion Interface under, and the TV on top. You won’t see it in this picture, though, because I removed it for the extension table. I figured I’d use the extension table since I didn’t have the space in my office for them both, and I wouldn’t lose any space with the hump.

So all it took was a damp rag and some time to wipe it down. But otherwise, its in great shape so nothing more to say here, at RACSIII.

Tagged , , , , , ,

About Tuc .

Tuc, owner and Sysop of RACS III started his computing adventures on an IBM 5110 with a 4 inch screen, 16K Basic, 2 8" floppy drives and a 132 column dot matrix printer in 1978. After retiring for a bit to Tucs Beachin OBX House in NC, he came back and is now the Senior Site Reliability Engineering Manager for a global SAAS company.
View all posts by Tuc . →

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.