• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I changed my motherboard, and the system won't boot now

G

Glendor

Diamond Member
I changed the motherboard in my system from a board based on the ALI M1689 chipset to a motherboard based on the SIS 755-A2 chipset (I know, not much of an upgrade, but I had my reasons).

Anyway, I didn't want to have to completely reload my OS (WinXP MCE 2005), and wanted to just boot into safe mode, and replace the ALI chipset drivers with the SIS drivers.

No dice.

It won't load Windows, and BSODs when trying to bring up the logon screen. Even in safe mode!

As safe mode is loading, I can see that the last thing it tries to load before the BSOD is ALIPERF.SYS which appears to be the ALi Disk Performance Driver.

Is there a way to load the SIS chipset drivers in this situation?
Should I boot off a different drive, with this one as a slave, and delete (or rename) the ALi files manually, then try to boot from the original drive? Any idea what will happen if the aliperf.sys file is missing when I try to boot from that drive?

I'm interested in any suggestions that will get this running without having to reinstall the OS.

Glendor...

 
Did you prep your WinXP installation properly? There's a FAQ on it and everything.

Try booting off the cd and using the recovery console or whatever it's called.
 
Thanks for the reply n0cmonkey, but I'm not sure what you mean by "prep" my WinXP installation. Unless you are talking about prepping an install for distribution like on a disk image when deploying to a lot of PCs. I hadn't thought of that, but that would mean I would need to reinstall the old mobo to get the OS to boot, then go through the 'prep' steps. Now that you've refreshed my memory on it... that might not be a bad idea, but I would like to save that idea for Next Time if at all possible, and try to get the OS to load on the new mobo This Time.

The original ALi mobo & harddrive have been up and running together for about two months before I decided to replace the ALi mobo with the SIS one.

I've used the recovery console for a few things in the past, but I'm not sure how it can help me in this situation. I'll look into the recovery console option when I get home.

 
You are likely getting a stop 7B at boot but there could be a few other things.

at this point you need to perform an "inplace upgrade"/repair on the OS.

Boot with your XP CD, hit F6 at the beginning of the text mode portion of setup then provide a mass storage driver with the 'S' key shortly thereafter (assuming you are using a newer SATA controller or possibly raid).

When you hit 'welcome to setup', hit enter to setup (NOT 'r' for repair!). You'll reach a screen where your previous install is detected. At that time go ahead and hit 'r' to repair.

Seeya back online in about 30min 🙂
 
I think I've been through that proceedure on a PC a couple of years ago, but doesn't this method still reinstall the OS, on top of itself?

If I do that, won't I have to reinstall all my applications (Office 2003, SiSoft, Norton, Games, etc...), and have to reactivate MCE & office?

Glendor...
 
An inplace upgrade pretty much runs the setup process against the system hive and reloads the OS without touching 3rd party registry entries. Your programs will all be fine. The only 3rd party items that can be affected are ones that tap into your actual OS. CD Burning software, antivirus, hardware monitoring tools and other apps that use drivers or filter drivers will need reinstalled.

It's really a pretty safe process. Back in the NT 4.0 days it was different. It was basically a reinstall to the same folder at that time.

When you swap motherboards like this you typically want to uninstall hardware related drivers and apps before you start (the antivirus etc. listed above). You can then run sysprep on the box which basically triggers this setup process the next boot. You are now past that point so the inplace upgrade is the next best (or possibly better) option.

So I guess the bad news is: you're screwed and have no choice at this point.
The good news: it's not that bad of a spot to be in at all 🙂 Roll with it and you should be fine.

keep us updated!
 
Really, with the repair installs, I've changed from AMD to intel, intel to AMD, KT133A to nForce3, etc. It really is a no-hassle way to swap motherboards. And sometimes due to failed equipment, there is no chance to uninstall the old drivers, yet that has never been a problem.
 
Thanks for the good advice. The repair worked great. The only issue is that I had to reactivate Windows with MS, and I had to do it over the phone.

Other than that, it went great.

Thanks again,
Glendor...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top