tin_can

That one that looks like a USB connector will be a DisplayPort, uh, port. :)

I can't believe there is a limit that it is impossible to reinstall beyond. Such a limit would have to be advertised, and would be hugely unpopular. Instead, I would imagine they use a similar system to their operating systems, office software, etc. - ie. the software 'knows' what hardware it is installed on, and checks that it is activated every so often. If the hardware changes, you have to re-activate, invalidating its use on the old hardware. They may make you jump through some hoops if you reinstall a lot (like the phone call trisager mentioned) but I can't see them actually removing the ability to reinstall full stop at any time.

Another vote for Acronis True Image here. I personally use it to create an image-based backup of the entire computer, stored on a couple of external hard drives - I make a new image every couple of weeks, and then update it with incremental backups overnight every night (it only takes 10-20 minutes-ish). Plus a couple of encrypted copies that live in my locker at work, but that's because I'm paranoid and geekish about these things. ;) I've been grateful for the backups a number of times!

Oh, I had this problem too (except that it was me who plugged the devices into whichever USB ports, not the maid ). I found that reinstalling the driver (over the top of the previous installation) with the device plugged into the 'new' port rectified the problem, and didn't stop the 'previous' USB port from working either. So in the end, I just reinstalled the driver with each component plugged into each USB port (including different ports on a hub), so that now any port works fine.

There won't be any problems with software activation, but there is a small chance you could get other issues like your system failing to boot, or stuff like that. Generally, I think, BIOSes are updated to fix bugs, to make them (and therefore the whole computer) run faster, or to include support for more hardware. Personally, I give it a good couple of months after a new BIOS has been released and check forums etc. for any issues they might cause before updating, so as to hopefully let any common problems pass me by.

You're absolutely right, of course. Personally, I like to know what's going on behind the scenes as much as possible ( :( ), but having found that out I might well use EasyBCD myself.Btw, as I'm new to these forums (and to modern flight-simming in general), do you know whether there's a "hi, I'm tin can, nice to meet you" section? I had a look around and couldn't see one, and it feels a little strange jumping in without saying hi first!

I'm not trying to compete with your method, just sharing this little bit of information that I have come across in my time. IMC should use whichever solution he likes, or another. :shrug:

Found it! See here for details - EasyBCD not necessary. (The instructions are from the free version of Windows Secrets, a newsletter that I subscribe to and recommend for general tips & tricks, and general tech and security news, though it's mainly geared to business.)

I'm sure I remember reading there is a way of installing XP into a multi-boot configuration with Vista with Vista already installed - let me rummage around a little and see if I can dig the method out - brb...

Thanks a million for starting this informative and inspirational thread, Noel! :( A little question: how are your monitors mounted? I'm in my very early days of flight-simming, and would like to build a system that one day builds into something along your lines (currently I've got just got a self-built computer with 24" WS monitor and the Saitek yoke, throttle and rudder pedals). I'm trying to work out some way of mounting monitors to a desk (I live in rented accommodation, and want to try to avoid having to screw brackets into the wall) in a way that I can expand as the system grows, perhaps using something like these. I'm not sure how easy it would be to use that kind of thing for the overhead panel monitor(s)...It'd be great to hear how others have got around these problems. :)