WinXP move to a different motherboard

I am planning on putting a new motherboard in this Windows XP system as the
present one has various problems. I built this system a year and a half ago
with an OEM version of WinXP, purchased with a new hard drive. So as I
understand the EULA, the hard drive is the part that this software is "tied"
to. That's fine with me, since it's just the motherboard that I want to
change anyway.

I presume this will be enough of a change to mean re-activating Windows?

There have been countless updates and upgrades to Windows itself and various
other software (ISP, antivirus, security, etc.) on the system over that year
and a half, and I hate to do all that all over again, so I am wondering if
there's any reason I can't just change the motherboard and keep the existing
hard drive as is, rather than doing a reinstall. The present board has a VIA
chipset and the new one will also, so I should think just a motherboard
drivers update would be all that's necessary, if even that.

Am I missing anything here? (It happens. :-) )

O.G.

Hi

Please try the following article:

"Windows Product Activation (WPA) on Windows XP"
http://aumha.org/win5/a/wpa.htm

--


Will Denny
MS MVP Windows Shell/User
Please reply to the News Groups

"Old Geezer" <nowhere@all.net> wrote in message
news:ej3aw6JDGHA.3140@TK2MSFTNGP14.phx.gbl...
>I am planning on putting a new motherboard in this Windows XP system as the
>present one has various problems. I built this system a year and a half ago
>with an OEM version of WinXP, purchased with a new hard drive. So as I
>understand the EULA, the hard drive is the part that this software is
>"tied" to. That's fine with me, since it's just the motherboard that I want
>to change anyway.
>
> I presume this will be enough of a change to mean re-activating Windows?
>
> There have been countless updates and upgrades to Windows itself and
> various other software (ISP, antivirus, security, etc.) on the system over
> that year and a half, and I hate to do all that all over again, so I am
> wondering if there's any reason I can't just change the motherboard and
> keep the existing hard drive as is, rather than doing a reinstall. The
> present board has a VIA chipset and the new one will also, so I should
> think just a motherboard drivers update would be all that's necessary, if
> even that.
>
> Am I missing anything here? (It happens. :-) )
>
> O.G.
>

The other existing components need to be compatible with the new
motherboard.
You will need to check these out before purchase. Hard drives are
problematic
when it comes to compatibility. It's the other items like memory etc.

Changing a motherboard is likely to prompt reactivation. However, if you get
to
talking to a Microsoft representative just explain that the existing
motherboard
failed.

What are the actual problems with the existing motherboard? How do you know
that the problems will be solved with a new motherboard?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"Old Geezer" <nowhere@all.net> wrote in message
news:ej3aw6JDGHA.3140@TK2MSFTNGP14.phx.gbl...
>I am planning on putting a new motherboard in this Windows XP system as the
>present one has various problems. I built this system a year and a half ago
>with an OEM version of WinXP, purchased with a new hard drive. So as I
>understand the EULA, the hard drive is the part that this software is
>"tied" to. That's fine with me, since it's just the motherboard that I want
>to change anyway.
>
> I presume this will be enough of a change to mean re-activating Windows?
>
> There have been countless updates and upgrades to Windows itself and
> various other software (ISP, antivirus, security, etc.) on the system over
> that year and a half, and I hate to do all that all over again, so I am
> wondering if there's any reason I can't just change the motherboard and
> keep the existing hard drive as is, rather than doing a reinstall. The
> present board has a VIA chipset and the new one will also, so I should
> think just a motherboard drivers update would be all that's necessary, if
> even that.
>
> Am I missing anything here? (It happens. :-) )
>
> O.G.
>

Old Geezer wrote:

> I am planning on putting a new motherboard in this Windows XP system as the
> present one has various problems. I built this system a year and a half ago
> with an OEM version of WinXP, purchased with a new hard drive. So as I
> understand the EULA, the hard drive is the part that this software is "tied"
> to. That's fine with me, since it's just the motherboard that I want to
> change anyway.
>
> I presume this will be enough of a change to mean re-activating Windows?
>
> There have been countless updates and upgrades to Windows itself and various
> other software (ISP, antivirus, security, etc.) on the system over that year
> and a half, and I hate to do all that all over again, so I am wondering if
> there's any reason I can't just change the motherboard and keep the existing
> hard drive as is, rather than doing a reinstall. The present board has a VIA
> chipset and the new one will also, so I should think just a motherboard
> drivers update would be all that's necessary, if even that.
>
> Am I missing anything here? (It happens. :-) )
>
> O.G.

