. . . but it's also the last 8 years of the millions using XP that have gathered a whole pile of System Config. tweaks / adjustments etc.
including Group Policies / Security Policies
Reg. edits etc.
applying your favorite hacks can take a lot of time if you use a bunch of them,
also, it's been 2 years since SP3 released, and there are almost 100 more updates to apply
a clean install today will DL over 70 Updates not including IE or WMP
and I've found that allowing multiple updates to install on a fresh install will almost always guarantee several
"Failed Updates"
which will need to be removed with the ...\spuninst\spuninst.exe
and then re-applied
since I've set the policy here that all updates are to be applied individually
we've have never had to remove & repeat any.
installing individually isn't that much trouble on a regular MS Crash Tuesday
but, it takes a good chunk of time when doing a fresh install
_ _ _ _ _ _ _ _ _ _ _ _ _ _
clonezilla:
- I use BESR (Backup Exec System Recovery)
and I have every base image taken right from the beginning
but to restore to the fresh install image will take down all my programs & SW activations etc.,
as this system has been up for 3 years now.
I don't mind restoring to a previous image of no more than a month or two old but that won't solve this problem as it's been an ongoing problem getting worse & worse
if I absolutely have to I'd rather do a fresh install than use the first install image for this system as so much of it has been changed since the initial build
including
- SP1 to SP2 to SP3
- Doubling the RAM:
original install 2GB 533MHz DDR2,
currently installed 4GB 800MHz DDR2
- Multiplying the HDD space:
original install 2x 298GB HDD,
currently installed,
1 x 298GB
3 x 933GB
1 x 1397GB
- a PCI-e SATA e-SATA Card
- another card reader
- enabled the integrated NIC
it was disabled from the beginning as no networking was needed at the time but adding a bunch of cheap file storage workstations made it necessary to install the network stack