Hi everyone,

After the Personal Paint, TurboText and AmiPixelShop tests in the earlier thread ( https://www.arosw...post_15534 ) , I've put together a downloadable preview so other people can try their own 68k software.

The package boots AROS ARM64 in QEMU, with Kaffeine ready to run 68k applications inside AROS. The aim is to bring this work into AROS mainline but I'd like to get more applications tested and find the problems I've missed.

Download preview: https://github.co...-arm64-001

The ZIP is about 451 MB and includes the system image, sources and licences. You'll need Python 3.9 or newer and QEMU installed separately, including qemu-system-aarch64.

I've tested this package on an Apple Silicon Mac with QEMU 11.0.0. Windows and Linux launch scripts are included, but actual boots on those systems still need testing. Physical Raspberry Pi hardware hasn't been tested with this package yet.

Extract the ZIP into a new folder and read the included README. With Python and QEMU available from the terminal:

- On macOS, double-click Start.command.
- On Windows, double-click Start.cmd.
- On Linux, run sh Start.command.

Each launch starts with a fresh copy of the disk. The session folder is kept under sessions, together with its logs. Sessions stop after 15 minutes by default, so finish your save and reopen tests before that limit.

Once AROS opens, go to Kaffeine → KaffeinePreview and double-click Test-JIT. This runs a small 68k program which saves a text file, closes it, reopens it and checks its contents. Then try Test-Moira, which runs the same test with the interpreter. The output and saved file are in Results.

To try your own application, put its files in a folder called MyApp beside the extracted preview folder. You'll also need mtools installed for this step. From a terminal inside the preview folder, run:



On Windows, replace python3 with py -3 in these commands.

Inside AROS, the imported files will be in:



For example, to launch an executable called MyProgram from an AROS Shell:



Some applications need their usual assigns or extra libraries set up first.

Try opening windows, using menus, editing something and saving a new document. Close the application, reopen it in the same VM and check the saved content. Then repeat the same steps after selecting Moira in that Shell:



That comparison helps me work out where a problem might be.

After closing the VM, create a report from the host terminal:



Use --result success if the test worked, or --result timeout if it stopped before finishing.

If you used one of the double-click launchers, replace ../test-my-app with the actual folder created under sessions, for example sessions/20261102-....

The report includes system details and the last part of the logs. Without --include-logs, it contains no logs. Nothing is uploaded automatically. Please read the report before sharing it, since logs can contain application text or filenames.

Submit a Kaffeine community test report: https://github.co...new/choose

Choose Kaffeine community test, attach report.zip and tell me:

- Your host OS, CPU and QEMU version.
- The application name, version and 68k build.
- What you did, what you expected and what happened.
- Whether you launched from Shell, Run or an icon.
- Whether the same test worked with Moira.

If you find a CPU backend: line in serial.log or serial-aux.log, please include it too.

Working applications are worth reporting as well as failures. You can link your reports here so we can discuss the results.