Hello All, I had a perfectly fine running 2.4.4-4G 7.2 personal system with KDE2.2pre1 installed. I upgraded a test box just like it to 2.4.7-4G w/k_deflt-2.4.7 from the suse site. I was careful to backup vmlinuz and initrd PRIOR to running rpm from the command line, followed by mk_initrd, then lilo. No problems, no glitches. Then I went to my main desktop and got through all of the steps until I tried to run lilo. I kept getting 'error /boot is a directory'. the whole partition is reiserfs and shares the drive with other linux distros and is booted from one of the other partitions by chainloader. I rebooted, without thinking and without being able to run lilo and now the box hangs with this message.... 'Loading Linux.....EBDA too big' and I cannot get into the partition to 'put things back". I have a copy of LinuxCare ER disk, but I am not sure how to use it. How can I get back to baseline or at least get to a command prompt to rerun lilo? Please, this is my production box and I need to get it back. Yes I could use the other distros, but I want my SuSE back - it was upgraded with all the lastest, except the kernel and this blew things. I did not use a pristine source, because the rpm went so smoothly on the test box with the EXACT same setup. Regards, Keith B.