LinuxQuestions.org - Lilo error

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Lilo error (https://www.linuxquestions.org/questions/slackware-14/lilo-error-573654/)

Hi there,
I've seen some posts on this mater, but none was my problem. Here it goes:

As said by others, LILO doesn't install properly when I install Slack12 on my new lappy. I've tried to removepkg lilo22.8 and installed lilo22.7 and the problem persisted.
I've switched my lilo.conf file by my previous lilo.conf file from slack 11 and it goes like this:

Quote:

#
# Start LILO global section
#

boot = /dev/sda
append="splash=verbose"

map=/boot/map
#bitmap=/boot/hgg.bmp
#bmp-colors = 4,,6,9,,14
#bmp-table = 42p,370p,1,2

prompt
timeout=60
#bmp-timer = 555p,180p,12,,15

#
# Setting definitions for VGA
#

# Normal VGA console
vga = 791
#
# End LILO global section
#

#
# Linux bootable partition config begins
#
image = /boot/vmlinuz
root = /dev/sda4
label = Slackware
read-only

#
# Linux bootable partition config ends
#

#
# Windows bootable partition config begins
#

other = /dev/sda2
label = Vista
table = /dev/sda
#
# Windows bootable partition config ends
#

With this lilo it adds slackware (an improvement from the conf file lilo22.8 generates) but it crashes on window$ add:

Quote:

LILO version 22.7.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2005 John Coffman
Released 17-Sep-2005 and compiled at 00:33:53 on Aug 8 2006.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Using MENU secondary loader
Calling map_insert_data

Boot image: /boot/vmlinuz -> vmlinuz-huge-smp-2.6.21.5-smp
Added Slackware *

Boot other: /dev/sda2, on /dev/sda, loader CHAIN
Device 0x0800: Inconsistent partition table, 2nd entry
CHS address in PT: 1023:137:12 --> LBA (16443137)
LBA address in PT: 10242064 --> CHS (637:137:29)
Fatal: Either FIX-TABLE or IGNORE-TABLE must be specified
If not sure, first try IGNORE-TABLE (-P ignore)

Here's my partition table:

Quote:

Partition Table for /dev/sda

First Last
# Type Sector Sector Offset Length Filesystem Type (ID) Flag
-- ------- ----------- ----------- ------ ----------- -------------------- ----
None 0 2047* 0# 2048*Unusable None
1 Primary 2048* 10242047* 0 10240000*Hidden W95 FAT3 (1C) None
None 10242048* 10242063* 0 16*Unusable None
2 Primary 10242064* 95135543 0 84893480*HPFS/NTFS (07) Boot
3 Primary 95135544 234441575 0 139306032 W95 Ext'd (LBA) (0F) None
5 Logical 95135544 99431207 12 4295664 Linux swap (82) None
4 Primary 99431208 171531791 0 72100584 Linux (83) None
6 Logical 171531792 202989167 12 31457376 W95 FAT32 (0B) None
7 Logical 202989168 234441575 12 31452408 W95 FAT32 (0B) None

It seems laptops these days come with an extra primary partition that is meant to be used as a rescue disk.... so I had to play around with the partitions :|

any solutions for my problem?
cheers in advance
**Cat**

I've used the

Quote:

lilo -P ignore

option, but I am not quite sure it's .... safe... :scratch:

i have experience with these. a friend and i once destroyed another friend's windows installation with these. ;)

maybe you can chainload linux with windows' mbr,but if you already run lilo, you'll first have to restore the mbr...

alternatively you could try grub. (in extra/ )

Quote:

option, but I am not quite sure it's .... safe...

me neither. try it..

I read that the Windows loader demands to be in charge ;) so running LILO doesn't really work with Windows NT of any kind. I've never tried to dual-boot with Windows, so I wouldn't know...

Joel

Quote:

Originally Posted by trashbird1240

I read that the Windows loader demands to be in charge ;) so running LILO doesn't really work with Windows NT of any kind. I've never tried to dual-boot with Windows, so I wouldn't know...

Joel

Hi,

The OP is using a Vista install. As long as the windows is installed first then the linux. It will be safe to write the bootloader to the 'MBR'. I've written several with no problems.

BTW, would you share the link or where you read that;

Quote:

I read that the Windows loader demands to be in charge ;) so running LILO doesn't really work with Windows NT of any kind.

Too paint with a broad brush you tend to cover up everything. Yes, to use the older Windows NT bootloader requires a little more work but it can easily be done.

But to use Windows XP or Vista is not that difficult. Just make certain that you load the Windows OS first then load your Linux OS. You can use lilo or grub.

Either will work. My preference is lilo because I've used it for years and it meets my needs.

Quote:

Originally Posted by onebuck

Hi,
BTW, would you share the link or where you read that;

Yeah, I read it in an older edition of Running Linux. Thankfully for the OP, it's out-of-date. Sorry for the misinformation, I know it distracts from taking the high road for Linux ;)

Joel

I assume the hidden FAT partition is the backup partition for windows, but what are the two "unusable" partitions before and after it?

For dual boot Linux + vista, please read http://apcmag.com/5046/how_to_dual_b...nstalled_first.

if you are trying to dual boot windows and slack i recommend Bootpart and the windows NT loader.Bootpart a simple DOS based program. To use it install Lilo to the superblock of your linux partition, restart into windows, and run bootpart, it will give you a .BIN file which you put in a folder and add its location to the boot.ini file in windows.
heres the link for the Bootpart File
http://www.winimage.com/bootpart.htm