Ok, let me explain first what it is.. Synerygy2 is a way to share multiple computers with one keyboard and mouse. No, it’s not a KVM replacement.. Synergy2 replaces only the keyboard and mouse, you’ll need to have a monitor attached to each machine on your desk. This is actually a plus. In the photo below you’ll see my working area at the office… I’ve labelled which each runs for an OS and below that the names of the computers (click to see the full size image)
The keyboard and mouse is actually attached to the Ubuntu machine, in other words that’s the “server”. The XP and Windows 7 machines are “clients”. One thing to consider with Synergy is that it’s not secure. It does send everything you type in plain text over the network. This can be avoided by tunnelling the connection over something like SSH. Perhaps I’ll cover that later. Synergy2 isn’t new, it’s been around a very long time.
I don’t want to reinvent the wheel or try to take any limelight from those that have already posted great articles on how to set it up, the best information can be found from the Synergy2 website itself.
What I’m posting about is really how to fix a problem that I’m sure others might have encountered. Right.. so the problem is this. As I’ve said, the server is on Ubuntu. Naturally the “Windows key” on Ubuntu has no natural meaning to the OS, it’s just another key and not mapped to anything out of the box. The problem I’ve had is that while using Synergy the “Windows Key” didn’t work on the Ubuntu machine even though I’d remapped it to do things, such as Win + T to open a new xterm, Win + R to open the Run Command Dialog (basically making it operate a bit like Windows). the fix for this was a change in the $HOME/.synergy.ini file on the Ubuntu machine. The weird thing was that when move the mouse to the XP machine the Windows key did what it should, however on the Windows 7 it wouldn’t work.
Right, so what was the fix? Here is my .synergy.ini file
section: screens burma: scotland: meta = super rambler: meta = super end
section: links burma: left = scotland right = rambler scotland: right = burma left = rambler rambler: left = burma right = scotland end
section: options screenSaverSync = true end
The important lines above are the “meta = super”. Under Ubuntu the Windows Key is called “meta”. This tells Synergy when the focus is on the windows machines to map the “meta” key to the “super” key, or in other words the Windows key. Once that was changed and synergys was restarted all was good again.
I’m posting this for anyone else that might have a problem with the windows key not working under synergy with Linux/Ubuntu/Unix machines and windows machines, but also as a reminder to myself should I forget how I fixed it I’d been through this exercise about 4 years ago but having rebuilt that machine I couldn’t for the life of me recall how I fixed it .. well, now that I’ve blogged about it I’ll at least have one good place to go and find the answer again
I should finish that statement by saying it’s my last Nokia phone, EVER!
I bought my NokiaN97 back in June. I’m not ashamed to admit that I, like everyone else that ever ordered one of these devices, was excited like I’d never been about a phone. The prospect of what was promised by Vodafone and Nokia was overwhelming the senses. However, I very quickly found myself, like pretty much everyone else that has ever ordered this device, sad and disappointed to entirely new levels.
Where do I start .. well the device came shipped with the then current firmware level of 10.x .. right out of the box it was acting odd.. dropped calls, low phone signals levels where there should full signals, etc, etc. The worst at the time was making and taking calls… you might be lucky and get a call in and you might be lucky to not have the device crash and reboot during or immediately after a call. This was frustrating to say the least.
While the start of my relationship with my new N97 was rocky it was manageable . Plus the promise of the much talked about V11 firmware and how it would fix a lot of problems, that and that alone kept me hopeful that we could make things work (me and the N97). Firmware V11 came and went, sure, some problems were resolved, but entirely new problems were introduced. Once again, we were on the rocks with our relationship. I managed, somehow, to tolerate the device. It wasn’t crashing randomly any more, which I suppose is a positive thing. However, one of the new problems that came with V11 was a memory leak that slowly filled up my C:. The first time it happened I received an “out of memory” error and the phone crashed and rebooted. Upon reboot I was confused at first since the C: had about 18meg free. I then noticed it would slowly fill as days went on and crash again.
Until now, I’ve not even touched on the other long laundry list of known issues with this device, including the much loathed Nokia N97 Self Harming issue where it scratches and destroys it’s own camera lense. Mine has been no exception to this issue, the lense is nicely scratched and gashed, thankfully not directly over the camera’s optics so the camera is still very usable. Others, however, have not been so lucky.
So, back to the story.. we last off with the tails of whoa over V11 firmware. Well, it was many months before Nokia finally released the even more anticipated V12 firmware. It was even longer for UK contract phone owners since the UK carriers either refused to push it out to us or they blamed Nokia for the delay. I don’t know where the problem really was or who was really to blame, suffice to say it sucked big time. Finally, V12 was released and the world cheered, until they installed it and noticed yet more problems were introduced, for some it was more problems then fixes. Some of my issues were fixed but my memory leak got worse. I could now only run my phone for 2 days before the C: would fill and the phone would crash or I had to reboot it.
Well, here I am now in Nov. After waiting for V20 to come out and then deciding not to wait until sometime next year I changed the product code on my phone by following the instructions on THIS PAGE. That worked a treat I was then able to upgrade to V20. That did not go well at all I have to say. The process of loading the firmware was fine, however after the initial reboot there were loads of performance issues and lots of crashes. After much Googling I’d come to conclusion that I needed to do a hard reset and rebuild my phone from scratch That was the first time I had to a full rebuild. Somewhat painful .. loads of apps to find and install, activation codes to find etc. More annoyingly was I had to rebuild all my menus again for all the apps. Very time consuming. Fine, I accepted that, the phone is crap, the OS is crap and Nokia is crap, just one of the little joys of having bleeding edge hardware and Beta software.
Well, last night the phone acted up and needed a reboot. This wasn’t the memory leak, that seemed to be mostly cured going to V20, I forgot to mention that above. I pushed the power button, turned off the phone. It did as it was suppose to. Power it back on.. it sits at the white Nokia screen for about 2-3 mins. This is NOT normal. 60-90 seconds boot time is normal for my phone. I pull the battery, try again. Leave it for 10 mins or so this time. Still, no boot. Bugger me. I pull the battery, sim card and microSD card out. Wait a few mins, replace the sim and battery and power on. Nothing, just the White Screen of Death. I tried all the “fixes” that others posted about, nothing at all. I was again forced to hard reset and rebuild my phone.
This was the last time I ever hard reset my phone for no valid reason. The next time the phone does this, I will hard reset it clear and format the internal mass storage and sell it on EBay for whatever I’m lucky enough to get for it. That will be it. I will also not be organizing my icons again or doing much else in the way of customizing my phone because of the hassles and time it takes, all to have it destroyed because Nokia can’t get it’s act together.
I would love to return the phone to Nokia for a full refund not to mention refunds for the software I’ve purchased for the device that will, on the next total lock up will become of no use to me since I won’t be using the device.
I am one very unhappy customer of Nokia at this point, the only good thing is knowing I’m no the only one. There are 1000’s and 1000’s of people that have bought this phone and posted about their deep disappointment with the device and Nokia in general. I hope, like me, they will all vote with their feet and refuse to by any more Nokia and Symbian based phones! I think my next phone will be an Android of some sort. It can’t be any worse. No, don’t even think of trying to talk into an Apple i-CAN’T DO WHAT I LIKE ON MY PHONE-Phone.
If you are thinking of buying a Nokia N97 I would strongly encourage you to spend 2 hours at least Googling about the device and issues people are having. Don’t take my rantings on here for it, see what everyone else is saying about the device. If you have any sense you’ll see it’s not a good investment, and a very costly one at that.
Right, well Easter is actually over, but I’m doing a blog posting now really just to put the pics of the kids online more then anything. The day was good, it started way to early though. Man the kids were up at the crack of dawn, if only it were the crack of dawn in the UK and not for say India .. shesh.
Thankfully, Yuki’s dad is here staying with us and he was looking after the kids.. Yuki and I managed to sleep in until nearly 9am, which was nice. In fact, we managed to sleep in until nearly 10am Friday and Saturday. I can’t even begin to recall sleeping in that late when vast amounts of alcohol was the direct cause of it. So can’t really complain much.
Anyhow, the day started with breakfast as usual.. then we sent the kids up stairs with their lao ye (grandfather in Chinese, it’s more specific then that, but trust me, you don’t want me to open that can of worms here and now ). Yuki and I took to hiding all the stuff for the kids.. candy, chocolate eggs, bunny’s, all sorts of rubbish haha. Then it was time to unleash the kids..
First, here is a quick tour of the hiding places of all the candy
Here’s a video of the “hunt” under way .. I love Emma’s comment at one point “I’ve got so many…”
Here are a few pics…
You can see all the pics and videos taken today by CLICKING HERE.
Enjoy the pics and videos. I hope to do more blogging in the future.. I’ve been pretty slack at getting out updates, but life has been full of upheavals that… well… frankly made blogging a chore.
Besides, I’m booked to attend WordCamp UK in July. It’s the second year for the event and the first year I’m going … it’s a weekend full of meeting other bloggers, some who do it for a living but most because they enjoy it (I assume anyhow). With enjoy luck this event will encourage me to blog more, or even just give me loads of ideas to make my blogging better (which frankly wouldn’t take much, I know I suck at blogging).
I’ve been working on this project for a few weeks (lack of time). Basically, I bought a huge 120A/hr battery to go camping with and to use for other things, such as portable amateur radio work.
Well, that’s all well and good, but how do I connect things to it? I wanted some easy way to connect multiple things to the battery without having to have a number of wires getting attached to the battery.
So, not wanting to spend ARM+LEG and either our first or second born to buy something already made, and it wouldn’t include the cig plugs either.
So, I made this:
Read on if you’d like to see the other pics .. or, you can just go and look at them in my Flickr Gallery
I’ve been searching the net for ages looking for the wiring diagram of the 12VDC power cable for my Respironics REMstar Plus CPAP machine.
Not having any luck at all on the net finding the information I needed to build a cable, I’ve finally broken down and paid £26.00 (including shipping) to buy one. I’ve wanted a DC cable mostly so that I could a) go camping without the need to have a tent pitch that was powered (extra cost), and b) be able to power my CPAP should we have a prolonged power outage at home (fairly low risk of this, but a risk none the less).
Click on the image below to see the full sized one. This is a page from the manual that came with my cable.
Basically, should someone have posted something like:
To make your own Respironics Shielded DC Cord, Part number 1001956, you will need the following:
1 x 2.1mm (5.5mm outside) X 15mm Coaxial DC plug Such as: Maplin’s Part number HH61R (www.maplin.co.uk)
2-3m of suitable wire for a max of 7amp DC (depending on your CPAP model)
2-4 Clip on Ferrite suppressors, such as Maplin’s part N89AB
1 x 12VDC cigarette plug, suitable for upto 7amp DC
The construction of a DIY Respironics CPAP DC Cable, model number 1001956 is quite simple. Wire up the cigarette plug to the DC plug that will go to the CPAP, be sure to wire the tip of the cigarette plug (Positive 12V, I suggest a multi-meter to confirm this in your car or battery pack you intend to use) to the centre connector of the 2.1mm DC plug. Wire the negative to the other remaining connections.
At both ends of the cable, as close as possible to each of the plugs, leave not much more then 3-4cm of cable “exposed” put a couple of the clip on ferrite RF suppressors. These are quite important as they will ensure the dc is free of RF (Radio Frequency) or Electromagnetic noise. These, should they get into the machine, could cause damage. You can likely get away without them, but frankly for the extra £5 it will cost for these it’s worth saving your £500+ CPAP.
That’s all there is to it. I really hope people find this useful, for some reason there has been a black hole of info about these cables, and I’m not sure why.
**DISCLAIMER** This information has been provided purely for theoretical and personal information. I will not, nor can not, be held responsible if you are not competent enough to build this simple cable and end up damaging or destroying your CPAP. I’m pretty sure in the wonderful lawsuit happy world we live in it’s also most likely a violation of your warranty to attach a home made DC cable to your CPAP machine. You have been warned, don’t come crying to me if you blow something up, also, don’t ask me to make one for you. These are beyond simple to make.
Why? Why not. I was wondering how else I could make use of Twitter for other things I thought “How could I use twitter with my Asterisk PABX?” Doing some Google searching showed I wasn’t the first to think of this (as if that would have happened). There are a few people doing various things with asterisk and twitter.
I didn’t really like much of what I found, or found it wasn’t really what I wanted to do with it .. so I decided to use some of that info and came up with something of my own.
The short story is this. When someone calls my Canadian number, my US Toll-Free number any number that ultimately rings the group of phones in the house, I will now get a direct message in Twitter from a special account I setup for this purpose, which also sends a SMS to my phone (device notifications in twitter).
Read more by clicking below… Be warned! Thar be scripts and technical stuff in them thar parts
I’m just testing a blogging app on my phone. so far its alright. if this posts I will update in the morning with details of the application.
Posted from moBlog – mobile blogging tool for Windows Mobile
Haha ok, well, the posting worked. I noticed that because the server is on UTC and my phone is on BST the posting actually was “scheduled” for posting 1 hour after I actually hit the submit button. There might be an option in moBlog for that, I’ll have to have a look. Otherwise this is slick, I can post blog entries from my phone, including being able to attach images to postings.
I’d been through this exercise about 4 years ago but having rebuilt that machine I couldn’t for the life of me recall how I fixed it .. well, now that I’ve blogged about it I’ll at least have one good place to go and find the answer again 
That was the first time I had to a full rebuild. Somewhat painful .. loads of apps to find and install, activation codes to find etc. More annoyingly was I had to rebuild all my menus again for all the apps. Very time consuming. Fine, I accepted that, the phone is crap, the OS is crap and Nokia is crap, just one of the little joys of having bleeding edge hardware and Beta software.
Cambridge, UNITED KINGDOM
Entries (RSS)