Custom Query (20 matches)
Results (1 - 3 of 20)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#9 | invalid | harddisc has not 63 sectors per track | ||
Description |
Hi, I wanted to partition an Advanced Format HDD with "geo ? 255 56" using DFSee. But if I try to install AIR-BOOT, I get the message "AiR-BOOT is unable to install. Your harddisc does not have at least 63 sectors per track". First attempt was with v 1.1.0, second with the original 1.06. So I think all versions are affected. Best regards, Axel Wein |
|||
#28 | invalid | Airboot shows a dumpfs partition as a boot choice | ||
Description |
This is an odd setup Airboot is installed on drive one and boot manager on drive 2 the dumpfs partition is on drive 2 not listed in boot manager. Airboot lists it as "Bigfat" Airboot version: Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#KIEWITZ:1.1.0#@##1## 2013/04/05 01:01:00 ecs-devbox::E:: 0::@@AiR-BOOT Boot Manager Vendor: KIEWITZ Revision: 1.01.0 Date/Time?: 2013/04/05 01:01:00 Build Machine: ecs-devbox Language Code: E File Version: 1.1 Description: AiR-BOOT Boot Manager |
|||
#1 | fixed | Licensing concerns | ||
Description |
README.TXT states that the application is distributed under GPLv3. However, the (earlier) DISCLAIM.TXT includes the following: This software may not be used in any way by US government. This means it may not be used on any US government/military computers in any case. It also means that if you are working for US government in any way, then you are not allowed to use it as well. Setting aside for a moment the closing remarks in that file, I'm wondering whether this file is still relevant, and should be removed. As an aside, I have always been bothered by the content of DISCLAIM.TXT, and this has kept me from ever using the software. Now that eCS 2.1 relies upon this is an official replacement for BM, my choices for my own installations are limited. If the restrictions in this file still apply, then I do not believe that the applicdation is in compliance with GPLv3. However, if these restrictions are to apply, then a modified GPL should be used (and I will find another application). GPLv3 should also be included in the package. |