UAE4ARM and existing (working) setup
-
I'm hitting a problem with this (and not just UAE4ARM, but all the Amiga emulators that ship with retropie).
I was an Amiga user for many years, with a heavily customised A1200 (Apollo 68060 board, CGX gfx card, MAS Player, IDE card, and a daughter board that I forget, all hacked into a tower with a sawn apart and re-assembled back panel ).
Before me and miggy parted company, I imaged my main system partition and (I thought - my programs - but something went wrong there). Nevertheless, after some tweaking (mainly emulator settings and s:startup-sequence) I got to the stage that I could easily boot the image (hdf) under emulation. It still works with FS-UAE on Arch Linux today.
Now, I have a Pi turned over to dedicated use as retropie, with it's own KB, Mouse, Gamepad and shared monitor. However, I've tried replicating the FS-UAE settings within the retropie emulator settings, and I can't get a successful boot. With some work, I can get a boot that fails to a shell, but ideally I'd like to get my old system booting again.
The '060 libraries have been disabled, so it's not an '060 OS specific problem, and I've made sure that any references to disks are either satisfied, or disabled, but all I get is a black screen.
This is not just a game issue - but a complete Amiga WB, with Picasso IV emulation issue.
Is there a way I can make the FS-UAE config that works work with UAE4ARM (or any of the alternatives)?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.