On 2014-05-03 18:26 (GMT-0400) James Knott composed:
Felix Miata wrote:
I have attached the MBR from both old & new drives.
They kdiff3 entirely identical until the partition table. There is a table difference that could possibly matter to W7's bootloader. The old HD's extended type is the standard 0x05, while the new is M$'s abortive 0x0f. Try changing the new to 0x05.
Actually, that's backwards, at least according to fdisk. I don't know
Dyslexia at work again on my end. :-p
why the old one is 0x0f, unless I might have created it with Windows and not Linux. The current extended partition was created by GParted. Regardless, Windows is on a primary partition (sda2) and not in the extended. Will changing that damage the contents of the extended partition?
Changing the extended ID changes nothing anywhere on the HD except that very byte. What else it can change is how Windows reacts to the partitions it finds on the HD. The extended ID could be one factor in its anti-piracy/must reactivate formula. So, because the ID on the new does not match that on the old, change the new to match the old to see if it helps. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org