Posted on

Ancient Web: The Test Card Gallery Remembers When Television Had to Show Its Work

Before television channels filled every unused second with programming, shopping, trailers, or somebody shouting about politics, they sometimes showed the machinery.

Visit The Test Card Gallery

Darren Meldrum’s site collects the tuning signals, test cards, clocks, captions, and other engineering images used by broadcasters when there was no normal program on the air.

These pictures were not decorative placeholders.

They were tools.

A picture designed to reveal what was wrong with your picture

Test patterns gave engineers and television repairers a stable visual target for checking geometry, aspect ratio, focus, convergence, grayscale, color response, resolution, alignment, and other parts of the broadcast chain.

The famous BBC cards are only one branch of the subject. The gallery also reaches into ITV material and test images from other countries and systems.

Some patterns are mostly circles, lines, gratings, blocks, and frequency wedges. Others became cultural objects in their own right because viewers saw them for years during off-air hours and trade transmissions.

Contemporary web references show the gallery was already being passed around online by 2000 as a place to find old BBC and international test patterns. That detail matters because the site is now preserving two histories at once: the broadcast engineering material itself and an early-web community that thought these technical screens were worth collecting.

They were right.

A test card captures the assumptions of a television system in one image. What resolution mattered? What shape should the picture be? How should circles appear? What tones and colors needed checking? What did a broadcaster expect a technician to diagnose from the screen?

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because ordinary technical artifacts are often the first things official histories omit.

The programs got archived.

Somebody also needed to save what appeared when there was no program.

Return to The Test Card Gallery

Posted on

Ancient Web: Kitana Rebuilt Battle Isle 2 in 23,000 Lines of BASIC

There are easier ways to preserve a 1994 strategy game than spending hundreds of hours rewriting it in BASIC. Kitana chose the educationally irresponsible option.

Visit Kitana’s Castle

Battle Isle 2020 is a from-scratch Windows reimplementation of Blue Byte’s Battle Isle 2 and Battle Isle 3. It is not a port of the original DOS source code. Instead, Daniel Bekowies reconstructed the behavior while still requiring the original game data for graphics, sounds, music, videos, and missions.

The project page says the program grew beyond 23,000 lines of PowerBasic code spread across more than 400 functions, with some assembly language mixed in.

Preservation by reverse engineering the assumptions

The interesting work was not merely drawing hex maps on a modern screen.

The original games encode terrain, units, missions, weather, movement, graphics, and other behavior in old formats that have to be understood before a replacement engine can use them. The project estimates roughly 60 hours went into decoding file formats alone, on top of more than 800 hours of programming.

The resulting program adds things a modern machine can provide without abandoning the original structure: scalable display, mouse controls, speech output, improved AI, multiplayer over LAN and Internet, a map editor, new campaigns, and compatibility with original mission content.

The AI can simulate possible combat outcomes before choosing an attack. Multiplayer replaces the old practice of handing save files between players with a live server-based mode. The map editor can build new missions using original units and terrain.

This is preservation through reimplementation rather than freezing software in an emulator.

It also preserves knowledge that would otherwise stay buried inside undocumented binary files.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like Kitana because the web is full of people who quietly reverse-engineered obsolete software simply because they wanted it to keep working.

Twenty-three thousand lines of BASIC is an absurd amount of affection for a hex-grid war game.

Which is why it belongs here.

Return to Kitana’s Castle

Posted on

Ancient Web: CPRR.org Built a Transcontinental Railroad Museum Out of Stereographs

CPRR.org is what happens when a family archive, railroad obsession, and late-1990s web design all agree that one museum building is not enough.

Visit the Central Pacific Railroad Photographic History Museum

The site launched in February 1999 and grew from a few galleries into a sprawling virtual museum devoted to the Central Pacific Railroad and the construction of the first transcontinental railroad.

Its strongest material is visual.

Thousands of restored photographs, stereoviews, engravings, maps, illustrations, and other period images sit beside primary-source documents and long-form historical material.

The railroad photographed itself into history

The site emphasizes that photography was not merely documentary. Railroad companies used images to promote construction and financing, and photographers carried large wet-plate equipment into the field while the tracks were still advancing across the West.

CPRR.org preserves work by photographers including Alfred A. Hart, Carleton Watkins, Eadweard Muybridge, A. J. Russell, and others.

The museum says Hart alone documented Central Pacific construction in hundreds of stereoviews. Its archives include more than a thousand railroad and city stereographs, while the wider site claims more than 4,500 restored railroad pictures and thousands of pages of material.

