🚀 go-pugleaf

In article <7femn3$2jk$1@nornet2.nor.com.au>, "Dave Chapman"
<chappo@nor.com.au> wrote:

>Hi dagger

Hello. :)

>I've seen this before ... but ...memory parity error :))
>
>Could be damaged boot record - I assume you don't have any DOS/FAT
>partitions from your description - get Linux up and redo your LILO
>installation with linuxconf (at the command line)

No dos/fat partition, I have reinstalled lilo (did lilo -v) checked the
config, tried to boot off a lilo boot floppy (created by the linux during
install), but i got a LI 10 10 10 10 10, and so on on boot.

>If that fails, it could be that you don't have an active partition, or maybe
>you only have an extended partition without any primary partition which
>would probably be an invalid configuration. With fdisk, you should be able
>to activate your partition, but if you only have an extended partition, you
>might have to reinstall from scratch using a primary partition instead.

Can you expand on this a little more please? I'm unfamilar with fdisk, any
directions on how to check and do so would be much appreciated

>One other possibility is that your hard disk has got more than 1023
>cylinders even though its not that big - some early drives only have two
>heads and over 1023 cyls - check in your C-MOS settings - if the drive is
>using LBA, you may have that problem. (not that likely though)

No, it only has 583 cylinders. I can't find a CMOS setting for lba....

Thanks in advance, :)

-- 
dagger
<mailto:dagger@bayside.net>
(Too much blood in my caffeine system...)