Implemented MP3 pausing and resuming.
Working on scan and auto play.

I'm at risk of falling down rabbit hole. Aready side tracking myself.
Been looking at ways to improve memory allocation. More specifically, reverse allocating available.
It cant be done on PSP (exactly like on Amiga), however we can simulate it, allocate small stuff low and caches high (only Paula and MP3 at moment).
Can also get UAE to use it and allocate in same way.

Think its better for me to note ideas down and revisit them, after improving rest of backend and getting speed up, via offloading more to ME, like blitter and copper.
Biggest slow downs are also in IO access, i.e. demo's State of art constantly loads from floppy, this is were the demo nose dives.

Also havo consider PSP-1000. I'm currently using my Go. PSP-1000 only has 24MB usable mem, Go (like all other PSP's after 1000 have 52MB usable mem).
Adding loads of caches, will limit 1000's usable ram, So setting Amiga ram to say Chip 2MB, Slow 1.5MB, z2 8MB and z3 8MB cause it to crash. Go doesnt care, it eats the entire user ram and just keeps going into extra 32MB hidden cache mem.

Hello,

About the kickstart version: you'll need one that supports drives bigger than 4GB, or you won't be able to access all partitions of AGS. It will boot, but won't access the games 
So original kickstart ROM 3.0 or 3.1 won't do, you will need either a newer 3.2.x, or a modified 3.1 with a fixed scsi.device .

If you have an accelerator with MapROM functionality (like a Blizzard IV), then you can keep the original ROM. This requires modifying the AGS image in WinUAE: you need to modify its startup sequence to make it load the new kickstart from a file and reboot.

And as for a PCMCIA IDE adapter, the big disadvantage is that you cannot boot from it, you will need to prepare a floppy for that.

Cheers!

The reason for assuming it was 32 bit was the JIT bug I experienced.
According to the amiberry lite issues listed on the github page there was a JIT fix, but it was only applied on the 64 bit version.
Since I still experienced the JIT bug, I assumed it was because this was a 32 bit version.

Review of the A1200NG and AmiBench in 2026 by Puni / AmigaOldskooler:

https://oldschoolgameblog.com/2026/03/17/a1200ng-and-amibench-in-2026/

As far as I know A600gs, and probably A1200ng  as well uses Amiberry-lite which is still at version 5.x
Also I suspect they use the 32 bit version, and it looks looks like Amiberry 8 is targeted at 64 bit only.

You are correct that we use the amiberryy-lite fork, with our own modifications, but we certainly use a 64 bit build, why would we not on 64bit hardware.