Ah me...

I've been through iso's that won't image and cd's that won't boot - to bios changes that don't correct. Over to downloads of RAWRITE and bare.i's that won't take - to lowmem.i's that do take - (finding hope at last..) to a full load of Slackware 12.0 (going through each and every package, one shouldn't take the "newbie" route, ouch...) to THE final config and some screen concerning writing to MBR or using what I used before (opting to take the "safe route" to preserve all that wonderful partitioning and swap file set up) to at LAST (trumpets!) , this:

Intel LANDeck (R) Service Agent II, version 0.99d
Copyright (C) 1997 Intel....

DHCP MAC ADDR: 00 00 39 77 A9 OC
PXE-E53: No boot filename received from BINL, DHCP, or BOOTP
PXE-MOF: Exiting LANDesk
Operating System not found

Assuming then, that this is a Network Boot... how in hell did this happen? I never requested a network boot, honest!

Not to be undone, I fired up the floppy boots again (lowmem & root 1&2), got back into setting up LILO somehow, but now I'm getting Error #127... "attempt to install has returned an error"...

If it's any consolation, I can get to a root@slackware: prompt

Any suggestions on what to do next?

Growing tired...

did you install LILO to the mbr origanally or are you using a different bootloader?

I have always found that bit of the slackware installation a little confusing but I am not sure that the safe route is the way to go. I have always installed to the MBR

Anyway. If you can get to a root prompt what you might try is

mkdir slackware

Then mounting your slackware root partition to this directory eg.

mount /dev/sda1 /slackware

chroot slackware

Then try running lilo.

You might have to check that /etc/lilo.conf is correct

Thanks for your immediate response.

Concering "install LILO to the mbr originally or are you using a different bootloader"... I tried to install to the MBR a second time, but via the setup program, but got the same error.

On "mounting your slackware root partition"... no luck here as well.

to parse your instructions
mkdir slackware - done

Then mounting your slackware root partition to this directory eg.
mount /dev/sda1 /slackware

no luck - I'm not even quite sure I'm involking my "root partition" correctly to be begin with?... How do I know?... Sorry for what appears to be the dummest Q of all time, but this is all too new

Can't find liloconfig either.. as in "Slackware Linux comes with a menu-driven configuration utility called liloconfig. This program is first run during the setup process, but you can invoke it later by typing liloconfig at the prompt"

Why can't I access this file?

from http://www.slackbook.org/html/booting.html#BOOTING-LILO

I assumed that your root@slackware prompt was arrived at by booting from an installation disc and you are not actually able to boot your installed system.

It might be helpful to know your partition set up. Where is your root partition? What is the output of fdisk -l?

Might be useful just post the output of ls. I am trying to figure out whether, when you get to root@slackware you are actually in an installed system or in the ststem on your installation disc.

Take a look in the Slackware forum; there is a sticky at the top for installation issues

Stick with it, it is worth the extra effort

Everyone, I would like to thank you for your support.

I did an install, this time with Smart Boot Loader in the flop point to my CD-ROM that wouldn't boot initially...

Made it through everything... booted from the hard drive, and???

I'm at a Welcome to Linux 2.6.21.5-smp (tty1) and it's asking me for a

home login:

I don't have a home login?... In the final stages of the install - network, it ask me for a domain and host, I used home.com. Is it trying to log into this?

Anyway to get out of this?... it resets after 30 sec.

Did you not set up a root password during the installation. If so log in as root with that password. Then run adduser to create a user account. If you do not have a root password then you had best get yourself to the slackware forum and ask for advice.

Arubin,

Happy to report that I'm coming to you live via my new KDE desktop.

Thanks for all your help... and yes, I'm cracking the manual now...

Pmac_slack

Great!
It is worth sticking with Slackware.

Good to see that you stuck with it, most people would have given up