Thanks James, I'm suspicious that there may have been a recovery partition installed by the IBM XP cd, but it seems that it would show up in fstab as well as in YAST. I did install XP first on a wiped HD: it booted fine with no problems. I then ran YAST in the Suse 9.2 dist, this compressed the WinXP Fat32 partition from 37gb down to 15gb. I've tried Lilo as well with no luck. It really is a bit of a puzzle as I've been running Win2k-Linux-Shared disk configutrations on this machine (an Thinkpad T30) and others for several years with no boot problems. Thanks for your suggestions. Glenn -----Original Message----- From: James Wright [mailto:jwright@blackriverproduce.com] Sent: Tuesday, April 19, 2005 8:05 AM To: Suse List Subject: Re: [SLE] GRUB loader on Thinkpad Glenn-KPU wrote:
Using,
title windows rootnoverify(hd0,0) chainloader+1
will not boot XP. After selecting WinXP from the Grub splash screen I get,
rootnoverify (hd0,0) chainloader +1
Thanks for the suggestion.
It may be worth your while to find out for sure if your XP CD from IBM is installing an additional partition. If I were you I would at least check with fdisk. It shouldn't bother the boot process, as IBM usually sticks the recovery partition after the Windows install. I have a tri-boot IBM Thinkpad and have not had any of these problems. I am assuming XP installed without complaining? If you can start from scratch wipe the drive, install XP first, then Linux. At the time I did this is was strongly recommended that Windows gets installed first (Not just on the first partition, but before Linux). I have had not problems with grub or lilo. You may try to switch boot loaders, but I prefer grub. I am sorry I can't be more help, hopefully this provides a little insight. - James W. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com