UAE config files location?

[amyren]

I tried to mount and browse the SD-card to see if I could locate the amiberry configuration files for my setups. The idea was that I was hoping to find my WB3.9 setup file and be able to manually modify it, adding more RAM, enabling gfx card, adding some of the shared storage media etc. I found the systemv46 uae file, but did not find any uae setup files for my own systems and games setups.
Anyone know how this works?

[arttu80]

If I understood correctly, you don't know directory path in WinUAE for config files? It can be seen at WinUAE properties window in Settings / Configurations. Mine config files are located like this "C:\Users\Public\Documents\Amiga Files\WinUAE\Configurations\"

[amyren]

If I understood correctly, you don't know directory path in WinUAE for config files? It can be seen at WinUAE properties window in Settings / Configurations. Mine config files are located like this "C:\Users\Public\Documents\Amiga Files\WinUAE\Configurations\"

This is for the A600GS, which runs a linux variant on a OrangePi Zero 3 board. It boots up with a A600GS customized GUI, and the Amiberry user interface is hidden for end users.
I did manage to browse the SD card file structure to look for these files, so the question was related to find the Amiberry setup files for each user system.

[amyren]

Tested Debian Bookworm (desktop edition) for OrangePi Zero3 on the A600GS, and here is a short summary of my observations.

OrangePiZ3 is quite snappy with Xfce and basic tasks like webbrowsing runs smoth.
The A600GS expanion board works out of the box, so USB and audio jack is working. I was not able to test the DB9 gameports.
The Amiberry executable can be copied from the A600GS sd card and run on the Xfce desktop, although not everything runs as expected.
A600GS version of Amiberry is Amiberry-Lite 5.7.5 but it seem to be differences between this version and the executable I got when building my own 5.7.5 executabe from the instructions on the github.
The A600GS executable will not do anything when pressing F12, so the only way to exit it is to make sure 'Alt+Tab to release control' is ticked before launching the emulation. I also had trouble getting RTG to work for OS3.9 with this executable. I could run Amibench but the LoadAB command fail to load on startup, so I had to use LoadWB to get a desktop.
The 5.7.5 Lite version I build myself does have the F12 mapped to opening the GUI, and RTG is working on OS3.9.
Also tried installing the Amiberry 7.0RC2 deb package but I can not enable JIT in that version so it runs much slower then the Lite versions.

The A600GS amiberry-lite executable and the one I buildt myself are the same size 12.7MB, and both run on Debian desktop. In the A600GS environment only the A600GS version of the executable will work.
In general Amiberry performs much faster in the A600GS environment than from the Debian desktop. I am not sure if this is due to the desktop environment is slowing things down or if there are other tweaks in the A600GS setup
For speed comparisation I ran AB3dII (Karlos-TKG edition)
Amiberry-Lite 5.7.5 on Orangepi Desktop: 10-12 FPS
Amiberry 7.0RC2 on Orangepi Desktop: 4-5 FPS
Amiberry-Lite A600GS environment: 46-50 FPS
Also tested Superfrog (WHDLoad) and it runs smooth on all systems, but the sound only good in A600GS envionment.

Now that AmigaKit have announced RTG and global disk support for the upcoming update I see less need to tinker with the Desktop version of Amiberry. But some kind of 'rabbithole' to be able to run certain linux apps (like chronomium) could be useful.