• 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.

How to get a new motherboard to work with exisiting system?

yanon

Senior member
After numerous crashes, caused by running Geforce MX with WinXP, my MSI K7T Pro (Via Kt133) finally died (can't boot ) yesterday. I went to the local Fry's and bought a ECS k7S5A motherboard because I want to continue using my SDRAM. I installed the motherboard without much problems (except power led don't work because I have a 3-pin power LED plug but the mother only has 2-pin for power LED). However, I can't get it to work with my exisiting dual-boot (Win98 on the hard drive which connects to the secondary IDE channel and Winxp on the hard drive which connects to the primary IDE channel) system. The Windows OS selection loaded properly. If I selected WinXP, the OS starting process would stop and post a blue screen which said the windows system can't start because it can't configure the new hard drive or hard drive controller. I know this problem is cause by the difference between the motherboard chipsets (ECS K7S5A uses SiS 735 and MSI K7T Pro uses Via KT133). How can I get around this problem and boot into Winxp? According to the ECS motherboard manual, I should install VIA serice pack (Via 4-in-1) 2.48v once boot into windows. Doesn't this suggest that VIA's driver is compatible with Sis 735? If there is no compability problem, then why doesn't Winxp boot properly?
BTW, I can boot into Win98SE.

Please help.
 
Win9x/ME and Linux will usually survive a new chipset at boot.
WinNT/2k/XP will choke and die in 99% of all cases.

A reinstall is the best solution, although manually removing the drivers (if possible) might work too (never tried it, though).
 
Does reintalling Winxp over an existing Winxp installation removes data files like *.doc, *.mp3, and etc.? Will doing a registry refresh in the Recovery Console do the trick? How about buying a motherboard with KT133A chipset? KT133A is essentially the same as KT133 except that it has a newer south birdge.
 


<< Does reintalling Winxp over an existing Winxp installation removes data files like *.doc, *.mp3, and etc.? >>

Nope.

Well, that is, unless the installation screws up. How far does your trust in Micros~1 go?


<< Will doing a registry refresh in the Recovery Console do the trick? >>

Not a clue. You could ask this in the Operating Systems forum.
[/i] >>

How about buying a motherboard with KT133A chipset? KT133A is essentially the same as KT133 except that it has a newer south birdge.[/i] >>

I think this would work. Not totally certain, though.
 
the few times done this,i had to fresh install the OS.
I did it successfully once using the repair feature(if i can recall correctly)

*shrug*
 
Back
Top