Windows 8 Installation Experience

A screenshot of Windows 8 being installed on a VirtualBox virtual machine running on a Mac

On Saturday, I decided to upgrade to Windows 8. I’ve been running a virtual machine with Windows Vista Business for some time, firstly in Parallels Desktop but later converted to VirtualBox. I never bothered upgrading to Windows 7 due to the lack of differences between the two; obviously 7 is a big upgrade from XP but not from Vista.

Another major factor is that, at the moment, existing Windows XP, Vista and 7 users can upgrade to Windows 8 Pro for a mere £24.99 as a digital download, or more if you need it on DVD. It’s a very good deal, but it’s only valid until early next year. And since I’d also heard that Windows 8 should run faster on the same hardware, upgrading seemed like a really good idea.

To upgrade, you should download the Upgrade Assistant which checks your current installation for compatibility and then downloads the files. You can then either proceed with the upgrade, or save an ISO file to a USB drive or DVD-ROM. I decided to proceed, but told the installer not to keep any of my documents or settings; after all, it was a virtual machine and anything important had been saved to Dropbox and was therefore available elsewhere.

This turned out to be a mistake, frankly. It installed the files, restarted a couple of times, and then froze. No animation, no CPU activity, no disk activity. So, I hard reset the virtual machine. At which point, setup decided that the installation had failed, and set about restoring Windows Vista. So, after a few hours, I was back at square one.

This time, I told the installer to save the ISO file, which I placed in a shared folder so it was accessible by my Mac as well. I then shut down the virtual machine, and created a fresh, new VM in VirtualBox with the optimal Windows 8 settings. Bear in mind that my previous VM was originally a Parallels VM, was then converted to the VMWare format, and then used with VirtualBox 2; now I’m on VirtualBox 4.2. I mounted the ISO file mounted as the CD drive, booted up, followed the instructions, and within the hour I was up and running with Windows 8. Success!

…or so I thought. Opening the ‘classic’ desktop environment saw the little icon for the Windows Action Centre pop up, telling me I needed to activate Windows – which was odd because I had entered the product key during installation. So I re-entered it, only for Windows to pop up a 0xC004F601 error, telling me that the product key was only valid for upgrades and not a clean installation like this one.

Some expletives were issued by me at this point, but thankfully Google saved my sanity as I found this blog post which explained a workaround. I had to edit the registry to change a value, re-run the activation manager and then reboot, but after this Windows activated with no problems. Phew.

Obviously I still have the old Windows Vista VM lying around but as that license is now invalid due to the upgrade I’ll be deleting it. That, and I shouldn’t need it anyway.

I’ll write more about my actual experiences of using Windows 8 when I’ve had a longer opportunity to use it. So far, it seems okay, and the ‘classic’ desktop is almost exactly the same as Windows 7. I’ll have to play with the new desktop (formally known as ‘Metro’) a little more before passing judgement.

Parting the Mists

The login screen for World of Warcraft: Mists of Pandaria, showing a 15 minute waiting time to login

I’m writing this blog post whilst waiting to connect to play a bit of World of Warcraft: Mists of Pandaria. Although the game has been out for several weeks, a combination of a lack of spare time and the server being full (as shown in the screenshot) with queue times exceeding an hour, has meant that my main character is only level 86. That said, I’ve managed to get around 12 hours of playtime in the new expansion, and, generally, I like it.

As you will know, if you’re a long-term reader, I’ve been a World of Warcraft player since June 2006, although I’ve not played as much since 2009 when I quit regular raiding and decided to just become a casual player. I’ve therefore played every expansion, and also the classic pre-expansion game as well.

Prior to Mists of Pandaria, the second expansion, Wrath of the Lich King, was my favourite. It built on the improvements of the first expansion, The Burning Crusade, but had a much better story, and some great quests – the Wrathgate and ensuing Battle for Undercity being especially memorable. The third expansion, Cataclysm, wasn’t quite so good; there wasn’t much to it in terms of max-level content (the release of the expansion coincided with a complete rework of the original game content, so resources would have been split), and it felt disjointed as the new zones were spread out without a strong consistent story between them.

I’m therefore glad that Blizzard has reverted to its classic expansion formula for Mists of Pandaria, where there is plenty of new content, on one new continent. And there certainly seems to be plenty of content – I’m about 39% of the way to level 90 and I’ve only managed to finish the first zone and a bit of the second; there are seven new zones in all. And the quests in that first zone, although less strictly linear than before, all led to one big plot moment at the end which was great. Like with the first two expansions, you can’t use flying mounts until late on in the new content, which also helps to provide the immersive experience that Cataclysm lacked. Although I’m a long way away from level 90, I also gather that there’s a lot more to do when I get there.

…And now I’m connected. It took 20 minutes rather than 15. The screenshot lies.

The probable abandonment of Twitter’s official OS X app

Update: Since this article was posted in October 2012, the official Twitter for Mac client has actually been updated. An April 2013 blog post from Twitter explains this.

Bird

It has now been well over a year since the official Twitter app for OS X was last updated. It launched with the Mac App Store in January 2011, and the most recent version, for Snow Leopard, was released in June 2011. Since then both Lion and now Mountain Lion have come along, and yet Twitter haven’t made any changes.

Early signs of ‘bit rot’ are setting in:

  • There’s no support for posting images using Twitter’s own image service (pic.twitter.com) – you have to use a third-party service
  • Of those third-party services, pix.im is listed but it no longer works
  • The app’s icon doesn’t use the revised Twitter logo from June
  • Promoted tweets and trending topics do not show in the timelines, as they do on the web and in the official mobile clients

It’s a shame to see the official client abandoned in this way. I used it as my main Mac desktop client for quite some time, before switching to Osfoora and then Tweetbot for Mac. And before January 2011 I used Tweetie, which was bought by Twitter and became Twitter for Mac. It’s especially concerning when Twitter has been discouraging third parties from developing ‘traditional’ timeline clients, because at present it’s the third-party clients that offer up-to-date features.