The text layer is just as deep: engineering history, timelines, railroad statutes, annual reports, first-person accounts, construction records, Chinese railroad workers, maps, locomotive information, and digitized books.

The site was established by the family of Central Pacific engineer Lewis Metzler Clement, which helps explain why the collection behaves less like a general railroad encyclopedia and more like a deeply accumulated research archive.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like CPRR.org because this is exactly what independent web preservation can do well: keep adding context until a hobby site becomes infrastructure for researchers.

A photograph of a locomotive is interesting.

Four thousand photographs, maps, reports, names, dates, and engineering records become a historical system.

Return to CPRR.org

Posted on

Ancient Web: Game Zero Builds a 4-Bit Processor One Logic Gate at a Time

Game Zero’s old processor-design tutorial starts with a dangerous educational idea: instead of telling you what a CPU does, build one small enough to understand.

Visit The Math Behind the Magic

The tutorial works upward from basic digital logic toward a four-bit processor. Half adders become larger arithmetic blocks. Incrementers manipulate binary values. Registers and buffers introduce storage and control. RAM, ROM, buses, and an accumulator eventually turn a pile of schematic pieces into something recognizable as a processor.

It is primitive by modern CPU standards.

That is exactly why it works.

Four bits is enough to expose the machinery

A contemporary processor hides staggering complexity behind layers of abstraction. Game Zero strips nearly all of that away.

The reader sees why a half adder is useful, how several small components can become a four-bit incrementer, and how a register changes a circuit from purely combinational logic into something that can remember a previous state.

The memory section distinguishes RAM, ROM, and output devices and places them on a shared data bus. A special register beside the arithmetic logic unit becomes the accumulator. The text then walks through what happens when data moves through the machine.

The diagrams matter as much as the prose. Small circuits are repeatedly wrapped into simpler boxes so later schematics remain readable. That is not only electronics instruction; it is abstraction being demonstrated in real time.

The pages also preserve their rough edges. Some diagrams are missing. Some text is unfinished. One section literally announces that an update is in progress.

That incompleteness makes the site feel like a workshop notebook instead of a polished textbook product.

CacheRat’s 1,967 Ancient Web Domains research list includes technical tutorials like this because the web used to contain a remarkable number of people patiently unpacking machinery that commercial documentation assumed you would never need to understand.

Four bits is not much computer.

It is enough computer to see the trick.

Return to The Math Behind the Magic

Posted on

Ancient Web: The Outhouses of America Tour Has Been Online Since 1996

The Outhouses of America Tour was created on Thanksgiving Day, November 28, 1996, which is almost too perfect an origin date for a website about outdoor toilets.

Visit the Outhouses of America Tour

The site says it began as a joke and then kept going until it became a genuinely large collection devoted to outhouses, backhouses, loos, and related sanitation history.

Its navigation includes real outhouses, definitions, FAQs, trivia and folklore, models, postcards, sketches, outhouse racing, outhouse digging, and visitor submissions.

That is significantly more outhouse infrastructure than most people expect to encounter before breakfast.

The joke became an archive

The strongest old-web sites often begin with a subject too narrow to justify a conventional publication. That is exactly why somebody can cover it properly.

The Outhouses of America Tour preserves examples from different regions and contexts, including restored structures, homemade buildings, unusual designs, military sanitation, and historically associated sites. One featured entry points to an outhouse connected with William Faulkner’s Frenchman’s Bend display in New Albany, Mississippi.

The archive also wanders into composting toilets, humanure, preparedness, and practical sanitation, which makes sense once the joke has accumulated enough real information.

The page openly asks visitors to send photographs of their favorite outhouses, especially ones they built or restored. That participatory model is pure personal web: a curator picks an odd subject, strangers discover it, and eventually the audience helps build the collection.

The site calls itself the home of a comprehensive outhouse information collection and proudly notes that it has been in business since 1996.

More importantly, the HTML still carries the shape of that era: image buttons, long navigation, visitor comments, small jokes embedded in labels, and a curator persona rather than an anonymous publishing system.

CacheRat’s 1,967 Ancient Web Domains research list contains many sites where an absurdly specific interest becomes valuable simply because someone refuses to stop documenting it.

Twenty-nine years after launch, the Outhouses of America Tour is still standing.

That sentence is doing more work than intended.

Return to the Outhouses of America Tour

Posted on

Ancient Web: Star Fighter 3000 Kept an Acorn Game Alive Long Enough to Outlive Its Hardware

