The laptop just does nothing on the boot. It doesn't say "no image found" or anything. If that's how it loads up, with my computer doing nothing and that stupid ass blinker just sitting around fine. But I've been working on the damn install since at least 4PM.

Specs? The laptop is OLD I don't know the specs, but I don't see how this is a issue. I just followed an FAQ and made a main partion(most of drive) and a swap(128). It's got 32mb of ram a 233 pentium and a 40gb harddrive.

If the first run takes forever. Or if there is some way I can fix it with a boot disk. I'd like to know. Try to keep in mind I'm totally new to linux.

Latest version of slackware, regular install, bootdisk seems to be a piece of crap. It wanted a 1.68 disk to begin with.

Welcome to LQ!

You need an attitude adjustment. Between your Slackware post and your Mandrivia posts you've already demonstrated nothing more than a spoiled brat, make it work for me attitude. This won't get you anywhere but on the ignore list of knowledgable Slackers.

If you're ready to proceed, take a deep breath and read!
http://slackbook.org/html/
http://slackbook.org/html/installati...OFTWARE-SERIES
http://www.catb.org/~esr/faqs/smart-questions.html

To run the latest version of Slackware with a GUI like KDE is going to require a PC with similar specs to Windows XP's requirements. Alright, that may be overstating it a bit... But unless you just want access to the command line, don't expect a lot from those specs.

As far as the problems you're having goes... Did you get any errors when installing the software or when installing the boot loader? The fact that it does nothing suggests to me that your boot loader didn't install.

Yeah. I made a partion, put an OS on it, and that partion was set to bootable. It won't boot though. Obviously, I am asking for something to help me make it work.

Nope. There were no errors. Is there anyway I can attempt to install that bootloader? I would expect the regular error my BIOs gives me when it finds nothing to boot up with.

It's all in your ability to read. Some guys may post stuff to you that is already in the links I gave you to read. I'm not one of them...

Yeah, I read the bleeding garbage and figured out how to reconfig my bootloader from the command line that my install CDROM gave me. Which is totally thanks to the other guy.

Why are you pulling an attitude with members of a forum that give up their time to help others? Don't give grief due to your ignorance of Linux procedures. It's not the install's fault; it's your lack of knowledge about it.

Either chinaman has been irked since my first post here. Or he just searched up an old post because he knew this post alone wasn't enough to bitch about. I'm not pulling an attitude with the guy who actually gave up time to help me, but rather the guy who gave me the auto-reply.

Jbernoski:
Installing a bootloader at the head of a partition doesn't do any good unless there's a bootloader on the MBR of the hard drive that points to it.

What probably happened is that you, the user, chose the default option of installing lilo (the LInux LOader, a bootloader) on your root partition, instead of on your hard drive's MBR. So when your laptop boots up, your BIOS (Basic Input/Output System) searches for a bootable drive (MBR on your hard drive), doesn't find it, and blinks away at you (which seems to be aggravating you).

What you need to do is boot from the slackware rescue CD (disk 2), and install lilo on the MBR (Master Boot Record) of the hard drive. This involves booting from the rescue cd, creating a mount point, mounting your root partition on that mount point, editing your lilo.conf file, and rerunning lilo with the appropirate options to reinstall lilo at the MBR.

It would look something like the following:
If your root partition is not hda1, then adjust accordingly.
You'll want your lilo.conf to have the following entry:
boot = /dev/hda (NOT /dev/hda1)

If you need more detailed instructions they can be provided. However, it's still unclear as to whether your problem is solved or not - More of your attention is going to people's opinion about your attitude than to your actual problem. What I'm saying is for you to post an update on the current status of your problem.

BTW: As far as people responding to your attitude and not your problem. That is because of comments such as:
and
You need to realize that you, as a totally new user to linux, are making harsh criticisms towards linux, particularly slackware linux, which is the favorite linux distro of most users on this forum. What else did you expect?

Thanks. However, I'm now knee deep in dcop and GUIs.
I meant the floppy bootdisk, and the normal blinking cursor(you know the blinking _). I realize that goofy anger toward storage media and digital objects seems very harsh to you, and I apologize.

I like slackware as it's the first distro to actually RUN the installer, furthermore to install on this machine.

I understood the first time.

You know, a lot can be learned by what I posted above. Instead to insist on focusing on the negative and shoveling your ____ here. With that attitude you won't learn very much about linux.

I'll just quote what I previously posted, since you must not have seen it:
So. . .what's the status? Believe it or not I'm actually trying to help you out.

Compared to Windows, Linux requires more RAM and less CPU. If you can't update that RAM to more than 128MB, you won't be able to run a desktop environment such as KDE. You can use a window manager, such as Fluxbox. Perhaps ICEWM might work also, ymmv.

It's going to be slow loading anything GUI with only 32MB RAM. My 5-year old daughter has an old Compaq laptop which now has 96MB RAM after I upgraded it. She's been running it for over a year (using Fluxbox) and it runs Firefox and Thunderbird reasonably well. They load slowly, but then work fine. The only editor we really tried was Abiword, which was okay, but not fast.

Sorry for not being clear. I figured it out the second someone mentioned that the bootloader didn't get installed. So I just read how to do it from a command line and did that.

Now I'm trying to get dcop to run KDE, even though it's likely to run like a slug on this system, I just want proof of concept. Unless the other environments run without that.

I'm messing around with the usernames and that stuff, reading the absolute reams of stuff on this dcop error message.

With that box, you might want to read A Slackware Desktop Enhancement Guide. Darrell has a section titled Optimizing KDE for Older Hardware, but to substantiate what I stated earlier, he says, I hope his entire site will help you to customize your Slackware box so that you can have a great experience with older hardware. Slackware is, after all, famous for just such as that.

Edit: As for usernames, if you haven't done it already, as root issue "adduser <your_name>" and after creating a normal user, logout as root and login as that normal user. Running a Linux box as root is the same as a "screen door on a submarine."

I thought I could use XFCE or something without having to worry.

I did make another user account, but I can't currently run things from it. I don't have the network card for this system currently (which isn't a problem is it?) so I'm not currently worried about security.

Before reading this. Remember I haven't configured anything really. So if there is some sort of device or basic configuration I've missed. I've checked the documentation and I can't find anything specific.

My XFCE error follows:for KDE in a pop-up I get
Could not read network connection list.
/root/.DCOPserver_darkstar__0

when I try to run dcopserver I get
I can't see how to get out of it to get into command line stuff.

EDIT: Okay. I can manage a slew of different error messages by going in as a normal user,but it still seems like it has issues with dcop.