You could use all 4 SATA ports for HDDs, and install using a USB optical drive or stick when needed (which won't be very often..)

Others such as Eli Lily or the UK Gov Dept of Pensions really don't need so many addresses

Someone in the UK government pointed that out recently - it turns out that "Dept of Pensions" allocation is actually used across most of the government as some sort of VPN extranet with various external contractors. Apparently, since they all use different RFC1918 blocks internally, they can't all be VPNed into any single RFC1918 block: they needed a globally-unique block for that purpose.

British Telecom uses the 30.0.0.0/8 block for managing all their customer modems - that block is actually allocated to the US DoD, but they don't allow external access to it anyway, so there's nothing to stop you using that block internally yourself as long as you don't need to communicate with any other networks using the same trick. Better than wasting an entire /8 of global address space just for internal administrative systems - or a /9, like Comcast grabbed back in 2010.

My inner geek - who cares about efficiency - would love to see all the legacy blocks revoked. I'm sure the DoD could use 10/8 instead of 30/8 quite easily for their non-routed block; the universities could easily fit in a /16 instead of a /8, or smaller with a bit of NAT. Still, we should be moving to IPv6 instead now: give each university and ISP a /48, or /32 for big complex networks needing multiple layers. I just have a nasty feeling we're in for a long time of CGNAT spreading instead - where we currently have ISPs that don't offer static IP addresses, in a few years they'll be refusing to issue anything other than a NATted 100.64/16 address.

Well, as I'm a Mac person these days, I've swapped out those sorts of issues for the ones that Apple produce. ;) About the only thing I really miss from Windows is the certainty of knowing when the next lot of security updates are due - at the moment, they're so slack they make Adobe look on-the-ball.

It was IE8. You start off with IE6, even after slipstreaming. I think. I didn't bother testing. I could try another day. I already killed the VM.

...yeah, if I've gotten a slipstreamed install disc with SP3 on it, I could have saved myself a lot of time when I did the same experiment. *shrug*

Out of interest, which version of IE did it have after install completed? I see you were prompted to upgrade to IE8, but my memory is hazy on whether IE7 was ever included on later XP install discs.

I'm aware you can still get XP discs second-hand or ex-stock here in the UK - Amazon lists several versions, although some look suspiciously like they may be OEM versions that are tied to specific brand/model PCs. I'm not aware of any PC maker here in the UK offering an XP options, though - maybe Windows 7, for business systems and workstations.

I recently wiped my old (2003 vintage) laptop, which originally came with XP, and installed Linux Mint - considering the machine's specs, it works fairly well.

I've read about ReactOS, but given the slow pace of progress I regard it as curiosity rather than a viable alternative.

Seriously. I remember trying out the preview version on my then-XP-running PC back in 2009, and being blown away by a) how much easier it was to install and get going, b) how well it ran all my existing software, c) how it let me finally use all of the memory installed in my machine, d) how much better it was than Vista. I pre-ordered a copy soon after, and the rest is history. Now, on my Mac, I have my Windows 7 VM for running various applications I still use.

Installing Windows XP today is not nearly as fun as you might think, particularly if you've got a pre-SP2 copy. When I tried it, I had to manually install some patches just to get Windows Update working, then some more before I could install IE8, and some more before I could install MSE. And then all the patches to bring the whole lot up-to-date - that took hours and hours to finish. I'd only recommend trying it if you're installing onto a machine that you don't actually need to use for a good while.

As for the 'but it's tried and tested" argument for hanging onto XP, I would point to the number of flaws that are still being uncovered in the Windows codebase, many of which are also in XP. Yes, you can mitigate against some by hardening your system, running only as a standard user, etc. - but for most current XP installs that will probably mean extra aggravation caused by third-party software written back in the Bad Old Days that expects to run with full admin privileges.

The only excuse for continuing with XP, to my mind, other than sheer obstinacy, is where you've got systems that absolutely, positively require XP running on physical hardware - specialised hardware or software that won't work via a VM because they need direct access through physical ports. Such systems should be segregated from local networks and the Internet as much as possible.