new mobo and xmasbus.sys problem

I just replaced my old motherboard with a new one and now Windows is not
starting up. I have WinXP SP2 and when is loading in safe mode it stops when
loading xmasbus.sys saying ESC if you don't want to load xmasbus.sys, after
that it reboots. If I do ESC or not either way it reboots.
Here are my specs

CPU: AMD Socket A 1.44Ghz
Old Mobo: Elitegroup L7VMM2, Chipset VIA KM266
New Mobo: Foxconn 748K7AA, Chipset SIS 964/748
Memory: DDR PC333 768Mb

I also have WinVista(β) and didn't want to boot either.
I read in other forums that Alcohol 120 creates issues with the xmasbus.sys,
in others that the change of chipset could be the problem. In both I should
format and do a clean install, but I can't afford to loose my info. I tried a
system repair with my XP cd but is not accepting my Admin password. If I
switch back to my old mobo, Windows loads fine. The chipset makes sence, but
how can I get Win to work with it?
Suggestions???
Thanks

Geto wrote:
I just replaced my old motherboard with a new one and now Windows is not
starting up. I have WinXP SP2 and when is loading in safe mode it stops when
loading xmasbus.sys saying ESC if you don't want to load xmasbus.sys, after
that it reboots. If I do ESC or not either way it reboots.
Here are my specs

CPU: AMD Socket A 1.44Ghz
Old Mobo: Elitegroup L7VMM2, Chipset VIA KM266
New Mobo: Foxconn 748K7AA, Chipset SIS 964/748
Memory: DDR PC333 768Mb

I also have WinVista(β) and didn't want to boot either.
I read in other forums that Alcohol 120 creates issues with the xmasbus.sys,
in others that the change of chipset could be the problem. In both I should
format and do a clean install, but I can't afford to loose my info. I tried a
system repair with my XP cd but is not accepting my Admin password. If I
switch back to my old mobo, Windows loads fine. The chipset makes sence, but
how can I get Win to work with it?
Suggestions???
Thanks


Normally, and assuming a retail license (many factory-installed OEM
installations are BIOS-locked to a specific chipset and therefore are
*not* transferable to a new motherboard - check yours before starting),
unless the new motherboard is virtually identical (same chipset, same
IDE controllers, same BIOS version, etc.) to the one on which the WinXP
installation was originally performed, you'll need to perform a repair
(a.k.a. in-place upgrade) installation, at the very least:

How to Perform an In-Place Upgrade of Windows XP
http://support.microsoft.com/directo...;EN-US;Q315341

Changing a Motherboard or Moving a Hard Drive with WinXP Installed
http://www.michaelstevenstech.com/moving_xp.html

The "why" is quite simple, really, and has nothing to do with
licensing issues, per se; it's a purely technical matter, at this point.
You've pulled the proverbial hardware rug out from under the OS. (If
you don't like -- or get -- the rug analogy, think of it as picking up a
Cape Cod style home and then setting it down onto a Ranch style
foundation. It just isn't going to fit.) WinXP, like Win2K before it,
is not nearly as "promiscuous" as Win9x when it comes to accepting any
old hardware configuration you throw at it. On installation it
"tailors" itself to the specific hardware found. This is one of the
reasons that the entire WinNT/2K/XP OS family is so much more stable
than the Win9x group.

As always when undertaking such a significant change, back up any
important data before starting.

This will also probably require re-activation, unless you have a
Volume Licensed version of WinXP Pro installed. If it's been more than
120 days since you last activated that specific Product Key, you'll most
likely be able to activate via the Internet without problem. If it's
been less, you might have to make a 5 minute phone call.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell

xmasbus.sys:
http://forum.alcohol-soft.com/lofive...php/t9275.html

--PA

"Geto" wrote:
I just replaced my old motherboard with a new one and now Windows is not
starting up. I have WinXP SP2 and when is loading in safe mode it stops when
loading xmasbus.sys saying ESC if you don't want to load xmasbus.sys, after
that it reboots. If I do ESC or not either way it reboots.
Here are my specs

CPU: AMD Socket A 1.44Ghz
Old Mobo: Elitegroup L7VMM2, Chipset VIA KM266
New Mobo: Foxconn 748K7AA, Chipset SIS 964/748
Memory: DDR PC333 768Mb

I also have WinVista(β) and didn't want to boot either.
I read in other forums that Alcohol 120 creates issues with the xmasbus.sys,
in others that the change of chipset could be the problem. In both I should
format and do a clean install, but I can't afford to loose my info. I tried a
system repair with my XP cd but is not accepting my Admin password. If I
switch back to my old mobo, Windows loads fine. The chipset makes sence, but
how can I get Win to work with it?
Suggestions???
Thanks