I'm trying to install amibian 1.4 on my raspberry pi 4B, it seems this is not compatible with eachother. Or am i doing something wrong?
jdryyz
Nov 25I successfully updated Amiberry from 2.18 included in Amibian 1.4 yo version 2.25. Because I ran into some other unresolved system problems, I decided to back up all the emu config data, etc and reinstalled a fresh amibian. Now when I attempt to update amiberry, it results in some error messages and I am left at v2.18. I believe this is because amiberry 3.03 now uses SDL2 (whatever that means). :) I assume the next version of amibian will support the latest amiberry??
1.4 is not compatible with Pi 4 or Pi 3A+. 1.4 works fine on a Pi 3. 1.5 final will be and is still in development. 1.5 beta no pi 4 either. But did at one point have uaegfx working on beta. Make sure to get good cooling as it is reported to cause the Pi4 to run warm so far. You can install FS-UAE on Raspbian desktop in the mean time as I have done.
thanks for the reply, i just have to be patient i guess... :0)
Me too... chomping at the bit to get mine. But I have a Pi 4, 3 Pi 3’s, a Pi 2 68k Apple ( My “Apple Pie” ) and other devices, and plenty of things to develop in the mean time... including faq related stuff in the forums and figuring out what is causing all these damn write errors corrupting my files!!! I have had to reload emulations 4 or more times. Even DietPi/Amiberry had issues. Do not recall having many issues with Raspbian. I back up frequently and am making an image library for rapid scratch installs and hdf repository so I can reburn image instead of re-install - with images already intact and pre-configured, and quickly add internet and music files and adf’s and WHDload games. I expect others to have better reliability than me. I think I have something going on locally.
Could it be due to improper shut-downs?
There is that possibility... but even the emulator itself has been corrupted not just the hard files. I power off after shutting down script. I do sometimes reset when I change hard files in the config. P.S. the more i think about it, i may have done both ways...i should try watching my behaviors more closely to see for sure...
The only thing I expected to get lost is directory cache on the Amiga images. This possibility has occurred to me though, thanks. Have already started to pay a bit more attention to this as well. I have also done write-read tests on a PC and found cards bad, as well as successful tests and then fails in operation... I will confess however to not shutting down the emulation between reboots, changing hardfiles or profiles ( I do Amiga Reset ) etc...