AirBoot is a track0 Boot Manager.
That means it is stored at the very start of the disk,
just after the Master Boot Record.
AirBoot is also an interactive Boot Manager,
which means it presents a list of Operating Systems in a menu
from which the user can select one to boot.
A Little History
AirBoot was initially designed and developed by Martin Kiewitz,
back at the time when LBA addressing was just becoming mainstream.
Over time, Martin continued to add features and fix reported problems,
which resulted in a stable and mature product.
When huge harddisks (>512 GiB) became more mainstream,
the OS/2 Boot Manager was not capable of correctly handling them.
After some investigation, it became clear that AirBoot would be a very
suitable candidate to replace the aging OS/2 Boot Manager,
but a few things needed to be fixed first.
Martin however, had moved on to other projects and was not
developing AirBoot anymore, but he kindly gave his permission to modify
AirBoot in any way required such that it could replace the OS/2 Boot Manager.
With the release of eComStation v2.1 (2011), AirBoot was ready to replace
the OS/2 Boot Manager and so it was included in that release.
It is safe to say that AirBoot saved the day at a time when
huge harddisks came along and the fight for primary partitions got worse.
Thank you Martin !
Some AirBoot Highlights
No Primary Partition Required
On The Fly Partition Scanning
Support For Huge Harddisks
Operating System Agnostic
Before Using AirBoot
Before installing AirBoot,
it would be a good idea to learn a little bit more about it.
This is especially true with regard to partitioning harddisks the way
OS/2 likes it (use its volume manager) and the co-existance
with other operating-systems.
See the section below where
to download AirBoot or view its manual.
(bootloader, installers & manual)
View the AirBoot v1.1.4 Manual Online
This project is *not* a fork of the original Netlabs project.
It is a *clone* done with
git-svn with the purpose to be able
to use Git Branching for testing and feature additions.
The bi-directional mapping is:
The preferred way is through Netlabs Track,
and you can create a new ticket using the following link:
Report a problem on Netlabs Trac
(note: you need to be logged-in to netlabs to create a ticket)
But, before you report a new problem,
please check if the problem you are about to report
was not already reported by somebody else:
View existing problem reports on Netlabs Trac