• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help: SuSE boots up fine but XP will not boot from bootmanager!

VisceralMonkey

Junior Member
I installed SuSE 8.0 and it runs fine, but when I try to load up XP from the boot manager, it stalls out and will not load. I know for a fact that my win XP is still there and all, I just cannot boot it up. I have a feeling the problem is with the boot manager and need a work around it. Hell, If I need to wipe out the SuSE boot manager I'll do it. Can anyone advise me on how I can boot up XP??

 
It's a known bug in SuSE 8.0. The LILO boot definition for Windows is wrong. Change it from /dev/hdb1 to /dev/hda1 and rewrite the LILO MBR. Let me know if you need more details (the official document of this problem is in the SDB).
 
Manly, thanks for the info. Actually, I could use more details, I'm a novice with linux so a quick step-by-step if its not too much trouble would be great!
 
Okay, boot into SuSE and as the root user, edit the /etc/lilo.conf file using any text editor. I'm assuming a *typical* setup where the boot loader is written to the MBR (most common case). The first line of the file should be:

boot = /dev/hda

The wrong line should be changed from
other = /dev/hdb1
to
other = /dev/hda1

That's it. Now, save the file and exit the editor. At the shell prompt, type the command lilo. That command reads from the config file you just edited, and recreates the proper boot loader. You're done. You can check out SuSE's document on this issue from their SuSE 8.0 known problems page.
 
Thank you!

Actually, my problem was a little bit different but your advice still got me to the solution. For whatever reason, my xp was another volume like hda2, and it was pointing to hda1. So I just switched it over and it works fine! Plus I learned some more stuff about Linux. Thanks again!
 
Back
Top