<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-7959034</id><updated>2012-02-16T09:51:31.353Z</updated><title type='text'>View From a High Place</title><subtitle type='html'>Comments from Pete Murray. Well, they never appear in my programming...</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.pemur.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default?start-index=26&amp;max-results=25'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>114</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-7959034.post-4561585378730586286</id><published>2010-03-09T22:25:00.001Z</published><updated>2010-03-09T22:25:36.502Z</updated><title type='text'>Welcome back, Feedburner!</title><content type='html'>&lt;p&gt;Postscript to the last post – so many places, so little recall of all of them.&amp;nbsp; Just figured out that the old site was still being hit from Feedburner. At some point in the past I must have agreed to syndicate it out via that route, and never remembered to change the feed when Google upped sticks on me.&amp;nbsp; Sorry, but you should be back on line now.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-4561585378730586286?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=4561585378730586286' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/4561585378730586286'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/4561585378730586286'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/03/welcome-back-feedburner.html' title='Welcome back, Feedburner!'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-3051552154389077507</id><published>2010-03-09T22:01:00.001Z</published><updated>2010-03-09T22:04:33.339Z</updated><title type='text'>Alice doesn’t live here anymore</title><content type='html'>&lt;p&gt;Decision made, implemented – and now I have to pay for it.&lt;/p&gt; &lt;p&gt;After more than enough research to make my eyes bleed, the best hosting solution seems to lie with a company at &lt;a href="http://my.vidahost.com/aff.php?aff=482"&gt;www.vidahost.com&lt;/a&gt;, and I have purchased a hosting account there, two new domains and commenced the migration of my previous domains from their current place of residence to a new home.&lt;/p&gt; &lt;p&gt;Everything was going smoothly, up to that last part.&amp;nbsp; Vidahost have what appears to be an unassailable reputation on the Internets, and my brief contacts with support there, in the form of Dominic, have been unfailingly helpful and positive.&amp;nbsp; Nothing is too much trouble, unlike 1and1 where anything at all seems to be too much trouble.&amp;nbsp; But I screwed up the domain authentication key for the old MS Live domain, and that set into place a chain of events that may or may not resolve successfully yet.&amp;nbsp; I think the Live domain will transfer OK, but one of the two 1and1 name transfers is currently reported as ‘cancelled’.&amp;nbsp; The co.uk one went just swimmingly – but there seem to be fewer rules and thus less chance of error, for UK-based transfers than .com ones.&amp;nbsp; I have faith that Dominic can sort it out, but fear I’m going to be facing another year’s fees from 1and1 – with probably no hope of ever getting out of it.&lt;/p&gt; &lt;p&gt;On the subject of moving, it occurs to me that my faithful public may not have the new RSS feed sorted out for the blog.&amp;nbsp; If you’re seeing this, then in all probability it’s OK, but I suppose I better put a short and final entry up on the original pages (see, Google – I can manage FTP even if you can’t) to announce the change of address.&amp;nbsp; Remember – it’s &lt;a href="http://blog.pemur.com/atom.xml"&gt;http://blog.pemur.com/atom.xml&lt;/a&gt; now.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-3051552154389077507?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=3051552154389077507' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3051552154389077507'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3051552154389077507'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/03/alice-doesnt-live-here-anymore.html' title='Alice doesn’t live here anymore'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-3361826991499179254</id><published>2010-02-27T21:22:00.001Z</published><updated>2010-02-27T21:22:17.047Z</updated><title type='text'>Moving on to the next point</title><content type='html'>&lt;p&gt;Since Google (bless ‘em) decided to stop supporting FTP for this blog, it appears that I no longer have access to an archive of the contents.&amp;nbsp; That’s only slightly disturbing, because I very much doubt that anyone will ever want to refer back to older entries.&amp;nbsp; In fact, unless it’s pushed directly in front of anyone (Facebook, I knew you were useful for something!), no-one probably even looks at the up-to-date stuff.&lt;/p&gt; &lt;p&gt;The point of all this rambling is that for one reason or another I’ve decided to look again at my domains and hosting arrangements.&amp;nbsp; 1and1 and I are likely to have a parting of the ways in the very near future, mainly because I don’t feel that they are very answerable to their customers.&amp;nbsp; The straw that broke the camel’s back was their unwillingness to provide me with proper access logs, including full IP addresses.&amp;nbsp; All I get is the /24 subnet.&amp;nbsp; This is not acceptable – and most certainly wouldn’t be OK if it were a commercial site.&amp;nbsp; Therefore, I’ve decided to vote with my feet, or at least with my credit card. &lt;/p&gt; &lt;p&gt;The requirements are for a domain registration and hosting service that allows me to manipulate DNS as I see fit (not under the strict 1and1 control) and which just provides the service and gets out of the way in terms of web sites.&amp;nbsp; Oh, and since the credit card comes into it, it also needs to be cheap.&amp;nbsp; &lt;/p&gt; &lt;p&gt;Of the possible candidates, none stand head-and-shoulders above the rest, but I do have a certain regard for &lt;a href="http://www.knethosting.co.uk/" target="_blank"&gt;kNET&lt;/a&gt;: they seem to offer reasonable storage, good bandwidth allowance, multiple domains etc all for no more than 1and1 charge.&amp;nbsp; Ok, bandwidth isn’t unlimited, as 1and1 claim to provide, but does that really matter?&amp;nbsp; After all, there’s little enough traffic nowadays, given that the blog no longer resides on my storage. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-3361826991499179254?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=3361826991499179254' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3361826991499179254'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3361826991499179254'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/02/moving-on-to-next-point.html' title='Moving on to the next point'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-2173277089313269305</id><published>2010-02-19T08:00:00.001Z</published><updated>2010-02-19T08:00:47.572Z</updated><title type='text'>Move along, nothing to see</title><content type='html'>&lt;p&gt;With reference to the last entry, it now seems to be definite that the BSODs linked with MS10-015 were linked to a root kit, and are not the result of sloppy programming by Microsoft.&amp;nbsp; Rather the reverse – it was those lazy hackers that did it.&amp;nbsp; However, you’ll all be pleased to know that they have got their act together and have &lt;a href="http://www.prevx.com/blog/143/BSOD-after-MS-TDL-authors-apologize.html"&gt;updated the root kit&lt;/a&gt; to prevent this happening in future.&amp;nbsp; Kudos to the malware authors.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-2173277089313269305?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=2173277089313269305' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/2173277089313269305'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/2173277089313269305'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/02/move-along-nothing-to-see.html' title='Move along, nothing to see'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-7039639303107487400</id><published>2010-02-12T12:24:00.001Z</published><updated>2010-02-12T12:24:15.985Z</updated><title type='text'>Cleanliness is next to …</title><content type='html'>&lt;p&gt;Given the problems with the latest batch of Microsoft updates, and KB977165 in particular, it’s been interesting following the development of comments across the Internet.&lt;/p&gt; &lt;p&gt;Confusion over which update was causing the issues was rampant at first, with suggestions that all the recent ones needed to be removed before the BSOD was avoided, was quickly resolved as the ‘guilty’ party was identified.&amp;nbsp; But there still remained the question about what was actually causing the blue screen.&lt;/p&gt; &lt;p&gt;An early idea was that the only systems suffering from blue screens were already infected with something, and it now appears possible that at least &lt;a href="https://patrickwbarnes.com/blog/2010/02/microsoft-update-kb977165-triggering-widespread-bsod/"&gt;one underlying cause has been found&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;However, my interest is in some of the associated comments regarding how this was missed pre-release – and this poses an important question.&amp;nbsp; Presumably Microsoft keeps there system as malware-free as they can.&amp;nbsp; Patches are tested in a known environment, and while they can be expected to take into account as many variables in terms of configuration and hardware as possible, is it fair to suggest that they should take into account all the possible malware infections as well?&lt;/p&gt; &lt;p&gt;Those that shout loudest are likely to be people with infected PCs, but surely it’s their own responsibility to keep the system clean, not Microsoft’s to test against an already corrupt setup.&amp;nbsp; In essence, my argument is that KB977165 is not the root of the problem; as usual, this is clearly the fault of IT Security in ensuring that no infections got into MS.&amp;nbsp; A case of “damned if you do, damned if you don’t”.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-7039639303107487400?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=7039639303107487400' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/7039639303107487400'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/7039639303107487400'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/02/cleanliness-is-next-to.html' title='Cleanliness is next to …'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-1250881344783920310</id><published>2010-02-03T20:07:00.001Z</published><updated>2010-02-03T20:07:05.559Z</updated><title type='text'>A new hope</title><content type='html'>&lt;p&gt;Didn’t someone use that title elsewhere?&lt;/p&gt; &lt;p&gt;Welcome to the brave new world, which seems to be functional including the archives.&amp;nbsp; So perhaps Google did overcomplicate matters in their instructions, or I’ve just been lucky.&amp;nbsp; First time if so.&lt;/p&gt; &lt;p&gt;All I needed to do, in the final analysis, was to set up a CNAME for blog.pemur.com, pointing at something going by the slightly worrying name of ghs.google.com, and then switch my Blogger settings to a Custom Domain, pointing at &lt;a href="http://blog.pemur.com"&gt;http://blog.pemur.com&lt;/a&gt;, and it worked – after a while.&amp;nbsp; There’s even a valid RSS feed, on &lt;a href="http://blog.pemur.com/atom.xml"&gt;http://blog.pemur.com/atom.xml&lt;/a&gt;, should anyone find this worthwhile subscribing to.&lt;/p&gt; &lt;p&gt;The negatives include the loss of my favicon: I’m going to miss that.&amp;nbsp; A boring orange B that looks like nearly every other blog on the web isn’t a suitable replacement.&amp;nbsp; Also, the RSS feed that Google provides (&lt;a title="default" href="http://www.blogger.com/feeds/7959034/posts/default"&gt;default&lt;/a&gt;) isn’t exactly inspiring, either. &lt;/p&gt; &lt;p&gt;However, if nothing else, moving the blog should kill the overheads on my web stats for the pemur.com/.co.uk domain.&amp;nbsp; I never did have much luck extracting out the real data from the occasional spider and regular FeedDemon lookups.&amp;nbsp; On the downside, I guess it will be even more disheartening once these hits are gone.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-1250881344783920310?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=1250881344783920310' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1250881344783920310'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1250881344783920310'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/02/new-hope.html' title='A new hope'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-7520582274135595784</id><published>2010-02-03T19:41:00.001Z</published><updated>2010-02-03T19:41:01.033Z</updated><title type='text'>This may be the last update for a while</title><content type='html'>&lt;p&gt;Not that there have been any at all, recently, if I’m honest.&lt;/p&gt; &lt;p&gt;No, in common with many others today, I’ve received an email from Google informing me that blogger.com blogs will no longer support FTP updates to my own web space, and I’m going to have to transfer to a custom domain, hosted on their system – if I understand it correctly.&amp;nbsp; Apparently, FTP is too complicated for them to deal with.&lt;/p&gt; &lt;p&gt;Google, I’ve got news for you.&amp;nbsp; Your Custom Domain looks too complicated for me to deal with.&amp;nbsp; They promise some sort of migration tool, but when I have the vagaries of 1&amp;amp;1’s DNS to cope with (including the all too common lack of control) this may not work.&lt;/p&gt; &lt;p&gt;What’s so difficult about FTP?&amp;nbsp; You give it a target, a username and password, and tell it to transfer the files.&amp;nbsp; The data remains under my control thankfully, so even if Google can’t transfer stuff I still have it for a manual upload later if necessary.&amp;nbsp; What would future generations do without access to these gems of erudite wisdom?&amp;nbsp; (That is a rhetorical question – I have a pretty good idea of the answer…)&lt;/p&gt; &lt;p&gt;So perhaps it’s time to rethink the pemur web presence – I own the critical domains (.com, .org, .me.uk and .co.uk) and so far they all do different things (apart from pemur.me.uk which does absolutely nothing at all).&amp;nbsp; The original idea was that .org would be sort of work-related, and .com would be my personal domain, including biking stuff.&amp;nbsp; Now I’m back on two wheels that may well take off again, and if the Google migration doesn’t work out then I can look in more detail at managing the structures myself. &lt;/p&gt; &lt;p&gt;Don’t think of it as the end of an era, just the start of a new phase in the Internet’s development.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-7520582274135595784?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=7520582274135595784' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/7520582274135595784'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/7520582274135595784'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2010/02/this-may-be-last-update-for-while.html' title='This may be the last update for a while'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-848212473297550538</id><published>2009-11-15T10:55:00.001Z</published><updated>2009-11-15T10:55:01.469Z</updated><title type='text'>Progress report</title><content type='html'>&lt;p&gt;Things aren’t quite as bad as I thought last night.&amp;nbsp; I have, for instance, got Agent working, by the simple brute force expedient of running it in Win XP compatibility mode.&amp;nbsp; Sometimes the old ways are the best – literally, in this case.&lt;/p&gt; &lt;p&gt;However, I also ran off a list of all the installed software under the Vista regime.&amp;nbsp; This is going to take weeks to get everything back up and running.&amp;nbsp; Having made myself despondent I thought a bit of hardware hacking might help.&amp;nbsp; It’s always therapeutic to pull the insides out of a PC and put them back together again – as long as it works afterwards.&lt;/p&gt; &lt;p&gt;Needless to say, in this case it didn’t.&amp;nbsp; I’d found an extra SATA power adaptor and data cable, so went for the three drive setup.&amp;nbsp; This involved moving the current system drive to another SATA port – when the right-angle cable necessary to fit under the extended graphics card broke, leaving part embedded in the motherboard connector.&amp;nbsp; One fine pair of pliers later, the offending plastic was removed, and I was able to get all three SATA connections up and running.&lt;/p&gt; &lt;p&gt;Reboot – and only two drives showing.&amp;nbsp; The original data drive was AWOL: this was not what I expected, since it was the one cable I hadn’t touched, so it’s back inside the case again and check all the connections.&amp;nbsp; Turns out that the power lead to the drive had become adrift, so everything gets hammered back in as usual (which is possibly why the SATA connector above broke in the first place…), switch things back on and hey presto, three drives.&amp;nbsp; &lt;/p&gt; &lt;p&gt;Next question – which Samsung is the data drive and which is the old system drive in the BIOS?&amp;nbsp; Trial and error (emphasis on the latter) eventually got the drives in the right order, and I now have a Windows 7 workstation which boots up, complete with operational software.&amp;nbsp; Well, some of it’s operational, which is where we started.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-848212473297550538?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=848212473297550538' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/848212473297550538'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/848212473297550538'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/11/progress-report.html' title='Progress report'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-5558318314474246402</id><published>2009-11-14T22:12:00.001Z</published><updated>2009-11-14T22:12:44.898Z</updated><title type='text'>Wish I hadn’t started</title><content type='html'>&lt;p&gt;After all the hype, it seemed reasonable to try an update to Windows 7 on my main workstation.&lt;/p&gt; &lt;p&gt;I think my first mistake was to try to to this as a new install, rather than an update.&amp;nbsp; On second thoughts, perhaps the mistake was in the decision to upgrade in the first place.&lt;/p&gt; &lt;p&gt;We have any number of&amp;nbsp; PCs at work with complex configurations and obscure software, half of which is either totally obsolete or tied to hardware that probably belongs in a museum.&amp;nbsp; Frankly, they’re easy compared to this home monstrosity.&amp;nbsp; Servers running tightly optimised programs?&amp;nbsp; No problem.&amp;nbsp; This box?&amp;nbsp; Well, it has so many old and undocumented applications that I can’t track down sources for that there’s no way I can realistically hope to reproduce it in a new build.&lt;/p&gt; &lt;p&gt;So I took a decision to drop all the old stuff, and just concentrate on a core group of applications – the usual things, browsers, mail, usenet.&lt;/p&gt; &lt;p&gt;Problem number 1 – all my passwords and install keys are on the system drive that I’m replacing, and so far I haven’t been able to get three SATA drives running on the PC.&amp;nbsp; It will come with time, but to start with I need the new Win7 drive, plus my main data drive.&amp;nbsp; Why I didn’t store the passwords on the data drive is a mystery that will probably never be solved.&lt;/p&gt; &lt;p&gt;OK, several drive swaps later we have most of the info.&amp;nbsp; On to loading the applications, starting with Firefox: do you think I can find half the add-ons that I’m used to?&amp;nbsp; No, and to get details I have to re-attach the old system drive – again.&lt;/p&gt; &lt;p&gt;Even the Outlook install was difficult, mainly because of the number of external email accounts that I like to monitor directly.&amp;nbsp; I’ve forgotten most of the server names needed for IMAP and SMTP connections.&amp;nbsp; Thankfully, IE does work out of the box and I was able to research the necessary information.&amp;nbsp; Where would we be without the internet?&amp;nbsp; Oh, we wouldn’t have email…&lt;/p&gt; &lt;p&gt;Forte Agent – OK, it installs, and I even got the server account sorted (eventually); but on restarting the app it just hangs.&amp;nbsp;&amp;nbsp; I don’t have the strength to fix this.&lt;/p&gt; &lt;p&gt;On reflection, the easiest components are still the Microsoft ones.&amp;nbsp; The company may come in for a lot of stick, but when things work, they work well: witness this, Windows Live Writer set up and blogging in no time at all.&amp;nbsp;&amp;nbsp; Now if only Steve Ballmer would invest in buying a few more companies – like Forte.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-5558318314474246402?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=5558318314474246402' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/5558318314474246402'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/5558318314474246402'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/11/wish-i-hadnt-started.html' title='Wish I hadn’t started'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-1726707787610783848</id><published>2009-05-02T12:55:00.001+01:00</published><updated>2009-05-02T12:55:23.125+01:00</updated><title type='text'>Tied down again</title><content type='html'>&lt;p&gt;This wireless stuff is all well and good, but it’s not something that I would necessarily want to rely on in a case of life-or-death.&amp;nbsp; All too often, the links from more than one of the PCs at home break for no apparent reason.&amp;nbsp; There’s no pattern in it, just one machine or another stops responding.&lt;/p&gt; &lt;p&gt;So it’s back to the wired network, and the subsequent upheavals in the office as I try to find out exactly which of the cables I left from last time connect to what.&amp;nbsp; OK, it might have been sensible to leave them plugged into the client systems, but I genuinely thought I’d be removing them for good – only to find out that I’ve somehow managed to thread them through locations where they simply cannot be removed without ripping all the furniture out, so there are a lot of loose RJ45 connectors lying around.&lt;/p&gt; &lt;p&gt;What will be interesting will be the potential effect moving the router of the main BT socket to an extension cable running off a spur socket.&amp;nbsp; I can expect around 5 Mbit/second at the moment – anything more than a 20% reduction in that will not be acceptable.&amp;nbsp; However, the only way to tell will be to try it, so I suppose it’s time to dig underneath the desks – and hope I have left a power socket free.&amp;nbsp; The good thing is that the wireless link will still work (as well as it ever has) after I move the router, so some testing before final installation should be possible.&lt;/p&gt; &lt;p&gt;Oh, the life-and-death bit?&amp;nbsp; Ever tried battling your way through a Guild Wars instance when the connection drops?&amp;nbsp; I lost a Survivor title when that happened once, and that’s not something I’m inclined to allow again.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-1726707787610783848?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=1726707787610783848' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1726707787610783848'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1726707787610783848'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/05/tied-down-again.html' title='Tied down again'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-3969855385708082206</id><published>2009-03-23T22:18:00.001Z</published><updated>2009-03-23T22:18:29.271Z</updated><title type='text'>How not to do it – the Microsoft way</title><content type='html'>&lt;p&gt;Does Microsoft (or any technology company for that matter) really understand the concept of being business user-friendly?&amp;nbsp; Leaving aside the abomination otherwise known as Office 2007, which replaced a perfectly workable toolbar with a ribbon interface that seems to actively hide the most useful components, there’s a lot of stuff going on under the hood of any self-respecting PC and/or network that requires fixing in the default setup of Windows.&lt;/p&gt; &lt;p&gt;The latest example of the annoyances in this regard comes in the form of the default behaviour of Server 2008 with regard to remote sessions.&amp;nbsp; Who on earth thought it was a good idea to restrict user logins to a single session?&amp;nbsp; It’s become a joke now when I or my fellow conspirators throw one another off the administrative sessions we have so lovingly crafted just because the system thinks ‘one user, one login’.&amp;nbsp; Actually, what’s really annoying is that this is controlled by a group policy setting that I can never recall – it’s now firmly entrenched in the ‘IT problems and gotchas’ of our company SharePoint site, and needs to go into a build document.&amp;nbsp; But I still wonder why we should have to do this, when the old Server 2003 way worked perfectly well out of the box.&lt;/p&gt; &lt;p&gt;Another&amp;nbsp; default setting that annoys is the prejudice against NAT.&amp;nbsp; I’m tired of going through the registry edit and reboot required to get PPTP or l2TP working via a standard router to the Internet.&amp;nbsp; For bonus annoyance points, MS decided to change the required registry values between XP/2003 and Vista/2008.&lt;/p&gt; &lt;p&gt;The final target of ire this evening is the Windows Firewall.&amp;nbsp; All very nice in theory, but deplorable in practice.&amp;nbsp; We set up all these nice client PCs, get back to base – and find we can’t access them remotely.&amp;nbsp; Group policy to the rescue again, and disable that service.&lt;/p&gt; &lt;p&gt;I seem to spend half my time switching off, cancelling or simply bypassing roadblocks put in the way of simple, successful system management.&amp;nbsp; By all means create a ‘home user’ build for Windows, but please can we have a ‘business edition’ without all the unnecessary hindrances?&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-3969855385708082206?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=3969855385708082206' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3969855385708082206'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3969855385708082206'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/03/how-not-to-do-it-microsoft-way.html' title='How not to do it – the Microsoft way'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-7709693284355872978</id><published>2009-03-15T19:44:00.001Z</published><updated>2009-03-15T19:44:48.689Z</updated><title type='text'>Atom’s back</title><content type='html'>&lt;p&gt;Someone was working over the weekend – RSS functionality has returned to Blogger, and the feed definitions are being updated correctly.&amp;nbsp; Or at least as correctly as the Blogger style sheet will allow.&amp;nbsp; One monolithic line of code makes it difficult to be absolute about things like this.&lt;/p&gt; &lt;p&gt;I may be old-fashioned (OK, there’s no doubt – I am old-fashioned) and I certainly prefer human-readable text.&amp;nbsp; What does it cost to put a few line breaks and tab characters into a text file?&amp;nbsp; In this particular case, about a 2% increase in file size, which should not be a deal breaker.&amp;nbsp; For that, you get a text file that can be understood, and even parsed by the human eye&lt;/p&gt; &lt;p&gt;Perhaps you might argue that these things are not intended to be read by humans: their function is simply to define a set of data for a computer to work with.&amp;nbsp; But I would respond that we should not lose sight of the need for people to understand what computers are doing.&amp;nbsp; OK, there are some time and space-constrained operations where maximum efficiency is needed, but XML code is not amongst these: by its very nature, it’s a form of text, and doesn’t aspire to terribly efficient operation.&amp;nbsp; There’s a tremendous amount of repetition, unnecessary descriptive strings, and sheer bloat in even the most tightly structured XML file.&amp;nbsp; So why not add that extra 2% and make it readable?&lt;/p&gt; &lt;p&gt;If you want that space back, do something like parameterise the contents.&amp;nbsp; For instance, my atom.xml file contains my name repeated many times over – why not reduce it to a simple variable defined at the start of the list?&amp;nbsp; &lt;/p&gt; &lt;p&gt;If the standard insists on fully expanded strings, then go all the way and just add those two or three extra characters per line and make them proper lines.&amp;nbsp; Apart from anything else, this ensures that mistakes can be picked up more easily – but I must admit, the original mistake with the generating code that caused empty XML files to be created wasn’t going to be found very quickly from a blank output file.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-7709693284355872978?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=7709693284355872978' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/7709693284355872978'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/7709693284355872978'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/03/atoms-back.html' title='Atom’s back'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-674097917370773203</id><published>2009-03-14T20:17:00.001Z</published><updated>2009-03-14T20:17:20.452Z</updated><title type='text'>Don’t update software on a Saturday</title><content type='html'>&lt;p&gt;What’s today’s problem?&lt;/p&gt; &lt;p&gt;Well, bear with me, there’s a list:&lt;/p&gt; &lt;p&gt;Blogger has lost my RSS feed – and that of a lot of other people as well, apparently.&amp;nbsp; The automatically generated atom.xml is being created as a zero byte file.&amp;nbsp; So there’s a better than even chance that you won’t even see this post, at least while it’s meaningful.&amp;nbsp; There is a workaround, for anyone who needs it: use the feed identifier in the form of &lt;a title="http://www.blogger.com/feeds/7959034/posts/default" href="http://www.blogger.com/feeds/7959034/posts/default"&gt;http://www.blogger.com/feeds/7959034/posts/default&lt;/a&gt;, where the number needs to be updated to your own account value.&amp;nbsp; Drop that intot he template, republish, and it’s working at least as far as anyone picking up the RSS feed this time around.&amp;nbsp; Apparently, it’s also possible to copy the actual file to your own atom.xml, but this needs to be done each and every time the blog gets updated, so to date I simply haven’t mustered up the energy.&amp;nbsp; Blogger already know about the problem, but it’s the weekend now and I suppose they’ve taken the time off.&lt;/p&gt; &lt;p&gt;Twitter – someone went and changed the API or something, and my old &lt;a href="http://www.kosertech.com/blog/?page_id=6"&gt;ceTwit&lt;/a&gt; application on the phone gave up reading posts.&amp;nbsp; I did manage to download an update, but this doesn’t seem to show a public timeline, and is consistently reporting a possible broken API and I’m left wondering if this is actually working at all.&amp;nbsp; However, I did manage to locate, download, configure and use a different product &lt;a href="http://www.infinitumsoftware.com/twobile"&gt;Twobile&lt;/a&gt;, which is working OK.&amp;nbsp; Since I seem to post Twitter updates even less frequently than I update this blog, however, it probably won’t break their service too soon.&lt;/p&gt; &lt;p&gt;For my final act of IT vandalism today, I thought I’d update the nVidia drivers for the graphics card in the workstation, a mere 8800 GT card.&amp;nbsp; Wonders will never cease – this actually worked.&amp;nbsp; Being flushed with success I also thought I’d go for the Windows Live tools (including Live Writer), and this is where it seems to have gone a little bit wrong – various components seem to be having issues with the firewall, and I no longer know if it will work.&lt;/p&gt; &lt;p&gt;Still, look on the bright side: even if it does work and this post gets published, no-one will ever see it as long as RSS is broken.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-674097917370773203?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=674097917370773203' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/674097917370773203'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/674097917370773203'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/03/dont-update-software-on-saturday.html' title='Don’t update software on a Saturday'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-6679135924462914228</id><published>2009-03-14T09:11:00.001Z</published><updated>2009-03-14T09:11:20.545Z</updated><title type='text'>Caution - low flying laptop</title><content type='html'>&lt;p&gt;The driver update didn't have the desired effect.&amp;nbsp; Still no profile updates, unless I manually change the registry entry.&amp;nbsp; One possible bright spot was the discovery of a script to do that job semi-automatically, but... it's in German and designed for Windows XP, not Vista.&amp;nbsp; My translation skills weren't good enough to get it working in the fifteen minutes or so before my attention was diverted elsewhere.&lt;/p&gt; &lt;p&gt;There's considerable discussion about how the video drivers achieved WHQL certification with such an evident bug - and why they haven't been fixed in over a year.&amp;nbsp; I see a lot of trumpeting success in getting the certification - but not an ounce of responsibility for errors like this.&amp;nbsp; Who is really at fault here - nVidia, Microsoft or Dell?&lt;/p&gt; &lt;p&gt;On the other hand, one beneficial effect of the new video drivers has been to prevent the irritating loss of dual screen functionality that occurred when the PC was locked: on return to activity, I'd see the second screen active for about five seconds, then it would switch off and push all active windows back to the primary screen, necessitating a trip to the keyboard to reactivate the monitor and then drag everything back over.&amp;nbsp; As the system still knew the second screen was there for those few moments, why did it then disable it?&amp;nbsp; Anyway, this bug at least is now fixed.&amp;nbsp; What's interesting is that it took me most of the day before I noticed the change in behaviour, which only goes to show how it should have been right in the first place.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-6679135924462914228?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=6679135924462914228' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/6679135924462914228'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/6679135924462914228'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/03/caution-low-flying-laptop.html' title='Caution - low flying laptop'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-4489721730856151470</id><published>2009-03-12T19:26:00.001Z</published><updated>2009-03-12T19:26:58.050Z</updated><title type='text'>Driven to distraction</title><content type='html'>&lt;p&gt;I use a Dell Precision M4300 laptop for work - whilst not the lightest device around, it has sufficient horsepower and storage, and offers enough interfaces and screen real estate to cope with my various demands.&lt;/p&gt; &lt;p&gt;But since purchase it's been running slowly - Task Manager showed around 20-40% CPU utilization, all down to the System process.&amp;nbsp; Now this is a real can of worms, nearly everything that keeps the PC running is handled by this.&amp;nbsp; So I lost patience today and started to research the problem.&lt;/p&gt; &lt;p&gt;Turns out it's a fairly well known issue - Mark Russinovitch (he of Sysinternals fame) had already seen the same issue, and (being who he is) had &lt;a href="http://blogs.technet.com/markrussinovich/archive/2008/04/07/3031251.aspx"&gt;figured out the cause&lt;/a&gt;.&amp;nbsp;&amp;nbsp; Wonders will never cease - it turned out that it was the same driver, same symptoms and same cure that was effective for me.&lt;/p&gt; &lt;p&gt;This begs the question of why an issue that was known about a year ago (April 2008) has still not been addressed by Dell.&amp;nbsp; I was able to follow the Broadcomm links from Mark's blog entry to an updated driver for the NIC, but Dell's support site was less than helpful.&amp;nbsp; Once the new driver was installed, it was like working on a new PC - so much faster, better response to keyboard inputs, sheer luxury.&amp;nbsp; Imagine how much I would have appreciated it if Dell had taken the opportunity to&amp;nbsp; update their support site drivers to match.&lt;/p&gt; &lt;p&gt;Another issue on the same lines is the odd behaviour of the domain profile I use: apparently, this hasn't been updated on the server since around November of last year.&amp;nbsp; This means that changes I make on my desktop, for instance, are not reflected in the server copy, but files I thought I had deleted keep coming back: I have to log on to the server and delete the files from the copy there.&amp;nbsp; This one is weird: turns out it is a problem with the Nvidia display driver (for the FX 360M, a device that seems to be supported only by Dell, not Nvidia themselves) that screws up a couple of entries in the registry, a problem that only becomes apparent when you use Windows Server 2008 as a domain controller.&amp;nbsp; It just so happens that we switched to Server 2008 last November... Not sure if this latter problem is resolved yet, having already rebooted the PC several times to try and fix the NIC driver earlier in the day, I didn't get around to doing it again, so we'll see if the desktop reverts again tomorrow.&amp;nbsp; If so, I suspect the next step is to see if a laptop PC can develop wings in the short time it will take to fly across the office.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-4489721730856151470?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=4489721730856151470' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/4489721730856151470'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/4489721730856151470'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/03/driven-to-distraction.html' title='Driven to distraction'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-9183627959531814459</id><published>2009-03-07T14:02:00.001Z</published><updated>2009-03-07T14:02:27.010Z</updated><title type='text'>A site for sore eyes</title><content type='html'>&lt;p&gt;I wonder if there's a degree course somewhere in website optimisation?&amp;nbsp; Even leaving aside the search engines completely, actually managing a site isn't a one-click operation.&amp;nbsp; Over time, the contents get more complex: this is true even (especially?) of a site like mine, which has been in existence for at least five years, albeit woefully lacking attention.&amp;nbsp; During this time, I occasionally discover new tools and new systems that get tried out, leaving remnants of pages and folders containing code that I have no way of identifying or managing properly.&lt;/p&gt; &lt;p&gt;It must take a very organised and disciplined approach to keep a site clean over time: even something as simple as multiple copies are likely to proliferate as local machines are replaced or new server installations come into play.&amp;nbsp; For instance, I have at least two copies of my own site on my home machine, and no real way of keeping them synchronised: Filezilla gives some help in this regard, but it's not really able to deal with things in the same way as, for instance, SyncToy or Microsoft Live Sync.&amp;nbsp; These latter two are very nice, but I haven't managed to get hem to support an FTP folder yet, so they don't quite fit the bill.&lt;/p&gt; &lt;p&gt;Once I have a local copy that I can depend upon, usually achieved by creating a new folder (don't want to risk losing old data.&amp;nbsp; Oops, there's another copy now!), I can check the contents out, and this is where I get really confused.&amp;nbsp; Some of the pages were created in MS Word (I know, I should have used Notepad, but I was feeling lazy); some were creating using whatever the tool of the moment was on the hosting company's site; some are straight from Photoshop or Lightroom; some are out of Blogger.&amp;nbsp; So far, I haven't gone as far as using Expression or anything like that, but I am seriously considering junking nearly everything (bar the contents of the blog) and starting again, with a properly designed site and a tool that I can stick to.&lt;/p&gt; &lt;p&gt;Whatever I select will need to have certain features:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Photo management.&amp;nbsp; Part of my lazy approach is that I don't like emailing pictures to all and sundry.&amp;nbsp; However, neither do I trust Flickr or the like to hold my photos.&amp;nbsp; (The truth is probably that I don't reckon they'd stand up to the public scrutiny there.)&amp;nbsp; So I like to just upload batches of pictures, mail interested parties and leave it up to them.  &lt;li&gt;Blog integration.&amp;nbsp; I like Blogger, and also Live Writer's integration.&amp;nbsp; It may not be professional, but it sure is easy.  &lt;li&gt;Ease of experimentation.&amp;nbsp; There's no way I'll be able to resist trying something new.&amp;nbsp; Pages will find their way in which aren't published via the approved route.&amp;nbsp; A site management tool must be able to integrate these back from the web into local storage.&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;I think the search is on.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-9183627959531814459?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=9183627959531814459' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/9183627959531814459'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/9183627959531814459'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/03/site-for-sore-eyes.html' title='A site for sore eyes'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-8677588526761059671</id><published>2009-02-26T21:10:00.001Z</published><updated>2009-02-26T21:10:53.129Z</updated><title type='text'>Two steps forward, one step back</title><content type='html'>&lt;p&gt;I’m seriously considering reverting to a wired network.&amp;nbsp; Not intending to drop the wifi entirely, but it seems that it doesn’t present the stability and reliability that I’ve come to expect.&lt;/p&gt; &lt;p&gt;A large part of this is down to the adaptors and aerials used by the system.&amp;nbsp; Of course, no two devices are from the same manufacturer, so I can’t really expect complete integration without problems.&amp;nbsp; Come to think of it, no two devices are actually running on the same platform (Win XP, Vista, 7, Mobile 6, and whatever variant of Linux is running on the actual router).&amp;nbsp; I suppose it’s a miracle that they manage to talk at all.&lt;/p&gt; &lt;p&gt;It’s not that connections to the router show any difficulties (apart from the USB stick wifi adaptor on the Win XP box – but that seems to fall out of the USB port if you even glance at it – this takes the concept of quick release to new heights).&amp;nbsp; But I also need to copy data between devices, and this is where it falls down.&amp;nbsp; Speeds are nothing short of appalling, less than the broadband link&amp;nbsp; would be expected to support, and without a properly managed DHCP/DNS on a server, even finding the other boxes can be tricky.&lt;/p&gt; &lt;p&gt;So do I really want to return to the rat’s nest of cables stuffed behind desks and book cases?&amp;nbsp; No, but I may not have the choice.&amp;nbsp; Unless I can sort out a no-cost (and most especially no-extra-box) solution, it will have to be back to wires everywhere.&lt;/p&gt; &lt;p&gt;The real negative, though, is going to be that the router will have to move.&amp;nbsp; It’s currently connected directly into the BT master socket, for best broadband performance.&amp;nbsp; But the no-extra-box constraint means that I can’t use a switch in the study, so the router will have to move up there and serve, with a likely drop in WAN access speeds.&amp;nbsp; And that’s not something that I really want to see happening.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-8677588526761059671?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=8677588526761059671' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/8677588526761059671'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/8677588526761059671'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/02/two-steps-forward-one-step-back.html' title='Two steps forward, one step back'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-5947498042337934500</id><published>2009-02-14T22:17:00.001Z</published><updated>2009-02-14T22:18:24.378Z</updated><title type='text'>Feature bloat</title><content type='html'>&lt;p&gt;You know what it’s like – a nice new PC, all shiny, loads of disk space.&amp;nbsp; Then three days later it’s all slow, fragmented, and you start to think that maybe the old system wasn’t that bad after all.&lt;/p&gt; &lt;p&gt;Well, that’s the situation here.&amp;nbsp; The brand new 120 GB disk in my new netbook (has that term been trademarked?&amp;nbsp; If so, I’m in trouble – along with maybe nearly everyone else who has written anything on the web in the last six months) is now no longer showing 120 GB of free space.&lt;/p&gt; &lt;p&gt;OK, I put the Technet Windows 7 beta on it – whoops, there goes well over 7 GB free space in the OS folder alone.&amp;nbsp; Then there’s everything MS loads by default into Program Files.&amp;nbsp; Plus 4.5 GB of pagefile and hiberfil.sys.&lt;/p&gt; &lt;p&gt;Then I started. There are all the default things, like Acrobat Reader, &lt;a href="http://www.irfanview.com" target="_blank"&gt;Irfanview&lt;/a&gt;, &lt;a href="http://java.com/en/" target="_blank"&gt;Java&lt;/a&gt; etc.&amp;nbsp; The whole of the Windows Live suite – or at least, all the useful bits – like Live Writer!&amp;nbsp; Now it started getting out of hand: Silverlight, &lt;a href="http://www.digiguide.com" target="_blank"&gt;Digiguide&lt;/a&gt;, &lt;a href="http://filezilla-project.org/" target="_blank"&gt;Filezilla&lt;/a&gt;, &lt;a href="http://keepass.info" target="_blank"&gt;KeePass&lt;/a&gt;, &lt;a href="http://notepad-plus.sourceforge.net/uk/site.htm" target="_blank"&gt;Notepad++&lt;/a&gt;.&amp;nbsp; Anything else?&amp;nbsp; Yes, &lt;a href="https://sync.live.com/learnmore.aspx" target="_blank"&gt;Live Sync&lt;/a&gt;!&amp;nbsp; After all, why waste disk space on one PC when you can waste it on two or more?&amp;nbsp; What was surprising was that so far, the Program Files folder was still only around 1 GB in size&lt;/p&gt; &lt;p&gt;The final straw was Guild Wars – on its own, this doubled the Program Files folder.&amp;nbsp; However, this isn’t the worst of it: I can afford the disk space, it’s the fact that GW will probably take up all the time I’m likely to save with the new system.&amp;nbsp; Ah, the perils of new technology.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-5947498042337934500?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=5947498042337934500' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/5947498042337934500'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/5947498042337934500'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/02/feature-bloat.html' title='Feature bloat'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-1469691968136364522</id><published>2009-02-06T19:01:00.001Z</published><updated>2009-02-06T19:01:18.112Z</updated><title type='text'>PANs and POTS</title><content type='html'>&lt;p&gt;Bluetooth on a mobile phone is an amazing invention - wireless headsets and hands-free calling alone would make it worthwhile.&amp;nbsp; However, for over a year I've had no luck at getting it to work as a modem for my various laptops.&lt;/p&gt; &lt;p&gt;Until today.&amp;nbsp; The new netbook, with a bit of tweaking and twisting, is now making L2TP connections via bluetooth and the ORBIT2, and thence via O2's network, all the way to the company network.&amp;nbsp; This has bugged me for so long, and now it's working!&lt;/p&gt; &lt;p&gt;The real answer lay in using Internet Connection Sharing on the phone - I could easily get the PC to see the phone, but never had any way of getting info in and out.&amp;nbsp; This last step fixed that.&amp;nbsp; Naturally, it isn't necessarily that easy - the bluetooth settings on the laptop take a bit of getting the head around, but I have satisfied myself that the functionality is reproducible.&lt;/p&gt; &lt;p&gt;The worst bit, so far, is the absolutely appalling lag - ping times in the 400-600 ms range mean that anything like a complex web page is going to load &lt;em&gt;very&lt;/em&gt; slowly.&amp;nbsp; At that sort of rate, I'd almost be better with an old 300 baud modem on a POTS line.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-1469691968136364522?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=1469691968136364522' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1469691968136364522'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1469691968136364522'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2009/02/pans-and-pots.html' title='PANs and POTS'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-3601960710162899590</id><published>2008-09-02T08:02:00.001+01:00</published><updated>2008-09-02T08:02:38.443+01:00</updated><title type='text'>On the instability of reality</title><content type='html'>&lt;p&gt;Over the years, I've noticed that IT equipment has a habit of simply disappearing.&amp;nbsp; When you absolutely know you had several power adaptors, spare memory chips and patch cables in the cupboard, and yet the most diligent search doesn't reveal anything more than a dusty old graphics card or 300MB HDD, then you become aware of the essential fragility of nature.&lt;/p&gt; &lt;p&gt;I'm not sure about the power strips or memory, but I do know why the network cables go.&amp;nbsp; Anyone who has worked with a patch panel and network infrastructure very quickly becomes aware that network cables inevitably become tangled.&amp;nbsp; You can leave things as neat and well-laid out as you like, but once you close the server room door and turn the lights off, those cables start to squirm and wriggle, and eventually end up in a state that makes a bird's nest look like a rigidly formatted mathematical progression.&amp;nbsp; There's a Nobel prize waiting for the first person to invent tangle-proof patch cables.&lt;/p&gt; &lt;p&gt;Eventually, the cables reach a state of complete instability - the knots are so complex and topologically impossible that reality can no longer support their existence.&amp;nbsp; And poof - no more network cable.&amp;nbsp; Note that this only happens to cables that are not in use - there must be some extra dose of stability introduced by the passage of TCP/IP packets up and down the line, something that helps the cable keep a tenuous grip on existence.&amp;nbsp; But for those wires left on the side, or simply attached to dead port switches there's no hope.&amp;nbsp; Eventually they will pass over the edge of normality and there's a small collapse of matter in that region.&amp;nbsp; It must be small, because no energy is released - possibly because it's all taken up in maintaining the complexity of the knots.&amp;nbsp; And so, when you come to look for spare cables for that essential new link, and you remember buying a dozen or so 1 metre patches just a month ago, but none are there, then you have proof that matter can destroyed without trace.&lt;/p&gt; &lt;p&gt;Either that, or one of your co-workers has nabbed them for another site.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-3601960710162899590?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=3601960710162899590' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3601960710162899590'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3601960710162899590'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2008/09/on-instability-of-reality.html' title='On the instability of reality'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-1890651750206267104</id><published>2008-08-26T18:46:00.001+01:00</published><updated>2008-08-26T18:46:53.194+01:00</updated><title type='text'>YAMNMP</title><content type='html'>&lt;p&gt;This blog is rapidly becoming a clearing house for Microsoft Network Monitor problems.&amp;nbsp; The latest is an issue with Firefox - if you're trying to download add-ons or extensions for Firefox, and receive a "Download Error -228" in place of the desired coloured tabs or whatever, just disconnect MNM from the network settings and try again.&lt;/p&gt; &lt;p&gt;The acronym?&amp;nbsp; Yet Another Microsoft Network Monitor Problem.&lt;/p&gt; &lt;p&gt;The solution?&amp;nbsp; Works for me (which is an acceptable bugfix resolution code as far as I'm concerned).&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-1890651750206267104?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=1890651750206267104' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1890651750206267104'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1890651750206267104'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2008/08/yamnmp.html' title='YAMNMP'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-401741944379680953</id><published>2008-08-25T21:04:00.001+01:00</published><updated>2008-08-25T21:04:19.511+01:00</updated><title type='text'>How to handle a file</title><content type='html'>&lt;p&gt;Occasionally, I come across a problem that, while annoying, isn't really going to be any kind of a show stopper.&amp;nbsp; I'll work at it for a while, then eventually decide that it's too much trouble, put it on one side and forget completely about it.&amp;nbsp; Until I notice that whatever it was still hasn't been resolved, then I'll start worrying at the bit for a while again... and so on and so on.&lt;/p&gt; &lt;p&gt;One of these problems is the inordinate number of file handles that one of my system processes seems to use up over time.&amp;nbsp; I'm referring to a process called 'audiodg', which is apparently associated with removing the DRM data that may be attached to various audio files before permitting other processes to play the file.&amp;nbsp; It's another puny attempt to control access to data.&amp;nbsp; (Hint to MS and various music publishers - someone, somewhere WILL crack whatever protections you use, and then it's all downhill from there on.&amp;nbsp; Why waste your time, our resources and everyone's patience chasing a goal that's unobtainable?)&lt;/p&gt; &lt;p&gt;Audiodg is run as a protected process, to stop all those nasty hackers from breaking whatever DRM the publishers have added (see above).&amp;nbsp; This means you can't easily see what it is up to.&amp;nbsp; However, when it is listed as holding in excess of 4 million file handles after a day or so running, I think questions of exactly what it is up to become irrelevant: what interests me is how to stop it.&lt;/p&gt; &lt;p&gt;Fortunately, the cure is very simple - stop and restart the audiosrv service.&amp;nbsp; This kills and recreates the audiodg process, with a nice clean no-handle instantiation.&amp;nbsp; It doesn't stay that way, but it does at least work reproducibly.&lt;/p&gt; &lt;p&gt;Give the nature of the beast, info is not easy to find.&amp;nbsp; I can't see anyone else complaining about this problem elsewhere, so perhaps there's something odd in my setup.&amp;nbsp; I had put it down to the SoundMAX audio driver, but I'm not so confidant that this is the real culprit - surely if that were the case someone else would have seen and reported this.&amp;nbsp; In the meantime, having just restarted the service, I'll probably forget all about the issue - until I notice the system running slowly and chewing up memory like there's no tomorrow again.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-401741944379680953?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=401741944379680953' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/401741944379680953'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/401741944379680953'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2008/08/how-to-handle-file.html' title='How to handle a file'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-3738700517354777580</id><published>2008-08-17T19:04:00.001+01:00</published><updated>2008-08-17T19:04:42.481+01:00</updated><title type='text'>I learn something every week</title><content type='html'>&lt;p&gt;Two little snippets of knowledge picked up this week, both in answer to some issues that have been troubling me for some time.&amp;nbsp; I offer them here on the offchance that they will be picked up by whatever search engines happen to come across these pages, and will prove of use to others seeking answers.&lt;/p&gt; &lt;p&gt;1) Microsoft Network Monitor 3.1 can be a right pain.&amp;nbsp; There's some kind of problem between MNM and the Intel wireless network card in some laptops (specifically, in my case, a Dell Precision) which results in a runaway state on boot-up where the SYSTEM process chews up CPU time and memory usage goes up and up.&amp;nbsp; Eventually, various peripherals such as a USB mouse and even the keyboard stop working and it's BRB (Big Red Button) time.&amp;nbsp; Re-booting &lt;em&gt;sometimes&lt;/em&gt; works, but equally often just allows the same thing to happen.&amp;nbsp; I've had up to five reboots before I end up with a usable system.&amp;nbsp; The trick (once you do manage to get logged in) is to disable to Network Monitor Driver in the adaptor network properties.&amp;nbsp; All seems to work nicely then&lt;/p&gt; &lt;p&gt;2) Vista does nasty things to some 'shared' files.&amp;nbsp; I have to report a very unusual source for this snippet - although we've been actively using Vista for over a year now, I hadn't seen either the problem or the solution until recently.&amp;nbsp; The nature of the issue is that supposedly shared files aren't always - they can disappear when another user logs on to the local system.&amp;nbsp; This is because Vista tries to virtualise data wherever possible, moving it from the normal 'Program Files' area to a hidden folder in the &lt;strong&gt;user's&lt;/strong&gt; individual 'Local' tree.&amp;nbsp; (There's one oddity which explains why we haven't seen this before - disabling UAC apparently prevents this behaviour.&amp;nbsp; Although Microsoft would probably disapprove, this is exactly what we do as soon as we get hold of a Vista PC.)&amp;nbsp; Where did I come across this?&amp;nbsp; In Usenet, of all places in the uk.rec.motorcycling group, a source of knowledge that is unequalled anywhere else on the 'Net.&lt;/p&gt; &lt;p&gt;That's it for this week.&amp;nbsp; If anything else of interest comes up, you can read it here - assuming the search engines do manage to find this.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-3738700517354777580?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=3738700517354777580' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3738700517354777580'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/3738700517354777580'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2008/08/i-learn-something-every-week.html' title='I learn something every week'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-1112050037239381798</id><published>2008-07-22T20:12:00.001+01:00</published><updated>2008-07-22T20:12:24.504+01:00</updated><title type='text'>I've been given the sack</title><content type='html'>&lt;p&gt;Not quite a 'gadget', but |I've just taken delivery of a new rucksack.&amp;nbsp; Hardly earth-shaking, but it looks like it will resolve a couple of problems.&amp;nbsp; I've been looking for a reasonably discrete way of carrying both a laptop and my camera gear round, and the Lowepro Fastpack 250 fills the bill.&amp;nbsp; It holds a 15.4" widescreen laptop (Dell - tick), a large camera (translate - Nikon plus battery pack - tick), extra lenses, memory cards, something termed 'personal accessories', etc.&amp;nbsp; About the only area where I'd take issue with the description is that the bag is intended to hold a flash unit - so far, I haven't been able to find a way of fitting my SB-600 in without straining the zips unmercifully.&amp;nbsp; So it stays out for the time being. &lt;/p&gt; &lt;p&gt;The rucksack has a waist strap, and fully loaded is relatively comfortable when worn properly.&amp;nbsp; Lots of pockets and little hideaways for, well, hiding things away.&lt;/p&gt; &lt;p&gt;The nice bit about it is that it's a side-loader, i.e. by swinging the bag around on the left shoulder you can remove the camera without taking the bag off completely.&amp;nbsp; Whilst this is helpful in that you don't need to shrug the bag off completely, I'm thinking it will take some time to get the hang of it to get to the stage where it's much quicker.&lt;/p&gt; &lt;p&gt;The bag is described as meeting airline restrictions for carry-on luggage, and while I'd think it was stretching the limits a bit, it's certainly nowhere near the size of some bags I've seen being slung into an overhead locker.&amp;nbsp; I seriously wonder how the passengers involved can think these are reasonable - I swear I saw one the size of a cricket bag (that's the luggage, not the passenger) once.&lt;/p&gt; &lt;p&gt;Conclusion - looks like I'm going to recommend this.&amp;nbsp; Of course, it will have to stand up to the wear and tear of daily trips, probably not always fully loaded with gear, but my bags tend to either fail early, or make the grade over extended use.&amp;nbsp; By all reports, the Lowepro's are reasonably well-made and don't seem to suffer from poor workmanship.&amp;nbsp; Some of the zips seems a little small for the loads they are expected to take, but perhaps that's just because I always try to cram more in than the bag is designed to take.&amp;nbsp; Time will tell.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-1112050037239381798?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=1112050037239381798' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1112050037239381798'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1112050037239381798'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2008/07/i-been-given-sack.html' title='I&amp;#39;ve been given the sack'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7959034.post-1868075259678321028</id><published>2008-07-16T23:03:00.001+01:00</published><updated>2008-07-16T23:03:43.532+01:00</updated><title type='text'>It's high time</title><content type='html'>&lt;p&gt;About 25 metres high, if the kite lines stretch to that.&amp;nbsp; Yes, time to invest in some new nylon and string in the form of another power kite.&amp;nbsp; Having taken the 3 m2 one out last weekend, and only just got it airborne due to lack of sufficient wind, a larger model is clearly necessary.&lt;/p&gt; &lt;p&gt;OK, this is me getting 'need' and 'want' mixed up again, but it's in a good cause.&amp;nbsp; Really!&amp;nbsp; Kite flying is just about the most exercise you can have without actually have to get up and do something strenuous.&amp;nbsp; Yes, it's really good for you, promotes health (if not wealth).&amp;nbsp; You're concentrating on what that sheet of fabric is doing (or, if you're better at it than I am, what it is about to do) so much that you don't realise until after half an hour or so just what strain this has been putting on your arms.&amp;nbsp; But at that point it's brought home with startling clarity just what a strain it has been - the forearm muscles are screaming with cramp, the shoulders ache, and you have a crick in the neck from trying to watch where the kite is, your feet are, and what that horrible little dog is about to do just down the beach - although with a little bit of practice, you can sweep the kite low enough and fast enough to give the dog enough of a fright that it ends up doing whatever it was a long way further down the beach.&lt;/p&gt; &lt;p&gt;So I'm now wondering what to move up to - a kite with sufficient lift to start jumping?&amp;nbsp; Or something with even more traction for pulling me along the ground (scudding)?&amp;nbsp; The thought of trying kite-powered buggying is also attractive, albeit even more expensive.&amp;nbsp; That would suggest the lift option is less likely - but the whole idea of grabbing air just seems to say go for it.&amp;nbsp; Then the idea of the damage I'm likely to do to my knees says "no way".&amp;nbsp; I'll probably settle for a 5 or possibly 7 metre intermediate kite - nothing too basic, but not a sports model.&amp;nbsp; Although kites used to be a kid's game, I suspect the extreme powerkites&amp;nbsp; have not matured quite enough to be suited to my advanced years.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7959034-1868075259678321028?l=blog.pemur.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7959034&amp;postID=1868075259678321028' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1868075259678321028'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7959034/posts/default/1868075259678321028'/><link rel='alternate' type='text/html' href='http://blog.pemur.com/2008/07/it-high-time.html' title='It&amp;#39;s high time'/><author><name>Pete Murray</name><uri>http://www.blogger.com/profile/17186814543629326358</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://bp0.blogger.com/_NyBDWLGAvQc/R5ylZBIipKI/AAAAAAAAAAQ/sFpLCc3NyN0/S220/DSCN0024.JPG'/></author><thr:total>0</thr:total></entry></feed>
