new mobo, cpu, memory, XP Pro w/SP2 will not install nor repair

[Amy 0]

We just put in a new motherboard, cpu, memory, with same everything else. XP will not load, repair, boot, anything. It freezes up when it starts and the loading bar starts running, freezes up. Tried every single option you can get where you choose what action to take. No avail. Will flash the WinXP load screen, then flash a blue screen, and computer restarts. Can't read the blue screen, managed to see something about "restart your computer..." and we cannot pause it either.

 

The new hardware is as follows:

MSI K8N Neo3

AMD Sempron 64 3100+

Kingston 1G DIMM

 

All the mobo settings we've checked a million times, video works, can get into the BIOS, no luck there.

 

Okay, I read that you have to reinstall XP when you change the mobo but it will not install, repair, nothing, just freezes.

 

if we get to a DOS prompt, it freezes pretty quickly, doesn't let us get through to make any commands.

 

I also read that you can make a change in the device manager BEFORE changing the board, changing to "standard dual channel PCI IDE controller", then "don't search, i will choose the driver to install", then "standard.....controller". what i don't know is if we're stuck putting the other hardware BACK in to try this.

 

husband is a power user, much experience, can follow complex instructions as you can give, technical explanations. so lay 'em on me if you can. we absolutely cannot reformat these drives, the information is way too important.

 

also have two external DVD combos, two internal CD's, two hard drives.

 

i took the board back out today, to check to see if there was any visible damage, any contact with the case perhaps. i found that one of the little red washers had come off one of the case screws and i didn't know it, so there was some contact with the case screw on the top left, by the keyboard/mouse plugs. i've seen this happen before and this was not the effect, so i suspect that was not the problem.

 

please help, i'm supposed to gather research while he's passed out. :-)

 

Amy

[Amy 0]

uh, also, i have a confession to make.

 

i was really tired when i changed out the hardware. instead of plugging in the two external usb combos into two of the usb slots, i plugged in the two usb's from the ups's.

 

please tell me this is not my problem, that i shorted the board by doing this.

 

amy

[Amy 0]

just to be clear, hardware ID's fine during intial boot process, memory tests fine, the hard drives are listed in the same order as they should be, sees the cdroms and dvd combos, the BIOS works fine, but we cannot even do a clean install away from the primary drive even, just tried that also.

 

it doesn't behave like a damaged motherboard, freezes up during different parts of any type of install.

 

what on earth......we've never had this kind of behavior out of a machine, and we've done many many machines over the years.

 

argh.

 

Amy

[Amy 0]

okay, i reseated the CPU also now. no avail. however, it came out a little to easily, came out with the heat sink, did not seem to be seated properly. I've never seen a CPU come out without lifting the lever.

 

however, when we tried to do clean install prior to this, the drive letters changed, and now the hard drives are not being detected, and we're having to go into the BIOS every restart to detect them.

 

sheesh.

 

amy

[Relic 0]

Originally posted by amy:

Quote:

okay, i reseated the CPU also now. no avail. however, it came out a little to easily, came out with the heat sink, did not seem to be seated properly. I've never seen a CPU come out without lifting the lever.

 

however, when we tried to do clean install prior to this, the drive letters changed, and now the hard drives are not being detected, and we're having to go into the BIOS every restart to detect them.

 

sheesh.

 

amy

 

Well, the CPU coming out with the heatsink does happen, it's not a good thing, but as long as none of the pins on the CPU are bent, it's not a problem.

 

In your case(no pun intended), the new mobo/RAM/CPU means that you'll need to format those HDD's, unless you want to go back to your old system, retrieve the info you need, then format.

 

You're kinda stuck there, especially if you're moving from an Intel system to an AMD system.

 

The only suggestion I can offer you is to clear your CMOS, either by using the jumper on your mobo, or by pulling the battery. First you have to shut the computer down, then turn off the power switch on the back of the PSU, then unplug the PSU.

 

Whether you're using the jumper, or pulling the battery, leave it on the "clear cmos" pins/keep the battery out for a good 10 minutes. This MAY do the trick for you, but I doubt it.

 

The problem is that your boot drive holds all the info for drivers, including your mobo drivers, which are not compatible with your new mobo.

 

One other possible option, which I'm not sure is available to you, I'm really not understanding how far you get when trying to reinstall XP, BUT, if you boot from the XP CD, you will be offered an option to use the "Recovery Console", that's the first time the "R" option is available, if you can get that far, enter the recovery console, then type in "fixmbr", that will re-write your master boot record.. Possibly, just possibly, this might get you back into Windoze, it's worth a shot.

[Amy 0]

Hey Relic,

 

I just did passing-out for 5 hours, and am trying to catch up to where hubs is at. We did the CMOS thing of course, didn't work. Couple days ago. The CPU pins were not bent, but it didn't help us. Changing out the hard drive cables got us farther though.

 

We're not going from an Intel, but from another AMD, KM2M Combo mobo.

 

Last night we did put the other hardware back on for while to go take a look at the drives and make some disks, hubs had some ideas.

 

He's gotten it to stop freezing up so much and I see XP getting farther into install, but we get to the "new and exciting look" screen and an error popup comes up "(blah blah blah).....The manifest file contains one or more errors."

 

Any more ideas, since we can get this far now?

[Amy 0]

He can get into the C drive and all that, but nothing works. message from hubs)

 

amy

[Amy 0]

sorry, i meant to say "The manifest file contains one or more syntax errors."

[Amy 0]

Well, update. We've gotten XP to get to within 2 minutes of finishing setup now, before freezing. We're on our way. I will stop bugging you, but look back and see if you have any suggestions at all. Then when we get to the end, I'll letcha know what we did.

 

Amy

[Amy 0]

another update Relic,

 

we have managed to get XP set up, with my husband manually going through directory freedom and loading the original program over from D to set up. but the video is elusive still. it will load and all you see is black screen with white mouse pointer.

 

any advice for me? i am going through the archives and doing more research. husband is quite skilled, i'm amazed he's gotten this far. we should have the process down pretty good by the time we get done with this machine, so we can upgrade other people's mobo's who have XP also. quite a task.

 

amy

[Amy 0]

if you want to see which direction we've done to get as far as we have, see this link:

 

http://65.24.134.81/KipSolutions/MovingXPNewMotherboard/MovingXP.htm

 

so far so hellish anyway. what a hassle.

 

amy

[American Zombie 0]

Having upgraded 100's of boards and swapped out about the same amount of drives as well as other hardware I only have this to say.

 

I would never follow the advice on that site. You may not have noticed but if using those hacks you are putting many Intel entries into your registry on an AMD board.

 

That board has onboard graphics and some also had an optional AGP slot. You have to set the bios to whatever you are using.

 

Init Display First

This item specifies which VGA card is your primary graphics adapter. Settings: PCI Slot and AGP

 

PCI if using onboard graphics and AGP if using a card in the AGP slot if your board has one.

 

You can also try Booting into safe mode and see if the video comes up as XP will use the VGAsave driver.