i tried putting kde 3.4 on to try and resolve some relocation errors ive been getting when trying to run some utils and k3b
after i installed all the packages i typed in startx and i get an error saying kdeinit cant start, check installation
im still pretty much a noob when it comes to resolving OS problems in linux so i removed all the packages in hopes of getting X to load, but that didnt help
so i go back thru the slack setup and reinstall kde 3.2 - bootup and i get this L 99 99 99 99 99 99 ect error, ive gotten it before but i forgot what caused it and how i fixed it
so now im having to boot up from the cd to get my box to boot right

can anyone shed some light on what i did wrong? and why the slack setup is causing this error?

instead of "startx" type:

xinit /opt/kde/bin/startkde &> startup

this will create a text file called startup with the output of the above commands, check it over for errors, if you see any post them. Also, did you configure X ( slack doesn't automatically do it like some other distro's).

yea i tried reconfiguring x but i got an error saying bash command not found :-\

im running swaret right in hopes this fixes all my problems
if that works then i have to figure out why i cant boot my image

on your lilo problem, reinstall lilo ( check over the /etc/lilo.conf file first, the as root type "lilo")

what command did you use to try to configure X? were you root ( to write the /etc/X11/xorg.conf file you will need to be) and if you used su to get root priveliges did you source /etc/profile ( type source /etc/profile in a terminal).

figured out the issues
i had to fdisk my mbr, forgot to try that route
and i was using xf86config and not xorgconfig *smack on head*