>From your description, either of two things might be happening (or a mix of
them ... or, of course, something else I'm not thinking of).
1. Are you sure that the apps are really on your system? Even if an app is
listed in X's pop-up menu, it may not actually be on your disk. Slackware is
notorious for having this problem (listing non-existent apps in the X menu),
and I've seen it on other distributions too. Check the stderr output of
startx/X (if you do use startx, this will be written to the virtual terminal
that you started it from -- you can see this by pressing CTL-ALT-F#, where #
is the number of the F key corresponding to the VT you started from) to see
if you're getting messages that say something like "application not found".
2. Are you sure your swap is working properly? I'm impressed that you even
get bare X running in 8 megs, and apps will surely be relying heavily on
swap. If you can, open an xterm before you start trying to run the other
apps, and run "top" in it -- watch what happens to free space and to the
list of apps when you try to start one of the problem ones.
At 11:54 AM 7/26/99 +1000, Praxus wrote:
>I am still having a few problems with X mainly running most of the
>programs. X loads up very quickly and is currently running fvwm2 very
>good. The problem is when I try to load some programs it never
>happens. I have waited 15-20 minutes and they never load. when I try
>to load them there is a brief period of disk activity but that's it.
>several programs do work, like X-Term, xfm, x-filemanager, and
>xlander but that's it. This problem happens on KDE and GNOME as well
>so I know the problem is not fvwm2 specific. The computer is 486DX66
>8MB RAM, 128MB SWAP, 400 MB Root, Slackware 4.0.
> Thanx
>From
>
>Robert Hickey
>
>
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA 94303-3603 [EMAIL PROTECTED]
----------------------------------------------------------------
