11. Search CD Archives and Historical Software Collections
In the previous chapters, we investigated original project websites, gaming news archives and Usenet discussions. These sources can reveal where a modification was announced and how it was distributed. However, they do not necessarily preserve the files themselves.
Another important source is physical media, particularly CD-ROMs distributed during the 1990s and early 2000s.
Many Quake modifications were collected and redistributed on magazine cover CDs, shareware compilations, BBS collections and commercial or semi-commercial collections of third-party software. These discs can preserve releases that have disappeared from the original project website and are no longer available from online mirrors.
This chapter explains how to search digital archives of physical media, identify relevant discs and recover files from them.
Understand the Different Types of CD Collections
Not all software CDs were produced in the same way. Understanding the different types of collections helps you identify where a modification might have been distributed.
Magazine cover CDs
Computer and gaming magazines frequently included CDs containing demos, patches, utilities, maps and modifications. A magazine might promote a particular game in an issue and include a collection of related downloads on its cover disc.
For Quake, these discs could contain:
- New maps and map collections.
- Total conversions and gameplay modifications.
- Bots and other gameplay enhancements.
- Patches and updates.
- Editors and development tools.
- Utilities, skins and other custom content.
The CD might have been assembled by magazine staff, a publisher or a third-party supplier. Its contents could include files collected from websites, FTP servers and community contributors.
Magazine CDs are especially useful because they sometimes preserve material that was only briefly available online.
Shovelware and shareware compilations
Another source is the large number of software compilations distributed on CD-ROM.
These collections often contained hundreds or thousands of files gathered from public download sites, FTP servers, BBS systems and other sources.
Examples include collections associated with sites such as CD-ROM.COM, as well as compilations of BBS software and shareware.
The quality and organisation of these discs varied considerably. Some were carefully categorised, while others were simply large collections of ZIP files grouped into directories.
A Quake modification might be included in a general games collection without any reference to its original project website.
Semi-commercial collections of third-party material
During the 1990s, various CD collections containing third-party software were sold commercially or semi-commercially, particularly in Europe.
These discs often gathered freeware, shareware, game modifications, utilities and other downloadable material into large collections.
They were not necessarily produced by the original developers. Instead, a publisher or distributor collected material that was already circulating online and packaged it for distribution.
Such collections can be valuable because they may preserve files from small projects that never appeared on major magazine CDs.
Other physical media
Although CD-ROMs are the main focus of this chapter, do not limit your research to them.
Quake modifications could also have been distributed on:
- Floppy disks included with magazines.
- BBS compilation disks.
- Game compilation CDs.
- Collections of shareware and freeware.
- Backup discs created by individuals or communities.
The important point is to investigate collections of software, not just discs explicitly labelled as Quake or gaming collections.
Important CD-ROM Archives
Several online resources make it possible to investigate historical CD-ROM collections without having the original discs.
Internet Archive
The Internet Archive (https://archive.org) hosts a large collection of historical software and CD-ROM images. Its collections include magazine cover discs, shareware compilations and other software collections.
Start by searching the Internet Archive for terms such as:
Quake CD
Quake addons
Quake levels
Quake magazine CD
Quake shareware
CD-ROM collection
cover CDYou can also search for magazine names, publishers and known CD titles.
When you find a relevant item, inspect its description and available files. A CD-ROM image is commonly provided as an ISO file, although some collections are available as ZIP files or other formats.
If an ISO is available, you can download it and inspect its directory structure on your computer. This lets you browse the disc as if you had the original physical media.
Do not limit your search to discs that mention Quake in their titles. A general magazine cover disc or shareware collection might contain the modification you are looking for.
Useful Internet Archive collections include:
- CD-ROM Software Library
https://archive.org/details/cdromsoftware - CD-ROM Software Collection
https://archive.org/details/cd-roms - Vintage Software Collection
https://archive.org/details/vintagesoftware
The archive’s search and collection structure can change over time. Search broadly and follow relevant collection links rather than assuming that one search query will find everything.
QuakeDiscs
QuakeDiscs (https://QuakeDiscs.com), a website I created for fellow Quake Archivists) is a catalogue dedicated to third-party add-on CDs for the original Quake. It is particularly useful because it indexes the contents of individual discs, including files contained inside archives.
QuakeDiscs is one of the most directly useful resources for researching Quake CD distributions. It provides a catalogue of discs, with information about their publishers, dates and contents. Its file listings can include files nested inside ZIP, RAR, ARJ, PAK and other archives.
This means you can search for a filename without first knowing which CD contains it.
For example, you might search for:
aq2.zip
actionquake
readme.txtIf a matching file is found, inspect the disc’s dedicated page. You may be able to identify:
- The CD title.
- Its publisher.
- Its publication date.
- The directory containing the file.
- The archive containing the file, if applicable.
- Other files distributed alongside it.
QuakeDiscs is focused on Quake add-on CDs, so it should not be treated as a complete index of every magazine or general-purpose software disc. Its catalogue also does not directly host the CD images or downloadable files. Instead, it helps identify where content was distributed and points towards other sources where discs may be available.
DiscMaster
DiscMaster (https://discmaster.textfiles.com) is a search engine for files contained on historical discs preserved by the Internet Archive.
DiscMaster is especially useful because it searches inside the contents of old CD-ROM and floppy disk collections. Rather than requiring you to identify a disc first, you can search for a filename or a distinctive phrase and find collections containing matching material.
This makes it a good resource for searching for:
- Modification names.
- Release filenames.
- Readme filenames.
- Unique phrases from documentation.
- Filenames of maps, models, sounds and other custom assets.
For example, suppose you are looking for a modification called Shadow Arena. Searching for the project name might not produce a result because the CD’s contents are stored under a generic filename. Searching for a distinctive sentence from its readme might locate the file and identify the disc.
DiscMaster can also help you find files that have been extracted from their original ZIP archives. This is important because some CD collections contain the contents of a modification as ordinary files in directories rather than as the original downloadable archive.
DiscMaster also allows you to search the content of files that it has indexed. A good tip for DiscMaster is to search for unique content from the mod’s readme file, such as the mod’s homepage URL or name of the primary programmer.
Other historical software collections
Continue looking for other archives and catalogues of historical software. Some specialise in particular platforms, magazine collections, countries or types of physical media.
For example, personal catalogues of magazine cover discs can identify titles that are available on the Internet Archive, while other preservation projects document the contents of particular CD collections.
A useful approach is to search for the names of magazines, publishers and CD collection brands you discover during your research. A disc that is missing from one archive might be preserved elsewhere.
The important lesson is that there is no single complete catalogue of historical software CDs. Treat each resource as another way to discover possible distributions.
Search for the Modification’s Name and Filenames
Once you have identified the relevant archives, begin searching for the modification itself.
Use the same general search strategy introduced in earlier chapters, but adapt it to the contents of physical media.
Search the modification’s name
Start with the project’s official name, then try alternative spellings and abbreviations.
For example:
Action Quake 2
Action Quake II
ActionQuake2
AQ2
Action QuakeAlso search for the names of developers, development teams and related projects.
A CD might include a modification under a directory named after its author rather than the project. A collection might use a shortened name or a generic category such as mods, addons or quake2.
Search known release filenames
If you have already recovered a release, search for its original filename.
For example:
action15.zip
actionquake15.zip
aq2-1.5.zipA match can reveal which CD contains the file and where it appears in the directory structure.
Do not assume that the same release will always have the same filename. A magazine or CD publisher might rename files when assembling a collection.
Try variations of the filename, including shortened names and names without version numbers.
Search unique filenames inside the modification
This is one of the most important techniques in CD research.
A modification might have been distributed on a CD under a generic name such as:
aq2.zipSearching for the project name might not find it. However, the archive may contain distinctive files that are much easier to identify.
For example:
action_readme.txt
aq2_server.cfg
shadow_arena_map.bspSearch for these internal filenames individually.
The idea is to search for content that is likely to be unique to the modification, rather than relying only on the name of the project.
This technique is particularly useful when:
- The CD publisher renamed the original archive.
- The modification was extracted before being added to the CD.
- The files were placed in a generic directory.
- The project name does not appear in the CD’s catalogue.
- The original archive filename is unknown.
If you have recovered one release, inspect its contents and make a list of distinctive filenames. These can become search terms for finding other copies of the release on physical media.
Search distinctive phrases from readme files
Readme files are another excellent source of search terms.
A readme might contain a distinctive description of the modification, a copyright statement, installation instructions or a list of credits.
For example, imagine a readme contains this fictional sentence:
Shadow Arena introduces a new team-based combat system
with custom weapons and modified player movement.Search for a distinctive part of the sentence, rather than the entire paragraph.
This can locate a copy of the readme even if the modification itself has been renamed or extracted into a directory.
Try searching for:
- A distinctive sentence from the introduction.
- An unusual phrase from the installation instructions.
- A developer’s name or email address.
- A distinctive copyright notice.
- A unique entry in the credits.
- A particular changelog entry.
When searching full text, remember that punctuation, spacing and line breaks can vary. Try shorter phrases if an exact search does not produce results.
Search for other content in the distribution package
Do not restrict your searches to files that appear to be documentation.
A modification may contain unique maps, models, sounds, textures, configuration files and scripts.
For example, a Quake modification might include:
progs/player.mdl
maps/arena1.bsp
sound/weapons/custom.wav
gfx/menu/custom.lmpSome filenames will be too generic to be useful. Others may be distinctive enough to identify the project.
Look for files that are unlikely to appear in unrelated Quake distributions. A custom map name, unusual model filename or project-specific configuration file can be a useful search term.
The more familiar you become with the contents of a modification, the more opportunities you have to search for it in other collections.
Search for Content, Not Just the Original Archive
An important difference between online downloads and CD distributions is that the files may not have been preserved in their original packaging.
When a modification was originally distributed online, it might have been downloaded as a ZIP file. A magazine publisher or CD collector could then extract the ZIP and copy its contents directly onto a CD.
For example, the original download might have looked like this:
aq2.zip
readme.txt
pak0.pak
pak1.pak
config.cfg
maps/
sound/On a CD, the same modification might appear as:
QUAKE2/
MODS/
ACTION/
readme.txt
pak0.pak
pak1.pak
config.cfg
maps/
sound/There is no longer an aq2.zip file to find.
This is why searching for filenames inside the original release is so important. You might find the modification even when its original archive has been renamed, extracted or reorganised.
It also means you should not dismiss a CD search result just because its file structure differs from the release you have already recovered.
Compare the contents
When you find a possible copy, compare its contents with your known release.
Look for:
- Matching readme files.
- Matching PAK files.
- Matching maps and other assets.
- Matching configuration files.
- Matching version information.
- Matching file sizes and hashes.
If the files are identical, you have evidence that the CD contains the same release. If some files differ, investigate whether the CD contains a modified copy, a repackaged release or a different version.
A CD publisher might also have included additional documentation, installers or promotional material. Record these items rather than assuming they were part of the original release.
Investigate the CD and Its Contents
Finding a matching filename is a lead. The next step is to identify the disc and inspect its contents.
If a catalogue such as QuakeDiscs provides a file listing, use it to identify the relevant disc and directory. If you find a disc image on the Internet Archive, download it and inspect its contents.
For an ISO image, you can generally mount it or open it using software that supports ISO files. On many operating systems, mounting an ISO makes its contents accessible as a normal directory.
Once you have access to the disc, investigate the surrounding files and directories.
For example, if you find:
QUAKE/
MODS/
ACTION/
readme.txt
pak0.pak
pak1.pakInspect the readme and compare the files with known releases.
Also inspect nearby directories. The disc might contain other versions, patches, maps or supplementary files related to the same modification.
Record the original CD structure
Preserve the directory structure as it appeared on the disc when documenting the source.
For example:
PC_ZONE_QUAKE/
QUAKE/
MODS/
ACTION/
readme.txt
pak0.pak
pak1.pakThis provides useful provenance. It shows where the files were located within the original collection and helps distinguish the CD copy from an independently recovered download.
If you extract files for your own archive, keep the original CD image or source collection separate from your working copy where possible.
Record the CD title, publisher, publication date, source URL and relevant directory path in your research notes.
Distinguish Release Dates from CD Distribution Dates
Physical media introduces an important dating problem.
A modification might have been released online in March 1998 but included on a magazine CD published in September 1998.
These are two different events.
The release date describes when the modification became available from its developer or original distribution location. The CD publication date describes when a particular collection containing the modification was distributed.
Do not confuse the two.
For example:
| Event | Date |
|---|---|
| Modification originally released | March 1998 |
| Modification downloaded by magazine publisher | April 1998 |
| Magazine CD published | September 1998 |
| CD image added to Internet Archive | 2012 |
These dates describe different stages in the history of the files.
A CD’s publication date can provide useful evidence that a modification existed by that time. It does not establish that the modification was originally released on that date.
Be careful with file timestamps
Files on a CD may contain timestamps that are older than the disc itself.
For example, a ZIP archive might have been created in March, copied onto a CD in September and later extracted from that CD in 2010.
The timestamps you see depend on how the files were originally created, packaged and copied.
A timestamp inside a ZIP archive may preserve information about the original files. A timestamp on an extracted file may reflect the original file’s modification time, or it may have been changed during extraction or copying.
Use timestamps as supporting evidence, not as definitive release dates.
Record the different dates separately
When you discover a release on a CD, record both the release information and the CD distribution information.
For example, an entry in research/history.md might look like:
#### Version 1.5
- Release date: March 1998 (estimated)
- Original filename: action15.zip
- Recovered from: PC Zone Complete Quake CD
- CD publisher: PC Zone Magazine
- CD publication date: December 1997
- CD directory: QUAKE/MODS/ACTION/
- CD source: [Internet Archive URL]
- Files: readme.txt, pak0.pak, pak1.pak
- SHA-256: ...This is a fictional example. Notice that the release date and CD publication date are recorded separately.
If the dates appear inconsistent, investigate further. Perhaps the release date is wrong, the CD date refers to a different edition, or the files on the disc were added after its original publication. Do not silently resolve the discrepancy by choosing one date.
Repackage Recovered Releases Carefully
A release recovered from a CD-ROM may not be in the same form as the original download.
For example, the original developer might have distributed a modification as:
shadowarena11.zipHowever, the magazine CD might contain the extracted contents of that archive:
QUAKE/
MODS/
SHADOW/
readme.txt
pak0.pak
pak1.pak
maps/
sound/To make the recovered release easier to distribute and use, you may want to repackage these files into a ZIP archive.
This is reasonable, but it is important to distinguish a repackaged archival copy from the original release file.
Use a _repack suffix
When creating a new archive from files recovered in an extracted or otherwise modified form, use a filename that clearly identifies it as a repackaged copy.
For example:
shadowarena11_repack.zipDo not give the new archive the original filename as though it were the original download. Someone retrieving the file should be able to tell that it has been repackaged by the archivist.
If the original archive is recovered elsewhere, preserve it separately under its original filename.
Preserve the recovered contents
When repackaging, avoid changing the contents of the release unnecessarily.
- Preserve the original filenames.
- Preserve the directory structure where possible.
- Do not modify readme files or configuration files.
- Do not add new documentation inside the repackaged archive unless there is a clear reason.
- Do not silently remove files that appear unnecessary.
- Record any changes you make to the recovered contents.
The purpose is to make the recovered files accessible, not to create a modified version of the original release.
If you need to repair, rename or otherwise alter files, document those changes separately.
Record the repackaging in history.md
The release entry in research/history.md should explain that the original archive was not recovered and that the downloadable copy was created from files found on a CD-ROM.
For example:
#### Version 1.1
- Original filename: shadowarena11.zip
- Recovered from: PC Zone Complete Quake CD
- CD directory: QUAKE/MODS/SHADOW/
- Original archive recovered: No
- Archival copy: shadowarena11_repack.zip
- Repackaging: Created from extracted files on the CD-ROM
- Contents: Preserved from the CD directory
- SHA-256: ...Also record the source CD and its publication date, as described earlier in this chapter.
Why this distinction matters
Repackaging is a practical way to make otherwise inaccessible releases available to others. However, it introduces a new archival object that did not necessarily exist in that exact form when the modification was originally distributed.
A future researcher should be able to distinguish between:
- The original archive distributed by the developer.
- A copy of that archive recovered from a mirror or CD.
- A new archive created by the archivist from extracted files.
These distinctions preserve provenance and prevent the archive from accidentally presenting a reconstructed package as an original release.
The guiding principle is simple: preserve what you find, make recovered content accessible when necessary, and clearly document anything you have reconstructed or repackaged.
Summary
Physical media is an important source of historical Quake modifications. Magazine cover CDs, shareware compilations, BBS collections and semi-commercial software collections often preserved files that are no longer available from their original websites.
The Internet Archive provides access to many historical CD images. QuakeDiscs provides a specialised catalogue of Quake add-on CDs, while DiscMaster makes it possible to search the contents of many archived discs.
The most important search technique is to look beyond the modification’s name. Search for known release filenames, unique filenames inside recovered releases and distinctive phrases from readme files. A modification might have been renamed, extracted or reorganised before being copied onto a CD.
Finally, distinguish the original release date from the date a particular CD was published or its files were extracted. These are separate historical events and should be recorded separately.
Outcome: You can identify releases preserved on physical media and recover files that might not exist on the original project website.
In the next chapter, we will use modern search engines to discover additional websites, files, references and distribution locations that have not yet been found through the historical archives.