I had a succesful install of KDE2, from the SourceForge SuSE binaries, at http://ftp.sourceforge.net/pub/mirrors/kde/stable/2.0/distribution/rpm/SuSE/... and things have, for the most part, been running ok for the last three days. First, let me describe my PC. It's a Sony VAIO, P166 with 64MB of RAM , and 128MB of swap file. I have 3 HDs, a scsci attached to a Mustek scanner, a Cannon BJC-620 on lp0 and a 100MB Zip attached via parport as sga or sga4, depending. Everything is behaving beautifully, for the most part. As far as software goes, Quanta, KDevelop, KMail, KNode, XEphem, XSane and everything else works nicely under KDE2 EXCEPT MuPAD-1.4. It always dies with a 'unknown graphical' error while initializing. The main thing I notice different is that under KDE, with nothing running, my cpu works along at under 10% capacity, with occasional spikes to the higher levels, but under KDE2 it is always working at 30-40% with significant amounts of time at 60% or higher. Most of the time in KDE, the swap file is hardly used. But, under KDE2, the swap file behavior is different. As long as I use just KMail, like I'm doing know, app the swap file usage remains at 2%. If I just use Konqueror, the cpu gets busy, spending most of the time at or close to 100% usage, while the swap file climbs to 5% usage. If I open a second Konqueror window the cpu stays hammered at 100% usage and response falls in the toilet. More importantly, if there can be something more important than pegging the cpu, is that if I open a third window the swap file usage starts creeping up. If I am reading and repsonding to mail, checking sites, etc. then after a while the swap file reaching 50% and the disk thrashing become noticable. AT THIS POINT, if I just let the system set, or at the most move my mouse, the swap usage continues to climb till it reachings 100% usage. Free memory, which is usually around 30%, drops below 10%. The system become nonfunctional. The only way I can regain control is to kill the xserver (cntl-alt-bksp). If I manage to logout with this condition in affect the disk thrashing (swap usage) continues at a high level for several minutes even while the system is setting at a kdm login screen. In the last incident, just before I began writing this email, it appeared that the LVM had starting killing icons off my desktop before the xserver kill took effect. Anyone else notice this problem, or is my PC too wimpy to run KDE2? One thing that I also noticed, while exploring this problem, is that swap file problems don't appear to occur on konqueror while it is being run under kde1, and it appears snappier. If it weren't for my wife using this PC I'd kill the graphical login and use startx so I when I have to kill the xserver I'd drop to a comfortable console command line. Jerry -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq