Feature release
Amiga Imager now updates itself. No more downloading a zip and dragging it into Applications – it tells you when a new version is out and installs it for you, and it will never do that in the middle of a build or a card write. The file manager also shows your Amiga’s own default icons for drawers and files that have none.
Maintenance release - macOS 14+, Apple Silicon and Intel. Build: 260731.
Until now, “Check for Updates…” could only open the release notes in your browser – you downloaded a zip, unpacked it, and dragged it into Applications yourself. From this version on, Amiga Imager offers the update and installs it for you.
It checks once a day, and you can turn that off in Settings. Every update is verified twice before anything is replaced – against a signing key built into the app, and against Apple’s own code signature – so a tampered download is refused rather than installed.
An update never interrupts your work. If a build is running or a card is being written, the installation waits until that has finished. A twenty-minute build and a half-written SD card are not worth a point release.
One last manual step: this version still has to be installed by hand, because the ability to self-update arrives with it. From 0.99.8 onwards, updates come to you.
The Amiga File Manager already showed the actual Workbench artwork for anything with
its own .info. Everything else fell back to a generic folder symbol.
Now those entries show the volume’s own default icons – the
same ones Workbench itself would use, read from the image you are looking at.
So a GlowIcons image shows GlowIcons defaults and a standard image shows the classic ones, automatically, because the icons come off the disk rather than from the app.
.uae config asks for, and needs its own.
Without it, programs fail in ways that point somewhere else entirely.Two fixes worth naming. The Refresh button in the GadTools GUI had silently stopped being drawn two releases ago – it is back. And updating is now called update everywhere, instead of the three different words the two GUIs and the command line used between them.
When a command produces no output at all, amipkg no longer sends you to an empty log file: it explains that the command could not start, which on a 68k machine almost always means memory, and tells you what to do about it.
Existing images update themselves with amipkg upgrade on the Amiga;
newly built images ship it.