I've read the other L 99 99 99 threads in this forum (actually, almost everything in google -- some are not in English) and tried to do what was written there but nothing seems to solve the problem.

I'm already using loadlin, and could go and use grub (hopefully) or another boot manager but I really want to get loadlin to work because I can integrate it with Windows XP's (-- make that NT's) boot manager.

I've done
1) using lba32 (can't use linear but have tried that too)
2) restoring old mbr (/boot/boot.300 --> /dev/hda)
3) redoing the steps from the start, following the instructions found in www.slackware.com/book (at Dual-Booting section)
4) setting my drive as CHS and Large, and checking. Now back to LBA.

-- I'm using Slackware 9.0

-- I posted this on the lilo site but you guys might know about this so I decided to post here too--

I'm having problems having LILO work. Basically, what I'm trying to do is load Slackware 9.0 using Windows NT's boot.ini

I've configured the boot.ini ok, and when I select Slackware from the choices, it'll go into LILO, but the L 99 99 99 ... DISK BOOT FAILURE INSERT.... shows up.

I have searched about this in google, tried out the solutions, including the one here, and having exhausted my options decided to also ask about it here.

My Linux installation resides at /dev/hda6 while my boot.ini file resides at /dev/hdc1

Anyway, here are the things you might want:

fdisk -l dev/hda
Device Boot Start End Blocks Id System
/dev/hda1 1 701 5630751 7 HPFS/NTFS
/dev/hda2 702 4997 34507620 f Win95 Ext'd (LBA)
/dev/hda5 702 1402 5630751 7 HPFS/NTFS
/dev/hda6 * 1403 1914 4112608+ 83 LInux
/dev/hda7 1915 2045 1052226 82 Linux Swap
/dev/hda8 2423 4997 20683656 b Win95 FAT32

fdisk -l dev/hdc
/dev/hdc1 * 1 702 5638783+ b Win95 FAT32
/dev/hdc2 703 4865 33439297+ f Win95 Ext'd (LBA)
/dev/hdc5 703 1212 4096543+ b Win95 FAT32
... (I don't think the rest are necessary)

lilo
Added SlackwareLinux*

/etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda6
#compact # faster, but won't work on all systems.
#prompt
#timeout = 5
# Normal VGA console
vga = normal
lba32
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/hda6
label = SlackwareLinux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends


/etc/lilo.conf (without most of the comments)
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda6
vga = normal
lba32
image = /vmlinuz
root = /dev/hda6
label = SlackwareLinux
read-only

I've followed exactly what is written in http://www.slackware.com/book/index....rce=x1776.html
with regards to dual-booting
the dd ~~~, copying the bootsect.lnx, and editing boot.ini

Please help, thanks.

i am only a newb, but i had a similar problem. are you installing LILO on the MBR of the drive it is on? I kept choosing to install it on the first sector of the boot partition, but actually if u have more than one drive it needs to be installed on the MBR of whatever drive it is on.

Some info about my computer
- -
Windows XP resides in hda1
Windows XP's bootloader resides in hdc (yup c)

Basically, in my BIOS, my boot sequence starts with D:

I reformated just now, Linux now resides on hda3 and it's a primary, bootable partition

---

I've done both.

If I setup lilo to the mbr (of dev/hda), and my boot sequence starts with C: in the BIOS, I can boot up Linux no problem but I won't be booting up Windows XP's boot manager.

If I setup lilo to the superblock and my boot sequence starts with C:, I think nothing worked (forgot).

If I setup lilo to the mbr (of dev/hda), and my boot sequence starts with D: in the BIOS, I can boot Windows XP's boot manager but if I try setting everything up (bootsect.lnx, etc.), I'd get the L 99 99 99 ...

I haven't set up lilo on the mbr of dev/hdc, but I'm thinking that if I do that, I'll lose Windows XP's boot manager, which is what I'm trying to preserve.


Can you elaborate on how you fixed yours? Thanks.

sure, i had windows xp on hard drive a, then i bought a new drive, hard drive b to install linux. i then chose to install GRUB on the MBR of hard drive b. when my computer loads, i get a GRUB screen, from that i am able to select either redhat or xp. XP loads via the chainloader. that enuf?

Last thing, is your XP NTFS?