Hmm... well, the original error was using the Slackware setup process. When I boot (using sata.i root=/dev/hda2 noinitrd ro after DVD startup) login as root, I can get access to the lilo.conf file, which is different from the one given in the initial setup. lilo -v gives:
LILO version 22.7.1, Copyright (C) 1992-1998...
Released 17-Sep-2005 and compiled at 00:33:53 on Aug 8 2006.
Reading boot sector from /dev/hda2
using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz
added slackware *
edit: sorry, forgot some stuff:
boot other: /dev/hda1, on /dev/hda, loader CHAIN
Device 0x0300: inconsistent partition table, first entry
CHS address in PT: 1023:137:12 --> LBA (16443137)
LBA address in PT: 10242048 --> CHS (637:137:13)
Fatal: either FIX_TABLE or IGNORE_TABLE must be specified
If not sure, first try IGNORE_TABLE (-P ignore)
And here's the new lilo.conf file:
Code:
# Start LILO global section
lba32 #allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda2
#compact # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @1024x768x256
vga = 773
(more console stuff here)
# ramdisk = 0 #paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Vista
table = /dev/hda
#Windows bootable partition config ends