On May 20-21, 2013, the Library of Congress hosted one in its series of small invitational digital content at-risk summits, this one on the topic of software preservation. “Preserving.exe: Toward a National Strategy for Preserving Software” covered a wide range of topics around software preservation, every type of software and interactive media art and engaged multiple communities from software creators to curators. Details on the meeting are here.
Vintage TRS-80, photo by Leslie Johnston
While there will be later posts and detailed reports from the meeting, there was one topic that I kept considering and that came up at two other conferences that I attended this week: hardware preservation. I have long been part of the camp that was in favor of building collections of hardware, in part because I have seen the necessity of doing so for audio and video collections, where such hardware is vital for the replay of media for researchers or for digitization. While I have seen successful emulation projects, it seemed like a dream that we could potentially build so many emulators.
This week I had my mind changed.
It was really brought home for me the astonishing extent of hardware and lower level software infrastructure we would have to locate, restore, and keep running to run the application software needed to provide access to content files in our collections. It is a daunting task, and colleagues at institutions where they do collect hardware provided a reality check at this meeting as to what it takes.
I saw or heard about some exceptionally successful emulation projects this week. We were given a brief sneak peek at pilot for the Olive Executable Archive from Carnegie Mellon University, and were witness to fully playable Virtual Machines of games. The Multiple Arcade Machine Emulator is so successful a project, that, after 10 years, they have a short list of the games they cannot emulate. New York Public Library has been testing interactive visualizations of theatrical lighting design that run using files that are part of their Theatrical Lighting Database. The emscripten project provides a robust framework for emulation in the browser.
For some more recent and common environments–as well as common media format readers–we will almost certainly need to keep hardware running in our organizations to assist us in making preservation copies of media and files that we receive as part of our collection building. And we will need to provide such hardware in our reading rooms. There is a need. But I was convinced this week that emulation may serve our needs better than hardware, except for the need to read the media in our collections to preserve their content.
We cannot all become museums of computer hardware. There are wonderful organizations like the Computer History Museum, the National Museum of Computing, the Heinz Nixdorf MuseumsForum, and the Centre for Computing History that serve that purpose well. And none of this diminishes my feeling that hardware should be collected and preserved. These are artifacts from our computing history. They are examples from the history of industrial design. They are part of my (and other’s) personal histories. When we display vintage hardware and media at our personal digital archiving events, they always attract a crowd and elicit many personal stories that help us engage with visitors about the management of their digital files. For all of those reasons I will continue to be an advocate for hardware preservation, but with a different endgame than I had in mind at the beginning of the week.