Release ImageUploader 1.0.0 · parsamajidi21/ImageUploader

The first release of ImageUploader: flash disk images to USB drives and SD cards, and create backups.

Downloads

File
`imageuploader_1.0.0-x86_64-win-gdi.zip`	Windows 10/11, 64-bit. Extract and run `imageuploader.exe`
`imageuploader_1.0.0_wo-x86_64-win-gdi.zip`	Windows, simplified write-only interface
`imageuploader_1.0.0-arm-macosx-cocoa.zip`	macOS on Apple silicon (M1 and newer), macOS 11+
`imageuploader_1.0.0-intel-macosx-cocoa.zip`	macOS on Intel Macs, macOS 10.13+
`imageuploader_1.0.0-amd64.deb`	Linux: GTK, recommended for Ubuntu 22.04 / Debian 12 or newer. `sudo apt install ./imageuploader_1.0.0-amd64.deb`
`imageuploader_1.0.0-x86_64-linux-gtk.zip`	GTK, portable, needs udisks2
`imageuploader_1.0.0-x86_64-linux-x11.zip`	X11, portable, minimal dependencies
`imageuploader_1.0.0_uf-x86_64-linux-x11.zip`	X11 with an embedded font, for systems without Unicode X11 fonts

Linux packages are x86_64. Verify downloads with sha256sum -c SHA256SUMS.

First start on Windows and macOS. The apps aren't code-signed yet, so the system warns about them:

Windows: SmartScreen may say "Windows protected your PC". Click More info, then Run anyway. The app asks for administrator rights, which it needs to write to drives.
macOS: move ImageUploader.app to Applications, then run xattr -cr /Applications/ImageUploader.app in Terminal once. Without that, macOS reports the app as damaged. It asks for your password, which it needs to write to drives.

Modern GTK interface: header bar, card layout, symbolic icons, a clearly marked Write action, drag and drop, device refresh button, and light/dark theme support
Writes raw (.iso, .img, .bin, .raw, .dd) and compressed images (.gz, .bz2, .xz, .zst, .zip, .zzz, .tar, .cpio, .pax) on the fly, with verification
Raw and ZStandard-compressed backups, serial transfers, 18 languages

Truncated or partially downloaded compressed images are now rejected. Previously they were written only partly and reported as "Done. Image written successfully"
tar archives in pax format (GNU tar's --format=pax) and tars with long file names were rejected with "Encrypted ZIP not supported"
Raw backups of drives ending in empty space were shorter than the drive
Compressed backups could fail when the compressor buffered data
GTK: the buffer size selector had no effect; a successful backup didn't show "Done"
X11: crashed on start when no window manager was running
Packaging: .deb built without udisks2 now gets the right permissions

Windows and macOS packages are built by GitHub Actions from commit ee89f21 (this tag plus build fixes for those platforms, no behaviour changes). On each platform the image and backup tests pass (23 checks: every format byte for byte, truncated images rejected, backups), the app starts, and the Windows window opens.
Linux: automated end-to-end tests drove the real GTK interface (full and write-only) and the text interface: 13 image and archive formats written and compared byte for byte, verify on/off, buffer sizes, error dialogs, truncated images, and backup round trips (raw and compressed).
Not tested yet: writing a physical USB drive on any platform, and the Windows and macOS interfaces beyond starting up.

When writing a tar archive inside a compressed file (e.g. .tar.xz), up to about 8 KB of the archive's zero end padding is written after the image. This is harmless unless the image almost exactly fills the drive. It's inherited from USBImager.

ImageUploader is based on USBImager by bzt, MIT license.