Brian_lad, that didn't work.

Truoc444, I'll try it.

@Truoc- I tried the first idea, and it just gave back:

And it just sat there, doing nothing.

I tried the second thing, it gave:

When I press a key, it takes my to a text based grub bootloader.

Anything else?

i'm out of ideas. have you tried any of the other forums? maybe the suseforums

I found this on a google search

title windows 2
root (hd1,0)
makeactive
chainloader +1

It isn't your exact situation, but might be helpful.

Here is the site:
http://susefaq.sourceforge.net/faq/inst_winxp1.html

Brian

Brian, It gives me an error...

God, I don't know. Anyone else?

for Windows it should be
instead of
because (hd1,0) does not need to/can't be mounted
everything else seems ok.
I would not recommend "savedefault" - what for?

That doesn't seem to work, Jomen. If there are any more details that would help solve this problem that I can fetch, just tell me.

I forgot about this - windows is just not happy with being not on the first drive.
And it probably was'nt when it was installed.
This maps the drives so windows thinks it is on the first.

You need to make sure device.map is set up correctly. It should say:

(hd0) /dev/hdc
(hd1) /dev/sda

After you set device.map up this way, then change your menu.lst like this:

title Windows
root (hd1,0)
chainloader +1

Then it will work.

XP doesn't much care where it is booted from; I boot the NT family from all kinds of strange places. Needs to be close to the front of the drive, but doesn't have to be the first drive.

Also, when you say that something "doesn't work" or "gave an error", that is not useful. You need to be very specific in setting forth exactly what the error is.

Jim, my device.map was already set up that way, so I'll try that way soon.

Jomen, I'm off to try your solution.

Thanks you guys.

Then the syntax I showed for menu.lst should work.

root and rootnoverify should work effectively the same if the Windows installation is in front of the drive.

I may be mistaken, but I *think* you have to use map before using root or rootnoverify; it is something else to try. If, however, you find that map does solve your problem, you would do better to change your device.map, then change the hd1 and hd0 references throughout your menu.lst.

Map will only work for you if your system is using BIOS to access the swapped disks. If you have a special driver, it won't work. Probably, since you have a SCSI drive in the system, map won't work. I don't know about SATA drives; are they handled through BIOS?

Actually, this might be your problem. There has to be a SCSI driver on the Windows partition for the SCSI drive to boot. Maybe swapping device.map around is the thing to do.

I have no clue what happened, but after messing with it enough, I couldn't boot up any OS.

So I lost all my info, I just reinstalled Windows, and I'll just set up linux with no bootloader this time.

Thanks anyways!

I just can't believe that your hardware is so special that it just isn't possible...
Reinstalling Windows is overkill - just let it fix its MBR with the help of the install-cd - too late now I guess.
And for reinstalling linux (or anything...): no way you lost ANY info/data by tampering with grub.
Did you know, that you can use it even if it is so messed up that it does not schow you a menu - or a wrong one?
(pressing "c" when it comes up will do that - then enter the commands manually).
Too bad...

Once again, I'm new to linux, so I have no idea about any commands.

It's ok though, this is a brand new computer that had no information on it what-so-ever, so all it is was time consuming.

This might help you get started easier:

for basic usage of the command-line:
http://freeengineer.org/learnUNIXin10minutes.html

some documentation on how to set up grub - you will also find it here in the sticky threads on the forum...:
http://www.sorgonet.com/linux/grubrestore/
http://www.geocities.com/cyberkabila/main/grub.htm
and of course the manual and faq from the original grub-website:
http://www.gnu.org/software/grub/gru...upport.en.html