Star Fighter 3000 has the kind of software history that only exists because somebody kept caring after the original machine stopped being normal.

Visit the Star Fighter 3000 archive

The game was launched in late 1994 for the Acorn Archimedes and Risc PC by Fednet Software. Andrew Hutchings and Tim Parry wrote it in ARM assembly language, combining a 3D flight shooter with mission structure, formations, ground targets, upgrades, and the wonderfully excessive tone of 1990s game fiction.

Then the hardware changed.

That is where the archive becomes more interesting than a normal fan page.

Compatibility became part of the game’s history

The original code made extensive use of techniques that were perfectly reasonable on the machines it targeted, including self-modifying code. StrongARM upgrades and later RISC OS changes exposed assumptions that no longer held.

In 2000 Christopher Bazley released SFpatch to address incompatibilities. Later releases incorporated fixes directly, added improved sound support, restored effects, and eventually produced versions capable of running on newer RISC OS systems.

By 2003 a 32-bit-compatible edition ran natively on the Iyonix PC and could run in a window on the RISC OS desktop. Development and fixes continued after that.

In 2014, twenty years after the original launch, Star Fighter 3000 was made available as a free download.

The archive documents gameplay, development history, versions, upgrades, technical fixes, and the strange path a commercial game takes when the community becomes its long-term maintenance department.

That kind of history is easy to flatten into a release date and a screenshot.

The site preserves the messier truth: old software survives because people patch around processors, operating systems, sound systems, memory assumptions, and everything else that changed underneath it.

CacheRat’s 1,967 Ancient Web Domains research list includes pages like this because software preservation often happens in tiny specialist sites long before institutions notice the problem.

Star Fighter 3000 did not merely survive emulation.

People kept repairing the actual lineage.

Return to the Star Fighter 3000 archive

Posted on

Ancient Web: Blizzard’s Warcraft II Strategy Archive Still Explains the Game

Blizzard’s old Battle.net pages still contain the kind of official game documentation that modern publishers usually scatter across launchers, wikis, videos, patch notes, and community posts.

Visit Blizzard’s Warcraft II strategy archive

The Warcraft II section covers basic play, units, Orc-versus-Human differences, general strategy, advanced tactics, water combat, scoring, hotkeys, map editing, and enlarged multiplayer map images.

It is less a promotional page than a technical handbook for people who intend to get better at the game.

The combat equation is right there

One section explains how damage works using basic damage, armor, and piercing damage. Another lists unit statistics and scoring values. Advanced pages get into spell comparisons, demolition tactics, formations, production, expansion timing, and naval control.

The water-strategy material is particularly period-specific. Warcraft II’s land, sea, and air systems all mattered in competitive maps, so the archive devotes substantial space to battleships, submarines, transports, blockades, ship control, and common mistakes on water-heavy maps.

The map pages are another excellent fossil.

Blizzard says enlarged map images were assembled from development tools and screenshots, then resized so players could study starting positions, resource locations, terrain, and tactical routes. The page even suggests printing favorite maps and keeping them beside the computer during play.

The custom-map documentation feels equally old-school. It refers to Windows 95/98/NT, Macintosh, Windows 3.x with Win32s and WinG, PUD scenario files, sound editing, starting conditions, and AI schemes such as Land Attack, Air Attack, and Sea Attack.

Nothing here needs nostalgia to be interesting. The archive is valuable because it preserves exactly how Blizzard taught players to understand its game when official websites were expected to contain deep reference material.

CacheRat’s 1,967 Ancient Web Domains research list includes old game sites because mechanics, tools, and multiplayer culture often survive better in contemporary web documentation than in retrospective summaries.

Warcraft II is still playable.

Its manual on the web is still waiting too.

Return to Blizzard’s Warcraft II strategy archive

Posted on

Ancient Web: PhotographyHistory.com Keeps Antique Cameras From Becoming Unidentified Lumps

Old cameras have a nasty habit of surviving longer than the paperwork that explains what they are. PhotographyHistory.com was built for the people left holding the mystery box.

Visit the International Photographic Historical Organization

The International Photographic Historical Organization, or InPHO, traces its origins to 1985 and launched its website in 1997. Its purpose is unusually broad: historical research, identification, appraisal, collecting guidance, preservation, articles, timelines, and access to material from the Internet Museum of Photography.

One article on the site, David Silver’s discussion of 127 roll film, shows exactly why that kind of context matters.

A dead format can explain an entire era of camera design

