I better try to clarify a few things:
>
> I'm a bit confused about what you are doing as regards X
> installation. You
> say "I have run XF86Config and that didn't help." I'm not
> surprised, since
> XF86Config is a text configuration file read by the X server
> when it runs,
> not an executable.
>
> There is xf86config (note the different capitalization; case
> counts in
> Unix/Linux), a text-based program that guides you through X
> configuration,
> creating for you the file /etc/XF86Config .
you are right. I RAN xf86Config but that didn't work. I looked at
/etc/X11/XF86config to see if there was anything that I might change
without going through the program again.
>[....]
>
>
> I don't know what you mean when you say "I have always been
> able to run
> startx and am not intending to mess with that." Since this
> is the normal way
> to start the X server, why are you messing around with configuration
> programs if you already have X working? If you don't have X
> working, then
> what *does* this sentence mean?
when I type startx, I go into KDE or Gnome. no problem. When I type X,
(which i am assuming is a different program required by WINE, I get the
gray screen.
If I'm wrong, please clarify it for me, but I see startx as a method of
starting either KDE or Gnome. The X must be a different program since
it doesn't work and has a different configuration program than the
others. If it went to the same place, why wouldn't it work?
As far as using 'X', I don't really care at the moment because Im using
KDE and have enough to learn on it (FWIW, I didn't like gnome because
it doesn't have its own web browser like KDE does and leaves no choice
but to use Netscape and with KDE, I can use either -but this is all
unrelated to this thread so please make any comments to this remark in
another thread)
That's why I didn't want to change anything on startx. I am using it
just fine the way it is.
Back to X. Should something different come up or is it just another
entry point for KDE/gnome/etc...? I thought it must be something
different.
If it is the same, is there a way to get Wine to work - since this is
what all this is leading up to is trying to get Wine to work.
> Anyway, assuming you do not yet have X running, I'd suggest you:
>
> a. get it configured by way of xf86config
been trying. still trying...
I used Xconfigurator just fine for startx-KDE-gnome with no problems at
all.
>
> b. run it using startx
startx puts me into KDE, and I don't want to screw this up to run
wine..
==
hour or so later....
I just thought the Heck with X. I went into KDE and tried to run wine
from INSIDE and existing window program and it no longer tells me I
need a display, so maybe this is what it expects.. If it is, I never
saw something that simple in any manual.
I'm now getting messages that say 'could not start MANDRAKE_FLOPPY,
IGNORING drive A:
and says I may not have configured the /etc/wine.conf file (I haven't).
maybe my last problem is solved and I'm on to another one.
If any of you know if I n eed to re-define the words MANDRKAE_FLOPPY,
let me know. I'll be looking to find this part. all the things I have
read so far say to do it when you compile it and it's already compiled.
I'll post what I find works and what doesn't..
ken
I just ignored X and went to