You'll need to do a repair install of XP. Don't try to boot the system
first just to see if it works. Run the repair install first.

http://michaelstevenstech.com/XPrepairinstall.htm

--
Rock
MS MVP Windows - Shell/User

I dont think you mean this;
> Hard drives are
> problematic
> when it comes to compatibility.

"Old Geezer" <nowhere@all.net> wrote in message
news:ej3aw6JDGHA.3140@TK2MSFTNGP14.phx.gbl...
>I am planning on putting a new motherboard in this Windows XP system as the
>present one has various problems. I built this system a year and a half ago
>with an OEM version of WinXP, purchased with a new hard drive. So as I
>understand the EULA, the hard drive is the part that this software is
>"tied" to. That's fine with me, since it's just the motherboard that I want
>to change anyway.
>
> I presume this will be enough of a change to mean re-activating Windows?
>
> There have been countless updates and upgrades to Windows itself and
> various other software (ISP, antivirus, security, etc.) on the system over
> that year and a half, and I hate to do all that all over again, so I am
> wondering if there's any reason I can't just change the motherboard and
> keep the existing hard drive as is, rather than doing a reinstall. The
> present board has a VIA chipset and the new one will also, so I should
> think just a motherboard drivers update would be all that's necessary, if
> even that.
>
> Am I missing anything here? (It happens. :-) )
>
> O.G.


O.G.
I see you've received a number of responses to your query but I'm not sure
they've been totally responsive to the issue you raise, so let me give you
my experience...

It's a crapshoot at best as to whether you'll even be required to
re:activate the system following installation of your new motherboard,
although there's a strong likelihood that activation *will* be necessary.
However, we have encountered a number of instances, similar to your
situation, where the activation process was not required.

In other instances where activation *was* necessary, in some cases it was
automatically accomplished without further ado, and in other instances the
telephone process involving speaking to a MS rep was necessary. After
explaining to the rep the need for a motherboard change to replace a
defective one, in every instance I'm acquainted with, the system was
activated. I'm unaware of any instance where activation was refused under
these circumstances.

Now as to the motherboard change itself...

It is likely, but not necessarily absolute, that you will need to run a
Repair install following the motherboard change as Rock has indicated. And,
of course, I'm sure you're knowledgeable enough to know that you will have
to install the necessary drivers from the motherboard's installation CD
after you install the new motherboard. But there is a real possibility that
the system will boot *without* the need for a Repair install. Even if the
new motherboard is a completely different make/model from the one it's
replacing.

You needn't fear to try to boot with the new motherboard immediately
following its installation (including its drivers). As I've previously
indicated, it's worth a try. I note Rock's comment, "Don't try to boot the
system first just to see if it works. Run the repair install first." And
I've come across other similar admonitions in this situation. I'm at a loss
as to why that cautionary note is expressed so frequently. I have performed
dozens of motherboard changes in an XP environment and I've never come
across a *single* instance where a failed first attempt with a new
motherboard caused any subsequent problems with the operating system. I've
talked with other technicians about this and they confirm my experience. At
worst you'll have to perform a Repair install.
Anna

"Anna" wrote:

