HMG, the social contract, and the elephant joke

Sunday, June 7th, 2009

According to the BBC, the man who used to be in charge of listening to you, thinks all of us should be listened to a lot more. Not ‘listening’ in the sense of careful, attentive and responsive duty to serve: rather, listening in the sneaky, all-encompassing, watching out for bad guys style of listening.

I can’t help thinking that this is an echo of a dried-up, bureaucratic and increasingly irrelevant administration: reading the plaintive call of the uber-spook side-by-side with the quiet and simple statements of the man brokering the expenses leaks gives some idea of the error being made by the modern British civil servant.

(more…)

Windows 7: networking

Tuesday, October 28th, 2008

Networking has been beefed up in a number of subtle ways in Windows 7. The first is a new feature called HomeGroup. This essentially turns all the Windows 7 PCs on the home network into a combined pool of data and files, much like a Windows Home Server or a NAS appliance.

Using a new feature called Libraries in Windows Explorer, you select and open files on the HomeGroup network as if they were stored locally on your PC. It’s also possible to search for files (using tags and filenames, or more advanced searches, such as the month a photo was taken) across the entire HomeGroup.

(more…)

Windows Vista in helpful message shocker!

Thursday, May 29th, 2008

I’m not the world’s biggest Vista fan. I don’t have it on my desktop machines, but I do on my laptops since even I’ll admit its suspend & resume is far more reliable than XP’s (or Ubuntu’s, or Fedora’s for that matter). One of the things I truly hate about it though, is the networking configuration interface. It never fails to lead me round in circles no matter how much I use it. It’s like a maze with moving walls and it gives me the willies.

So imagine my surprise today when it actually did something useful. (more…)

Having fun with Windows’ networks-diagnosis tool

Monday, May 19th, 2008

It could be that I’m incredibly unlucky, or it could be that the built-in Windows network repair tool is entirely hopeless. I’ve lost count of how many times I’ve used it, but can remember with absolute certainty how many times it’s worked: none.

The most recent time I optimistically pressed the ‘Diagnose and repair’ link was this weekend, when it came up with the entirely unhelpful message that the reason for my faulty wireless network was because a cable wasn’t connected into my Ethernet port. A big thank you to the Microsoft error dialog writers for that one.

In the end, I had no alternative: I had to resort to the time-honoured reboot. Even that didn’t work. Nor did rebooting the router. In fact, it was only when I called my dad and talked the problem through that he pointed out the error must be a software setting somewhere. This, I should shamefacedly admit, was after I’d swapped out the router and all the connecting cables.

It took me a princely 24 hours to solve the problem, and with a better diagnosis tool I reckon that would have been 24 seconds. Surely it’s not beyond the ken of Microsoft to build a tool that works out the two bits of a network that aren’t connecting as they should?

So am I just unlucky? Are other people out there having success with it?