I have before me an ECS K7S5A. I built this 2.5 years ago and it has run flawlessly. However, the person I built it for brought it back to me with a bad power supply. When I say bad I mean kaput. Dead. I put a new 450W PSU in it and the system came back to life. It had Windows Me on it so I asked if they wanted to upgrade to XP. They said sure. Here's where it gets ugly.
I attempted an install and got all the way through. Then when it finally finished Win XP wouldn't load up. I get the WINDOWS\SYSTEM32\CONFIG\SYSTEM corrupt error. I followed the instructions on the M$ website but to no avail. Okay. I have ruled out the following:
RAM
HDD
PSU
The system specs are as follows:
ECS K7S5A
Athlon 1.2GHz
512MB Samsung PC2100
Diamond V.90 Winmodem
Matrox PCI vid card
NSpire 450W PSU
Pioneer DVD
MSI CD-RW
I suspect something bad happened to the mobo when the original PSU went kaput. Any other explanation?
Okay, brain. You don't like me, and I don't like you, but let's get through this thing and then I can continue killing you with beer. -- Homer Simpson.
Try to disable onboard audio in BIOS before install. This is fairly common with some older on-board audio. You'll probably have to redo the installation from scratch though. You can try to enable on board audio afterwards, but I recommend turning off the Soundblaster (or Legacy) option.
Dev
---
My Sig:
))
(( ___________________
|||_____________|_____|
In the bios make sure you run your memory speed in sync with your fsb. So with a 200 bus TBird 1.2, set the mem speed to 100 (200) not 133(266). I have had instability issues with K7S5A's when trying to run a Duron with mem set to 133. Set it to 100, all was well.
Try to disable onboard audio in BIOS before install.
I'll give it a shot.
Quote :
In the bios make sure you run your memory speed in sync with your fsb. So with a 200 bus TBird 1.2, set the mem speed to 100 (200) not 133(266). I have had instability issues with K7S5A's when trying to run a Duron with mem set to 133. Set it to 100, all was well.
It is a 1.2GHz Athlon with a 133MHz FSB. However, in an attempt to get this thing going I will clock it down and see what happens. Either way a new board is on the way.
Okay, brain. You don't like me, and I don't like you, but let's get through this thing and then I can continue killing you with beer. -- Homer Simpson.
Why rule out the hard drive? If you have a corrupt file error, you *could* have bad sectors in your windows folder. I'd guess it's the HDD, or maybe the IDE controller on the mobo.
I did a low-level format. I then ran Western Digital's test software which indicated the drive was okay. I still got the error. Then I tried two other HHDs and again I got the error.
Okay, brain. You don't like me, and I don't like you, but let's get through this thing and then I can continue killing you with beer. -- Homer Simpson.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.