![](https://seccdn.libravatar.org/avatar/5d9661f2110f00363e99f5b309b530b9.jpg?s=120&d=mm&r=g)
I suppose you've actually had a look in the /boot partition and made sure you actually have space in it. A soft crash may dump into here and fill up the available space to the capacity of your ram if my memory serves me right. I also seem to remember it doesn't autodelete when it comes back up. just my 2 bits scsijon At 01:46 AM 4/4/02 +0200, Michael wrote:
Hi.
On Thu, 4 Apr 2002 01:18:28 +0200, Henne Vogelsang wrote:
Hi,
Warning: CHANGE AUTOMATIC assumed after "other=/dev/hda1"
Thats the problem. Lilo returns another exit code than 0 and YaST2 thinks it has failed.
boot = /dev/hda3 change-rules reset vga = 788 read-only menu-scheme = Wg:kw:Wg:Wg
[....]
The change rules reset should do it. Just copy those 2 lines into your lilo.conf and try again.
It didn't work. YaST2 STILL said "Could not write the LILO boot sector" -- and when I then reopened the /etc/lilo.conf file I found that the lines "change-rules" and "reset" had been deleted!
I have also tried editing the /etc/lilo.conf file so as to cut out the Windows part altogether. YaST2 says "Could not write the LILO boot sector" and re-inserts the edited-out lines!
What now? I am utterly puzzled.
Michael Alachouzos alacos@equitonica.org
Date (dd/mm/yyyy) = 04/04/2002
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com