New Motherboard/cpu kills WinXP

Anon

Hi..
I recently experienced some trouble of when I bought a new motherboard/cpu (Abit KR7A w/ XP1800+ VIA266A) and dropped it in, thinking XP Pro OS would boot just fine.. I get the infamous XP Blue Stop screen every time, safe mode or not. I think the ide drivers for the new MBD may not be properly to recognize the new hardware? (I havent installed the VIA 4in1 deal, I dont know if XP still thinks I am using my Intel 815 chipset) though when I attempt safe mode it checks several system files located on the HD...
I noticed that the blue stop screen appears before the colorful "WindowsXP loading" screen.
Does windows have some hold to prevent hardware change? Siri mentioned the registration hardware change limit... to what extent would windows prevent boot, and what do I do!?!?
I really appreciate any help, and I thank you!

Sincerely,
Robert C

Anon

I have heard of such a \"feature\". If you are not running the developer version of XP, it will not work when you make major hardware changes, such as a new motherboard and CPU. You can thank Microsoft for their \"innovative\" anti-piracy techniques.

You should contact Microsoft and have them provide you with a solution.

Anon

What do you mean by te "developer" version?
I am pretty sure I have PRO beta or something with a VLK "volume license key"..

Would that insist a boot stop with"

0x0000007b ?
-Rob

Anon

Basically, Microsoft license a copy of XP to your computer, not to you. When you change a major component, such as your motherboard or CPU, technically you have a different computer and so you need to buy a new license for XP.

As has been said, thank Microsoft for their new "anti-piracy" techniques

Anon

This problem has existed since NT4 and carried over to 2000 and XP, before you replace the motherboard you should remove all the motherboard drivers from the system (Right click MyComputer, go to properties, Hardware, Device Manager) then remove all motherboard related devices (hdd controllers, etc) this should be done from same mode. Then put in your new board and you should get to windows fine, it will find a lot of new stuff but you can get it to run. One problem with this is a lot of residual stuff in the registry that has the potential to be problematic, so a fresh load of the OS is preferable (although it should be fun calling Microsoft to see if they will let you use XP since it's already been activated once). Also, is this a question for the phpbuilder's site?