Custom Query (20 matches)

AirBoot? unable to show up when a USB harddisk (500gb) with more than one logical partition is attached at power up. Furthermore, if the disk has more than one logical partition, these partitions are destroyed after such an attempt to boot.

I have three usb harddisks at 500gb, set up with one, two, and three logical partitions respectively. When I power up my new machinery with one of those harddisks containing more than one logical partition attached right from the outset, the booting process stops before AirBoot? shows up, displaying the message: "Too many partitions found, AIR-BOOT is supporting up to 45". However, my system contains only 14 partitions, so there is a long way to the 45. The booting process is halted at this point, and the machinery must be turned off and restarted without the usb-harddisk attached. When looking afterwards at the external usb-harddisk in DFSee, the partitions that are following the first logical partition on the disk, have vanished and have been turned into 'bad sectors'.

When the single partitioned HD is attached at boot-up, or when a harddisk that is partitioned into a primary and only one logical partition, is attached in the same way from the very first power-up, the booting process goes smoothly and the usb-disk is left unharmed. When any of the disks is attached during the booting process - at some point after the appearance of AirBoot? - there is no halting of the process, and no harm done to the partitions.

When virus checking is enabled and the drive-letter feature is used, AiR-BOOT v1.0.8-rc3 mistakenly thinks a virus is active in the PBR.

Solution:

• Hold down the shift key when AiR-BOOT is about to start
  This will cause it to enter SETUP right away
• Disable the virus checking

This will be fixed in the next RC.

Situation: Multiple OS/2 installations on same drive-letter. One of them is a PRI partition. Without stick inserted the drive-letters display OK. With stick inserted, bogus drive-letter displayed or wrong LVM-hidden status. Looks like something goes wrong with getting info from Master LVM-record.