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.1

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.

Icaros Desktop Live! and Light 2.0.1 are now available in our download page. Grab them while they're hot. These new builds should work better on systems where Icaros 2.0 failed to boot: at least, trying to add the NOACPI parameter to kernel at boot time shouldn't exclude all PCI devices anymore. A complete list of new features and bug fixes has already been published earlier this morning. If you're planning to install Icaros Desktop 2 on your real hardware or on a virtual machine, please use 2.0.1 and do not install the former 2.0 version anymore: this updated version also includes LiveUpdater 1.8a, which is a mandatory tool to support future update packs of your beloved distribution.



First update for Icaros 2.0 is now available for download. This is mostly a bug-fix release, but it also brings a new exciting feature users accustomed to 68K applications will love: running AmiBridge as a service, which basically means you can now run at startup either AROS M68K or AmigaOS 3.X (once integrated from Amiga Forever), with Janus-UAE hiding in background and running the guest operating system in coherency mode. This, independently from any current settings already chosen by user, which are still working when "manually" running AmiBridge through its usual scripts. But we will explain this better another day. Icaros 2.0.1 brings also some little enhancements to user interface: ZuneView now works from Magellan's "Programs" menu and a link to Prefs drawer has been placed in "Icaros" menu. Theme selector has been fixed and improved, removing many little and bigger quirks. From the very technical side, issues with FAT handler and ACPI library have been resolved, so downloading files from OWB straight to USB pendrives is possible again. Excluding ACPI for not-compatible PCs should also work without messing up all PCI devices.


NEW FROM ICAROS 2.0
- ntfs.handler moved to Storage/L (for new installations only)
- AROS system files brought to Dec 6th, 2014 Nightly Build
- SVN executables brought back to Development:bin
- Updated AntiryadIDE with a working version (see screenshot above)
- HDToolBox now shows drives connected to AHCI device (fixed missing icon tooltype)
- removed offending duplicated Datatype.info file
- fixed noacpi issue
- fixed regression: running AmiBridge at startup will work again
- fixed regression: Icaros will try to fall back to VESA mode first when selecting Native option in grub, like older Icaros (for new installations only)
- fixed Theme preferences
- removed offending (not working and crashing aros) themes
- added AmigaOS 3.1 theme
- fixed a bug preventing AROS68K from running, if themes were disabled in host environment
- updated ZuneFig and ZuneView to latest releases
- added "Prefs" option to Icaros menu in Magellan
- fixed ZuneView option in Magellan's "Programs" menu
- added a new version of WeatherBar


INSTALLING ICAROS FROM SCRATCH
Icaros Desktop Live! and Light 2.0.1 can be installed onto hard drive or USB pendrives as usual. Please follow instructions included in Icaros Desktop manual. If you're wondering wether installing Icaros 2.0 or 2.0.1, please go straigt for 2.0.1! It already includes LiveUpdater 1.8a, which will be mandatory for future Upgrade Packs.


UPDATING REQUISITES
To update your current installation of Icaros Desktop 2.0, you need the updated version 1.8a of LiveUpdater (LUPD). Please upgrade LiveUpdater to version 1.8a (and not 1.8) before trying to update Icaros Desktop, or you'll end up with a partial installation. LiveUpdater 1.7, coming with Icaros 2.0, is not able to perform needed operations on system startup files, so it needs upgrading.



UPDATING PROCEDURE
1) once installed LiveUpdater 1.8a, run it from SYS:Tools/LUPD, either through your main file manager or through AmiStart (System disk -> Tools -> LUPD -> LiveUpdater)
2) choose either the Internet or File installation. The former will download the update pack from Icaros website first, the latter, instead, allows to locate the update pack on any device connected to your computer, once manually downloaded from another machine.
3) wait for the procedure to complete, and reboot when required.

The following video will show you the procedure. Even if it is based on a older combo of LUPD and beta update pack, very little changed in the meanwhile.



After upgrading, a backup file for your current S:user-startup files will be created in S:, and a safety zipped version of core boot files will be created in SYS:Arch/. 

Unluckily, version 1.8 of LiveUpdater released yesterday has an unpleasant bug(*). The new 1.8a version is now available for download. People who will download and install Icaros Desktop 2.0.1 from scratch will find it already installed into the distribution, but people willing to update their current installation of Icaros 2.0 to the incoming update 2.0.1 should download and install this little program (20KB), which will improve update operations quality and efficiency. In particular, this new version brings these enhancement over the former 1.7 version, coming with Icaros 2.0:

- more polished output, using ZUnZip for update pack decompression
- existing kernel is now zipped and archived into sys:Arch/old-kernel directory
- all files in S get copied, user-startup is backupped into S:user-startup.LUPD-backup
- added updating of L drawer. It wasn't updated before
- LiveUpdater shouldn't show pointless error messages anymore, about files it could not find
- Fixed some other bugs here and there
- Fixed handling of S:user-startup that wasn't working in version 1.8

> Download LiveUpdater v1.8a (20 KB)

INSTALLATION
Just extract LUPD18a.ZIP file to any directory on your filesystem (RAM: might be a good place) and start the LUPD18a-Install script, either with the 'execute' command, or double-clicking on its icon. It will overvwrite older LiveUpdater version with the new one.

(*) What would happen if I'd update Icaros with LiveUpdater 1.8 and not 1.8a?
Nothing really bad. You should, however, manually delete S:User-Startup after installation, or many system programs like GUI, AmiStart, AmiBridge that Icaros runs at startup, would be launched twice (S:Icaros-Sequence would be executed both from S:startup-sequence and S:user-startup, since in Icaros 2.0.1 we've moved the 'execute S:icaros-sequence' command from the latter to the former). LiveUpdater 1.8 does not correctly handle updating S/ files, while 1.8a does.

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.