Going commando, possibly culottes

I'm fairly meticulous about planning trips. Dunno why, I just hate rushing and end up being late for ferries, aircraft etc etc. I also like to know where I'm spending the night - hence pre-booking hotels, locating them on the map and entering the coordinates (twice) into the Garmin.

We're doing a tripette to France with our friends at the end of May, they're going in their MGF-180 and we're going in the smart Roadster. Should be fun...

However, the French seem very keen to keep the English out (no change there then), because the first hotel directions are "turn right at the D976" but fail to specify which particular right turn. The booking website gives one location and the one from the hotel chain website lists another, neither of which are in the Garmin database. I have two manual Garmin entries "Hotel1a" & "Hotel1b" just in case. You never know, I may even get an answer to my email before we go.

The second directions are "turn right at the D56 and it's about 2km down there", and of course 2km "down there" is in a river. When I emailed them for a multimap url and/or GPS coordinates I got the reply - " Quoi? We do nit 'ave a computรจre"

Comments

Post a Comment

Popular posts from this blog

"The delivery extension for this subscription could not be loaded" when using SSRS

Image
OK, so we upgraded our server farm and put on the latest "stuff" (SSRS, SQL Server etc.) and the engineers gave me two servers to play with - SQL01 & SQL02. The idea being that we used high availability to help keep the factory running. We employed a contractor to load up and configure everything. At this point I wasn't involved. My involvement was to move all the reports and subscriptions from the old servers to the new ones once the servers had been configured. All went swimmingly, until I actually started to fire off the subscriptions to test them. Randomly (like 5 out of 10) I got the error in the title. I would edit the failing subscription and/or change the schedule time and it would work. I finally got around to moving 81 subscriptions for the same report (all slightly different parameters going to about 6 different engineers). I press the "go" button and every single one failed. Let's cut out the long story about how I went through about
Read more

Oooh, look, an Eagle...

Image
The Scottish Holiday . After the trauma of the Astra-breakdown episode and the gutless hirecar, we'd recovered sufficiently to begin to enjoy the rest of our holiday with our friends at the Castle... Chapter Seven: One of the things my wife really wanted to see was a seal, or seals if she was really lucky. So we decided to take a day out and around the Mull Of Kintyre. We stopped at "St Columba's Footprints" and carefully studied the jumbled collection of rocks and seaweed. "No seals there dear, let's carry on" "Oh, alright then, never mind. But that's where we were told they are most likely to be." We drove on and took a gated road signposted " To The Lighthouse ". This took us right up into the hills. As we were driving slowly along admiring the view, my wife whispered quietly... " Ooh, look an Eagle! " "Stop that, that's not funny." "No, really. Stop the car."
Read more

SQL Server 2008 / Reporting Services

Image
Since this has taken me four days to solve this one and, with almost no help from Google, I thought I'd log it here in case anyone else has this most bizarre problem. Scenario: You retrospectively install Reporting Services to an existing installation of SQL Server 2008. You try to configure it using "Reporting Services Configuration Manager" and as soon as you click "Find" you get "Invalid Class" 1 and no other information. These two links gave me the clue, they're essentially both the same. What they say is to run WBEMTEST 3 and connect to the Reporting Services WMI thingy. Then run the query, " SELECT * FROM __NAMESPACE ". When I did this I got: Note: TWO entries. The second one was a test database I had installed months ago and had removed at some point when I worked out that using the default instance of MSSQLSERVER was more convenient - but the registry(?) entries were still hanging around. I selected it by clicking o
Read more