UNSOLVED

rje49

updated

20 years ago

R

rje49

141 Posts

0

4603

December 23rd, 2006 00:00

IDE controller bad???

We have a Dimension 8100, running W2K, with a primary HD being a Maxtor 20gb, plus a secondary WD 160gb. One night recently, a storm knocked out the power. When restarting, it didn't re-boot, giving the error message: "Windows could not start because the folowing file is missing or corupt: \ Winnet\sytem32\config\systemced". After making sure the controller was "on", now it says "a disk read error ocurred". Googling the former brought me to Microsoft article 269075, which gives 2 possible causes - "The system hive in the registry is missing/damaged", or a "Promise Technology ATA66 PCI controller card is installed". Seeing as the hard drives plug into the MB, and not a PCI card, I went the route of repairing the OS.
First it said the the OS could not be repaired, so I went for a clean re-install. (I've sucessfully done this before). After waiting out formatting, it said the hard drive couldn't be formatted because it was damaged. I switched to the WD 160. Still booting from the CD-Rom, it goes through the "loading set-up files", partitioning, formatting, and "copying files to W2k installation folders". Then it re-boots and I'm back to loading files, etc again. It's simply going around in circles.
At this point I'm wondering if the HDs are ok (the WD is practically new) but the IDE controller is the culprit. I thought I'd "ask the experts" before buying a PCI card - or anything else.
  • rickmktg

    2 Intern

    11898 Posts

    203

    0

    Posted December 23rd, 2006 00:00



    RJE49 wrote:
    We have a Dimension 8100, running W2K, with a primary HD being a Maxtor 20gb, plus a secondary WD 160gb. One night recently, a storm knocked out the power. When restarting, it didn't re-boot, giving the error message: "Windows could not start because the folowing file is missing or corupt: \ Winnet\sytem32\config\systemced". After making sure the controller was "on", now it says "a disk read error ocurred". Googling the former brought me to Microsoft article 269075, which gives 2 possible causes - "The system hive in the registry is missing/damaged", or a "Promise Technology ATA66 PCI controller card is installed". Seeing as the hard drives plug into the MB, and not a PCI card, I went the route of repairing the OS.
    First it said the the OS could not be repaired, so I went for a clean re-install. (I've sucessfully done this before). After waiting out formatting, it said the hard drive couldn't be formatted because it was damaged. I switched to the WD 160. Still booting from the CD-Rom, it goes through the "loading set-up files", partitioning, formatting, and "copying files to W2k installation folders". Then it re-boots and I'm back to loading files, etc again. It's simply going around in circles.
    At this point I'm wondering if the HDs are ok (the WD is practically new) but the IDE controller is the culprit. I thought I'd "ask the experts" before buying a PCI card - or anything else.
     
    Reboot, hit F12, and run diagnostics on both hard drives.
  • rje49

    141 Posts

    203

    0

    Posted December 23rd, 2006 00:00

    F12 gets me "Error Loading OS".  Maybe because of re-formatting?
  • rickmktg

    2 Intern

    11898 Posts

    203

    0

    Posted December 23rd, 2006 01:00



    RJE49 wrote:
    F12 gets me "Error Loading OS".  Maybe because of re-formatting?

    Use the resource CD.
  • rje49

    141 Posts

    203

    0

    Posted December 23rd, 2006 01:00

    The Resource Cd won't play either. I get the same message. Ain't looking too good...
  • mombodog

    2 Intern

    12735 Posts

    203

    0

    Posted December 23rd, 2006 15:00

    Unplug the power cord, press the power button for 15 seconds, remove the cmos battery for a few minutes (15) replace with a new one it if you have one handy, or put the old one back in, unplug any hardware you do not need (strip it to the bare minimum, including add in cards) to run diagnostics or reinstall, and leave it unplugged, Close the case and try it again.
  • rje49

    141 Posts

    203

    0

    Posted December 25th, 2006 18:00

    OK, got it. Thanks to both of you. 
    Changing the battery brought the IDE controller to life in BIOS. 
    It still looks like the original 20gb Maxtor HD has a problem.
     I installed the OS on the 160gb WD (where I wanted to end up anyway).  After figuring out I had to switch to back to booting from HD after the initial set-up, it's all routine - drivers, utilities, programs, etc.   I'm still learning, and still know just enough to be dangerous!

    Message Edited by RJE49 on 12-25-200602:12 PM