Right, I return, this time I'm typing from a dinovo keyboard again. After months of working with only the mediapad and MX900 going along with a regular noisy clack-panel I finally found someone selling a spare silver MX900 and only the keyboard (no mediapad). Perfect!

Don't know if any of you remember, but I managed to kill my dinovo a few months back.
Anyway, I've been doing many late nights of development work and it's such a pleasure using this keyboard. No loud key noises and not much strain happening anymore.

I recommend this baby to those who can afford it. I took my chances on eBay and even with the death of one of the pieces I managed to get back up and running for much less than my local suppliers prices.
However, some words of warning. The keys along the edges do have a design flaw relating to the rubber pads under the keys. They pop out so sometimes you'll find a dead key or even have to hammer the key to get it to do anything. I figured that from the death of the keyboard.
This one I have is working really well, except that in .NET IDE I tend to use the left CTRL alot so occassionally it seems to display the problem in the rubber pad design.
Also, I run XP Pro with SP2 and I haven't managed to successfully get the whole bluetooth thing working. At the moment the dinovo hub shows up as some USB device, and not as a bluetooth device. It's a problem with Microsofts limited implementation of the bluetooth stack. However, there are issues with Widcomm and MS installations clashing. All we really need from Logitech is some form of decent signed driver. I managed to faff with a MSI BToes signed driver and finally got this hub showing up in the bluetooth section of WinXP. At present I don't run Widcomm stuff or any drivers. I run SetPoint 2.11. I think that functions of normal windows interface stuff and watches keystrokes so is not specific or anything. Or maybe the MS stack is working in the background. Dunno.
the problem is that because of the whole logitech/widcomm/microsoft software and driver issue with this unit, even though the unit is functional, I cannot use the stunning bluetooth hub (or any other bluetooth device not approved by microsoft) to search out and connect to other devices. Even though my dinovo items are shown as HID items, the hub/radio/transceiver itself is not really supported by SP2. Stupid moneygrabbing O/S maker.
Also, I did at one point have widcomm running along with SP2, but not for long and I have to admit it sure does eat up alot of resources and the response from the dinovo is laggy. Perhaps this might explain why some people complain about lagginess from the mouse/keyboard. With only SP2 installed it is much faster so I guess the MS BT is doing something or all comms is through the simple listed USB device. Now if only they'd recognise the logitech hub and allow it to function like a normal bluetooth setup...
Anyway, apart from software (forget about SP2) and keeping your fingers light on the keys on the edges, this puppy rocks, especially when you're doing those really long hours.
By the way, there's a new dinovo out. Looks exactly the same, but now with bluetooth 1.2 or something like that. Easier power consumption and some frequency hopping thing. Let's hope they at least make a decent driver to get this working nicely with microsoft stuff. (Honestly, would prefer to use MS BT stack 'cos I'm tired of the multitude of installs required when something goes wrong).
Excuse the long blurb... it's just so cool to type on this thing.

Next up I intend to get myself a CoolerMaster Stacker.