Amiga Imager v0.99.8.1

Bugfix release - macOS 14+, Apple Silicon and Intel. Build: 260804.

AmiSSL works again on PiStorm and Vampire

Images built with 0.99.7 or 0.99.8 shipped the wrong AmiSSL library for PiStorm/Emu68 and Vampire machines, so every program that uses AmiSSL – browsers, FTP clients, anything doing HTTPS – failed with an error, even though AmiSSL was fully installed.

AmiSSL ships separate builds for different processors, and 0.99.7 started choosing between them. That change was made to fix a different problem, which turned out to have another cause entirely (too little Fast RAM), so the selection is gone again and every image gets the build that runs everywhere.

If you built an image with 0.99.7 or 0.99.8, rebuild it. The fix is in the builder, so images already made keep the wrong library until they are built again.

With thanks to evil4admin, who found it and pinned down exactly which file was at fault on the machine itself.

Large WHDLoad collections are measured correctly

The check that decides whether your games fit added up file sizes, but an Amiga filesystem stores each file in whole blocks and needs a directory entry for it. For a collection of thousands of small files that under-counted by up to 50% – so the check passed, and the copy then filled the partition part-way through.

It now counts what the files actually occupy, so an over-large collection is refused before the build starts instead of failing after several gigabytes.

You can cancel a build

Builds now have a Cancel button. Copying a large games collection takes a while, and until now the only way to stop it was to quit the app. Cancelling stops at the next safe point rather than mid-write.

And when a build stops early – cancelled or failed – Amiga Imager now asks what to do with the half-written image instead of leaving a file that looks finished but will not boot.

Both suggested by evil4admin.