Motherboard upgrade - Win2K fails to repair, hangs at Config COM+...

  • Thread starter Thread starter Landy Atkinson
  • Start date Start date
L

Landy Atkinson

I am trying to upgrade my motherboard from an old ASUS P5A with ALI
chipset and AMD-K6/450 to a GIGABYTE with VIA chipset and Athalon 2800+
and having no luck getting past the point in the restore process where
the COM+ files are being configured. At least that is the text which
displays above the progress bar at the point it hangs.

I have tried to follow the instructions that I found in several articles
in the Microsoft Knowledge Base for upgrading hardware and emergency
replacement of hardware from a backup. Basically what I have done is
variations on the following:

1. Ghost the original hard drive to a new disk.
2. Boot from CD using the new motherboard with Ghosted drive as master.
3. Select upgrade existing Windows 2000 installation.
4. Select repair.
5. Answer questions and enter Install Code.
6. Watch the Win2K installer replace files & configure itself.
7. Watch progress bar get about 1/2 way and hang while saying it is
configuring COM+
8. Go back to 1. after making a BIOS or other change and
re-Ghosting the drive.

Anybody have any experience in working through this issue? Any
suggestions? My goal is to not have to reinstall the 30+ applications
that exist on the system as many are web downloads with many updates
that would take forever to replace, so if there is a way to do a clean
Win2K install and then migrate the registry and installed applications,
that would work just as well. I have done a clean Win2K install onto
another drive with the new motherboard and that works just fine!

-Landy
 
You changed 2 significant pieces of equipment -- the CPU (which often needs
a different HAL) and the MB chipset. Ghost was designed to clone between
similar (identical) equipment. I'm actually surprised you got as far as you
did without suffering a HAL or APM-related BSOD.

I'd try ghosting, then doing a maintenance reinstall of windows2000 on top
of the image. It may or may not fix your device manager conflicts well
enough to run. For best performance, however, would be to build from the
ground up a new workstation, configured exactly the way you want it, on the
new hardware and use that as your ghost source.
 
A maintenance reinstall is what I think I am doing! Is there another
way to install that I should know about? What I am doing is booting
from the Win2K CD, choosing the "Install" option and then the "Repair"
option. Is the Maintenance Reinstall different? I will search the MS
Knwoledge Base to see if I can find this specific term.

Is there an Installer Log file that I can view to try and isolate
exactly what is going on when the install fails?

-Landy
 
A maint reinstall is different from a repair install. It involves doing a
full or upgrade install without formatting first. It keeps your data, but
you'll most likely have to reinstall any 32 bit applications because the
registry gets replaced.
 
Back
Top