After searching through other posts I post this:

I'm having trouble(duh), I figure it's with my configurations through the command xf86config.

I'm using Slackware 9.1. I don't think it matters.

Here is what I get:
I think it may be my monitor, I have an M90 Hewlett Packard Pavillion monitor. I don't full understand the frequency horz and vert. I want my desktop to be running at 1152x864, max freq(which seems to be 75hz on Windows XP).

MX90 Manual.

That has all you need to know about your monitor.

I forgot to add "no screens found" which is printed above what I quoted

I configured my monitor 12..x.... @ 60 and 50-150(custom vertical, also I don't own a graphics card, it's on-board. I select option 7 for 16... I don't think the keyboard or mouse would bother the config so that it forbids the system to start.

Other ideas? Please.

In situations like this, it helps if you can post your XF86Config file and give some hardware specs.

What's the command line for opening the file in the this DOS-like console?

dos-like indeed.....

cat /etc/X11/XF86Config

Here's what I wrote down:
I hope this is sufficient.

I am running Linux on a 8650C HP Pavillion, my graphics chipset is an 810 Intel. On Windows XP, my display adapter is 82810 Intel Graphics controller .

Update on my activities...:

I configured the file to: 810(generic) intel chipset, "1024x768" "11??x???" "640x480", 16mb color, horizontal 11??x??? @ 74hz, and 50-150 vertical.

I got up to the KDE configure wizard, but then after pressing next after a few options, I got a barage of static multicolored vertical lines. I reboot and tried to reconfigure my xf86 file but now I get this message after the command line xf86config:

Cannot create directory "/temp/.xf86config268"

You have to make sure the information you give the config file is correct. It will do whatever you tell it, even if it screws up your monitor or hardware, so you have to make 100% sure that you're telling it the right things.

As for it not being able to create the temp file, all I can think of is that you don't have permissions, and you should be doing it as root, or you're running out of space on that partition(hopefully not).

Uh-oh, I am logging in as root. I did chop down a lot of my partition sizes that recommended for Slackware 9.1 ... here's what I have, I noted the partitions I think are important:

/ (root) 1024M
SWAP 768M
/usr 4864M
/opt 1792M(recommended 2048M)

If it would come down to resizing, I'd stil; have to reinstall Slackware so that it's SETUP could format it, it's way? Otherwise, I see no problem theoretically moving the head of my /home which is after /opt +256M and resizing /opt to about 2048M by adding +256M.

You could actually just do:
SWAP - 2-3 times your system's memory
/ - The rest

Unless you have multiple hard drives. My setup is more like this:
hda1(19.5gigs): /
hda2(500megs): SWAP

hdc1(20gigs): /home
hdc2(20gigs): /usr

That works out pretty well. / and /usr are actually just using about 1.5 gigs each, while my /home partition is nearly half full. I just download too much stuff.

I don't understand what you meant by the swap 2-3 times the system's memory( I have 310 RAM upgraded from 64). 2-3x that? Okay.

I don't see why I should have a memory problem, first of all I don't fully understand how SWAP works, I'll go look that up. Second, the log file keeps over-writing itself shouldn't get significantly bigger. Even, when I was running the KDE wizard and it saved something, where would that config go?

The thing is that I was able to access the config file with the command xf86config with my partition sizes as they were. Maybe there's something wrong with the way I shutdown my computer after my monitor stopped displaying the KDE wizard and the background of the desktop.

In case the memory overflows for some reason, it will spill over into swap. It's about the same thing as 'virtual memory' in Windows.

KDE config files usually go somewhere under your user's home directory. They're hidden, so you type 'ls -al'(or 'ls -a' if you don't want it to be listed like that) to find them. Your KDE config files shouldn't be the culprit, though, but you can test it. If you think /etc/X11/XF86Config is properly set up(it would still help if you posted its contents), do this:

$ su <--(assuming you're not logged in as root)
$ cd /etc/X11/xinit
$ rm xinitrc
$ ln -s xinitrc.gnome xinitrc <--(failing that, there are other xinitrc.<whatevers>, just do the same with one of them)
$ exit <--(again, assuming you're not logged in as root)
$ startx

If X starts up, then KDE is to blame. If it doesn't, then I still think it's your XF86Config file, and you should probably switch that symlink back to the way it was.

$ cd /etc/X11/xinit
$ rm xinitrc
$ ln -s xinitrc.kde xinitrc

Again, it's really hard to tell what's up if I can't see how you have X.

And as far as your partitioning goes, I think 1024MB is really small for a root partition, especially Slackware, as you want to install everything those CDs have to offer(makes compiling programs from source a lot easier). The poor partition might be overflowing.

1024MB ?!?

I have a pretty small install of RedHat 9.0 and I think it's about 2.5 GB.

512M for my SWAP sounds fine
That leaves a little over 13GB left for /usr, /, and /home

What would one recommend for me...? How should I distribute the memory?

In the future... if I do get another HD. Would it be possible to move a partition from one hd to another so that Slackware would still consider it as the install's /home for example.