Help installing new Mobo with existing win XP

[Bug Mekanic]

I currently have win XP home installed on my hard drive. I've just upgraded my mobo and proc (barebones computer). After adding my drives with the win XP installed, the computer won't boot. I get through post, then I get a stop error (blue screen) with the 0x0000007B error. I can't seem to find anything out on the net that addresses this. Best I could find was a site that said I'd have to reinstall the OS. Also, can't get the computer to boot from the win xp CDROM. Will boot up fine in my old computer from the CD. Could I have the bios settings wrong? The mobo is an ECS K7S5A V.3.1 and AMP XP 1900 cpu. I can't really wipe the drive because it has critical data on it. The win XP is an OEM version, not upgrade version. Also, I've downloaded the install floppies from MS support site but haven't tried them yet. HELP!

[D@ve]

Does it say anything else along with that error message??

[Bug Mekanic]

Also, can't get the computer to boot from the win xp CDROM. I've tried different boot orders in the bios with no luck. the XP cd boots up fine in my old computer from the CD. Could I have the bios settings wrong? I even tried having the bios set so it boots from the CD only. The mobo is an ECS K7S5A V.3.1 and AMP XP 1900 cpu. I can't really wipe the drive because it has critical data on it. The win XP is an OEM version, not upgrade version. Also, I've downloaded the install floppies from MS support site but haven't tried them yet. * I was able to boot with a Win Me boot disk and browse the Cdrom, but not the drive because it's NTFS...just more info.

[shamus]

Originally posted by Bug Mekanic
I currently have win XP home installed on my hard drive. I've just upgraded my mobo and proc (barebones computer). After adding my drives with the win XP installed, the computer won't boot. I get through post, then I get a stop error (blue screen) with the 0x0000007B error. I can't seem to find anything out on the net that addresses this. Best I could find was a site that said I'd have to reinstall the OS. Also, can't get the computer to boot from the win xp CDROM. I've tried different boot orders in the bios with no luck. the XP cd boots up fine in my old computer from the CD. Could I have the bios settings wrong? The mobo is an ECS K7S5A V.3.1 and AMP XP 1900 cpu. I can't really wipe the drive because it has critical data on it. The win XP is an OEM version, not upgrade version. Also, I've downloaded the install floppies from MS support site but haven't tried them yet. HELP!

Make sure your mobo is set to boot from a cd (errr...you already tried that....) or use the floppies you have. Also, no need to post in more than one thread. ;)

[NooNoo]

Threads merged :cool:

[shamus]

Originally posted by NooNoo
Threads merged :cool:

You are da MAM! :)

[Bug Mekanic]

The more I thought about it, the more I thought it was maybe a bios setting problem rather than the OS being it still boots the OS fine on my old computer. As far as the error messages, I get the 7B error, then a bout three in (*), but I can't recall what they are as the computer is at my home and I'm at work. I thought the 0X0000000's in brackets were memory addresses(?) Not really sure.

[kato2274]

XP does not like being moved from machine to machine or in your case motherboard to motherboard. If the two mobos were different XP is going to have a tough time, because the hal layer it created for your previous setup does not jive with the new hardware you have.

I've heard that booting from the CD and choosing repair the current installation can sometimes work.

another option would be to reinstall using the same folder. This is not like doing it in 9X though. your other programs though still installed and safe and sound, will not be in the start menu or the registry and most likely will not work until they are installed again over top of themselves. but you will not lose any data doing it this way, you just may have to reinstall some programs.

there was a link floating around here a little while ago about generating a new hal. I can't seem to find it anywhere. I think it was something like hitting F5 during the beginning of windows setup. anybody else remember.

[NooNoo]

f5 when xp setup says press f6 gives you the HAL types to install and you can override the auto setup this way. Usually you need to set a standard hal because the bios is not quite compliant with acpi standards for xp, but xp doesn't quite see that its not...

As kato says, swapping motherboards - especially different chipsets kill the xp install.

Either try the auto repair option when setup has run, or install over the top, or even to a different directory as a parallel install - this option will not keep your installed proggies, but it will not change any settings on the old install and you can access the data.

[Bug Mekanic]

I'd be willing to try a repair install...but right now she won't boot from the CD...I will try the floppies tonight, but shouldn't it boot from the CD?? Seems like it crashes before I even get the the xp boot...It won't boot in safe mode either, so I can't even try the F5 HAL re-do thing.

