Changeset 29 for trunk/DOCS/EN
- Timestamp:
- May 5, 2011, 2:00:00 PM (14 years ago)
- Location:
- trunk/DOCS/EN
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/DOCS/EN/FEATURES.TXT
r23 r29 25 25 º resetting the configuration º 26 26 º - MBR-Protection under Real-Mode º 27 º - Linux Kernel Support (from FAT-16 partitions), Kernel-Commandline and º 28 º automagically, but configurable root-partition º 27 º - IBM OS/2 / eCS LVM Support º 29 28 º º 30 29 ºÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĺ … … 42 41 º º 43 42 º AiR-BOOT is compatible to LVM, the Logical Volume Manager available for º 44 º OS/2 , eComStation and Linux-variants.º43 º OS/2 and eComStation. º 45 44 º º 46 45 º AiR-BOOT is able to get booted from CD-ROM. Simply generate a floppy disc, º -
trunk/DOCS/EN/INSTALL.TXT
r8 r29 7 7 º º 8 8 º 1. Get a blank, formatted disc. Insert this disc into drive A: and start º 9 º the file AIRBS_xx.EXE from the AiR-BOOT archive (where xx is your º 10 º language code). º 9 º the file MAKEDISK.COM from the AiR-BOOT archive. º 11 10 º º 12 11 º 2. Check your CMOS-Setup. Deselect 'Virus Warning', if this option is º -
trunk/DOCS/EN/Q_AND_A.TXT
r8 r29 48 48 º This had to be done JUST because of Microsoft. I can't stand this any º 49 49 º longer. There is no need for such checking. It's not documented º 50 º anywhere and the CLI is bullshit anyway, because one does not need to º 51 º disable interrupts to change stack or something. Any skilled assembly º 52 º programmer knows this. º 53 º º 54 º Q: Hey, why did you code this ? 'NT BOOT'/'OS/2 BOOTMAN'/'LILO' are great. º 55 º A: Yeah, sure. Let me say something about those things. º 56 º NT BOOT is crap. 100 KBytes for a BOOTMANAGER ? Are you nuts ? And it º 57 º definitly needs Windows NT installed. (or a FAT partition?!) º 58 º OS/2 BOOTMAN needs a primary partition, so just 3 are left. º 59 º LILO is stupid. First it can not boot Linux, if Linux resides not on º 60 º the first harddisk (at least the last time, I tried). It's loading the º 61 º Linux Kernel via HackIn, that I can't stand as well. And it's not that º 62 º easy to install and setup. It has to get adjusted, when you add new º 63 º partitions to your harddrive. etc. etc. etc. º 64 º º 65 º Most bootmanagers need a specific OS installed, so this isn't good as º 66 º well. btw.: If you add a new partition to a drive containing Linux, º 67 º LILO will not find the root partition anymore (haha, nice try). º 68 º That's your "premier" boot-manager. phew. AiR-BOOT will find it º 69 º (normally) automatically on-the-fly and boot it like normal. º 50 º anywhere and the CLI was needed on some of the earliest x86 computers º 51 º when changing stack. Anyway it's not needed in the MBR at least not º 52 º at offset 0. º 70 53 º º 71 54 º Q: Ohhh man, what do you got against LILO. It's soooo good. º … … 73 56 º partition. It was FAT and this nice little bugger overwrote some º 74 57 º internals *as documented* without even giving me any warning message. º 75 º I see LILO as on the same level as Mic keysoft products. Just believingº58 º I see LILO as on the same level as Microsoft products. Just believing º 76 59 º they would rule the whole computer and could do anything. º 77 º During AiR-BOOT alpha testing, it NEVER corrupted any partition table.º78 º The only problems were crashs, so I had to restore t he old MBR.º60 º Even all AiR-BOOT alphas never corrupted any partition table. º 61 º The only problems were crashs, so I had to restore to an older MBR. º 79 62 º During late beta testing, it never got any problems. And if there were º 80 º any, I just inserted the AiR-BOOT disc and wups, the problem was gone.º63 º any, I just inserted the AiR-BOOT disc and the problem was gone. º 81 64 º (btw: that's the way I noticed that Partition Magic 3.x overwrites º 82 º some sectors in the MBR). º 83 º º 84 º Q: So many options, no one will ever need this. Guess you wasted your time º 85 º A: Okay, well, perhaps there are too much options, and perhaps it's crap. º 86 º I believe many users will use different options, so they are good as º 87 º they are. Too much options would be, if the program is too slow or º 88 º handling is too difficult, but not in AiR-BOOT. It's tiny in size, º 89 º easy to setup...just like your BIOS. I have included REAL on-line º 90 º help, too. Not the way in most BIOSes. I included fancy things, like º 91 º color menus...look at BIOSes from 1989. They were really ugly. Colored º 92 º menus are somewhat cool. But I know, you are the one with WindowsNT, º 93 º which thinks it's the best OS in the world. You never tried OS/2, nor º 94 º Unix/Linux. You want a GUI, but you hate those silly colored-windows. º 65 º quietly some sectors in track 0). º 95 66 º º 96 67 º Q: I believe you have copied the text of your boot-menu from DocsBoot. º
Note:
See TracChangeset
for help on using the changeset viewer.