MOLOTOV(1)

πŸ“¦
version 1.3 Β· 3 versions
, in debian trixie, ubuntu questing, ubuntu resolute

πŸ’– MOLOTOV πŸ’–

okay so bestie, this is a page from section 1 of the manual β€” the User Commands girlies β€” and it's all about molotov, a lil command line utility that makes bootable media out of a Windows ISO. she's giving "one job, does it well" energy and honestly? obsessed. πŸŽ€


✨ NAME ✨

molotov β€” Create a bootable media from a Windows iso image.


🌸 DESCRIPTION 🌸

So molotov is a command line utility that's literally designed to create a bootable USB drive using a Windows ISO image. That's her whole thing, that's her main character moment. πŸ’…

To use her, you're gonna need two things:

  • a flash drive with sufficient storage space (no half-measures bestie, Windows ISOs are thicc)
  • a Windows image, which you can get by downloading it from Microsoft's website πŸ¦‹

and then two lil warnings that are not optional reading, okay:

  • You need to have root access in order to perform the USB drive creation.
  • Bear in mind that ALL data in your device will be deleted!
okay so that second one? that's not a vibe check, that's a whole funeral. ALL is in caps in the original for a reason. back up your stuff first, i am begging you 😭

⭐ SYNOPSIS ⭐

molotov -i <iso-image> -d <block-device> [OPTIONS]

πŸŽ€ EXAMPLE πŸŽ€

molotov -i Win10_22H2_BrazilianPortuguese_x64v1.iso -d /dev/sdc
-v -u

πŸ‘‘ OPTIONS πŸ‘‘

This program follows the usual GNU command line syntax, with long options starting with two dashes (--). A summary of options is included below. πŸ“‹

  • -i, --iso-image FILE β€” the Iso image to be used in the media creation
  • -d, --device DEVICE β€” the Device where the image must be burnt; it must be a block device
  • -h, --help β€” Display the help message
  • -v, --verbose β€” Turn on verbose output
  • -V, --version β€” Print molotov's version and exit
  • -u, --uefi β€” Make an uefi-bootable media (default is legacy)

Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. (so like, the shorties and the long ones are a package deal, no cap 🫢)


πŸ’€ EXIT VALUES πŸ’€

okay this part is the "how did it go" report card and you will be reading it:

  • 0 β€” Success! πŸŽ‰ iconic, flawless, ate
  • 1 β€” Some crucial internal function exited with the status 1, such as mkfs.ntfs or fdisk
  • 2 β€” Some crucial internal function exited with the status 2, such as mkfs.ntfs or fdisk
  • 64 β€” Unknown parameter
  • 65 β€” Missing required arguments, it happens when the user omits either the -i or -d flag
  • 66 β€” Iso image not found, when the user passes as argument a non-existent ISO image
  • 67 β€” Block device not found, when the user passes as argument a non-existent device
  • 68 β€” Indicates insufficient permissions to perform the requested operation.

Commonly occurs when attempting to write to a device that requires administrative privileges (root access).

Common causes:

  • The current user does not have write access to the target device
  • Device ownership is limited to root
  • The user is not root
68 is the "bestie you forgot sudo" error and honestly it's so real of her to be that specific about it 🌈

πŸ› REPORTING BUGS πŸ›

Report bugs to <https://codeberg.org/cizordj/molotov>


Copyright Β© CΓ©zar Augusto de Campos

License: GPL-3+


and that's the whole page, periodt. πŸ’– this was Molotov 1.3, dated March 2024, and it lives in section 1 of the manual, bestie β€” go forth, -i your iso, -d your device, and don't you dare forget root. mwah πŸ’…βœ¨πŸŒΈ

πŸ“¦ where this page comes from