Replacing motherboard problems with win2K

  • Thread starter Thread starter Corey Cooper
  • Start date Start date
C

Corey Cooper

For my office, I upgraded the motherboards for four computers using the info
from the MSDN article "HOW TO: Replace the Motherboard on a Computer That Is
Running Windows 2000 or Windows Server 2003". In all cases I was upgrading
from an Abit PII motherboard to an Intel PERL P4 system. I had no problems.
So when I decided to spend the money for my own machine with the same
set-up, I thought I would have no problems. The only difference between the
others I did and my home system is my home system has a Matrox G550 AGP card
setup with dual monitors (I disabled the second one for the MB swap) and my
home machine has LOTS more software. I tried to disable as much of the
auto-loaded on boot up stuff as I could (Norton Anti-Virus and the like).

What happened first:
I cloned my primary partition to another (smaller) drive I had laying around
just as a backup. I started the first part of the board swap (start Win2K
install, and stop it when it gets to the first re-boot.) I then swapped the
MB and continued. The install progress bar gets about ½ way through and
suddenly just re-boots, and if I let it, the process starts over and reboots
at the same point. I spent all weekend doing this over and over with every
variation I can figure out like disabling as much of the on-board
peripherals as possible, first un-installing the network card from the
original set-up etc.

Question one: is there any way to generate a log file of what is being
done, to figure out what is failing? Or if one is already being generated,
where is it?

At one point, I couldn't get the machine to boot at all, so I re-installed
from the backup and luckily everything worked fine. However, that threw the
fear of whatever into me, and I bought a new (larger) drive, cloned it
completely from my original, and went through the whole process again, using
my cloned drive.

Now, the install program won't start because it tells me that a program "has
not finished installing", and I need to re-boot and let it finish. No
matter how many times I re-boot, it still says the same thing. I can't find
out what it thinks hasn't finished! I checked the registry
HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Runonce but that
has nothing in it, and I can't think of anything else to look for to get
past this screen.

Question two: Is there something about putting a new drive in that could
cause the "something has not finished installing", and if so, how do I make
it complete the process?

Since I couldn't get the first part of the MB swap sequence to work, I tried
the "if the motherboard has failed" protocol from the same KB article. It
gets to the progress bar about ½ way done and suddenly re-boots, just like
above.

Corey Cooper
 
Corey Cooper said:
For my office, I upgraded the motherboards for four computers using the info
from the MSDN article "HOW TO: Replace the Motherboard on a Computer That Is
Running Windows 2000 or Windows Server 2003". In all cases I was upgrading
from an Abit PII motherboard to an Intel PERL P4 system. I had no problems.
So when I decided to spend the money for my own machine with the same
set-up, I thought I would have no problems. The only difference between the
others I did and my home system is my home system has a Matrox G550 AGP card
setup with dual monitors (I disabled the second one for the MB swap) and my
home machine has LOTS more software. I tried to disable as much of the
auto-loaded on boot up stuff as I could (Norton Anti-Virus and the like).

What happened first:
I cloned my primary partition to another (smaller) drive I had laying around
just as a backup. I started the first part of the board swap (start Win2K
install, and stop it when it gets to the first re-boot.) I then swapped the
MB and continued. The install progress bar gets about ½ way through and
suddenly just re-boots, and if I let it, the process starts over and reboots
at the same point. I spent all weekend doing this over and over with every
variation I can figure out like disabling as much of the on-board
peripherals as possible, first un-installing the network card from the
original set-up etc.


<snip>

you may want to try a repair installation...
it should work...but you'll need to install your updates afterwards
 
One problem is you don't know if the new mobo, processor, and memory work!
I would get an old drive and do a fresh install of an OS like win2000 or
win98 to verify that the new stuff works. I have received some bad ram
lately from Kingston. Get lots of errors. You can also run memtest86 to
check out the ram. That would be my first step, then after you verify that
the new hardware is good, then do the upgrade install.

Tom
 
I ran memtest86+ overnight on it, with no problems.

I installed Win2K on it 'clean' with no problems, but if I keep it this way,
I'll have to re-install all my software (shudder).

I have uninstalled all extra devices I could, like the Soundblaster and
network card, then tried the 'upgrade', and it still fails at the same
place. I've run Norton to make sure the regestry wasn't corrupt. I've
tried doing the upgrade but I can't because it insists there is something
that has not finished installing, but won't tell me what, and no amount of
rebooting makes it go away. I've tried the repair option on the install
program, and that gets through the first re-boot, comes up and gets half way
through the install, and suddenly gives me a blue-screen which immediatly
reboots so fast that sometines I don't even see the bluescreen, much less
have time to read it.

Anybody? Anything? Is there no log kept by this porgram to allow me to see
what it is doing when it suddenly fails? MS, you out there?

Corey
 
Did you ever get this resolved? I have a similar problem while trying
to upgrade my motherboard using an existing Win2K installation. Clean
install works just fine, but I don't want to have to reinstall and
update all the applications, same as you!

-Landy
 
Did you try booting in safe mode, then in deviice drivers
remove ALL mentions of mobo hardware, such as IDE, Video, USB,
ports etc. Then shut down, replace mobo and let win2k redetect
the hardware.
 
I tried your suggestion of rebooting in safe mode and then deleting
device drivers, but met with no success. Here is what I did. I put a
clone of the drive in the old setup and booted as normal. I then went
to device manager and began removing any devices that seemed motherboard
specific. Several removed with no problems (USB, Parallel Port, etc.),
but when I tried to remove the important ones (CPU to PCI bridge, PCI to
AGP bridge or PCI Busmaster IDE controller) the computer immediately
crashed.

When I rebooted with the old motherboard, Win2K just rebuilt itself with
the old drivers as if nothing had happened. If instead, I moved the
disk to the new motherboard, then Win2K never got past the first bladk &
white progress bar during boot. I have tried this several times
removing various "important" devices as the last one before the crash,
but have had the same bad luck with each.

Did I follow the procedure you intended? Any other ideas?

-Landy
 
Back
Top