source: trunk/1README.TXT@ 201

Last change on this file since 201 was 192, checked in by Ben Rietbroek, 8 years ago

Adjusted '1README.TXT' a bit [v1.1.1-testing]

CAUTION:
This is a testbuild !
AirBoot uses the BIOS to access disks and a small coding error can trash
partition tables or other vital disk structures. You are advised to make
backups of TRACK0 and EBRs before using this testbuild. More info at:
https://rousseaux.github.io/netlabs.air-boot/pdf/AirBoot-v1.1.0-manual.pdf

File size: 4.9 KB
Line 
1===============================================================================
2 1README.TXT -- General Information about AiR-BOOT
3===============================================================================
4
5 AiR-BOOT (c) Copyright 1998-2009 M. Kiewitz
6
7 This file is part of AiR-BOOT
8
9 AiR-BOOT is free software: you can redistribute it and/or modify it under
10 the terms of the GNU General Public License as published by the Free
11 Software Foundation, either version 3 of the License, or (at your option)
12 any later version.
13
14 AiR-BOOT is distributed in the hope that it will be useful, but WITHOUT ANY
15 WARRANTY: without even the implied warranty of MERCHANTABILITY or FITNESS
16 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
17 details.
18
19 You should have received a copy of the GNU General Public License along with
20 AiR-BOOT. If not, see <http://www.gnu.org/licenses/>.
21
22
23
24Preface:
25--------
26When you are reading this file you are either browsing the AiR-BOOT sources
27or you have 'checked-them-out' from the Netlabs or GitHub repositories.
28Either way, this is what you should be aware of:
29- AiR-BOOT was originally invented and designed by Martin Kiewitz.
30- Martin seems to not develop it anymore and his last version (v1.06)
31 can be found on sourceforge.
32- *This* version is a 'fork' and although the name is the same,
33 it's sources reside on Netlabs and GitHub and another developer maintains it.
34 So, please do not bother Martin with bugs in this 'fork'.
35- This AiR-BOOT fork has been enhanced to cope with issues like 'huge disks'
36 and it's goal is to be a replacement for the ancient IBM Boot Manager.
37- With the release of ArcaOS v5, in may 2017, this AiR-BOOT 'fork'
38 is distributed with it and positioned as the 'preferred bootmanager'
39 for ArcaOS.
40- While AiR-BOOT is 'operating-system agnostinc', meaning that it is not tied
41 to any particular OS, the main effort of this 'fork' is to replace IBM-BM
42 and be highly compatible with ArcaOS.
43- The secondary goal of this 'fork' is to support even more operating-systems,
44 new 'boot-technologies' like UEFI, new partitioning schemes like GPT
45 and more.
46
47
48Note 1:
49-------
50This is the "ArcaOS Edition" of AiR-BOOT and it is maintained by a
51different developer. The file you are currently reading, 1README.TXT,
52replaces the original README.TXT as created by Martin Kiewitz.
53The latter can be found in README.MKW, but note that the information
54in there about building AiR-BOOT is completely outdated.
55Please refer to BUILD.NFO for more information about building AiR-BOOT.
56
57
58Note 2:
59-------
60Martin, at the time (1998+), found that it was important that AiR-BOOT could
61be completely built on a DOS-system. In that 'era' this was a reasonable
62requirement. With AiR-BOOT replacing IBM Boot Manager, and upcoming stuff like
63EFI and GPT, AiR-BOOT itself and it's 'build-environment' need to break out of
64the 'DOS-box'.
65
66Therefore, the 'build environment' has been 'revamped' to use Makefiles
67and the Open Watcom tool-chain in combination with the JWasm Assembler.
68This tool-chain can operate under DOS,Win32,OS/2 and Linux.
69
70While care has been taken that the major components of AiR-BOOT can still be
71built on DOS (or DOS-emulation environments),
72the preferred build-environment is now eComStation -or- Linux.
73
74If you really need to build on DOS, beware that:
75- The DOS build-environment has limitations regarding memory and filenames.
76- An ArcaOS DOS-Session needs to have DPMI set from 'auto' to 'enabled'
77 and the XMS mem-limit needs to be set to 0, to be able the use of JWasmD.
78- It has not been tested as thoroughly as the ArcaOS and Linux environments.
79- It will be dropped in the *very near* future.
80
81
82Note 3:
83-------
84An other 'operating-system' from a company that thinks it owns all computers,
85all the disks in them, all it's users, their pets, and whatnot,
86is also supported. AiR-BOOT can boot Windows and there is also a Win32 version
87of the installer. (AIRBOOTW.EXE)
88
89However, the AiR-BOOT Installer code for Win32 is much less tested than
90the ArcaOS version. This however, does not apply to the AiR-BOOT loader,
91which will do it's very best to boot any Windows it finds.
92
93
94Note 4:
95-------
96AiR-BOOT can also boot Linux, or more accurately, chainload GRUB.
97For this to work, GRUB needs to be installed on the partition Linux resides
98on, since the MBR is taken by AiR-BOOT. If GRUB is installed in the MBR it
99needs to be moved to the PBR. The procedure for such an action depends
100on the GRUB and Linux versions used.
101
102
103
104Building AiR-BOOT
105-----------------
106- Checkout the sources from http://svn.netlabs.org/air-boot.
107- Setup the Open Watcom build-environment for your OS.
108- Download JWasm for your OS.
109- Run '_build.cmd' to build AiR-BOOT for all languages.
110
111See BUILD.NFO for more information.
112
113
114
115Ben Rietbroek <rousseau.os2dev@gmx.com>,
116
117 AiR-BOOT maintainer.
Note: See TracBrowser for help on using the repository browser.