Thank you all for your answers!
It seems to me that is somehow a hit'n'miss...
I tried four different times in four clean installs of Icaros on the same PC. You can imagine that I had plenty of free time during the weekend!
Only one time I had smooth integration of Amiga Forever and all steps went well. All other installations finally gave black screen and Janus crash.
I am familiar with uae and it's conf files. I tried a lot of changes without success. I cannot understand what is going wrong with automated Amibridge setup.

If you're having problems with amibridge I'd recommend setting things up from scratch yourself. It will mostly likely require reading the euae/Janus docs, but they're clear and easy to follow.
Take it one step at a time, test, then move onto the next step, test, and so on.
This way a person can see exactly where the problem is.
Debugging amibridge and customizing it is probably trickier as there's a lot more variables to consider.

Setting up UAE is quite easy anyway once you've done it once or twice.

p.s. Ctrl+alt+q can come in handy (closes Janus) as can Ctrl+all+f1 through f4 (swap disk df0 through df3)/

Quote:

Beware this solution is absolutely discouraged on Icaros Desktop. You risk your own directories being overwritten applying Icaros system updates.

I have tried the janus version that's on the icaros cd, belonging that I was not interested integration then started janus I removed all partitions and created a new one, then a directory with the 3.1 system files.

Hi

The best result I got was from booting a HDF running Classic Workbench P96, but of course it was missing the integration features. Also AROS 68K started working after removing the shared ram drive and then the WBRun command would work from the x86 side, which was pretty cool, but it was still a bit crashy. I certainly got familiar with the Janus hotkeys (Ctrl+Alt+J) when testing.

I spent some time changing Janus settings one by one to get each system to boot. I may come back to it but at the moment I'm having some fun setting up a hosted system as a second boot option.

Did you have any progress?
Experiencing the same exact problems, I didn't have any solution either in native or vesa modes. Copying over and over again the system folder from Amiga Forever didn't help. I still get a black screen and nothing more. After that Janus seems to crash, can't stop and quit.

OK I can confirm that after manually re-copying the system folder from the Amiga Forever DVD AmigaOS now boots!

During the first copy attempt DOpus reported one copy error. On the second attempt (different install) it reported three copy errors. I'm now thinking this may have been the problem during the import as the AmiBridge:System folder looks incomplete:

disk.info 3066 ---rwed 27-Sep-15 09:20:45
sys Dir ---rwed 27-Sep-15 09:19:41
svenska Dir ---rwed 27-Sep-15 09:19:41
suomi Dir ---rwed 27-Sep-15 09:19:40
srpski Dir ---rwed 27-Sep-15 09:19:40
russian Dir ---rwed 27-Sep-15 09:19:40
Locale Dir ---rwed 27-Sep-15 09:19:40
Libs Dir ---rwed 27-Sep-15 09:20:45
L Dir ---rwed 27-Sep-15 09:19:36
Fonts Dir ---rwed 27-Sep-15 09:19:35
Expansion.info 2918 ---rwed 27-Sep-15 09:19:15
Expansion Dir ---rwed 27-Sep-15 09:19:15
Devs.info 2883 ---rwed 27-Sep-15 09:19:15
Devs Dir ---rwed 27-Sep-15 09:19:15
Classes Dir ---rwed 27-Sep-15 09:19:11
prefs Dir ---rwed 20-Feb-15 23:33:14
S Dir ---rwed 27-Sep-15 09:20:45
C Dir ---rwed 27-Sep-15 09:19:09

I'm no Amiga expert but should this folder look different? Copy errors during install would certainly explain some of the problems..

I'll have a look into the Import script soon, thanks again.

Have a deep look at the "integrate Amiga Forever" script, since you need to make some modifications to startup scripts in S: (amigaos side) in order to use AmiBridge functions. Please notice that AmiBridge is a "simplification" tool which starts from the assumption that user shouldn't do anything by himself, and let AmiBridge scripts do everything by themselves. If you start modifying here and there, or try to integrate things by yourself from a customized system, AmiBridge won't work properly, unless you're really good at it.

Small update: AROS 68K boots successfully if the shared RAM drive is removed from the UAE config, WB Run then also works.

As for AmigaOS I'll try re-copying the System folder.

Thanks for the replies, I have made some progress. This is a clean install of 2.1.3 testing on both native and VESA drivers.

I selected the Fullscreen preset > enable > save.

AmigaOS 3.1 didn't boot however. I got a full grey screen with a black rectangle in the middle, but nothing more. By replacing the HD0 drawer with an HDF I can boot to workbench however.

Trying the M68K AROS environment did boot a couple of times, I was able to set the screen mode and even open Ignition. It was pretty cool, but after a reboot it stopped working again. It doesn't boot beyond a grey / black screen, which is what I was getting before.

It just seems as if the default HD0 folders for AROS and AmigaOS are reluctant to boot. I'll continue investigating..