Handbook
Amiga Imager v0.88
Current handbook for Amiga Imager v0.88. This guide was checked against the shipped 0.88 / 260520 build and is the current public handbook until a newer revision is published.
Handbook
Current handbook for Amiga Imager v0.88. This guide was checked against the shipped 0.88 / 260520 build and is the current public handbook until a newer revision is published.
This is the public day-to-day guide for Amiga Imager v0.88. It is meant to match the current app build. It covers the two main workflows, the current build screen, platform-specific notes, and the settings panes introduced in the newer releases.
Amiga Imager is a native macOS app that builds ready-to-use Amiga systems from one workflow.
.img files..hdf files.For a normal build you should have these items ready:
Media expectations depend on the AmigaOS version you select:
Optional but often useful for current v0.88 builds:
This is the main mode and the one most users will spend their time in. It lets you select a target platform, point the app at your install media and ROM, choose optional software, review a Build Summary, and generate a ready-to-use disk image.
This mode writes an already built image to removable media. The UI is simple: choose the image file, choose the target disk, optionally keep Only show external disks enabled, then click Write to Disk.
Writing to physical media may ask for your administrator password. On macOS you may also need to grant Full Disk Access to Amiga Imager if raw disk access is blocked.
PiStorm / Emu68, Classic Amiga, or MiSTer (Minimig).Simple is the fastest route. It applies safe defaults for a first build, including bundled assets, EN plus your system locale, Roadshow Demo, and the shareware Picasso96 path when RTG is needed.
Advanced is where the full app lives. Use it when you want custom hardware choices, manual Roadshow or Picasso96 archives, transfer folders, package-specific registration files, custom image sizing, or profile save/load.
This card is where you set the platform, OS version, media, ROM, and output image. On Classic builds it also exposes the current hardware selectors for Machine, Accelerator, RTG Graphics Card, and Network Card.
In Advanced mode this is where current v0.88 setup choices live:
None, Roadshow (Demo), or Roadshow (Full), plus Wi-Fi where supportedSimple mode offers a one-switch community package path. The current UI describes it as including tools such as SysInfo, NoClick, MUI 3.8, IBrowse, AmiSSL, and WBDock 2.
Advanced mode exposes grouped package selection. Some packages open extra fields only when needed, for example:
Use this card to choose the image size and start the build. Simple mode stays on the preset path. Advanced mode exposes the full image size controls, partition layout, profile save/load, and the final build actions.
.img output file.VA2000, P-Vision, Vampire SAGA, and ZZ9000.A314 and ZZ9000Net alongside other Classic NICs..hdf output file.The current app has a dedicated Settings window with five panes:
DEVS:a314.config outputIf you keep the default setup, you can ignore most of these. They are mainly useful when matching specific hardware or refining repeated build workflows.
Use Install / Retry. The app needs hst-imager before build mode can run.
The most common causes are missing install media, missing Kickstart ROM, or no output image path. For AmigaOS 3.9, also check that both Boing Bag updates are present.
Enable Full Disk Access for Amiga Imager in System Settings -> Privacy & Security -> Full Disk Access, then retry. Replugging the target device can also help.
Make sure the network stack is set to Roadshow Demo or Roadshow Full. A314 is not supported with None.
Reduce the preset, adjust the custom size, or use the storage size-reduction settings to leave more headroom for real SD media.
Use Export Log after the failure and keep the build summary details. That is the fastest way to capture the exact configuration used by the current build.