Did read the release note and tried to find the setting of “do not check Write Generic Boot Code to MBR” But didn’t find it.
Now I can still boot into preexisting vista, and upon power up pressing blue ThinkVantage will still do, but will not being about to get into thinkpad service partition.
Message:
rootnoverify (hd0,0)
chainloader +1
BOOTMGR is missing
Press Ctrl+Alt+Del to restart
Not urgent, but will be good to have a clear solution.
Thanks,
If you don’t have a proper Vista DVD, you can get a repair disc here:
Windows Vista Recovery Disc Download — The NeoSmart Files
Although I have a ThinkPad, I don’t have this issue. So I can’t offer more advice really. Except perhaps to say, if it were me I would give the Laptop a right good hacking and try all options, just to see what I could do - BUT I have the advantage of having a Full Vista DVD.
If you repair the MBR and can boot back to Vista, perhaps give this a go to manage booting to Linux
Download EasyBCD 1.7.2 - NeoSmart Technologies
caf, and if that doesn’s work, replace “hacking” with “kicking” Always works for me lol!
Actually pretty sure the later TP’s had a different setup for the recovery partition and the way it’s invoked from the Access IBM button. Your R61 will be different from legendbb’s T40. I’ll look out a link that gives a good explanation of how it sets up and how to restore the functionality.
@legendbb, bit late in the day to be telling you this but the changes to GRUB config need to be made by editing the proposed config setup during install - it’s not a default option to change it, you actually have to intervene and choose to edit - I only know this because I have a somewhat exotic multi-boot setup on both my TPs and need to make sure the existing MBR and GRUB aren’t changed with new installs.
IG
Not the thread i was thinking of, but this one also gives a link to a method of repairing the MBR to enable you to get back to your service/recovery partition. It actually refers to the problem following a secondary install of Win7 to a Vista machine.
If I remember right, the problem was/is that the only IBM tool to fix a “broken” MBR was a 3.5" floppy boot/repair disk
I assume the outcome will be a machine you can boot to Vista or can get to your IBM R&R…but not to Suse, so you’d probably need to carefully re-install Suse, paying particular attention to GRUB config.
I don’t bother to keep the R&R partitions on my machines or I’d just tell you how they were set up !
Meanwhile I’ll keep searching for the good explanation !
IG
You might want to ignore my previous post.
This is the topic I was thinking of…and makes much more sense.
IG