If you check over the My Computers page, you’ll see that the monitors attached to Eclipse have changed (more specifically, most of the systems have changed!). I’ve made a few upgrades here and there, but the best one from a usability point of view has been the changes in my monitor setups.
So… I figured I’d post an update (even if it is a few months old) regarding Hamachi and running it as a service under Windows. LogMeIn updated their licencing to a commercial/non-commercial system as opposed to the basic/premium setup. There’s no difference in functionality now, but it’s assumed that if you use Hamachi in a commercial environment, you’ll pay for it.
That being said, it’s quite easy to run Hamachi as a service now. Click on the gear in the main Hamachi window and select “Preferences” to bring up the configuration options. Under “System”, click on the button that says “Run Hamachi as a Windows Service”. It will restart Hamachi, and voila!
If you’re seeing this (and the hideous default WordPress theme) then it means that the site is being hosted from its new home! Hooray!
EDIT – Yay! The old theme is back again. I’ve also improved the Hamachi status indicators to make the site faster. They’re now being pulled from a database which is updated by the server every 5 minutes. 🙂
A few days ago, I decided to update my Zune with some new music I had got. When I double-clicked on the desktop icon, there was no sign of the Zune window, and instead given a friendly message saying “Microsoft Zune has stopped working”. Clearly, this was a problem.
Depending on how tech-savvy you are, you may have heard about the DNS vulnerability that many DNS providers are working hard to fix. For more information about what DNS is, check out the Wikipedia page on it. Long story short, a hacker can attack an unpatched DNS server, forcing it to show you “bad” pages when you try to view something as simple as Google.com. Chances are, if you’re a typical home internet user, your DNS requests are handled by your internet service provider. Some ISPs haven’t fixed their DNS servers yet, making them still vulnerable to this kind of attack.