But in the end, all roads lead to a new install.



-zsejk

Reading your post, one issue does come to mind. Before Linux, I had FreeBSD installed. It gave me a loader that looked like this:

F1: DOS
F2: ??? (WIndows)
F3: FreeBSD

I've since reformatted the partition that FreeBSD was on, but even after, I still had that same loader. Could this be disrupting LILO?

all you need to do is set the windows partion to active i used partition magic

FreeBSD's bootloaders do have a tendency of being a bit funky. I have installed FreeBSD using its loader, GRUB and LILO, to the MBR and not to the MBR, and each and every time I had to do a fresh install of at least Linux to get things to work again after I'd had enough of FreeBSD. I'm sure there's some workaround for this issue, but if there's nothing of importence on your Linux partition (i.e. if it's still a fresh install), I would suggest re-installing *it* including LILO to the MBR (even though it says during installation it is "Possibly unsafe"). But it's up to you of course.



Since I, however, am not really offering much of a solution beyond "Re-install!", I shall refrain from further comments.



-zsejk

You should verify which device Windows is on if you're still getting that blinking cursor. I wish I could do it for you because I'm sure the problem is something simple. I wouldn't fsck around with partition magic neither; it may pose more problems than what you already have. Have you been to Slackware's website? They have a Lilo tutorial, you should look at it if you haven't already.

EDIT: Or better yet, go to www.tldp.org (The Linux Documentation Project). They have TONS of HOWTO's in store, one of which includes a Lilo HOWTO.

from your lilo.conf:

other = /dev/hda1
label = Windows
table = /dev/hda

whats that "table" entry doing there ?

here is my lilo.conf - which works perfectly:
( /dev/hda1 = windows /dev/hda2 =linux)


------------------

Jonathan:~$ cat /etc/lilo.conf
boot=/dev/hda

map=/boot/map-bmp
install=/boot/boot-bmp.b

bitmap=/boot/ins64a.bmp
bmp-colors=14,11,,15,9,0
bmp-table=21,287p,2,4,175p
bmp-timer=73,29,12,8,0

prompt
timeout=50

image=/boot/linux-2.6.7
label=linux-2.6.7
root=/dev/hda2
append="video=aty128fb:1024x768"
read-only


image=/boot/lfskernel
label=linux-2.4.24
root=/dev/hda2
append="video=aty128fb:1024x768"
read-only


other=/dev/hda1
label=Windows-XP

--------------

Hmm, well. I somewhat got the problem fixed. I can now boot into Windows and Slackware using LILO from a floppy, which is good enough for me for now. Now I just need to resolve some KDE issues and I'll be good to go. Thanks for the help and suggestions.

Hmmm...in the end...the roads do NOT lead to a re-install. It's all about how you want/need to manage the boot options. Now...I use Linux for most things, but there are times I need Windows for work related tasks. This is really a simple solution...take a peak at THIS thread. Things are not always as complicated as they seem

Well, that all depends on whether or not you consider having to boot from a floppy the optimal solution...



-zsejk

I've got GRUB up and running so the floppy days are over :P

Good on you!!!



Care to tell us how you ended up doing it? It might help other people who have the same issue.

-zsejk

After reading this Insyte's guide I wonder why I didn't try lilo's expert setup during the slackware install. That was easy.

http://www.insyte.uni.cc/

nice guide