The first isn’t actual strictly speaking a Blog at all as such, other than in name, as I can’t link to it via my blog listings and so you can find it listed under ‘Useful Resources’ in the right-hand sidebar or click on its name here (highlighted in blue). Entitled; Michael Masterson’s The Spanking Blog it is a spanking photo studio site with loads of free spanking galleries for you to investigate (I didn’t have time myself on my visit – but I’m going back later). The other I came across was Spanking Porn-blog which can be found in the sidebar blog listing in the conventional manner. You can also go see it for yourself directly from here, as above.
Yesterday I got stuck working away from home, so could work on the book but had no WiFi access for the day. Today I’m hard at it once again and even I hope to do a little prelim work on the design of the book cover later – something that excites me greatly!
I was actually quite industrious yesterday – despite being away from home - and very nearly finished the last chapter of the new book, which I have now put in place in book form (although I shall have to do a little more to it shortly, when I finish this). Despite this and despite returning home late (near midnight) I managed to update my PicasaWeb albums (right-hand sidebar) adding more scanned catalogue pics to the 1960s – 1970s Alexandra workwear album and creating a whole new album entitled Prison Uniforms that concentrates on prison uniform dresses. The problem regarding PicasaWeb deleting certain spanking art folders from my assemblage some time ago – notably the work of Hobbs / Thorn I am working on circumventing by way of creating a public DropBox folder that I shall then post a link to here. If that works, and within the limitations of the storage space available, I shall create folders of all sorts of scanned and / or downloaded stuff that has inspired and fired me up over the years for you to explore and that I have archived.
It's bloody snowing here now, freezing - I thought global warming was supposed to take care of all that. The good news is that it helps put me off going to the pub for a while. I'm saving that up for closer to Christmas. Not Christmas itself, though, as my other half doesn't drink much and so I try to abstain and instead get my kicks by going for food that I would not ordinarily allow myself. We are going to be off to a nice (I hope) hotel in Ascot, where the famous Royal Ascot horse race course is and not far from Windsor and the Thames; might even try a little fishing on Boxing Day.
Or a more negative note: I have a chest infection that has gone on for weeks and that seems to gradually ease off only to worsen again after each visit to the gym. The upside (I suppose) is that, what with the inclement weather and my hacking cough, I am confined to the home today and so after a brief blog update will be hopefully getting a lot done towards getting this book thing finished.
On the subject of the blog: I went away for the weekend to the ‘Other Half's’ place - as always - and although it would be difficult to do much towards finishing the book while there I nevertheless intended to get a blog update posted. Accordingly I took all source materials I would need with me on a data stick.
I arrived to find a hysterical woman journalist / lecturer (namely 'The Other Half') and a computer that had fallen over and that now displayed unblinkingly the dreaded Windows blue screen, a hole batch of hexadecimal memory addresses and error codes and the information that it had ''performed a dump - mmm, nice! (a little too much information there, on all sorts of levels - taking a 'dump' can have a whole different meaning here in London). She had tried to transfer some work she had completed onto a data stick... and down it had gone - just like that. Further investigation showed the hard drive to be so full as to barely allow Windows to operate (she only has 512 Mb of RAM). I used the Windows disk cleanup utility, compressed some files and off it went again... only to fail to download and install a Windows update a few hours later. The cause? Insufficient disk space - the free space was down to a couple of hundred megabytes again. Interestingly, thinking back I seemed to recall that earlier in the year when last I had checked there had been about 15 Gb of free space on that drive, and she only deals in text , a few still pics and PowerPoint presentations, things like that and nothing flash either. Obviously I suspected a virus of some flavour. I trawled through the hard drive looking for some overly enormous usage some place - and found it! Symantic Norton antivirus: in the programs, common, directory a directory labeled Symantic was 15Gb in size! Closer inspection showed the culprit to be the virus signatures folder which was bulging at the seams with 12.8 Gb of signatures, temp files and the rest.
To cut a long story short; the thing seemed unstoppable. I would tell it to empty its temp cache, and it would - only to fill it up again almost immediately. I reduced the disc space allowed for Norton's temp files, but to no avail. Then, while still investigating the problem and having again freed up disc space by compressing old files, Norton proudly announced that it was trying to update and would I kindly make more disk space available to it on the hard drive as it was having a little difficulty (or words ti that effect)... Ahhhh! Poor thing!
That was it: I knew then it had to die... Die!... DIE!!!! ARRRGH! Not so easy to kill off though - it is an antivirus program after all! I had first to stop it loading on start up it turned out. So off I went to the registry and pulled out its plug. Then it was back to the Windows Add / Remove utility, a gun to its head BANG it was dispatched.
I'd always hated Norton, right from the start. It took up too much memory and would slow her ancient (2002) computer to a snail's pace. To be honest, though; originally her machine had run quite happily with 256 Mb RAM - even with Norton - until she'd had added the latest version of Norton, a few years back. Then it had ground practically to a standstill and a little investigation soon showed that Norton itself was taking up 128 Mb for its own use. Thus I upped the memory to 512 Mb for her (she didn't want to spend much - she's of Scottish ancestry; I'm sure you understand. Ha! Ha! No offence meant to any of you from the other side of The Wall, you must understand – that of Hadrian's constructing of course). I have now replaced Norton with Avast, which is the antivirus I run here, cleaned up the registry and optimized Windows - and of course defragged the hard drive (which is a tale in of itself - never bother with the Windows XP defragmenter tool is my advice; it's crap, deeply crap!). Now her antique machine is razor sharp (for its vintage). Of course it lacks the punch of my brace of 10,000 RPM Raptors configured in RAID 0 (though strictly speaking that shouldn't be called RAID at all as neither drive is redundant - far from it). Bye for now!