Release notes

Amiga Imager v0.92

A major native-tools release that turns Amiga Imager into a much broader macOS workflow: the new Amiga File Manager, native Greaseweazle floppy support, faster Build & Write to Card, and a now feature-complete AmigaDiskKit engine all land together in v0.92.

  • Beta release
  • Native disk, floppy, and direct-write workflows
  • Build 260716

Beta - macOS 14+, Apple Silicon and Intel. Current downloadable build: 260716.

What stands out in v0.92

v0.92 is the release where Amiga Imager stops feeling like only a system-image builder and starts feeling like a broader native Amiga toolkit on macOS. The headline features are the new Amiga File Manager, native Greaseweazle floppy support, faster Build & Write to Card, and the continued maturation of AmigaDiskKit.

  • Amiga File Manager - browse and work with Amiga images, SD, CF, and SSD media, drawers, ADFs, and archives directly on macOS without needing to boot an Amiga first.
  • Native Greaseweazle support - read real Amiga floppies into ADFs, write ADFs back out, browse disk contents directly, and capture raw flux when deeper preservation or troubleshooting is needed.
  • Faster Build & Write to Card - go straight from your selected settings to real SD, CF, or SSD media, skip the separate export step, and avoid wasting time writing empty space.
  • AmigaDiskKit now feels complete - introduced in v0.90 and now feature complete in daily use, the native Swift engine covers FFS, PFS3, ADF, LHA, and the core PiStorm FAT32 path with better speed and less legacy-tool dependency.

New native tools inside the app

The biggest shift in v0.92 is that more of the workflow now happens directly inside the app through native implementations, instead of relying on external helper paths for everything.

  • Amiga File Manager adds a real media-management layer to the app: dual-pane browsing, Finder-like browser mode, drag and drop between sources, and direct access to images, ADFs, host folders, and physical SD, CF, or SSD media.
  • Archive browsing is now part of that same flow, so LHA-based content can be inspected and staged much more naturally before boot.
  • Greaseweazle support is built in as a native macOS path and works out of the box for real floppy read and write workflows instead of depending on a separate Python-driven setup.
  • Build & Write to Card makes it much quicker to go from configuration to real hardware without a manual image-export detour.

Greaseweazle and floppy workflows

v0.92 is also the first release where Amiga Imager can talk to a Greaseweazle as part of the main app experience. That means real floppy workflows can live next to image-building instead of outside it.

  • Read DD and HD Amiga floppies directly to ADF.
  • Write ADF images back to real disks with verification.
  • Browse floppy contents through the same File Manager workflow.
  • Capture raw flux when lower-level disk preservation or troubleshooting is required.

Build & Write to Card is much more practical

Direct write-to-card was not added as a gimmick. It is designed to make real hardware iteration faster.

  • The build can target real SD, CF, or SSD media directly from the Image & Build workflow.
  • The write engine skips holes and zero-filled areas instead of wasting time rewriting empty space.
  • Verification still happens at the end, so speed does not come at the cost of confidence.

AmigaDiskKit in v0.92

v0.90 introduced the first public AmigaDiskKit-based engine path. v0.92 is the release where that work starts to feel complete from a user point of view. The native Swift engine now carries much more of the real product, including the File Manager and floppy work alongside the core build path.

  • Native handling for FFS, PFS3, ADF, and LHA workflows.
  • Native FAT32 handling for the PiStorm boot-partition path.
  • Better speed, cleaner verification, and less dependence on brittle legacy-tool chains.

Broader tested platform coverage

v0.92 also expands confidence across the supported platform surface. UAE, Amiberry, and MiSTer with RTG support are now confirmed tested and working alongside the existing PiStorm and Classic Amiga paths.

That matters because the same project can now move more cleanly between PiStorm, Classic hardware, emulator setups, and MiSTer testing, instead of requiring a separate mental model for every target.

Why this matters

v0.90 and v0.91 laid the groundwork for the native engine. v0.92 is where that work becomes much more visible to users: faster builds, more direct hardware workflows, easier inspection of Amiga media on macOS, and a broader platform story that feels genuinely unified. It is one of the biggest workflow releases Amiga Imager has had so far.