Windows 98: inspect the boot structure of an archived CD ISO

A collection of visible CD files is not automatically a bootable CD. An existing ISO image from a Windows 98 archive can be inspected separately for its file tree and El Torito boot information. This procedure uses current xorriso on Linux, not a tool inside Windows 98. It does not modify the image or launch Setup or the old operating system.

1. Identify the archive copy

Record the label, language, edition, provenance and corresponding image file. An ISO suffix alone proves neither origin nor completeness. Keep the unchanged archive copy separately and inspect an additional working copy on a suitable current system. Do not launch unknown programs from the image. Installation keys do not belong in public reports.

This workflow applies to ISO 9660 data images with possible El Torito structures. It does not replace suitable archival methods for audio/mixed-mode CDs, special copy protection or multiple sessions. If only a folder of files was saved, label it as a file copy, not a verified bootable image.

2. Read the boot catalog

Install xorriso from a trusted package source on the modern Linux system. Replace the example path with the existing working copy. Quotation marks remain important for spaces:

xorriso -no_rc -indev "/path/archive/w98-copy.iso" -report_el_torito plain -rollback_end

-no_rc comes first and prevents startup files containing additional commands from being read. -indev loads the input; -report_el_torito plain reports boot catalog information. -rollback_end exits without writing pending changes. Do not add options to burn, add, delete or rebuild.

Record the tool version, all messages and the inspected file path. A detected catalog shows boot information exists, not that booting succeeds. A missing catalog may mean the CD was never intended to boot directly or that the backup is unsuitable. Do not add a catalog to the archive original merely to make a test pass. xorriso explains report lines with -report_el_torito help.

3. Check files independently

Open the working copy with a suitable archive or ISO reader. Compare expected folders, filenames and important content with available documentation. A directory listing is not a complete read test; selected important files must actually be readable. Extract to a new empty directory if needed without executing files. Record read errors and missing components.

A checksum helps detect later changes to copies. It proves neither provenance nor that the original read captured all required sessions and areas. Keep the image, checksum and report together, and a second copy separately.

4. Treat booting as a separate test

An actual boot test belongs in an appropriately configured isolated environment without access to production disks or network shares. Do not begin installation on the work PC. Firmware mode, emulated hardware and any additional boot floppy must suit the medium. Failure in an arbitrary modern VM does not automatically prove the image is defective. Record results separately: files checked, boot catalog present or absent, boot test completed or still pending.

Sources and related guide