Hello all. I recently installed a Slackware 10.2 onto a 9 gig partion of my 40 gig hd. I have XP installed on hda1 and slackware on hda2, with a 400 or so mb swap as hda5. I installed LiLo as the boot loader and it detected that I had XP installed already on hda1. All seemed to be going well until I tried to go into windows (Slack boots ok, has a few keyboard and video issues, but they don't effect the overall system once booted). The label is "NT" and all it does print "Loading NT..." and hangs. I have tried tinkering with my lilo.conf, but I'm not that great at Linux yet. Trying to learn. Here is my lilo.conf:

boot=/dev/hda
lba32
prompt
timeout=50
root=/dev/hda2

image="/boot/vmlinuz"
label="vmlinuz"
root="/dev/hda2"
read-only

image="/boot/vmlinuz-ide-2.4.31"
label="2.4.31"
root="/dev/hda2"
read-only

image="/usr/src/linux/arch/i386/boot/bzImage"
label="Linux_Compiled"
root="/dev/hda2"
read-only
optional

other=/dev/hda1
label="NT"

image="/dev/hda1"
root="/dev/hda1"

Anything I change (Like the image, ect) results in an "Unusable config file" message. This has been driving me nuts. I'd even just like to boot into winblows one last time to backup a few files (Yes, I forgot to backup. Nasty habbit, that). If more info is needed, I would be happy to comply.

Sorry if this question has been asked before. I tried searching the forums for someone with a similar problem, but most entries were about GRUB. I don't normally ask for help like this, as I prefer to finger it out on my own, but this is driving me MAD!!

Hi, and welcome to LQ!

It's been quite a while that I last saw a windows
dual-boot set-up :}, but I think that root and image
are reserved for linux installations. Try removing
image="/dev/hda1"
root="/dev/hda1"
and run lilo again, and then see what happens.


Cheers,
Tink

Technically, you mean "dual" as a duel is kinda like a fight..

Well, I tried that and the same thing happens. Just hangs there with:
"Boot NT"
"Booting NT"

Thanks for the suggestion though!

Hey there The_Rogue,

try these changes and run lilo again - it should report no errors once lilo updated the changes and you should be able to boot up your Windows XP again - good luck and let me know if it worked :P

You can also try 'liloconfig' as root and do the "expert" setup instead of simple install. Don't let the expert thing daunt you, it's not that hard. Just follow the prompts. ALso, make sure you have lilo installed on the MBR.

regards,
...drkstr