← All stories
● Covered by 1 source · 1 reportLow impact1 neutral

Developer Creates Valid ZIP File That Also Functions as BIOS-Bootable OS Image

🔄 Updated 5d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • A single file functions as a ZIP archive, BIOS-bootable image, and Multiboot OS.
  • The ZIP file can be unpacked or booted directly from BIOS or Multiboot loaders.
  • ZIP metadata is at the end, allowing boot code at the beginning.
  • The first file, ZIPHEAD.COM, contains the bootloader and Multiboot header.

A Multifunctional File Creation

Developer David Oberhollenzer, known as Goliath, created a unique file that serves multiple purposes. This file is a 100% valid ZIP archive, a BIOS-bootable image, and a Multiboot-compatible operating system image all in one. This project showcases an unusual approach to file system and bootloader design.

Booting and Unpacking Capabilities

The created ZIP file can be unpacked like any standard ZIP archive. Additionally, it can be booted using Linux's GRUB, QEMU, or any other Multiboot-compatible loader. A notable feature is its ability to be image-written to a floppy disk and booted directly from a PC's BIOS without any modifications to the system.

Leveraging ZIP File Structure

The design exploits the structure of ZIP files, where metadata (the file directory) is located at the end of the archive. This placement allows the data at the beginning of the archive to contain executable code. The first file within the ZIP, named ZIPHEAD.COM, is stored uncompressed at the start of the archive.

This initial uncompressed file contains the necessary bootloader code. For Multiboot compatibility, the required 0x1BADB002 bytes and checksum are placed within ZIPHEAD's data, making it easy for Multiboot loaders like GRUB or QEMU to recognize and initiate the boot process.

BIOS Booting Mechanism

Achieving direct BIOS bootability required additional work. A disk is considered bootable by BIOS if its first 512 bytes end with the signature 0x55AA. The developer ensured that the ZIP file's initial bytes, including the bootloader within ZIPHEAD.COM, met this requirement, allowing the BIOS to execute the embedded code directly.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

David Oberhollenzer developed a ZIP file that is simultaneously a valid archive, a BIOS-bootable image, and a Multiboot-compatible operating system. This creation demonstrates an unconventional use of file formats and boot processes, allowing the same file to be unpacked, booted via Multiboot loaders, or directly from BIOS on a floppy disk.