Comment 31 for bug 476625

Ah, sorry, comment #7 is on the other bug report linked to this bug
report in launchpad.
Here is a quick link...
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/476625/comments/7
And I can confirm that using the hive method is the only way that
reliably works for me.
The reason why is in comment #4...
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/476625/comments/4

-Daniel

On Wed, Nov 10, 2010 at 6:20 PM, Jérôme De Greef
<email address hidden> wrote:
> God, as I said it was only a temporary fix and we already face a case where
> it doens't work.
>
> What's the BCD of your recovery partition ?
>
> And btw what's comment #7 ? I don't see any number identifying the comments
> here.
>
> I assume this is not easy to fix as we depend on the way recovery partition
> are named and this is up to the distributor to choose a name (Windows Setup,
> Windows Recovery, Windows Recover Initial Setup, Windows Help It's Crashed,
> whatever, you name it). Were're trying to deal with an os that as no
> standard and that's not easy.
>
> A solution would be to identify Windows 95, 200x, XP, Vista, Seven  and put
> anything else as revovery or unindentify (fat, fat32, htfs) but that will
> only work until the next version of Windows, grrrrr.
>
> --
> Grub2 affected when os-prober incorrectly identifies Windows and Recovery partitions
> https://bugs.launchpad.net/bugs/476625
> You received this bug notification because you are a direct subscriber
> of the bug.
>