[NooNoo]

Have you set it to boot from cdrom in bios?

Do you get the message press any key to boot from cd after the bios is done?

[Bug Mekanic]

yeah, I've set it to boot from the CD first. No luck. Also tried "Optimal" bios settings, tried removing all components except 1 stick of SDRM and the HD, but still no luck...

[NooNoo]

does the bios see the cdrom? When its counted ram, and the ide is set to auto for the cdrom - does it report the cdrom's presence properly?

[Bug Mekanic]

The bios does see the CDRom when set to auto detect. I did have a problem with it detecting the CD at one point last night but can't recall what I did to fix that (It was late and I was beat). But at latest boot try, Yes the bios does recognise the CDs.When its counted ram, and the ide is set to auto for the cdrom what do you mean by "counted ram"?

[NooNoo]

On a standard computer you get the following sequence

The video card bios loading
The System board bios - Ami or Award usually
Then it start's the POST
One of the first checks is to count through the ram.

OK on an old machine it can take forever, and on the newer machine you can blink and miss it.

After the ram has been checked, any ide devices set to auto then are reported on the screen...

This is followed by any other devices with their own bios. Finally you get a screen showing all the pci devices and their irqs and address used. At this point, if it's set to boot from CDrom you will get the message - press any key to boot from cdrom. You have about 3 seconds to hit a key. Failure to hit a key will result in cdrom being ignored and it will move on to the next boot device in the list in bios.

[Bug Mekanic]

OK, I'm with you now. I get to the PCI/IRQ stuff, but didn't notice the blurp about press any key to boot from the CD--but I could have easily missed it not knowing it was there. When I get home in a few hours, I'll run through it and see if that statement isn't there and see if that doesn't fix my Cd Boot problem.

--UPDATE--

Wasn't able to boot from the CD...I can hit F8 (boot option at post) and select CD, but still get the blue screen. If I disconnect the hard drive from the IDE cable (primary master), it won't blue screen, but it wont boot (nothing to boot from). It does look for something to boot though. I'm kinda new with win XP, so this is kicking my butt. I'm formatting the floppies now so I can try to boot from then...I'll update.

[Bug Mekanic]

Hey it works!! Used the instal floppies, did a repair instal and all is well...

This is what I think was the problem --

The old mobo had a Via controller on it and my new board had an Sis controller. The problem I think was that the two different controllers were detecting my hard drive differently. The Via said my drive had like 255 heads and the Sis was like 6700 (not sure of the last value, but it was way different). I did have to re-do the registration with MS, but all my old settings etc. were there just like I left them. Thanks for all the great support. I can always get answers at Windrivers! You guys came through again!

Sincerely,
Parrish Jackson

[kato2274]

Originally posted by Bug Mekanic
Hey it works!! Used the instal floppies, did a repair instal and all is well...

This is what I think was the problem --

The old mobo had a Via controller on it and my new board had an Sis controller. The problem I think was that the two different controllers were detecting my hard drive differently. The Via said my drive had like 255 heads and the Sis was like 6700 (not sure of the last value, but it was way different). I did have to re-do the registration with MS, but all my old settings etc. were there just like I left them. Thanks for all the great support. I can always get answers at Windrivers! You guys came through again!

Sincerely,
Parrish Jackson

parrish,

your problem did not lie in how your board detected the hard drive (though that is a bit strange) Your problem was related to how windows XP is designed to work with hardware.

Operating systems built on the windows NT kernel rely on a HAL or Hardware Abstraction Layer. here is a brief definition.

In computers, a hardware abstraction layer (HAL) is a layer of programming that allows a computer operating system to interact with a hardware device at a general or abstract level rather than at a detailed hardware level. Windows 2000 is one of several operating systems that include a hardware abstraction layer. The hardware abstraction layer can be called from either the operating system's kernel or from a device driver. In either case, the calling program can interact with the device in a more general way than it would otherwise.

This function helps with overall system stability because it doesn't allow direct access to system hardware. Everything is negotiated in that Hardware abstraction layer. Because of the way the technology works, the HAL must be built for your individual PC and it's installed hardware and that happens when you set windows up.

when you changed your motherboard, the HAL that XP had previously built for your old board was no longer valid because you had a much different hardware configuration. hence it would not boot.

By doing a repair install of XP you allowed XP to create a new unique HAL for your new hardware.

just thought you might want to know the root of your problem and the reasoning behind the suggested fixes.