Computer keeps restarting....

You are probably on the right track.
One of the most common causes of the problem under these conditions is that the proper chipset drivers are not installed.
So, it is boot on a floppy, and install the chipset drivers, as the first step.
Regards, Chris

Windows XP and 2000 unlike Windows 9X and Me do not take well at all to having major hardware changes.
Even installation images have problems if the hardware is different.

The "recommended" method for changing the motherboard is:

Backup the system not including the hardware abstraction layer.

Install the new hardware.

Install Windows clean onto the hard drive.

Restore from the backup.

While I have never tried it myself, I have been told that you can indeed run a repair installation and that will correct the problem.

Another resource is:

http://tinyurl.com/4xbw

Chas

It appears there are two schools of thought and practice on how to fix a problem like yours.

1. Backup data (if necessary by connecting the HD to a working computer) and start from scratch. You have to reinstall all software and copy back data that you backed up.

2. Reinstall Windows on top of the current one. Actually Microsoft RECOMMENDS this method on Windows 2K or Windows 2K3 (See MS KB Article 824125: HOW TO: Replace the Motherboard on a Computer That Is Running Windows 2000 or Windows Server 2003). Or tinyurl.com/j9u7
Pay attention on ?Replace a failed motherboard?.
I have used this method on Windows XP (Home or Pro) numerous times and so far never failed. If there were important data, I always backed them up and used precaution of MS KB Article 312369: (You May Lose Data or Program Settings After Reinstalling, Repairing, or Upgrading Windows XP). Or tinyurl.com/176b

If you need more info, please add a comment.

It is indeed a chipset issue - nothing to worry about though.

Just to be on the safe side, I'd throw the HHD into another XP machine as a secondary drive and back up the data first. When it's all done you really should get your clients to enforce a backup regime. Data protection is their concern not yours and too many users like to blame poor techos for "losing data" when it's really their own fault for not having a more recent backup.

Boot to your XP cd and choose to install. XP will detect the existing install and ask you if you want to do a repair. Do so.

Should fix your issue or at least get you to the point where you can boot and install the correct chipest yourself.

Enjoy!

Note to The Chas - w2k is a much more robust os then you give it credit for. I've had no problems with w2k swapping mobos and then installing appropriate chipsets just like I used to in safemode with win9x. I have also even in a pinch splatted SOE images onto very different hardware builds and then installed relevant drivers afterwards. It's not pretty and generally involves alot of reboots but it can be done - nothing ventured, nothing gained!

XP is set to autorestart on system errors.

To see the exact error that is occuring on boot, you will need o disable system's autorestart feature. This way it will simply crash to a BSDOD and give you a hardware error code to ease debugging ( probably an issue that one of the above posts have outlined.)

To disable system autorestart on error:

Start>control panel>system>startup and
recovery. Once there UNCHECK "automatically restart" under system failure.

Now at least you should get a hardware code to trace the root fo the problem.

Your Clients problem is specifically why I never put a system together with Less than two drive partitions. One partition for only the op system and one for non-windows programs and data. The more MS advances their systems the easier it is to stop up the wheels of motion. I can only hope you aren't using the NTFS system which while great when everything works, is a disaster when things go arye.

regards
rick

All you have to do is to create a back up to store all important data of your client and after that, reformat the hardisk and re-install all sofware needed to support both the computer and data needed of your client. remember, we all know that XP is the highest OS of MS but, XP cannot recognized all kinds of motherboard and other hardware components because these components are also upgrading to perform its best. XP recognize only what has been loaded to itself. Or buy newest edition of XP and figure it out that this new edition has support of your new mother board.
I hope i give some ideas and facts about your problem

This question was closed by the author