[signetone]

Originally Posted by swerdna

That's one of the cases where the manufacturer puts a utility partition first up on the drive (sad1) and then the bootloader goes sometimes into sda1 and sometimes into sda2. So it might be one of two possibilities. But before I go on, what does the file menu.lst contain after you made the new bootloader as per my first post? To open the bootloader's menu file and look at it, run this command:

Windows works fine from the menu with the new bootloader.

Suse 11.1 stops at the login screen and does not go for the X window or KDE3.5
I can login to suse from safe mode and

also
linux-n2vd:~ # /boot/grub/menu.lst
-bash: /boot/grub/menu.lst: Permission denied
linux-n2vd:~ # /boot/grub/menu.lst
-bash: /boot/grub/menu.lst: Permission denied
linux-n2vd:~ # /boot/grub/menu.|st
-bash: /boot/grub/menu.: No such file or directory
-bash: st: command not found
linux-n2vd:~ #

Thanks