• The Storm Ate my Broadband

    Like many in the country, the storm has left me feeling somewhat isolated - that is to say my broadband is down. Don't get me wrong, I'm just glad the power is (mostly) back, and I'm far better off than some who've had their lives affected.

    The simple fact, though, is that I have things I need to do, and not having a broadband connection really gets in the way of that.

    Living where I do, there's precisely one place in the house that gets a 3G signal, unfortunately that place isn't particularly conducive to sitting comfortably. Whilst the Wifi hotspot functionality on my phone helps, the range isn't great enough to let me sit somewhere that I might be able to concentrate.

    So, somewhat convoluted workaround needed;

  • Virtualisation: Google Play Music Manager cannot identify your computer

    Although there seem to be an increasing number of things which irritate me about Google's Play Music, there's no denying that it's an incredibly convenient way to listen to music when not at home. Whether using the Android App, or playing in a browser, it makes your library available wherever you are.

    It's a pity then, that Google have decided to make it such a royal PITA to upload music (I'm also not too happy about the requirement to have card details on file, even if you plan on using the free version - you should only ever need to provide card details when the plan is to actually use them, it reduces the likelihood of them being compromised).

    As Google's Play Music Manager now won't run on my desktop (something I need more introduces a conflicting dependency , I figured I'd run Music Manager in a virtual machine and just point it at the right NFS share.

    Turns out it wasn't quite so simple, as Music Manager returns the error 'Login failed. Could not identify your computer'.

    After some digging, it's incredibly easy to resolve though.