New M/B - Win XP doesn't boot

[Luke]

Hello,

I've just installed a new motherboard and used the same
hard drive (win xp with SP1). In the past, I've done this
with windows 98 and didn't experience any significant
issues. Now, win xp gets into an endless loop very
shortly after it begins to load (using the Safe Mode with
Command Prompt, it stops at the driver loading of
MUP.SYS - it freezes here and then the PC automatically
shutdowns and begins the cycle over again). This is not
BIOS related and all other components are the same except
for the motherboard. If anyone has any suggestions how I
can restore my operating system, it would be greatly
appreciated.

Thanks,

Luke

Athlon XP 2700+
Win XP
768MB Ram
GeForce FX 5700 Ultra

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

Assuming you have an actual XP CD as opposed to a recovery CD, you need to
do a Repair
install as follows:
NOTE, while a repair install should leave your data files intact, if
something goes wrong during the repair install, you may be forced to start
over and do a clean install of XP. If you don't have your data backed up,
you would lose your data should that eventuality occur.

Boot from the CD. If your system is set to be able to boot from the CD, it
should detect the disk and give a brief message, during the boot up, if you
wish to boot from the CD press any key.

Once you have pressed a key, setup should begin. You will see a reference
asking if you need to load special drivers and another notice that if you
wish to begin the ASR (Automatic Recovery Console) depress F2. Just let
setup run past all of that. It will continue to load files and drivers.

Then it will bring you to a screen. Eventually, you will come to a screen
with the option to (1) setup Windows or (2) Repair Windows Installation
using the Recovery console.

The first option, to setup Windows is the one you want and requires you to
press enter. When asked, press F8 to accept the end user agreement. Setup
will then search for previous versions of Windows. Upon finding your
version, it will ask if you wish to Repair your current installation or
install fresh. Press R, that will run a repair installation. From there
on, follow the screens.

If you only have a recovery CD, your options are quite limited. You can
either purchase a retail version of XP will allow you to perform the above
among other tools and options it has or you can run your system recovery
routine with the Recovery CD which will likely wipe your drive, deleting all
files but will restore your setup to factory fresh condition.

 

[David B.]

Now that you've moved to XP, forget most of what you know about 98, you cannot do what you did and expect to have a bootable system
when your done, you will need to perform a repair install to get your system up and running.

 

[Guest]

That's very interesting. I appreciate your time in
answering my question (especially with the detail you
included). I've had this problem before when I tried to
move my ATA133 hard drives to my old motherboards ATA
hard drive controller - I used the #2 option of Repair
WIndows Installation. When all was said and done, I had
to do a clean install because the repair didn't take.
Once again, thank you, Michael!

Any ideas why the mup.sys file gets corrupted?

 

[Luke]

Naturally, I would have to learn that the hard way!!
Thanks for the info, Dave!

Do you know why mup.sys gets corrupted with a change like
that in the hardware profile?

-----Original Message-----
Now that you've moved to XP, forget most of what you

know about 98, you cannot do what you did and expect to
have a bootable system

when your done, you will need to perform a repair

install to get your system up and running.

 

[NobodyMan]

Hello,

I've just installed a new motherboard and used the same
hard drive (win xp with SP1). In the past, I've done this
with windows 98 and didn't experience any significant
issues. Now, win xp gets into an endless loop very
shortly after it begins to load (using the Safe Mode with
Command Prompt, it stops at the driver loading of
MUP.SYS - it freezes here and then the PC automatically
shutdowns and begins the cycle over again). This is not
BIOS related and all other components are the same except
for the motherboard. If anyone has any suggestions how I
can restore my operating system, it would be greatly
appreciated.

Thanks,

Luke

Athlon XP 2700+
Win XP
768MB Ram
GeForce FX 5700 Ultra

If you bought a new base unit for a cordless phone that is very
different from the old one, but tried to use the OLD handheld unit
with it, would you expect it to work?

It's never been a good idea to put on old HD into a new box that has
different hardware than the old box. If you've gotten it to work with
little problems in the past, even with win98, then count yourself
lucky. It won't work in winXP until you do a repair install.

 

[Steve C. Ray]

To do a repair install:

Start the operating system from the CD-ROM (you may have to set your BIOS to
have the CD drive as the first boot device)

When the computer starts from the CD, the system checks your hardware

and then prompts you to select one of the following options:

To set up Windows XP now, press ENTER.

To repair a Windows XP installation using Recovery Console, press R.

To quit Setup without installing Windows XP, press F3.


Press ENTER.


Press F8 to accept the Licensing Agreement.

A box lists your current Windows XP installation, and then the system

prompts you to select one of the following options:

To repair the selected Windows XP installation, press R.

To continue installing a fresh copy of Windows XP without repairing, press
ESC.

Press R to start the automatic repair process. After repairing Windows XP,

you will need re-download all updates,starting with SP1.

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

The issue is not mup.sys, the issue is the nature of XP and replacing the
motherboard. It could report any file, it just happened to report that file
in your case. A new motherboard installation on Windows XP requires a
repair install in order for the operating system to properly recognize the
board.

 

[NobodyMan]

The issue is not mup.sys, the issue is the nature of XP and replacing the
motherboard. It could report any file, it just happened to report that file
in your case. A new motherboard installation on Windows XP requires a
repair install in order for the operating system to properly recognize the
board.

MUP.SYS is almost certainly NOT causing the problem It's the last
system file to load during boot, so of course it will be the last
system file being loaded. Whatever happens happens AFTER mup.sys has
loaded. In this case, XP is confused as hell when it expects MB A and
sees MB B. Result = crash/lockup.

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

I believe I said, the issue is NOT mup.sys and said pretty much what you've
posted. I only bring that up because your response references my post. If
you meant only to add to or reinforce what I said I apologize but if you
were under the impression that what I said disagrees with what you've said,
I suggest you re-read my post.

 

[David B.]

It's not corrupt, that's just where it hangs. The problem is the IDE controller, when you changed the board you changed the
controller, that is the whole reason why XP won't boot.

 

[NobodyMan]

I believe I said, the issue is NOT mup.sys and said pretty much what you've
posted. I only bring that up because your response references my post. If
you meant only to add to or reinforce what I said I apologize but if you
were under the impression that what I said disagrees with what you've said,
I suggest you re-read my post.

I did read your post. You said:

It could report any file, it just happened to report that file in your
case.

This can easily imply the problem WAS with mup.sys. It wasn't
reporting mup.sys in any way, but that's what that quote implies.

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

The first 5 words of my post not only contraindicate that, they explicitly
say it:
"The issue is not mup.sys,"