Vista and Misbehaviour
Mar30
Well, yesterday I finally bit the bullet and installed Vista.
Ow.
The aim of the game was to install Vista on an entirely separate partition from XP, partly for testing, and partly because I didn’t trust Vista’s compatability levelse etc.
It failed to install the first couple of times – just froze on the Expanding Files section without any progress bar.
After a couple of tries, it then trashed my XP install so that XP wouldn’t boot (a nice BSOD going on about HAL.DLL and with lovely hex digits on it. It’s been a long time… XP must be more stable than I realised).
Some help from Steve sorted out the disk partitioning, which seems to have caused some of the problems. This required an Ubuntu LiveCD. Which just goes to show how far Linux has come, when you’re booting it from a CD to fix problems with a box intended for Window. I wish every OS was as friendly.
So, Vista finally installed. Lack of wireless drivers soon sorted out. Still no working XP until I fiddled around with boot.ini this morning, after realising the logical names for the partitions had got screwed. So, happily, XP and Vista now both run.
But as for Vista… *sigh*
This damned new security model is just so frustrating. That Apple advert isn’t so far off the mark. Almost everything I’ve tried to do in the last day or so has popped up a ‘are you sure?’ security warning, sometimes three or four. It’s unbelievable.
The only real problems/nagging annoyances I’ve had so far are from things like haXe, which works fine (apart from the installer, but not a big issue) but accesses the registry every time the compiler runs – which pops up a security alert! It’s a command-line compiler and part of our Ant build system – and do you know how annoying it is to type ant then click a dialogue every time I rebuild? (Typically a couple of times every five minutes at the moment). Yes, it may be an issue that haXe accesses the registry (Nicolas is going to take a look at it) but, really, is it that much of a security risk..?
Edit: If you set up your command-prompt to have administrator privileges it seems to get rid of the haXe issue. Not ideal, but better.

