Feature release

Amiga Imager v0.99.12

Emu68 1.1 on PiStorm, done properly: the boot partition is writable again, the board is pinned, and PiStorm16, FrameThrower and USB builds get the 1.1 they need. New in Manage Amiga Software: update Emu68 in place on an existing PiStorm image or SD card, with a one-step Restore. Plus the Amelinium browser as a package, your tokens and Wi-Fi passwords in the macOS Keychain, and Settings changes that apply the moment you make them.

Download v0.99.12 Handbook PDF Browse all versions
  • PiStorm: Emu68 1.1 with a writable EMU68BOOT
  • Update Emu68 on existing images and cards, with Restore
  • Amelinium web browser as a build package, in the dock
  • Tokens and Wi-Fi passwords live in the Keychain
Back to all releases

Feature release - macOS 14+, Apple Silicon and Intel. Build: 261003.

PiStorm: Emu68 1.1

Emu68 1.1 changed how it reads its settings: the old cmdline.txt switches for the SD card are ignored, and by default the whole card is read-only – EMU68BOOT included. Images now write the 1.1 settings in config.txt, per Pi model, so the boot partition is writable again. The board (PiStorm32 or PiStorm16) is pinned there too: 1.1 ships one kernel for both and would otherwise guess the board from its pins, which clone boards get wrong.

PiStorm16, FrameThrower and PiStorm USB only work on 1.1, and now pull it automatically. Until now an A600 PiStorm16 image could silently get 1.0.7 and stop at the Emu68 logo. If no 1.1 is available, the build stops with a clear message instead.

When GitHub stops answering release queries (it allows 60 per hour), a PiStorm build used to fail within a second. It now uses the last release it saw – but only one from the channel you asked for, so a stable build never quietly gets a beta.

Three safety fixes for 1.1 images:

  • If the VideoCore driver 1.1 needs cannot be downloaded, the build stops. It used to finish with the old driver – an image with no RTG at all.
  • TransferKick deletes your Kickstart files from EMU68BOOT only after the copy succeeded. That never mattered while EMU68BOOT was read-only; on 1.1 a failed copy could have cost you the ROM.
  • The old Emu68-Updater on the Amiga only knows the 1.0 layout. On a 1.1 system it now explains that and exits without touching anything, and points you to Manage Amiga Software.

New: update Emu68 without rebuilding

Open a PiStorm image in Manage Amiga Software and it shows which Emu68 release is installed, for which board, and what the newest release on your channel (stable or prerelease) is. Update backs up the current boot files to EMU68BOOT:Emu68Backup, writes the new release and VideoCore driver, and moves your HDMI and FrameThrower settings over when it goes from 1.0 to 1.1. Your kick.rom and Wi-Fi settings are never touched. Restore puts the backup back. Updates only go forward; going from 1.1 back to 1.0 is a Restore.

Open Card… next to Open Image… does the same – and package management – directly on an SD or CF card.

Please read this before using it on a card. The update and restore were tested on image files, round trip included. Writing to real cards is new in this release and has not had wide testing yet. Back up the card first (an image of it is enough), and tell us how it went – good or bad.

Amelinium, one Poseidon, newer amiagent

  • Amelinium, the web browser with JavaScript (and the Emalinium mail client), is now a build package with its own icon and a place in the dock. The build picks the right version for your CPU and adds AmiSSL for HTTPS.
  • USB: images carry exactly one Poseidon, 4.5. Before, a 2.x copy was installed and then overlaid, which left three Trident programs on the disk – the dock opened an old one – and an amipkg upgrade poseidon on the Amiga could have put the old version back and broken PiStorm USB.
  • Built images now carry amiagent 0.13.1 (was 0.10.0): larger uploads, the task list, and the same files amipkg upgrade amiagent installs.
  • Icons the build adds to Prefs and Tools are laid out in rows below the ones AmigaOS ships, which stay exactly where they were. Drawer windows grow to show them; the Programs drawer no longer hides its last row on RTG screens.

Settings, profiles and the build screen

  • Changes in the Settings window apply right away. Some – boot mode, DF0, prerelease, UserFiles and the Settings-window build options – used to reach the build only after a relaunch.
  • The DF0 toggle showed "on" for anyone who never touched it, while the build used "off". It now shows what the build actually does. Images are unchanged.
  • Cancel in the Flash pane during a build hid the build while it kept writing the image. It now really cancels it.
  • Loading a profile no longer switches the network stack to Roadshow Full when you had chosen the Demo, and no longer loses the emulator CPU and RTG choice.
  • The same configuration now always gives the same dock order. Before, it could change from one build to the next.
  • Choosing only a folder in Save As keeps the automatic image name, so it keeps following your settings. If you did type your own name, a Use automatic name link brings the automatic one back.

Your secrets in the Keychain

The amiagent and Home Assistant tokens were stored in the app's preferences as plain text. They now live in the macOS Keychain; existing tokens move there automatically on first launch. The token and Wi-Fi password fields support Password AutoFill from the Passwords app. From this Mac fills in the password this Mac already saved for the Wi-Fi network you typed – macOS asks you first. Wi-Fi passwords you build with are remembered per network, in the Keychain. None of these secrets is ever written into a saved profile.

Profiles: new format

Profiles are saved in a new format and now also carry the build options from the Settings window (A314, amiagent, ami2ha, Vampire, amipkg, network at boot) – without tokens or passwords. Older profiles still load. Older versions of Amiga Imager cannot open profiles saved by 0.99.12, so keep a copy if you switch back and forth.

Also

  • Deleting files from a PiStorm boot partition (FAT32) now frees their space. It used to stay lost.
  • Bundles amipkg 0.7.11, unchanged from 0.99.10.