After switching over to the LILO (v. 22.1) that comes with SuSE 8.0, I found that I could no longer boot Windows 98. I get the Win startup screen but it hangs after a few seconds with the startup screen still displayed. As it happens, there's an item in the SuSE support database on this very problem -- but the solution given there doesn't work for me. To quote the essential part of the database article: <begin quote> Symptom After having installed SuSE Linux 8.0, your Windows operating system does not boot with the boot manager LILO. Your Linux system, however, boots correctly. Linux and Windows are located on different hard disks. Cause The cause is an incorrect entry in LILO's configuration file. Solution Change LILO's configuration manually. First, open a shell as root by performing the following steps: Press the key combination ALT+F2 in KDE. Enter "xterm" in the entry field. Click on "Run". Enter the command "su -" in the displayed window. Enter your root password at the prompt. Execute fdisk -l to obtain an overview of how your system is partitioned. The output may be similar to: Disk /dev/hda: 64 heads, 63 sectors, 1023 cylinders Units = cylinders of 4032 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 1023 2062336+ 6 FAT16 Disk /dev/hdb: 255 heads, 63 sectors, 1655 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 2 16033+ 83 Linux /dev/hdb2 3 19 136552+ 82 Linux swap /dev/hdb3 20 1655 13141170 83 Linux In this example, Windows resides on the first partition of the first hard disk, referred to as /dev/hda1. <omitted stuff for Yast here> If you prefer to edit LILO's configuration file manually, proceed as follows: Open the file /etc/lilo.conf with a text editor of your choice. Search for the boot entry for Windows. It might be something like: other = /dev/hdb1 label = windows Change the device entry. According to our example, it would be: other = /dev/hda1 label = windows Save the changes and exit the editor (key combination CTRL-X in pico). Now execute the command lilo in the shell to update the boot manager with the new settings. Restart your computer. Booting Windows should no longer pose a problem. <end quote> In this example, Windows is on the first drive and Linux is on the second drive. But in my case, it's the other way around: Windows is on the second drive, Linux on the first drive. The relevant section of my lilo.conf file is: other = /dev/hde3 label = "Windows 98" Since I get the Windows bootup screen, I clearly have the partition information right. I also have a DOS partition on the second drive, with a similar section in lilo.conf; that one behaves similarly, displaying a couple of startup lines and then hanging. Is this a known problem? Is there a known solution? Paul