Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 13 of 13
Headcase, it seems that the setup to get GRUB to boot is messed up, and there seem to be more than one way of getting it to boot, but not ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Guru dylunio's Avatar
    Join Date
    Aug 2004
    Location
    Cymru
    Posts
    4,157

    Headcase, it seems that the setup to get GRUB to boot is messed up, and there seem to be more than one way of getting it to boot, but not all work on all machines.

    Try this for the Windows stanza:
    Code:
    title              Windows XP Media
    root             (hd1,0)
    savedefault
    makeactive
    chainloader   +1
    dylunio
    Registered Linux User #371543!
    Get force-get May The Source Be With You
    /dev/null
    /dev/null2

  2. #12
    Linux Newbie
    Join Date
    Sep 2005
    Posts
    140
    Quote Originally Posted by Headcase
    --> could you give me an example of how to use google for this type of problem search?
    This is from Suse 9.3
    http://www-uxsup.csx.cam.ac.uk/pub/d...t2.repair.html
    Something similar should be in your installed manual.
    If you're curious about it boot up from disk1 and play around. This probably won't help in this situation. I was only trying to explain my post in the earlier thread.

    Something isn't making sense here. The disk order your describing doesn't agree with what Suse is seeing. If Suse is actually hd0 and windows hd1 there is a trick called diskswapping where something like this would be added to the windows entry
    map (hd0) (hd1)
    map (hd1) (hd0)
    Maybe someone else knows if that should be used in this case.

    My dual boot has been Suse/Slackware for nearly a year, so the windows
    install knowledge is pretty rusty.
    WARNING: I may be telling you more than I know !

  3. #13
    Just Joined!
    Join Date
    Nov 2005
    Posts
    78

    Smile

    Quote Originally Posted by googled first
    This is from Suse 9.3
    http://www-uxsup.csx.cam.ac.uk/pub/d...t2.repair.html
    Something similar should be in your installed manual.
    If you're curious about it boot up from disk1 and play around. This probably won't help in this situation. I was only trying to explain my post in the earlier thread.

    Something isn't making sense here. The disk order your describing doesn't agree with what Suse is seeing. If Suse is actually hd0 and windows hd1 there is a trick called diskswapping where something like this would be added to the windows entry
    map (hd0) (hd1)
    map (hd1) (hd0)
    Maybe someone else knows if that should be used in this case.

    My dual boot has been Suse/Slackware for nearly a year, so the windows
    install knowledge is pretty rusty.

    Hello and Thanks to everyone that has pointed me in the general directions.

    The map command was the ticket for this machine anyhow.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •