Gecko/20110414 Thunderbird/3.1.10
eta,comp.os.os2.setup.storage
UTC)
p.os.os2.misc:3344 comp.os.os2.beta:176 comp.os.os2.setup.storage:403
From: Jonathan de Boyne Pollard
> Notes: For now, the volume must be formatted using the FAT
> filesystem. This is a temporary limitation. As far as firmware is
> concerned, I've tested this on machines with Phoenix-Award and AMIBIOS
> firmwares and it works as designed. Dave Yeo is currently having
> trouble with another machine. If you experience an FE01 error, which
> is a firmware "invalid parameters" error, you're in the same boat as
> M. Yeo. We're currently investigating what is going on with M. Yeo's
> firmware. You'll find that the Boot Manager has spat out a load of
> stuff at you. Let me know the details via electronic mail.
>
> Another thing that M. Yeo has is discs partitioned with IBM's LVM.
> Boot Manager should pull out the partition names from the LVM metadata
> and display them. But as noted in a previous message I've added in
> the IBM LVM partition table support blind, and, in the absence of
> documentation as to the exact algorithm for locating the IBM LVM
> metadata this might require some tweaking to cover all possibilities,
> which of course I cannot do here without something to test against.
>
The world is nipping at M. Yeo's heels. Someone else has just tested
Boot Manager against a disc with the LVM metadata on it, and we've done
the tweaking to locate the partition names properly. (Although coded
blind, there wasn't much to do, apart from fix a wrongly sized field
declaration in a data structure.) I've been sent a screenshot of Boot
Manager correctly displaying the LVM partition names. There were no
FE01 problems, so thus far M. Yeo is still alone in that particular
boat. (-:
--- Internet Rex 2.31
* Origin: virginmedia.com (1:261/20.999)
|
