Re: recovering win7

[Jake Thomas]

> Message: 1
> Date: Sun, 13 Jan 2013 11:03:29 -0700
> From: Chris Murphy <address@hidden>
> To: Jake Thomas <address@hidden>
> Cc: "address@hidden" <address@hidden>,
>   "address@hidden" <address@hidden>
> Subject: Re: Help-grub Digest, Vol 60, Issue 16
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> On Jan 13, 2013, at 1:51 AM, Jake Thomas <address@hidden> wrote:
> 
>> If it loads bootmgr (after re-installing Grub so that its mod files, 
>> grub.cfg, etc. are on the NTFS partition), no Microsoft boot code will need 
>> to be restored.
>> 
>> That alone would do. Bootmgr is a file on the NTFS partition, and will not 
>> need to be squeezed into any 440 byte region. Grub's ntldr should be able to 
>> load bootmgr, even though it is a file.
> 
> That is *vastly* more complicated. He's already blown away all prior 
> partitions, and restored Windows. Yet he can't boot Windows because of this 
> 440 bytes of grub remnant. By removing just those 440 bytes, his problem 
> should be fixed. He can't re-install grub. He can install a fresh grub, but 
> he'd need a Windows binary to do that.

Actually, the OP said he has Ubuntu Live CDs. Should be able to re-install Grub 
from there, but, again, if using "--boot-directory" is too advanced for the 
average user, this would be too advanced.

Personally, I keep an external hard drive and thumb drives bootable into Linux 
for such things.

> Grub2 doesn't install itself like old grub did.
> 
> Chris

Jake