Icaros Desktop is a pre-configured AROS desktop environment for the PC platform, distributed on a bootable live media. The AROS Research Operating System is a open source lightweight, efficient and flexible desktop operating system, aiming at being compatible with AmigaOS 3.1 at the API level, while improving on it in many areas.

Icaros Desktop 2.0

The best AROS experience you've ever had. Grab it while it's hot!

Enhanced integration of 68K applications

Would you believe they are old Amiga 68K applications running on a common PC? Well, they are! Discover the new AmiBridge integration mode which does not need original Amiga ROMs and OS anymore!

Play Hurrican and other classics

Linux format said "Icaros Desktop is the best OS to frag productivity". Why? Because you can play thousands of old classics and dozens of great remakes. And every game Amiga had.

Image editing with Icaros Desktop 2.0

This video will show you how images can be shown, rotated, edited and cropped using Icaros Desktop's powerful tools.

My work to improve AmiBridge before Icaros update 2.0.1 continues. I've found many little and bigger quirks in almost every place (in S:icaros-sequence.m68k for both AROS68K and AmigaOS 3.X, in AmiBridge's launch scripts, even Prefs/Icaros Settings wasn't saving some environment variables correctly) but, luckily, this revision effort is proceeding very well. On this post's top left corner there is a screenshot of the new AmiBridge panel of Icaros Settings (click to enlarge). As you can see, I've decided to add a new option; to promote the last five as 'advanced' ones and, last but not least, to replace that obscure "Amiga M68K VM" caption with a more user-friendly "At startup run", which better describes what this option is meant to do. The new "...transparently" switch allows either to run AmiBridge using current user settings and presets (when off), or to run it as much hidden as possible, like if it was a system service, in coherency/integration mode. This way, you can still manually run either AROS M68K or AmigaOS 3.X (from Amiga Forever) using your favourite settings (for instance, full-screen or in windowed mode, at a lower resolution), but also having Icaros launching one of them for you in background. When running a 68K OS in background, Icaros Desktop won't show any message or UAE icon on the screen, nor it will open UAE-Control or a 68K shell: the emulation environment will be always ready to run your classic programs: just launch them from Wanderer, from AmiStart or Magellan (right click -> WB Run) as usual, and their windows will pop up on the screen.

AWeb and AmigaAMP running under AmigaOS 3.X, and Ignition for 68K running under AROS M68K, all integrated into the same AROS host screen. Let me say that 'only Icaros Desktop makes it possible'...

Almost three weeks after v2.0 went on-line, it's now time to work on the first update which will be, of course, mainly a bug-fix release. We've already addressed many of the problems reported by users on AROS-EXEC and other Amiga related forums, but obviouly there will be also some little enhancements to existing features. The first one getting some love is AmiBridge, as shown in the following video. It will show you how to setup classic Amiga software integration and, of course, it will show a new feature many of you asked for: the ability to run AmiBridge at startup in a more integrated fashion. Enjoy!



Some times, it does not matter how much time you spend testing things and trying to fix all issues before a release. Something embarassingly big always eludes controls. This time it happened with Icaros' Theme selector in Prefs. We noticed long ago it wasn't working very well with newer AROS files, but we put it in the 'to-do' list and then we completely forgot about it. Result is that people who wish to change their theme can actually do that, but after many pointless debug windows popping up on the screen, not counting issues with some themes (OS3.1, Special, Mason) which weren't actually themes but simplier AROS system images, and sadly crashed Icaros at reboot when chosen. For this reason, yesterday evening I thought that my daily travel by train, from office to home, would have been better spent by debugging the Theme program in Prefs. I'm not a LUA coder but, as you might have already read in the past, I started learning something about it with the Icaros Setting program. You can appreciate the results in the top left screenshot: it looks exactly like it was before, but now it works as expected. My works on the Theme program also led to a discussion on AROS-EXEC, since themeing needs some lines in the startup-sequence I proposed to change. There are still some minor problems when themes are disabled, but we'll find a solution, some day (it's in our to-do li... ehm...).

PS: if you have an Acer AspireOne ZG5, but even if you haven't any, don't miss this article on Epsilon's Amiga X1000 blog. A great page about Icaros Desktop we couldn't appreciate more.

Our friend and talented developer Neil Cafferkey posted to AROS-EXEC a nice guide to most common issues people met with Icaros Desktop 2.0 in the first days after release. If you have issues, before sending a help request to our support forum, please try these hints:

The native SATA/AHCI driver doesn't always work. If you get errors related to ahci.device, try disabling it. Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ahci.device entry, and delete it with Ctrl-K. Then press Ctrl-X to boot. If your disk isn't accessible at all with this change, you might need to change the SATA controller to IDE legacy mode in the BIOS: however, making this change will likely cause problems booting Windows on the same machine (if it's already installed). To disable ahci.device permanently, edit the text file "SYS:Arch/pc/grub/grub/cfg", and remove the ahci.device line from all boot entries you intend to use.

The ATA driver doesn't always work. If you get errors related to ata.device, try using the alternative, older version provided: Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ata.device entry, and change it to read "module /Devs/Alt/ata.device". Then press Ctrl-X to boot. To make this change permanent, edit the text file "SYS:Arch/pc/grub/grub/cfg", and change the path to ata.device in all boot entries you intend to use.

The NTFS filesystem driver doesn't always work. In some cases, ntfs-handler locks up during boot if you have NTFS (i.e. "Windows") partitions on your PC. To disable ntfs-handler, move it from "L:" to "SYS:Storage".

AROS won't boot when some themes are selected. Avoid choosing the os3.1 or mason themes. If you want a similar appearance to the os3.1 theme, move "C:Decoration" to "SYS:Storage". If you've already selected a broken theme, you can recover the situation as follows:
Boot from your installation media.
Move "AROS:C/Decoration" as described above.
Reboot from your HD, and select a working theme.
Restore "Decoration" to its original location ("C:").


The "noacpi" boot option cause all PCI devices to be invisible to AROS. Although disk drives may still work, network, sound etc. drivers won't.

Changing video resolution may cause a crash, especially when using the Intel GMA driver. I'm not sure if the new resolution will still be saved for the next boot. If not, you can work around the problem by temporarily switching to Wanderer in Icaros preferences.

Some VirtualBox settings are incompatible with AROS. Do not select ICH9 or ICH6 chipsets, nor SATA drives. Only use AC97 audio.

Hello. Since some users on forum seem to be a little confused by Icaros Desktop 2.0 defaulting to Magellan, I've set up a short video placing both file managers side to side, and explaining the most basic concepts about them. I hope you'll appreciate. Sorry for speaking Paulish™ again, but I'm really tired and my damn headache doesn't help my English to well express itself.


As reported by AROS-EXEC.org's user Chain-Q, while still working on the distribution, we left out svn client executables by mistake. Here's our official answer:

Something really wrong happened with subversion. It was added to Development directory (so it should have been available in Live! distribution only), and even the Subversion: assign is set by default... but lately the development dir has been replaced. And svn executables left out by mistake.

To fix the issue, please download svn for aros here
> http://archives.aros-exec.org/index.p ... rsion-1.1.4.i386-aros.zip

Extract archive files and copy the 'bin' subdirectory contents (the various svn* executables) in Development:bin

We're sorry for the issue, that will be fixed in the first available update. For now, SVN has been temporarily removed from the feature list of Icaros 2.0.