After a week of frustration I've finally got Suse 8.0 installed but..... Using LILO I can boot Suse but when I try to boot Windows it hangs with "Loading Windows". I've looked on the Suse web site and found a reference to that. The reference said the Lilo config was wrong and to do fdisk -l to get the right Windows boot drive. Thing is my lilo.conf was set up correctly. Hardware: MSI K7T266 Pro2 Series motherboard w/integrated Promise RAID Maxtor Ultra-133 PCI IDE card No hd's connected to mb ide 1 or 2. Two hds form RAID 1 on the mb, and two are connected to the PCI IDE controller card as master drives. The RAID drive is my Windows installation. The motherboard allows you to choose which physical hd to boot from. When I set it to boot from a hd connected to the Ultra 133 Lilo starts and I can boot linux but not windows. When I set the mb boot to the RAID, Lilo bombs out. If I take the floppy out bypassing Lilo, Windows boots ok. When I set the mb to boot RAID, Linux installs but the only way I can get it to boot is through the DVD. I installed Suse 8.0 by setting my mb to boot hda, first hd on the PCI IDE. Not knowing this I installed Windows with the mb booting from RAID. Drive C on the raid is the only primary bootable partition. Suse was installed in an extended linux partition on a hd connected to the PCI IDE card. Here's my lilo.conf file. I commented out booting from hda6 and set it to boot from floppy. I also ran lilo to update the configuration. # Modified by YaST2. Last modification on Fri Jul 5 12:38:19 2002 #boot = /dev/hda6 boot = /dev/fd0 change-rules reset read-only menu-scheme = Wg:kw:Wg:Wg lba32 prompt timeout = 80 message = /boot/message image = /boot/vmlinuz label = linux initrd = /boot/initrd root = /dev/hda6 vga = 791 image = /boot/vmlinuz.suse label = failsafe append = "ide=nodma apm=off acpi=off" initrd = /boot/initrd.suse optional root = /dev/hda6 vga = 791 other = /dev/ataraid/d0p1 label = windows image = /boot/memtest.bin label = memtest86 #end of lilo.conf fdisk -l shows /dev/ataraid/d0p1 as the boot device which is my Drive C in Windows. Device Boot Start End Blocks Id System /dev/ataraid/d0p1 * 1 128 1028128+ b Win95FAT32 But then I get some error messages I think: Device Boot Start End Blocks Id System /dev/ataraid/d0p1p1 ? 120513 235786 925929529+ 68 Unkown Then it tells me the Partition table entries are not in disk order and unable to read /dev/ataraid/d0p2 and stops. hda is the first hd on the PCI IDE controller card. hdc is the 2nd. I can mount Windows Drive C. Haven't tried any other drives. I'm under the assumption that the RAID is working on the mb and no additional modules etc need to be set up in Linux. Is this a false assumption? Any ideas would be greatly appreciated!! I dread the idea of having to change CMOS settings everytime I need to switch OSs. Thanks! Eric -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -------------------------------------------------------