My AF11 ISO has a rom.key file in the ROMs directory but not sure if that means that the ROM files are encrypted or not.

The AmigaOS 4 versions of Blastaway, BOH and KOG were a bit behind with respect to the Windows versions due to the fact that at some point my AmigaOne stopped working and I could no longer compile them. Lately I finally got around to install qemu and produce updated executables.
The games are available for pay-what-you-want (even as little as 0) download from https://www.retream.com / https://retream.itch.io as usual.
Many thanks to klx300r for testing the executables on his X1000.

Blastaway v1.6
* Avoided redundant operations when a video/pixel mode change requires a re-initialization of the screen/window.

BOH v2.5
* Fixed resuming of the sounds of tiles clusters (e.g. moving floors) after unpausing the game, which caused them to remain always active at maximum volume.
* Removed contact email address from executable.

KOG v2.10
* Avoided redundant operations when a video/pixel mode change requires a re-initialization of the screen/window.
* Removed contact email address from executable.

     The Swedish Commodore Club (SCK) had its annual show on September 5-7.  Check out the Commodore and Amiga computers and presentations in the following videos:

Walk-through of SCK Commodoreträffen 2025

https://youtu.be/ez2adY07r68

Anemo - SCK Commodoreträffen 2025

https://youtu.be/V4b1fdu7Ado

Mical - SCK Commodoreträffen 2025

https://youtu.be/Eqo36s4tndU

          Pictures to come,
          Robert Bernardo
          Fresno Commodore User Group -
          http://www.dickestel.com/fcug.htm
          Southern California Commodore & Amiga Network -
          http://www.portcommodore.com/sccan

I'm using 46.2.1312 and hit a few issues (though also saw this on 1303 version).  I'm not sure what to call the A600GS GUI that is available before emulation begins and so will refer that as the "frontend".

1) Frontend pointer pops up when using F12 menu. However, when I leave that menu. There is a single pixel pointer that is left behind and follows the emulated pointer.   

2) I'm using a HDF file and boots okay initially.  I can do multiple reboots and still is okay but at some point the emulation no longer sees the partitions in the HDF as bootable anymore and so I just get to the kickstart insert disk.   Yesterday, I booted from an ADF and used HDToolbox to look at the RDB of the partitions on the HDF and saw that all that I have specified as bootable was still shown as bootable.   But for some reason the emulation still does not see it as bootable.  I have to recopy over the entire HDF again.  This HDF is a 20GB one.   I'm not sure if it is messing with the Frontend  settings changes anything but this time I noticed that after I disabled RTG and disabled network, save and then started it became non-bootable.

3) Frontend Wifi SSID list.  There are multiple entries of same SSIDs in the list that shows up.

4) I was trying to get P96 to work for A600GS.card by using BOARDTYPE=A600GS.  When I enable this, I get a strange error saying that ModeID is same for "A600GS and A600GS"  A600GS text is shown twice in the requester.

5) Only files with extensions *.hdf are recognized.  Would be good to also recognize *.img and *.hda as well as these were how the ones I have were named.   My hard drive file was basically created on exFAT SD card on Windows 11 using this example from the ZuluSCSI site https://github.com/ZuluSCSI/ZuluSCSI-firmware

Windows: fsutil file createnew HD1.img 1073741824 (1 GB) --> I changed this to 20GB

I then used a ZuluSCSI on a real A4000T to do the partitioning and formatting.  I copied everything over on my A4000T to that hard drive file and then copied it over to A600GS.

46.2.1303 PUBLIC:
Speed up startup times by fetching amisphere server data asynchronously.
Set shorter timeout in case of server error when logging in.