hi
i TOO have the L 01 01 01... problem. in most other threads, everyone is asked to paste their lilo.conf file. so here it is (clipped):

# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
delay = 300
# VESA framebuffer console @ 800x600x64k
vga = 788
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = windows
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdd6
label = linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

hda is a 20 GB. hdd is an 80 GB disk. hdd1 is a 32 GB vfat, hhd2 is 37 GB NTFS. the rest are linux and one linux swap. hdd6 has the required linux install.

would this be the same 1024+ cylinders issue? i thought the bios that comes with a via kt 133 motherboard would be recent enough to handle that.

btw, does the addressing mode have to be set to LBA in bios? neccessarily? for both disks?

ty
abs

Where is your lilo stored? If it is stored anywhere but the MBR please reinstall lilo so that lilo is in the MBR. That should solve your problem.

Looks like LILO is already in the MBR, since boot=/dev/hda.

According to the lilo man page, 01 means "invalid disk command" (really helpful eh?) The only line of your lilo.conf that looks odd to me is the table=/dev/hda part; I've never needed it, so you may be able to remove it. It might be causing the error (I'm not sure where Windows keeps its partition table, though /dev/hda sounds like a likely candidate).

I've no clue what effect LBA has. I have two machines with 80GB drives and I've never had to make any adjustments to the BIOS or anything, but then again maybe I just have good BIOS

yes, it is already in the MBR. also, that's the file that the slackware setup generated when i choose expert mode since there were 2 different OSes to load (soon 3). i'll try it after removing the table line. just for info, i used to boot linux normally using the setup cd and typing something like:
boot: linux root=/dev/hdd6 (that's what i did this time)
so does that confirm that the bios can handle large disks without any issues?

btw, when i do something like: # lilo -u -s /boot/boot.0300
it uninstalls lilo and restores my orginal mbr. (did this to recover from above error). so now, does boot.0300 still contain my original MBR data or does it have the lilo stuff. i.e. is it a swap or just a restore? (anyways, backed it up before this step)

i don't remember seeing the error messages thing in the lilo man page, maybe i'll go look again (at online man pages) :P

does the setting/entry need to be different if it's winxp?

i've noticed that alot of ppl who've posted their lilo.conf's HAVE the table= line. any other ideas? are there any diffs for a winxp partition?

No idea if it's different for XP; I haven't installed anything newer than 98SE

I'm afraid that's about the limit of what I know... maybe someone else can give some clues.

k, thanks though.

btw, the file boot.0300 will always have my mbr right? does it get the lilo mbr when i do: lilo -u -s /boot/boot.0300 ?

will continue to boot off cd. maybe i'll try grub, though i don't see how that'd work out.

i installed lilo to the mbr after compiling a new kernel. this time i used the normal vga console. worked fine.

is there a place where i can find the various lilo errors are 01 01 01 , 42 42 42 etc. :P