
*Title*
National Videogame Archive - Game Preservation & Public Access Solutions
*Detailed description*
+Data Extraction+
It is extremely important that this is done as soon as possible. Media degrades over time ([bit rot|http://en.wikipedia.org/wiki/Bit_rot], etc.), so the longer the wait, the higher the chances of failure when reading the original data.
Note: this is one way to prove old software is 'near death'; getting the data off the media may be difficult due to the unavailability of drives, or the inability to connect these to current systems.
Possible solutions:
* [Kryoflux|http://www.kryoflux.com/]: A highly precise (using "magnetic flux transition timing") USB-compatible device to read data from 3.5" / 5.25" disks. Ideal for creating images that contain copyright protections schemes (e.g. relying on bad sectors, etc.) for use by researches. Listed at €109.95 for the hardware, but for commercial institutes the price of the image reading software, not listed on website, may be quite high (the Dutch Library was quoted in the thousands of euros), although a special price may be negotiated for "research" purposes (e.g. several hundred euros). YMMV
* [FC5025|http://www.deviceside.com/fc5025.html]: a simpler USB device to read 5.25" disks. May not read as low level as Kryoflux or be able to read copyrighted disks, but should provide images for repay/emulation value. Listed at US$55.25.
For large collections, creating disk images can be labor-intensive, e.g. up to 15 minutes per disk. Not aware of any reliable multi-disk reading stations.
+Preservation+
Metadata: you want as much information as possible (of course\!), but at a minimum enough to deduce the required 'environment' (stack of hardware/operating system/application/file type, e.g. rendering a PDF requires x86/Windows XP/Adobe PDF). A lot of videogame metadata is already available online, see for example [Moby Games|http://www.mobygames.com/], [Home of the Underdogs|http://homeoftheunderdogs.net/]. For more general metadata regarding file formats, software, etc, there is [PRONOM|http://www.nationalarchives.gov.uk/PRONOM/Default.aspx], [UDFR|http://www.udfr.org/].
Indispensable is also the historical context, such as input (controllers, specific keyboards), manuals (including copyright protection keys), specific instructions (such as the WordPerfect Fx commands, OS commands to start games/applicatsions).
Relevant software components of the environment stack (OSes such as DOS, Windows, Mac; applications such as PDF readers, Office suites, supporting drivers for video/sounds cards) will also need to be archived, and might be of interest by themselves.
*TBD:* Set up networked, backed up digital storage drive - similar to BR-RPS. Produce audit of digital files. Work with ICT and procure storage - £2000 for 1tb, can grow over time. How will this be funded?
*TBD:* Link data to MIMSY - work with ICT/CCI staff to add new fields within the cataloguing software to hyperlink/reference digital files and supporting materials.
+Access+
At the time of writing (20-09-2012), the following emulators where known to provide reliable rendering of images. Note that this list only contains open source emulators (unless noted); there may also be good proprietary emulators available.
|| Platform || Emulator || Further infomation \\ ||
| x86 \\ | [Qemu|http://wiki.qemu.org/Main_Page]\\ | The de facto x86 emulator. Can also emulate other platforms, but is used mainly for x86. Configurable via command line. No shared folders. Comes with useful converter tool for system images (qemu-img). |
| Atari-ST \\ | [Hatari|http://hatari.tuxfamily.org/] | Offers shared folders to host system |
| Commodore 64 | [VICE|http://www.viceteam.org/] | |
| Commodore Amiga \\ | [WinUAE|http://www.winuae.net/] / E-UAE \\ | The Windows version (WinUAE, v. 2.4.1) is far more stable/advanced than the Linux version (E-UAE, v. 0.8.29), although they seem to come from the same code base \\ |
| Amstrad CPC | [JavaCPC|https://sourceforge.net/projects/javacpc/] | |
| BBC Micro | [BeebEm|http://www.mkw.me.uk/beebem/] | Very responsive developer, who was quick to bugfix/implement requests \\ |