Thanks to mdiegi and atolboo for the replies.
Well, with the intention of installing yawp as suggested by mdiegi I deleted pyplasma-weather. When I did this, the crashing stopped.
So, it seems, that on my machine at least, this particular widget is not a happy widget.
However, I was unable to install yawp as it seems I don't have the repo for it.
The video posted by mdiegi is impressive and this is exactly what I want. However, don't I already have kwin as part of KDE4.2? So, how do I get the rotating cube?
All that I have is a lot of transparency and some very stuttering wobbly windows which do not at all wobble smoothly like they do in Ubuntu with compiz-fusion.

Thanks for the replies.
However, what atolboo suggests is, in fact, exactly what I had already done as I mentioned in my first post.
OK, so I got some desktop effects but nothing like what I'm used to in  Compiz-Fusion which I have used in many distros (rotating cubes, 3D windows, truly wobbly windows).
The wobbly windows in Pardus, after enabling desktop effects, are only a pale shadow of what I have in Ubuntu, Linux Mint and OpenSuSE on this same machine.
Now that I've been using Pardus 2009 for a little while I'll just mention some other problems that I have although it may be better to open a new thread.
The major problem is that the Desktop Manager (KDE 4.2) in Pardus keeps crashing even after relatively minor operations such as opening a terminal.
I have put quite a few widgets on my Desktop. In booting to Pardus, the Desktop opens perfectly without any problems.
Then if I do anything (opening a terminal or opening the "Wine Glass" menu) everything on the Desktop disappears leaving a black screen other than, strangely, the horizontal RAM and Network usage bars.
So, nothing is available for me to do anything other than press the power button on the machine to get it to reboot.
Essentially, Pardus 2009 is unusable like this.
I may try to reinstall even though the md5sum of what I installed from was correct.
Another problem concerns the Google Weather widget which insists on showing me the weather in Munich Germany even though I'm actually on the other side of the world. So even though I have entered my own city and country and these are accepted, after every reboot it reverts back to Munich.
Has anybody else experienced similar problems? 

After a few days playing around with Pardus 2008.2 on my EeePC 901 (Intel 945GM graphics), I have now upgraded to Pardus 2009.
Looks great (KDE 4.2) and works well, but I'm unable to find how to install compiz-fusion.
In Pardus 2008.2, I easily found these in the repos and they worked very well. In Pardus 2009, I have enabled five of the six repos mentioned in this thread  (all except Pardus-Gnome) but still no compiz stuff appears when I search the repos.
Now I have enabled various Desktop Effects (System Settings >> Desktop >> Conffigure Desktop Effects). However, these really don't come close to what I normally expect from Compiz-Fusion (even with wobbly windows activated) and what I already saw in Pardus 2008.2.
Obviously, I'm overlooking something.
Any clues?

Thanks for your reply.
This is an astute observation.
Strangely, though, the Ubuntu partitions are mounted in the /etc/fstab of Pardus EXACTLY as are the partitions of the other OSes I have on my EeePC 901 (OpenSUSE, Linux Mint -- actually it's amazing how much you can squeeze into the 20GB of SSD space on this little machine). None of these others gives any booting problems after rebooting from Pardus.
On delving a little further into the error message I get on trying to boot Ubuntu, it seems the problem is that the time at which the Ubuntu partitions were mounted within Pardus is in the future (maybe 15-20 minutes). It seems that this relatively minor error is what trips up the Ubuntu boot. Surprisingly, the same problem occurs with Linux Mint but fsck during the boot is able to repair the problem without halting the boot.
In any event, as I don't really need the Ubuntu partitions to be mounted, by commenting out the Ubuntu lines in the /etc/fstab of Pardus, I can boot in and out of Pardus without messing up Ubuntu.
Still need to look into why Pardus records the boot time in the future though but it's obviously a clock problem.

Thank you for your reply.
Well, I don't recall having a brain seizure last night but it seems that I did.
Despite numerous attempts yesterday I was unable to find either the rt2869sta driver or any compiz-fusion stuff in the Pardus repos.
Today everything is available. So, I now have both a wifi connection and a lot of eye-candy.
Perhaps whatever repos I needed for this stuff were inactive for whatever reason when I tried yesterday.
The fourth problem I referred to in my first post remains the same -- annoying and unresolved.
However, in answer to your question, yes I can boot into both Pardus and Ubuntu. However, on booting to Ubuntu immediately after rebooting from Pardus, both / and /home in Ubuntu report fsck filesystem errors and the boot fails.
To eliminate these problems I need to boot to Linux Mint on the same machine and run "fsck -y /dev/sdXY" for both partitions. The problems are resolved quickly which seems to indicate that whatever the corruption was , it is minor. After this, I can now boot normally into Ubuntu.
Other than that, Pardus is starting to look very good although I know I'll be posting here for a while as there are still some things that are bothering/puzzling me 

Hi, I just installed Pardus 2008.2 on my EeePC 901 (after getting some help from the Turkish Pardus forum).
It's currently installed on a 3.7GB primary partition on the 16GB SSD and boots through Ubuntu's Grub which is in the MBR.
It works fine but I have the following issues and would appreciate any comments:

1. No wireless devices detected (wireless card is Ralink 2860)
2. Can't figure out how to upgrade to Pardus 2009 other than by re-installing
3. Does Pardus not support 3D effects (Compiz Fusion)?
4. This one is really weird. After using Pardus, the two filesystems on the Ubuntu install on the same machine (/ and /home) become corrupted but can be easily fixed with fsck. The two Ubuntu partitions are also both primaries and are located adjacent to the Pardus partition. Booting to Ubuntu without having used Pardus immediately before gives no problems.

Anybody got any clues as to how I can resolve any of these issues? Just for information, I have three years of Linux experience but not even one day with Pardus.