Well I re-installed it. I didn't see most of the problems that I mentioned. I rebooted once and found that desktop effects weren't working again. Just like before though all I had to do was open the desktop effects menu, change something, and click apply and they came back. I was even able to remove bookmarks in Firefox and install extensions. I didn't get to see if sbopkg wanted to re-create that directory every time I booted in again as I can't access Slackware again... This time I know the problem (kinda). I attempted to have it load the generic kernel. This is what the end of my lilo.conf looks like

After that I ran lilo and rebooted. When I chose Linux from Lilo I got the message

So it seems I did something wrong. Not sure what though. One other question, if I were to modify lilo.conf from a Live CD, I'd need to run lilo afterword right? How does one do that? I attempted to earlier when I got rid of the bit that I added just to get back into Slackware, but I then realized that I have no idea how to run it since "lilo" doesn't work.

The two words in red need to be different. You need a different name for each kernel or distro you want listed at the LILO prompt.

It seems obvious now. Judging by the fact that I still only saw Windows and Linux after changing it I'm guessing I do indeed need to somehow run lilo from a LiveCD.

You can boot with the Slackware install CD/DVD (or any other LiveCD) and chroot into the system to run lilo. However, you should mount proc and dev within the chroot as well or LILO may spit out some errors.
Reboot and voila (assuming everything else is setup properly).

There are also instructions on the Slackware install CD/DVD to boot into your system using the huge kernel contained on the disc (so you can boot up your system fully without having to go through the chroot nonsense).

Bah, got back in with your help only to see that desktop effects are disabled, sbopkg insists that the directory it created doesn't exist, and now System settings crashes any time I try to enter the Desktop portion. If I believed in fate I'd say that I'm simply not meant to use Slackware.

I don't know if you have a 64 bit computer but vmlinuz-generic-2.6.33.4 is a 64-bit generic kernel.

For a 32-bit system you need to use vmlinuz-generic-smp-2.6.33.4-smp.

64 bit computer, here.

Riff, try installing Slack w/o KDE. Use Xfce instead. You won't have those issues.

Maybe not the visual but I still had the sbopkg issue.

Actually I fixed the desktop effects issue by disabling functionality checking. If I can get sbopkg to stop being stupid I think I'll be fine.

Correction: I'm the stupid one. I edited my /fstab to empty the /tmp directory upon shutdown. Is there any way to mark the SBo directory as an exception?

Have you got multilib set up right?

No idea, I've never even heard of it. Apparently I don't need to mess with multilib though as most of my problems have been solved.

And now I've gotten Firefox to look pretty. Well, compared to what it looked like before I installed GTK styles. I'd love to check out Chromium but that takes like, two hours to build and install so I'll let it do that overnight.

So right now things are working. Well, except autologin, I haven't tried that yet and I'm not going to until I see if I can find any information on that error. The only other thing is sbopkg. I'd like to set up my fstab file so that it clears out my /tmp directory (because I won't remember to) but that clears out SBo too.

You can set SBo/sbopkg directories to reside anywhere, so it doesn't have to be /tmp. You can also edit rc.local to 'rm -rf everything-but-sbopkg-stuff' rather than how you're currently doing it (or probably a variety of other methods). Also, if you just want sbopkg to shut up about the directories and go ahead and recreate them, there's the MKDIR_PROMPT variable. sbopkg.conf(5) and the sbopkg.conf detail all this but the rc.local bit.

Thanks. So far Slackware is great but KDE on the otherhand.... Good god, there are lots of things I don't like about it but the one that annoyed me the most is that when I transferred a folder from my external HDD to Slackware it only transferred 30000 of the, oh I don't know, 100000 or so the files in it. I haven't used XFCE or the Window Manages included with Slackware yet but I'm not real fond of them either.

I think I'll have to try Slackware in the future. I like the system itself but I don't like the desktop environments. It's not just about personal preference, it's also a functionality issue. So I guess I'll return to Debian for now and try Slackware again in the future when KDE 4 is a little more reliable. Thanks for all the help.

Sure. But, Slackware ships with a lot of desk top environments and window managers. Maybe, give XFce a try?