VmwAROS 1.0

VmwAROS is a pre-configured AROS environment.

  Add it to your Download Basket!

 Add it to your Watch List!


Rate it!

What's new in VmwAROS 1.0:

  • New, customized system files
  • Shutdown Wanderer funcion on supported hardware
  • Widescreen graphic modes on selected cards
  • Added Ken Lester's iconset
Read full changelog
send us
an update
3.0/5 14
Paolo Besser
ROOT \ System \ Operating Systems \ Other
VmwAROS is distibuted as harddisk image file(s) that can be run in VMware virtualization software (Player, Server, Fusion, Workstation). The distribution contains a number of preinstaled software packages, including email application, text editor, image editor, development environment, compilers pack, web browser, IRC client and much more! It delivers network connectivity either via manual configuration or DHCP client and you can run it on your Windows, Linux or Mac box! You can also upload and download files from AROS using the distribution`s built-in ftp server.

VmwAROS will come installed on a virtual HD0: FFS partition, and will sport a pre-formatted SFS Work: partition with the most interesting AROS applications available. File transfer between the Windows or Linux host operating systems, and the AROS guest will be made easy, thanks to a the pre-configured YAFS ftp server on the AROS side. Just connect with any FTP client and you're OK.

About AROS

The AROS Research Operating System is a lightweight, efficient and flexible desktop operating system.

The AROS Research Operating System is a lightweight, efficient and flexible desktop operating system, designed to help you make the most of your computer. It's an independent, portable and free project, aiming at being compatible with AmigaOS 3.1 at the API level (like Wine, unlike UAE), while improving on it in many areas. The source code is available under an open source license, which allows anyone to freely improve upon it.


The goals of the AROS project is it to create an OS which:

1. Is as compatible as possible with AmigaOS 3.1.
2. Can be ported to different kinds of hardware architectures and processors, such as x86, PowerPC, Alpha, Sparc, HPPA and other.
3. Should be binary compatible on Amiga and source compatible on any other hardware.
4. Can run as a standalone version which boots directly from hard disk and as an emulation which opens a window on an existing OS to develop software and run Amiga and native applications at the same time.
5. Improves upon the functionality of AmigaOS.

To reach this goal, we use a number of techniques. First of all, we make heavy use of the Internet. You can participate in our project even if you can write only one single OS function. The most current version of the source is accessible 24 hours per day and patches can be merged into it at any time. A small database with open tasks makes sure work is not duplicated.


Some time back in the year 1993, the situation for the Amiga looked somewhat worse than usual and some Amiga fans got together and discussed what should be done to increase the acceptance of our beloved machine. Immediately the main reason for the missing success of the Amiga became clear: it was propagation, or rather the lack thereof. The Amiga should get a more widespread basis to make it more attractive for everyone to use and to develop for. So plans were made to reach this goal. One of the plans was to fix the bugs of the AmigaOS, another was to make it an modern operating system. The AOS project was born.

But exactly what was a bug? And how should the bugs be fixed? What are the features a so-called modern OS must have? And how should they be implemented into the AmigaOS?

Two years later, people were still arguing about this and not even one line of code had been written (or at least no one had ever seen that code). Discussions were still of the pattern where someone stated that "we must have ..." and someone answered "read the old mails" or "this is impossible to do, because ..." which was shortly followed by "you're wrong because ..." and so on.

In the winter of 1995, Aaron Digulla got fed up with this situation and posted an RFC (request for comments) to the AOS mailing list in which I asked what the minimal common ground might be. Several options were given and the conclusion was that almost everyone would like to see an open OS which is compatible to AmigaOS 3.1 (kickstart 40.68) on which further discussions could be based upon to see what is possible and what is not.

So the work began and AROS was born.

Last updated on December 15th, 2008

#AROS OS #operating system #virtualization software #AROS #OS #VMWare #virtualization

Add your review!