HELP!!! Changed motherboard, Win2000 keeps rebooting

  • Thread starter Thread starter Michael Mason
  • Start date Start date
M

Michael Mason

Hi there -

I need to get this fixed by dawn - don't know how to
approach fixing this. I always knew that Windows was
never really happy restarting, only to find out it has a
new motherboard installed. Win9x and ME seem to cope
rather well after recognizing and installing misc. drivers
for the on-board features.

Is Win2K Pro so finnicky it won't do this? I get to the
point where Windows is about to start, you get
the 'movement' at the bottom of the screen (broken bar
solidifies, etc.) and then it reboots again, POSTs and
then over and over.

Is there a quick fix to this? It was a P3-750 processor
that I just put on a Trinity 400 mobo. I had it on an
Asus board but it couldn't seem to remember bios settings
from one day to the next. I replaced the battery,
etc. and that didn't correct anything. All other
components seem to be working just fine.

Please - any tips would be appreciated at this point.

Mike
 
The trouble with that is you have changed the chip sets which is very
embedded into the OS. There are work arounds that may work without sending
you into DLL hell but I suggest you re-install. In the long run you'll be
much better off.

Yes Win98 and earlier would allow a motherboard change without what seemed
any problems but then your talking a much simpler OS. Your in with the big
boys now.
 
Michael Mason said:
Hi there -

I need to get this fixed by dawn - don't know how to
approach fixing this. I always knew that Windows was
never really happy restarting, only to find out it has a
new motherboard installed. Win9x and ME seem to cope
rather well after recognizing and installing misc. drivers
for the on-board features.

Is Win2K Pro so finnicky it won't do this? I get to the
point where Windows is about to start, you get
the 'movement' at the bottom of the screen (broken bar
solidifies, etc.) and then it reboots again, POSTs and
then over and over.

Is there a quick fix to this? It was a P3-750 processor
that I just put on a Trinity 400 mobo. I had it on an
Asus board but it couldn't seem to remember bios settings
from one day to the next. I replaced the battery,
etc. and that didn't correct anything. All other
components seem to be working just fine.

Please - any tips would be appreciated at this point.

Mike
Click to expand...

Which dawn? In my time zone, you posted your message at
13:20!

Win2000 is quite finicky when it comes to changing motherboards.
Many methods rely on you re-installing the old motherboard in
order to prepare your existing installation for a hardware change.

In any case, I strongly recommend that you save your existing
installation on some spare disk, using DriveImage or Ghost, so
that you can revert to a healthy installation in case things go
horribly wrong (which they are likely to do!).

Below are a few methods that might fix your machine.

Good luck!

- The quick-and-dirty: Replace the specific IDE Controller driver
with the generic driver. This seems to work in about 90% of
all cases.

I have only collected the methods below but have never tried
any of them.

- Run SysPrep.exe if you replace any hardware. There are lots of
Knowledge Base articles on this.

- How to Move a Windows Installation to Different Hardware
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q249694

- How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/support/kb/articles/Q292175.ASP

- Start Windows 2000 setup from within Windows 2000 and select "Update".
Choose to setup Windows 2000 - on the next screen choose upgrade to
Windows 2000.
Start the installation.
First time it wants to reboot, switch of the computer, change all
hardware you want.
Once you turn on the computer again, Windows will continue installation
with a complete
new hardware scan and installation of Windows 2000.

- Boot into Recovery Console
Enter this command: enable atapi SERVICE_BOOT_START

- http://support.microsoft.com/default.aspx?scid=kb;en-us;271965
 
Nice post!
When I have done this, I always went into device manager and deleted all the
existing hardware then powered down and swapped boards.
Sometimes it worked, and sometimes it did'nt.

You have given me a few more options. :-)
 
Back
Top