You may be aware that I get a number of comments, observations, mickey-takes etc about this blog during the week and many of them – most really – come direct through one of my e-mail addresses as most 'regulars' have long since got to know them. I sometimes forget though that others use the 'contact page' on the Weekend Rails website and occasionally this can give a spot of bother.
Grr, Microsoft. I was (notice the past tense) running Windows 7 and was perfectly happy with it, hiding behind my Firewall and Anti-virus, Anti-Malware, anti-everything softwares. And what does Microsoft do? While my back is turned, under the pretense of it being an 'upgrade' to Windows 7, they calmly change my operating system to Windows 10 without my permission and lumber me with software I don't want (but Microsoft knows better and believes I cannot live without) and a changed system that is so radically different that a number of the programs I already have won't work anymore.
A pile of drawings arrived from an e-bay seller during the week. Ostensibly all of '04' class locos, some of them were relevant to '03s', several were duplicated, and some turned out to refer to the unique Southern 0-6-0DM numbered DS1173 (but inexplicably referred to on the drawings as a diesel electric!) which was mechanically like an 04 but whose jackshaft drove onto the middle axle and had a more simplistic style of bodywork. Ah well, I'm sure it will all come in handy some time.
I did say a couple of weeks ago that I would be reporting more about the inspection of the Mattersons after Allianz had decided to up the rate for LOLER inspection because it wasn't '4 locomotive jacks', rather 'a locomotive lift and two beams'. Well fairly early on Tuesday morning I was back at the Shed, opening up for another inspector.
I picked the title this week and wondered whether to start off with a “hell fire and brimstone” sermon. You know the sort of thing, you can find it on obscure satellite and cable channels, with some smartly-suited guy sat behind a desk, pronouncing how Man has lost his way and only by following the word of the Lord (or his interpretation of it) in the 'good book' (pick title of yours or his choices) can we redeem ourselves and gain ever-lasting salvation. (And there's a thought, we all know what is meant by the “good book”, but what would we understand to be meant by a “bad book”?) But then sermons aren't really my style. Meandering reminiscences, technical dissertations, maybe, but sermonising on Weekend Rails? Hardly.
A fair amount of variety in the illustrations this week, and for most of them, I must thank Steph as she has been around to record some of what has been going on. That of course means that even camera-shy me has turned up in a few, but I hope that won't put you off your breakfast/lunch/dinner.
With D8 “Penyghent” having a holiday at Etches Park, it was down to '901 to maintain the diesel end of Peak Rail services, and not only was there a Tuesday and Wednesday but a Thursday too. With only two passed drivers that meant I was rostered for two of the midweek days and then Saturday, so no rest for the wicked.
After the frenetic activity of last week, a quiet interlude perhaps? Not a hope.
As we drove back this evening, Andrew and I were trying to work out exactly what we did each day this week and were struggling to slot it all into place. The trouble is, he has had the week off (although you wouldn't believe it from the number of phone calls he's taken) and I had sort of agreed that I would keep pace with him, so let's see if I can get it right and in logical order.
As usual there's a hec of a lot to get through, so here goes....
Firstly, my apologies if you have had difficulties getting on to Weekend Rails this week. As I write this, people are telling me that they are getting server error messages. Now I “check” WR (and Andrew Briddon Locos) every day, a legacy of the trouble that has been caused by past hacking attempts (as a matter of interest, there have been over 500 spurious attempts to “log-in” to my side of WR this month) but I do so by means of the monitoring package which has been unaffected, so remained unaware. Hopefully it will not take long to fix.