I've already got the grief about wanting to install winbloze, please, I don't need more.

I have SuSE 8.0 installed on hda. I've got a second HDD that is not mounted automatically.

I unplugged hda and installed windows on the second disk, hdb. I needed to unplug hda to make windows think it was installing on the primary disk.

I've found that SuSE sees windows on hdb1, fine. I've tried to use YaST2 boot loader configuration. Windows will not boot. I don't get an error, but I'm given like a CGA LILO prompt. I boot Linux.

I'm thinking that windows doesn't boot because the disk is not mounted. Course, nothing is loaded at this point. So I'm not sure of what to do.According to the SuSE website, I've done things fine. I've told LILO to look at /dev/hdb1.

Should I swap the drives. Put Linux as the secondary HDD and windbloze primary? I'd rather not.

Erik

The mounting has nothing to do with dual-booting, you can search here for dual boot related issues as well as checking out some howtos. http://www.google.com/search?hl=en&i...ux+and+windows

Here's a site I found http://eksl.cs.umass.edu/~bburns/win...ter_linux.html
Incase anyone else is interested.

So I still cannot boot windows. I even booted with a win98 boot disk, went to the windows dir to execute win.com. the system gave me a blue screen! A message about vfat not being able to find a device. At that point, the HDD was seen as C:\ eventhough it's the secondary HDD. So far, the way I see, I'll have no choice but to physically switch the cabling even time I want to boot windows.

Erik

Dude just put the windows drive in first, but setup lilo so it will know windows is on the 1st drive and linux is on 2, but try this first set winblows as default in lilo. Windows is greety & wants to be number 1.

Yeah, I know windows is a #*%&. Though, I refuse to make it number one on my computer anymore. I'll try to figure something out.

he he he, so I see. It's not a problem, really. But if you are stressing about it, and want to keep your current configuration, please post your /etc/lilo.conf file here. More than likely you will have to do the following and all will be ok:

other=/dev/hdb1
label=winbloze
table=/dev/hdb
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80

and then re run lilo as root:
/sbin/lilo -v

This should take care of your problem.

Cool

MasterC, you truly are a Master. It worked :-) Thanks man.

Master fisherman, aka ...

Nah, I just paid good attention when linuxcool was handing out lilo advice. This was one of his trademark replies.

Glad I could though