DAW Motherboard Swap

Guys, I know this asking a lot to predict, but thought I'd toss this out there....
 
Any idea if I would be able to swap out a motherboard without Windows XP freaking out in some way?  Licensing, etc?   Here is the exact scenario:
 
Intel DG41RQ vs. DG41WV boards with the following differences:
- Intel P4 E5500 vs. E5700 CPU's
- DDR2 vs. DDR3 RAM
- FSB speeds a bit different.
- One board has a floppy controller but no IDE, the other has IDE controller but not floppy.
- One board has PCIe x 1 connector, the other does not.  This however is not used.
 
Everything else the same, right down to chips onboard - audio, GPU, etc.
 
Basically, these are the same series boards with same series CPU.  And NIC would always be disabled BTW.

Any guess as to what would happen if these motherboards were swapped out?  Would XP transparently adjust to the swap and tolerate it, or would it flip out and/or reject the license?
 
Sonic
 

Sanderxpander
If it's an OEM version of XP I don't think it'd work.

 
It is not OEM, regular license.

If you're making a significant change to the hardware, you'll most likely need to re-authorize Windows.
Doesn't matter if it's an OEM copy of "Full version"...

Jim Roseberry
If you're making a significant change to the hardware, you'll most likely need to re-authorize Windows.
Doesn't matter if it's an OEM copy of "Full version"...

But an OEM copy can generally not be reauthorized on a new mobo, right?

Sanderxpander

Jim Roseberry
If you're making a significant change to the hardware, you'll most likely need to re-authorize Windows.
Doesn't matter if it's an OEM copy of "Full version"...

But an OEM copy can generally not be reauthorized on a new mobo, right?

Never ran into any roadblocks with either Win XP OEM or Win 7 OEM.  Online activation always failed, but just used the phone activation method and all was good.  I think you get a few activations this way ... but if you do it too often, I've heard you might get blocked.

Sanderxpander
Huh, I guess I've never tried phone authorization, I understood OEM meant "tied to the system" which I assumed to imply mobo. I wonder if they have a number over here or if I'd need to use the US one. Thanks, I learned something!

As long as it's the same machine being repaired/upgraded (not being moved to a second physical machine), you're fine.
 
If Windows gives a BSOD with the new hardware, the OP can use something like Acronis Universal Restore.
 

Jim Roseberry
 
If Windows gives a BSOD with the new hardware, the OP can use something like Acronis Universal Restore.
 

The OP is working with XP.  Would that still be a good option for an unsupported Windows OS?

I've never had any luck upgrading hardware without a clean install of Windows. I've been building PCs since Win 95/98.
 
Last time, I even tried using the Microsoft sysprep method of moving Windows 7 Pro to a new motherboard.
https://technet.microsoft...cc721940(v=ws.10).aspx
 

What is Sysprep?

The System Preparation (Sysprep) tool prepares an installation of Windows for duplication, auditing, and customer delivery. Duplication, also called imaging, enables you to capture a customized Windows image that you can reuse throughout an organization.

 
It failed, apparently because the Win 7 version I had installed was pre-SP1, with SP-1 applied after original install.  That turned out to be unsupported for sysprep.  A couple of days wasted and I still had to clean install.
 
That brings up probably the greatest new feature in Windows 10.  It has a new Windows hardware abstraction layer that allows hardware changes without even blinking.  I have heard several recent success stories of motherboard swaps that went without a hitch! 

abacab
I've never had any luck upgrading hardware without a clean install of Windows. I've been building PCs since Win 95/98.

I prefer a clean install.
There are cases where I'll migrate.
ie: My main studio DAW undergoes hardware changes on a regular basis.  
I generally keep the OS clean/lean... and have little trouble migrating Win10.  
 

This last migration, the Microsoft agent wanted a receipt for the copy of Windows.  
I'm like... uhhh... I've got the copy right in front of me (jewel-case and all).
Had to take a picture of the Install Code... and leave that on the desktop for the agent to authenticate. 
Minor annoyance... but all was fine.  
 

Jim Roseberry

Sanderxpander
Huh, I guess I've never tried phone authorization, I understood OEM meant "tied to the system" which I assumed to imply mobo. I wonder if they have a number over here or if I'd need to use the US one. Thanks, I learned something!

As long as it's the same machine being repaired/upgraded (not being moved to a second physical machine), you're fine.
 
If Windows gives a BSOD with the new hardware, the OP can use something like Acronis Universal Restore.
 

I guess a new motherboard seemed like a new machine to me. You'd wonder where they draw the line, but I guess that's why there's a guy on the other end of the phone.

So as long as I keep the same case I'm ok? My systems are in a constant state of upgrading. I've used the same case and, two data drives and the DVD drive and monitors for the last three systems. I guess I've been on XP, Win7 and Win10 now so it doesn't really matter that much but it's a strange philosophy to me.

But that would also break the terms of a regular single Windows license, right?

I know, we were just discussing the difference between regular and OEM license, where I thought OEM was tied to hardware and regular is allowed to be moved. Both are for a single machine I thought.

Well I personally thought that was because they got tied to the mobo id. Whereas you can move a "regular" Windows license to a new system. Apparently that distinction in practical sense only existed in my mind, although Microsoft may have intended it that way at some point.