On Fri, 17 Aug 2007 12:23:55 GMT, "Benny" <no spam
ple@se.com> wrote:
>Thank-you all for your recommendations.
>A fresh install of a new XP licence along with new install of all software
>seems the only way.
>regards
>Benny
It is not the only way.
1) Yes you need a new license for this system if/when the
old license was OEM and sold bundled with the old system.
The new license has to be for the same version of windows,
if you are entering the license key at any time it should be
the license key # from the new certificate of authenticity.
If the new license is not compatible it may not accept that
key.
2) Obviously a fresh installation is the most comprehensive
solution, but it is not actually a solution at all when your
goal was to migrate the existing OS environment, not just
use the same OS version. There are ways to do move the OS
installation, migrate it to another system. Primarily the
problem is that for windows to finish booting it needs to be
able to continue accessing the drive controller on which the
drive booting is connected. At some point in the boot
process the drive controller driver is loaded and needs to
support the new drive controller. There is more info
available by doing a google search, links below.
WinXP will plug-n-play the hardware in the new system,
installing drivers it has *built in* for what it recognizes,
and then requiring you to install remaining drivers
yourself. The issue is that to plug-n-play the new
hardware, windows has to finish booting far enough to be
able to do it, to load enough of it's OS files to be at that
point in the detection and installation process.
Basically you make some adjustments to windows before moving
the drive to the new system. Adding drive controller
registry entries, a few files, and optionally uninstalling
old hardware drivers which are not applicable to the new
hardware. All of this while the OS is running on the old
system, and as others suggested it would be good to make a
backup first - perhaps even two backups to be thorough, one
backup before making any changes at all so the OS still runs
100% as it was on the old system, and one backup after
making all the configuration changes so if there were a case
that it wasn't 100% working on the new system, there is
still a chance to preserve the work you had done to change
it thus far and just do the remaining things needed to
finish modifying the OS installation so it is then ready for
the new system.
Considering that so many people have migrated 2K and XP
installations to other systems by now, it is a bit amazing
that nobody has mentioned it. Even a Google search fairly
specific like,
http://www.google.com/search?q=migra...22&btnG=Search
turns up quite a few relevant hits.
http://www.mostlycreativeworkshop.com/article11.html http://www.ngohq.com/home.php?page=A...read&arc_id=36
It is not 100% guaranteed that these two links or the other
hits windows finds will work 100% of the time, but the
process is straightforward, works a large % of the time
without anything further necessary, and in the worst case
scenario you can alway do the repair or reinstallation if it
fails. Whether it is worthwhile to migrate an existing
installation or do a clean installation can have a lot to do
with how long it would take to recreate your present OS
state. Sometimes it is good to start clean again to get rid
of some bloat accumulated over time, but otherwise a
successfully migrated OS installation can work fine, it is
not subject to "nasty registry errors" as some keep trying
to imply.