Amiga Forever 7 and AmigaOS 4.1 FE

[amyren]

I just installed this package and played a little with it.

Setting it up with PPC for AmigaOS 4.1 FE was very easy, compared to how I have strugled earlier before managing to set it up manually with WinUAE.

But I have one issue which I have not figured out yet. How to make it accept more than 128MB fastRAM with the AmigaForever setup?
In Winuae I have set it up with 512MB Z3 ram and 128MB ram for the PPC board. And this does work.
But trying to add Z3 ram in AmigaForever doesnt seem to work.
If I add smaller amounts of Z3 ram it boots up, but still reports 126MB fastram in the workbench header. Adding 512MB of ram makes it boot into a different / corrupted screenmode so I cant see the display properly.

[amyren]

Problem solved.  The issue that the workbench wasnt able to use the extra ram was solved by installing the update 1 and setting the norampager option in startup-sequence.

And the display corruption when setting Z3 ram to 512MB ram is due to zorro3 cards in use by the emulation. To get more ram, I simply removed the RTL8029 network card and added the A2065 card instead. And if I want to add even more Z3 ram, I could replace the PicassoIV Z3 card with a PicassoIV Z2 card - or just skip RTG and use native screenmodes. But the PicassoIV Z2 did not handle modes above 8 bit so well, so I kept the Z3 card.
On Amiga Forever this give me 768MB Z3 ram and 128MB cpuboard ram, and workbench sees 894MB fastram.
Using WinUAE settings there can be additional 256MB ram, since the four Z3 memory banks can be tuned closer to 1GB, and also 64MB can be added as mainboard ram. Totally WB says there are 1150MB fastram with that setting.
Anyway, I just did this for testing and I probably wont need that much ram in any case.

[amyren]

How well does 4.1 FE with Update 1 run under Amiga Forever 7?

-Slygon

My general impression is that it runs quite well (under windows 7, intel i5, 3.1Ghz, 8GB ram)
I have nothing to compare it with, since I have no other OS4 capable hardware.
But its not fast. IBrowse and AWeb is fast enaugh. Odyssey takes a bit time to load up, but not so bad. But launching TimberWolf is a heavy task, it did take 1 minute for the logo and progress bar to apear, and 15 minutes before it was ready to use.
Once loaded it was slow but usable.

FOLLET: I did try now to set it up with uaegfx instead of PicassoIV. I cant notice any big difference at first use. I did however get some more screenmodes to play with. And it seems to free a bit more Z3 adress space so that some extra ram can be added. In return I lost the OS4.1 bootup screen.