The essay follows 127 film from Kodak’s 1912 Vest Pocket Kodak through decades of folding cameras, box cameras, twin-lens reflex designs, and eventually decline under pressure from 35mm and 120 film.

Silver originally published the piece in Photo Shopper in March 1996. On the web it became something more durable than an old magazine issue: a reference page that still links a film format to specific cameras, production eras, design compromises, and collector values.

That is the larger strength of the site.

It does not treat an antique camera as an isolated collectible. Cameras sit inside systems of film sizes, shutter designs, lenses, manufacturing history, amateur markets, professional use, and changing expectations about portability.

InPHO also offers practical services such as identification and historical review of vintage cameras and photographs, research guidance, appraisal help, peer review, and access to a collecting community.

The design is unapologetically old-web: dense pages, image buttons, article indexes, and a table of contents instead of an infinite scroll.

CacheRat’s 1,967 Ancient Web Domains research list includes sites like this because preservation is often less about saving an object than saving enough context to understand the object later.

A folding camera without its history is a neat mechanical thing.

A folding camera with its history becomes evidence.

Return to PhotographyHistory.com

Posted on

Ancient Web: DriveMeInsane Has Let Strangers Control the Lights Since 1997

In August 1997, Paul Mathis put a webcam online and gave strangers the ability to mess with his lights.

Visit DriveMeInsane

The site’s FAQ says the project began under the name Spy on Paul Mathis. Visitors could watch a live camera, turn lamps on and off, and observe the result in real time. Over the years it accumulated more cameras, controllable devices, messages, chat, audio, and other features.

The site still describes itself with refreshing accuracy: an amusing hobby with no real purpose, financial or otherwise.

Home automation as public nuisance

The current interface exposes controllable lamps and other devices directly beside the camera feed. Visitors can switch hardware, send a message to a marquee, and in some configurations hear text read by voice synthesis.

The FAQ explains that the controlled lamps use X10 and other home-automation technologies. It also addresses the obvious question: doesn’t it get irritating to have strangers turning the lights on and off?

Apparently you get used to it.

The site’s later name came from a 2002 radio appearance. During a description of the project, a DJ sarcastically asked something like, “What is this, Drive Me Insane dot com?” Mathis did not yet have a working domain for the site, so he registered it.

That origin fits perfectly.

DriveMeInsane belongs to the same early-web tradition as coffee-pot cameras and other projects where connecting an ordinary physical object to the Internet was itself enough reason to build something.

Today remote switches, cameras, smart bulbs, voice control, and web-connected appliances are mundane consumer products. In 1997, making the web visibly affect a lamp in somebody’s room felt like a demonstration of what the network could become.

CacheRat’s 1,967 Ancient Web Domains research list contains many experiments like this because they preserve the moment when ordinary household objects first became Internet-accessible toys.

Most smart-home demos are boring now.

Letting strangers annoy you with yours remains funny.

Return to DriveMeInsane

Posted on

Ancient Web: Solar System Collisions Lets You Throw Asteroids at Planets for Science

The University of Maryland’s Solar System Collisions page has one of the better educational interfaces ever devised: choose an asteroid, choose a planet, and hit it.

Visit Solar System Collisions

Written by astronomer Douglas P. Hamilton, the tool has recorded millions of simulated collisions since the late 1990s. Users choose a target, projectile composition, diameter, and velocity, then see approximate consequences.

The joke is obvious. The educational design underneath it is not.

Destruction as a variable-controlled experiment

The accompanying classroom material asks students to change one variable at a time and record what happens.

How does increasing projectile diameter change the energy released? What happens when the same-size object is made of rock, ice, or iron? How does a collision on Earth compare with one on Jupiter or Pluto? How large is the crater? How strong is the resulting earthquake? How often would an event of that scale be expected?

The activity packets make students build tables rather than just click until something spectacular happens.

That matters because impact physics involves quantities that are difficult to feel intuitively. A change in diameter changes mass dramatically. Composition changes density. Velocity feeds directly into kinetic energy. A modest-looking change in the input can produce an enormous change in the result.

The site even randomizes terrestrial impact locations in some classroom exercises, which gave instructors a simple way to prevent every student from turning in exactly the same worksheet.

This is classic educational web design: a small interactive program, explanatory pages, downloadable activities, and enough structure for a teacher to turn curiosity into an assignment.

CacheRat’s 1,967 Ancient Web Domains research list includes university experiments like this because they preserve an era when the web itself was treated as laboratory equipment.

Twenty-plus years later, the button still does the important thing.

It lets you throw the rock.

Return to Solar System Collisions