>
> "Old Geezer" <nowhere@all.net> wrote in message
> news:ej3aw6JDGHA.3140@TK2MSFTNGP14.phx.gbl...
> >I am planning on putting a new motherboard in this Windows XP system as the
> >present one has various problems. I built this system a year and a half ago
> >with an OEM version of WinXP, purchased with a new hard drive. So as I
> >understand the EULA, the hard drive is the part that this software is
> >"tied" to. That's fine with me, since it's just the motherboard that I want
> >to change anyway.
> >
> > I presume this will be enough of a change to mean re-activating Windows?
> >
> > There have been countless updates and upgrades to Windows itself and
> > various other software (ISP, antivirus, security, etc.) on the system over
> > that year and a half, and I hate to do all that all over again, so I am
> > wondering if there's any reason I can't just change the motherboard and
> > keep the existing hard drive as is, rather than doing a reinstall. The
> > present board has a VIA chipset and the new one will also, so I should
> > think just a motherboard drivers update would be all that's necessary, if
> > even that.
> >
> > Am I missing anything here? (It happens. :-) )
> >
> > O.G.
>
>
> O.G.
> I see you've received a number of responses to your query but I'm not sure
> they've been totally responsive to the issue you raise, so let me give you
> my experience...
>
> It's a crapshoot at best as to whether you'll even be required to
> re:activate the system following installation of your new motherboard,
> although there's a strong likelihood that activation *will* be necessary.
> However, we have encountered a number of instances, similar to your
> situation, where the activation process was not required.
>
> In other instances where activation *was* necessary, in some cases it was
> automatically accomplished without further ado, and in other instances the
> telephone process involving speaking to a MS rep was necessary. After
> explaining to the rep the need for a motherboard change to replace a
> defective one, in every instance I'm acquainted with, the system was
> activated. I'm unaware of any instance where activation was refused under
> these circumstances.
>
> Now as to the motherboard change itself...
>
> It is likely, but not necessarily absolute, that you will need to run a
> Repair install following the motherboard change as Rock has indicated. And,
> of course, I'm sure you're knowledgeable enough to know that you will have
> to install the necessary drivers from the motherboard's installation CD
> after you install the new motherboard. But there is a real possibility that
> the system will boot *without* the need for a Repair install. Even if the
> new motherboard is a completely different make/model from the one it's
> replacing.
>
> You needn't fear to try to boot with the new motherboard immediately
> following its installation (including its drivers). As I've previously
> indicated, it's worth a try. I note Rock's comment, "Don't try to boot the
> system first just to see if it works. Run the repair install first." And
> I've come across other similar admonitions in this situation. I'm at a loss
> as to why that cautionary note is expressed so frequently. I have performed
> dozens of motherboard changes in an XP environment and I've never come
> across a *single* instance where a failed first attempt with a new
> motherboard caused any subsequent problems with the operating system. I've
> talked with other technicians about this and they confirm my experience. At
> worst you'll have to perform a Repair install.
> Anna
>
>
> That's if you don't have a copy of Windows like I do that has no option for a repair install.

Anna wrote:

> You needn't fear to try to boot with the new motherboard immediately
> following its installation (including its drivers). As I've previously
> indicated, it's worth a try. I note Rock's comment, "Don't try to boot
> the
> system first just to see if it works. Run the repair install first."
> And I've come across other similar admonitions in this situation. I'm
> at a loss as to why that cautionary note is expressed so frequently. I
> have performed dozens of motherboard changes in an XP environment and
> I've never come across a *single* instance where a failed first
> attempt with a new motherboard caused any subsequent problems with the
> operating system. I've talked with other technicians about this and
> they confirm my experience. At worst you'll have to perform a Repair
> install. Anna

I'm in complete agreement with Anna about this. Why not try and boot
first? If it works, you've saved time and if it doesn't, you won't
irrevocably break anything.

Yes, chances are excellent that you *will* have to do a Repair Install.
I can't tell you how many installations of XP I've done since it came
out 4+ years ago, but I can tell you that of the very many, only one
m/b change required *nothing* - much to my amazement. In that case I
went from an older MSI/AMD to a newer MSI/AMD. I've never had that
experience again and have always had to do Repair Installs. In rare
instances - for ex. when going from an AMD processor to an Intel
processor - the Repair Install didn't work and a Clean Install was
necessary. But in either case, it isn't any big deal. Just be patient,
have your drivers, programs, and backup at hand and take frequent
breaks and deep cleansing breaths.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

DL

You're on the ball. I meant the opposite, namely
not problematic. Thanks for the correction.

--

Regards.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"DL" <dl@spoofmail.nothere> wrote in message
news:ejRvHOKDGHA.2036@TK2MSFTNGP14.phx.gbl...
>I dont think you mean this;
>> Hard drives are
>> problematic
>> when it comes to compatibility.
>
>

"Malke" <notreally@invalid.invalid> wrote in message
news:eifOWEMDGHA.3876@tk2msftngp13.phx.gbl...
[ . . . ]
>
> I'm in complete agreement with Anna about this. Why not try and boot
> first? If it works, you've saved time and if it doesn't, you won't
> irrevocably break anything.
>
> Yes, chances are excellent that you *will* have to do a Repair Install.
> I can't tell you how many installations of XP I've done since it came
> out 4+ years ago, but I can tell you that of the very many, only one
> m/b change required *nothing* - much to my amazement. In that case I
> went from an older MSI/AMD to a newer MSI/AMD. I've never had that
> experience again and have always had to do Repair Installs. In rare
> instances - for ex. when going from an AMD processor to an Intel
> processor - the Repair Install didn't work and a Clean Install was
> necessary. But in either case, it isn't any big deal. Just be patient,
> have your drivers, programs, and backup at hand and take frequent
> breaks and deep cleansing breaths.
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User

Malke, thanks for the advice. That's what I'll do, try it first without the
Repair install. Yes, right about the "deep cleansing breaths." :-)

I appreciate very much the time everyone has taken to help me in this.

O.G.