Announcement

Collapse
No announcement yet.

Problem with my new built PC (aye again lol)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Problem with my new built PC (aye again lol)

    Basically the problem is this:

    System boots, takes about 3 minutes to detect my Primary Master hard drive.

    It then goes onto a screen (something along the lines of "Press Shift + F4 for raid) then says primary/secondary not detected

    It then goes onto the DM...whatever (Sorry dont know it off the top of my head) pool data section, and says "Boot Disc Failure etc"

    I've been in the bios, and the h/d again is detected (it takes ages to detect) but just wont boot into Windows

    Any ideas? Cause im fresh all out

    Mobo is Abit NF7S

    #2
    If you're using RAID, try using the RAID Config utility to check the system drives are correctly configured, all drive are online, and no faults have occured on the drives, (I presume you got a config util with the RAID controller).

    If your on IDE, check the jumpers on the drive...
    Master if you only have one drive on the cable
    Master and Slave if you have two (don't trust Cable select it's flakey at best).


    Hope this helps


    Eddie G.

    Comment


      #3
      Do you actually have 2 hard drives? If you don't then switch off RAID or plug the hard disc into a different IDE/SATA socket on the motherboard, which are not used for RAID. Manual will tell you this.

      Comment


        #4
        That motherboard doesn't have RAID on IDE, and it doesn't matter what SATA you plug the HDD into.

        If your not using SATA go into the bios and disable the SATA controller. If you don't know where it is, I'll check it for you next time I reboot.

        EDIT: The disk boot failure is because windows is not detected, or the HDD with windows isn't detected(sounds more likely in your case).

        Comment


          #5
          I'm not using SATA or RAID, im simply using bread and butter IDE

          I was merely pointing out that it has the ability to use SATA or RAID

          The problem is, its not booting into Windows...simply

          Comment


            #6
            Did you try the obvious, jumpers in right position, cables in right etc.

            You should try it in another PC to make sure its not buggered.

            Comment


              #7
              Cables are fine, Jumpers are correct

              Im currently only trying to get my C: to work.

              It is working, as im using it right now, on my old system, just doesnt want to work on this new one that i built today

              Comment


                #8
                How different is you old one from your new one.

                You might need to format and do a clean windows install on the new one.

                Comment


                  #9
                  well we are talking a 1.333 ghz K7 Athlon with ECS K75SA mobo

                  Comment


                    #10
                    I have never moved to a new motherboard before but I would be doing a clean install and then you won't get any problems with Windows detecting wrong motherboard drivers and things, when you do actually get into Windows.

                    Comment


                      #11
                      dont worry, its fixed now, i'm on the "Beast" as we speak :P and boy its a noisy ****er heh

                      Just had to install XP over the existing XP. After a few more teething problems (few reboots) i've got there in the end

                      w00t!

                      Comment


                        #12
                        Now, once you've backed up all your data, format that drive.

                        Windows over Windows is not an ideal solution.

                        Comment


                          #13
                          Update:

                          Well its working now, otherwise i wouldnt be writing this

                          lol came to another problem once i got past the h/d problem. System kept rebooting. Seems that my memory has been dodgy (out of my old system) all along.

                          No wonder my 1.33 would only go to 1.0ghz

                          Ah well

                          Its working now with some nice new shiny ram in it

                          Comment

                          Working...
                          X