Ok
I'm trying to boot windows from LILO boot manager and I have a graphical wizard to configure LILO. I've kept the original config but I added a windows 2000 pro item to the list of boot options. When I try to boot windows 2000 pro (guess what mr gates) it doesn't work I just see a blinking cursor and that's it. Windows worked fine before I installed linux but, ... here's a list of what I have done:

1st :I only had a windows 2Kpro on /dev/hdb1 installed a few times (I had troubles installing it so I installed it a few times, resulting in a boot screen that showed 3 windows 2000 pros installed on my system with actually one real installation)
2nd: a windows XP installed next to the 2Kpro on /dev/hda1
3rd: a linux on /dev/sda1
4th: (last but not least) I erased the damn xp on /dev/hda1

And I think the boot sector of the /dev/hdb1 (or what's its name again; where the small programs like LILO are installed on) is completely messed up because it has entries that doesn't exist anymore (windows xp and 2 windows 2000pro erased installations) it said something like press a key to reboot or no boot device, while my rom bios was configured correctly and windows was still on that disk.

To summarize:

Is this a LILO problem (did I configure it well) or is this a windows problem (the boot sector)

My first boot device is my /dev/sda1 (the linux disc on SATA). When the computer looks in the boot sector (of /dev/sda1) to find boot managers, and I say boot windows located on /dev/hdb1), is it going to redirect to the boot sector of the /dev/hdb1 because if so, it's clear to me that the problem is right there.

I have mandrake 10.1 on /dev/sda1 and windows 2000pro on /hdb1


Wannes