Suse's web site is misleading regarding these latest KDE updates which are said to be dated 26th November. If you look at the updates via ftp (e.g. with kbear), you'll see that there are no updates dated 26th, and only some are dated 24th. I'd already updated to those dated on or before 18th Nov, so I downloaded and updated all RPMs dated 24th. Konqueror is indeed far more responsive with the new qt. The latest kpackage package manager doesn't show you any of your RPMs, so I backdated the kdeadmin package from the 2.2.2-17 version (dated 24th Nov) to the last update. The kpackage from 2.2.2-17 has had the RPM package option removed from the "Options" screen (select Settings -> Configure Kpackage and its on the Types tab with earlier versions). All kernels I have compiled myself since 2.4.10 fail to load the sound module when booted (it can't be found). I've used the Suse config file for the builds. Doing a modprobe as root loads the module and sound works. I get the same behaviour at home and work (different sound cards), so it's not card related. Is there a workaround for this? Booting the failsafe kernel doesn't have this problem. I emailed regarding an error with building 2.4.16 with make xconfig which aborts before the GUI comes up. make menuconfig does work. Now I'm about to start playing with Sun's Forte for Java IDE. We use IBM's VisualAge for Java at work on winbloze, so Linux can't be the main development OS :( Work colleagues are impressed with what they've seen of it so far. Peter