Bdtyktl

I understand why an .iso file cannot simply be copied to a given storage device (USB stick, another hard drive etc) and then "just work". I'm wondering if the same holds true for "burned/extracted" results? And why not downloadable zip files instead of iso in the first place?

By way of a concrete example:

I wanted a disk wiping tool, and decided to use DBAN. The download was an iso file, which I burned to a USB stick, using Rufus. Can I now copy/paste the entire contents of that stick to another stick and expect it to work?

Another silly question: Why bother with iso files at all? Why not provide zip files to download instaed? I'm going to take a guess and maybe I'm answering my own question here: Because an iso is a sector-by-sector container copy of a physical storage medium like a DVD or CD. As such, the container is operating-system agnostic. And maybe also file system agnostic (so It's doesn't matter if the files system is, for example, NTFS or APFS)?

I guess you're referring to this earlier thread.

Can I now copy/paste the entire contents of that stick to another stick and expect it to work?

Still no, for the exact same reason: you won't be copy/pasting the entire contents, you will be copy/pasting only the part that's shown as "files and folders". But just like the .iso image had invisible data beyond that, the final USB stick also has data beyond that – such as the MBR bootcode, the partition layout, the particular choice of filesystems used – which a simple copy/paste will not pick up.

For example, PC BIOS systems require the disk's 0th sector to contain "boot code" – the first-stage bootloader. This is not stored as a file (because BIOS does not understand files), therefore it won't be copied if you only copy files.

UEFI systems do store the bootloader as a file, but they generally want it to be on a FAT16/FAT32 filesystem. If you copy & paste the files into an NTFS device, most UEFI systems won't be able to access them.

Because an iso is a sector-by-sector container copy of a physical storage medium like a DVD or CD. As such, the container is operating-system agnostic. And maybe also file system agnostic (so It's doesn't matter if the files system is, for example, NTFS or APFS)?

I think one clarification is necessary: The file system is not a special parameter that the "formatting" or "burning" process has to modify in a special way. In reality, filesystem structures are stored on the disk in exactly the same way as regular data. The same goes for the partition table; it's just some data on a sector.

Therefore a sector-by-sector copy of a whole disk will automatically include the entire filesystem – it'll include the fact that it's e.g. a FAT32 filesystem; it'll include every single bit of the filesystem's internal structure/metadata/attributes; it'll reproduce even the partition layout.

So it isn't merely that an .iso disk image is "filesystem-agnostic"; rather, it brings its own filesystem as part of the image. (Indeed this is where the "iso" name comes from: originally .iso files meant images of a CD containing the ISO 9660 filesystem.)

Can I now copy/paste the entire contents of that stick to another stick and expect it to work?

No; You would only be copying the contents of the bootable partition that exists on the bootable drive. You need to duplicate the partition in order to make the contents of the disk bootable.

Why bother with iso files at all?

ISO 9660 is a standard to distribute images of optical media. It literally exists for the exact purpose of distributing images of bootable media.

ISO 9660 is a file system for optical disc media. Being published by the International Organization for Standardization (ISO) the file system is considered an international technical standard. Since the specification is available for anybody to purchase,1 implementations have been written for many operating systems.

Source: ISO 9660