I’m often asked – in the course of my job or by an acquaintance – to explain ‘digital preservation’ and what I mean by it. And as I’m sure others in this field know, a frequent first guess is scanning – you’re scanning stuff, right?

It’s a reasonable and valid guess – digitization can and is used as a preservation strategy – but it’s a reply that leaves me stumbling, “Yes, but…” as it’s the born-digital content that is most likely to be overlooked for a newcomer.

I’m often tongue tied though to explain why born-digital material is important at a personal level for an individual. To some it seems immediately frivolous – perhaps resulting from a notion that the digital enterprise is inherently ephemeral, or that the ‘information superhighway’ – a dated term but one still with a legacy – is just a media-carrying superstructure over the real stuff.

Not having someone immediately agree with your assumptions startles you into explanation mode. So I reach for a personal example of born-digital vitality. But the truth is that in my recent past I’ve done a pretty good job of preserving the digital materials that are important to me. Setting up a reasonably safe (and this is key: automated) backup routine and checking media health every once in a while goes a long way. So I have no woeful narrative to relate there about personal digital material becoming lost (yet).

And as I’ve mentioned elsewhere in this blog, I find myself agreeing with David Rosenthal’s research that suggests file format obsolescence in a post-Internet world is not a major risk for the majority of digital materials. So I don’t feel terribly relevant trying to spook someone with the scenario of their Microsoft Word files becoming obsolete in a few years. They are far more likely to become lost through neglect before approaching obsolescence.

So I searched back through my own personal history to think of what born-digital content I have lost to time. Not just any old content that happened to be lost, but something that means a lot to me but is simply no more.

Now I’ve visited a near-loss and partial recovery with a high school art web site, so I recall here a complete content loss. Nothing remains but the recollection. This loss still smarts today – the code for my QBasic games. Hear my tale of woe, as I recreate here whatever will be left of those projects.

My kingdom for some GOTO code

When my family first purchased a computer, it took a few years for me to learn the ropes on it. I recall some unintended directory deletions while I was learning DOS, and at one point I thought I had truly broken the system through one of these errant deletes. The incident was only a mistakenly relocated set of files that broke a start-up routine, but it was not without its moments of vertigo that I had broken the family machine.

Eventually I got to understand command line customs, along with the basics of programming in the QBasic IDE, which came standard with MS-DOS and Windows for approximately nine years. Once I got the hang of basic user input and variable handling, I figured it was time to make games in QBasic.

Ah, to be young and just dive in! None of them were ever completed, though this does not bother me. I still believe just diving in is a handy practice.

Lend an ear and I’ll tell you about them.

The first effort was a fantastical text adventure with ANSI-style art inspired by the psychedelic landscapes of Kingdom of Kroz and Epic Megagames’ ZZT, but featuring the simple rules of a Choose your own Adventure novel. I got pretty far along before the tedium of hand drawing scenes row by row with the extended character set wore me down. I was still learning a lot.

The second game was identical in form, but took some less tasteful tones from Bethesda’s The Terminator title – an early stab for that studio at their now famous open-world design – as well as the Drugwars DOS game. I got even less far along than even the first game – just a couple of sequences before the player was abruptly dumped back into the sharp blue of QBasic’s IDE. I recall becoming bored and directionless at the monotone grimness the setting required, as well as the tedious, screen by screen gameplay.

The third game, and the most involved, was an RPG collaboration with an elementary school friend, very much modeled after the BBS classic Legend of the Red Dragon – but a single player affair. We had races, classes, a town, shops, NPCs, and had begun modeling the wilderness areas where the player would encounter whatever had to be fought there. However, school hedged in and the friend moved away, and our work stopped there.

I would give my right arm for the source code to any of these projects, but that last one hurts the most. My friend and I spent many hours and long nights developing the RPG – and never got very far – but this piece of digital content represents a huge investment of my enthusiasm and passion at that time. That it is utterly lost is painful. I don’t know what I could have done to have had the foresight to keep it, except to have kept the floppies around somehow by neglect. If this were a project nowadays, perhaps a forgotten email attachment could have wrought it up from the bog. Alas, at that time the only network we had was carting floppies between our houses.

There are other losses, such as my old MySpace page, which captures some of my disposition and contacts in the early college years, an embarrassing old fan site for a band I loved in high school, a lost DOOM level .wad – but the absence of this QBasic code hits strongest. This is simply how things get lost, alas – though I sigh wistfully when hearing of old game code being discovered. That someone, amazingly, has managed to create a modern game coded entirely in QBasic just makes me all the more wistful.

Citizens of tomorrow, your digital content – even if, like myself, you are not a heavy user of social media – can be profoundly important to you and very likely to others. Keep an eye on it, as I wish I had.